Map to the level where decisions and handoffs are visible, then stop. Walk the process with the people who do it rather than the people who manage it, capture the exceptions and workarounds because that is where the real complexity lives, and validate the map by having someone follow it. Only map current state at all if it informs the future state or the migration.
Why interviewers ask this
Process mapping can absorb unlimited time, so interviewers want to see that you scope it deliberately. They listen for a stated level of detail, for exceptions and workarounds captured rather than the happy path alone, and for the discipline to question whether current state mapping is even needed. Endless documentation with no decision attached is a classic way analysts lose credibility with delivery teams.
How to structure your answer
- Set the detail level at decisions and handoffs.
- Walk it with the people doing the work, not their managers.
- Spend most of the effort on exceptions and workarounds.
- Validate by having someone unfamiliar follow the map.
- Only map current state where it changes a decision.
Example answer
I map to the level where you can see the decisions and the handoffs, and then I stop, because the temptation is to keep going and produce something beautiful that changes nothing. The most important thing is walking it with the people who actually do the work rather than their managers, because managers describe the process as designed and the people doing it describe the process as it survived contact with reality. I spend most of my time on the exceptions, since the happy path is usually five boxes and the exceptions are where all the cost sits. On one process the standard route took a day, and about a third of cases fell into a manual exception queue that took nine, and that queue was the entire business case. Then I validate by handing the map to someone new and asking them to follow it, which finds missing steps very quickly.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What notation do you use, and does it matter?
- How do you handle a process that varies by region or team?
- When would you skip current state mapping entirely?
Related business analyst questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions