Member-only story
Hi! Let’s Capture Your Process
The pitfall of skipping the steps
A new project. A new analyst. Meet the stakeholders. A round of introductions.
Then, the tricky part — it’s time to start the analysis.
The project manager looks at the business analyst and nods. Take the stage. Go for it. Get those requirements down.
This must the most apprehensive moment for an inexperienced business analyst. You’ve taken the courses, you know, in theory, what to do. You’ve practiced writing user stories or requirement statements. But how do you actually start on a new project?
This is where an easy escape comes to mind: “So, let’s capture your process.” Oh, that’s better. Let’s write down the process steps. Boxes and arrows make a sequence. Just tell me what you do, step by step.
Yes, this definitely feels like progress.
It makes sense.
At the end of the day, we have a rough process flow and lots of follow-up questions.
We can report the progress.
And stakeholders, of course, love talking about their process and complaining about all its pain points. Someone is listening to their woes and writing it all down.
