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:

  1. 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?
  1. 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?

  1. 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?

  1. How do you handle things you don't understand?
    Do you clarify immediately, or note it down and come back to it later?

  2. 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!

reddit.com
u/Basic_Bend_609 — 6 days ago

Looking for advice from experienced BAs/Consultants on requirements gathering

Hi everyone!

I’m relatively new to Anaplan and I’m trying to better understand how requirements gathering / discovery workshops are actually conducted on real Anaplan projects.

I understand the general idea: meet with SMEs/business stakeholders, understand the current process, identify requirements, document them, and eventually translate them into things like user stories, functional requirements

But I’m more interested in the practical side of the workshops.

For those of you who have done a lot of Anaplan implementations:

  1. How do you prepare before a workshop?
  • Do you already have a list of questions prepared?
  • Do you prepare questions based on the business process, or do you mainly let the SME explain the process first?
  • If you're hearing the process for the first time, how do you know what questions you should ask?
  1. What questions do you typically ask SMEs?

Do you have a generic framework/checklist that you use for almost every discovery workshop? Or do you approach it differently?

  1. How do you take notes during the workshop?

This is something I struggle with. If I try to write down everything the SME says, I feel like I stop listening and lose the bigger picture.

Do you:

  • Take detailed notes?
  • Write only keywords and important business rules?
  • Use a predefined template?
  • Draw the process while they explain it?
  • Record the meeting (when permitted)?
  • Have someone else take notes?

And how do you make sure you don't forget important information after the workshop?

  1. How do you distinguish a requirement from just information?

For example, an SME might spend 20 minutes explaining how they currently perform a process. How do you identify which parts are actually relevant requirements for the Anaplan solution?

  1. How do you handle things you don't understand during the workshop?

Do you stop the SME immediately and ask for clarification, or do you note the question and continue so you don't interrupt the flow?

  1. 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 consultant/BA during these workshops.

I'm trying to understand what comes with experience/practice versus what can be learned through a structured framework.

Any advice, examples, templates, or lessons learned would be really appreciated!

Thanks!

reddit.com
u/Basic_Bend_609 — 6 days ago

Looking for advice from experienced Anaplan BAs/Consultants on requirements gathering

Hi everyone!

I’m relatively new to Anaplan and I’m trying to better understand how requirements gathering / discovery workshops are actually conducted on real Anaplan projects.

I understand the general idea: meet with SMEs/business stakeholders, understand the current process, identify requirements, document them, and eventually translate them into things like user stories, functional requirements

But I’m more interested in the practical side of the workshops.

For those of you who have done a lot of Anaplan implementations:

  1. How do you prepare before a workshop?
  • Do you already have a list of questions prepared?
  • Do you prepare questions based on the business process, or do you mainly let the SME explain the process first?
  • If you're hearing the process for the first time, how do you know what questions you should ask?
  1. What questions do you typically ask SMEs?

Do you have a generic framework/checklist that you use for almost every discovery workshop? Or do you approach it differently?

  1. How do you take notes during the workshop?

This is something I struggle with. If I try to write down everything the SME says, I feel like I stop listening and lose the bigger picture.

Do you:

  • Take detailed notes?
  • Write only keywords and important business rules?
  • Use a predefined template?
  • Draw the process while they explain it?
  • Record the meeting (when permitted)?
  • Have someone else take notes?

And how do you make sure you don't forget important information after the workshop?

  1. How do you distinguish a requirement from just information?

For example, an SME might spend 20 minutes explaining how they currently perform a process. How do you identify which parts are actually relevant requirements for the Anaplan solution?

  1. How do you handle things you don't understand during the workshop?

Do you stop the SME immediately and ask for clarification, or do you note the question and continue so you don't interrupt the flow?

  1. 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 consultant/BA during these workshops.

I'm trying to understand what comes with experience/practice versus what can be learned through a structured framework.

Any advice, examples, templates, or lessons learned would be really appreciated!

Thanks!

reddit.com
u/Basic_Bend_609 — 6 days ago