Looking for advice from experienced BAs/Consultants on requirements gathering
Hi everyone!
I’m relatively new to Anaplan and trying to better understand how requirements gathering / discovery workshops are conducted on real Anaplan projects.
I understand the general process: meet with SMEs/business stakeholders, understand the current process, identify requirements, document them, and eventually translate them into functional requirements, user stories, etc.
But I’m more interested in the practical side.
For those with experience in Anaplan implementations:
- How do you prepare for a workshop?
- Do you have a generic list of questions/framework?
- Do you prepare questions beforehand or let the SME explain the process first?
- If you're hearing the process for the first time, how do you know what questions to ask?
- How do you take notes?
I struggle with writing everything down while also staying focused on the discussion.
Do you use a template, take keywords only, map the process, record the meeting (when permitted), or have someone else take notes? How do you make sure you don't miss important information?
- How do you distinguish requirements from general information?
For example, when an SME spends 20 minutes explaining the current process, how do you identify what is actually relevant for the future Anaplan solution?
How do you handle things you don't understand?
Do you clarify immediately, or note it down and come back to it later?What happens after the workshop?
How do you go from workshop notes → process understanding → requirements → user stories/acceptance criteria?
I’d especially appreciate advice on the thinking process of an experienced Anaplan BA/consultant during these workshops—what comes with practice vs. what can be learned through a structured approach.
Any advice, examples, templates, or lessons learned would be greatly appreciated!
Thanks!