[Process/Documentation] How do you decide whether to use user stories, process flows, a BRD, or something else?

Example Answer

I choose the artifact based on what the team needs to understand and decide, not based on loyalty to one format. If the main issue is workflow clarity across teams, a process flow may be the fastest way to make the problem visible. If the team is building iteratively and needs implementable slices, user stories and acceptance criteria may be the right vehicle. If there is a complex business case, a lot of rules, or multiple stakeholder groups that need one reference point, a BRD or a more structured requirement document may still be useful.

I also think about audience. Business stakeholders, delivery leads, engineers, QA, and operations teams do not all consume information the same way. A good BA is flexible enough to pick the format that improves clarity for the people who need it.

So I do not ask, "What is the correct artifact?" I ask, "What format will make this problem easier to understand, validate, build, and test?" That usually leads to a better choice than forcing one template onto every project.

Common Poor Answer to Avoid

"I usually prefer user stories because that is the modern standard."

Why it's weak

• It makes the choice sound trendy and one-size-fits-all instead of driven by the needs of the work.

Why this works

• It shows adaptability and a clear link between artifact choice and project value.