Couldn’t agree more, Michelle. I find that I need that time too…as often as I reflect on what I learned from my stakeholders I come up with more elicitation questions. Typing up notes really supports that process for me, which is why I am hanging onto it!

Not at all! Though I do find that for some projects this intermediary step of confirming what was discussed, before capturing it in a requirements document, can help build trust and increase buy-in. If there are a lot of decisions to be made before you decide what goes in the requirements document, you might consider taking iterative steps, gaining confirmation or approval at each stage, before drafting a requirements document for review. Otherwise you risk creating the perception that you ignored what was said.

Nick,
Yes definitely. There is a big difference though between confirming elicitation results and approving requirements for implementation. Confirming elicitation results does not necessarily include requirements analysis, which is where I often find all those additional requirements are discovered.

The BABOK is a bit tricky in this respect as it separates out tasks that a lot of us naturally group together in our work and our thinking.