A business ask arrives as one line — “add step-up verification at login.” Behind it sit nine services, six API consumers, two partners, a data migration, a security control, and a release train. This site follows that one line all the way to production twice: the traditional path, meeting by meeting, and the path where one owner who has operated the architecture drafts the epic brief, the impact map, the API contract, the per-team notes, and a clickable mock before the first meeting — so the meeting reviews a document instead of starting from a question.
Writing a detailed brief, the breakdown, the dependency and impact analysis, the epic-to-story fan-out, the release plan and the stakeholder notes was always the analyst's craft. With AI-assisted coding it has also become the bottleneck: a team can now build the wrong thing quickly, and the debt that leaves behind is the expensive kind. Doing that analysis well needs someone who understands the system architecture — the services, the data, the DevOps pipeline, the release train — not only the process.
A real swimlane — horizontal role lanes, time left to right — of how the ask travels today: intake, discovery per team, the BRD, review cycles, architecture and security review, the late DB and partner questions. Hand-offs and waits counted (illustrative).
The same lanes, front-loaded: epic brief → impact map → consumer matrix → OpenAPI contract + Postman collection → clickable mock → per-team one-pagers → stories → acceptance → metric. Who still signs what.
Every artifact for step-up verification at login, actually filled in: the brief with a baseline and a target, the additive-vs-versioned decision record, the controls and non-functional requirements, ten stories with Given/When/Then, the disagreement and how it was resolved, the traceability chain, and a clickable prototype.
How Agile, Scrum and the release train relate; the work hierarchy; user, enabler, QA, DevOps stories and spikes; staggered QA as a constraint; one epic across many sprints; every meeting in order; release readiness. Nine copy-ready templates, each shown blank and filled. A glossary that drills down from every page.