Any tips for understanding use cases and course content?
When I interact with Anaplan and groups of people in the real world I find it easy to take notes and understand what the users want to achieve. I ask broad questions and get a good grasp of the landscape they operate in, their preferences etc.
When following the course material I miss this interaction with people. The descriptions never give enough flavour and the way things are worded are often not the way I would note down the same information from the same conversation. There is no opportunity to talk around a topic or ask follow up questions to the person who's user story it is, which is the way I hone my understanding of the requirement.
I understand courses need to be generic and that everyone thinks differently about the world, however, I find because of these differences 50% of the time I spend on the Anaplan courses is trying to interpret the requirements rather than finding solutions to them or learning the platform.
Does anyone else find this difficult? What tips have you got for making things more intuitive?