The Business Analyst path
From what the role is accountable for, through writing criteria a team can test, to elaborating and decomposing real requirements in ReqLens.
The order below is a suggestion, not a sequence you have to follow. Start wherever is useful to you.
- What a Business Analyst actually does
The Business Analyst turns intent into requirements a team can build and test. The real shape of the role, what it produces, and where it goes wrong.
Start with what the role actually owns, which is narrower than most descriptions suggest.
Foundation5 min read - Writing acceptance criteria that hold up
Acceptance criteria fail for predictable reasons. Here is how to write them so a QA Engineer can build coverage without asking you a single clarifying question.
The highest-leverage skill in the role. Everything downstream compounds from it.
Practitioner4 min read - How to decompose an epic into user stories
Most decomposition splits by layer or by screen, which produces stories that cannot ship alone. Here is how to slice so every story delivers something.
Where incremental delivery is won or lost.
Practitioner4 min read - Requirement Studio: rough to testable
How elaboration works in ReqLens: what it adds to a raw requirement, why every change needs approval, and how edits propagate to everything downstream.
How elaboration surfaces the assumptions you would otherwise leave unsaid.
Practitioner4 min read - Breaking a requirement into features
How ReqLens finds feature boundaries in a large requirement, why boundary detection and enrichment are separate steps, and what that separation protects.
Practitioner4 min read - From requirements to use cases
Use cases expose the paths a requirement implies but does not state. How ReqLens generates them, and why alternate flows are where the value sits.
Practitioner3 min read