Stop optimising the story. Start understanding the problem.
Notes for working business analysts, product owners, and product managers who suspect there is more to the craft than cleaner Jira tickets. The argument here is simple: problem-understanding first, story-writing second. Most BA content gets that order backwards.
Three things you will find: writing on the analytical work itself, on using AI without losing the thinking, and unsentimental reviews of the tools BAs actually use.
Featured
-
Assumption log template for business analysts: rank the ones that can sink you
An assumption log template that ranks risk instead of listing it: three questions per assumption, one score from 0 to 100, and a worked example.
-
Business requirements vs functional requirements: the difference that actually matters
Business requirements vs functional requirements, explained with examples, and the difference that actually changes how a BA works.
-
What separates BAs who compound from BAs who plateau
What separates business analysts who advance from those who plateau. Not talent or luck, but a specific, repeatable practice of calibration.
-
What to write up after the discovery conversation
How to document requirements after a discovery conversation: capture findings, not notes. The format that survives, and three things never to write.
-
How to actually run a stakeholder discovery conversation
How to run a stakeholder discovery conversation: the opening minute, the middle pivot, the close, and five mistakes that kill elicitation.
-
The AI-assisted requirements workflow that actually works
Using AI for requirements gathering without producing bad requirements faster. A three-stage workflow that puts the thinking before the generating.
-
The weekly written artifact rhythm
The weekly writing habit that separates BAs who advance from those who plateau: predictions, patterns, revisions, and why most cannot sustain it.
-
When the one-page artifact is the wrong tool
The one-page push-back artifact makes things worse in three situations. How to tell you have misread the room, and what to do instead.
-
The one-page artifact that earns the right to push back
The one-page format that lets a BA push back on a senior stakeholder: the sections, their order, and the moves that keep it from feeling adversarial.
-
Pushing back on people who outrank you
How to push back on senior stakeholders without ending your career: the pre-meeting move, escalating risk not disagreement, and earning trust.
-
When stakeholders won't answer your questions
How to handle stakeholders who resist your questions: four types of resistance, five tactics, and why pushback often means you asked the right one.
-
The five questions, applied: three worked examples
The five-question template applied to three requests every BA has seen: a health score dashboard, a loyalty program, and an AI support chatbot.
-
The requirements document is dead. Long live the requirements document.
Is the requirements document dead? Agile, Jira, and AI each declared it. The truth: documents didn't die, BAs stopped writing good ones and blamed the format.
-
What changed about being a BA between 2020 and 2025 (and what didn't)
What changed about being a business analyst from 2020 to 2025, and what AI didn't. The surface shifted, the craft barely moved, and that gap is a risk.
-
BA vs PO vs PM: the difference nobody writes about honestly
The real difference between a business analyst, product owner, and product manager, and who actually owns the outcome. Not another comparison table.
-
INVEST and SPIDR both miss the point
INVEST vs SPIDR for user stories: both tell you whether a story is well-formed, not whether it is worth building. The flaw they share.
-
Most stakeholder conflicts are authority disputes, not requirements disputes
Most stakeholder conflicts are not about requirements. Nobody has agreed who decides what, so the stakeholder defends territory. What to do instead.
-
How I use Claude to interrogate my own requirements before showing them to engineering
I write the requirement, Claude tears it apart, I rewrite. By the fifth draft, engineering asks half the questions they used to. Here is the method.
-
Why "as a user, I want to..." is the worst thing that happened to user stories
The "as a user, I want X so that Y" template was a useful crutch in 2001. Twenty-five years later, it's a substitute for thinking. Here's what to write instead.
-
The question most BAs forget to ask before opening Jira
"What do they want?" is the wrong first requirements question. The one most BAs forget before opening Jira, and how it validates the request.
-
Writing better user stories is the wrong goal. Here's what to optimise for instead.
BAs write better user stories than ever: well-structured, crisp acceptance criteria, every review passed. Projects still fail. What to optimise for.
Recent Posts
-
BRD vs FRD vs SRS: the real difference, plus a free Word template
BRD vs FRD vs SRS explained by who signs each one and what it decides, with a refund portal example and a free Word BRD and FRD template.
-
Requirements traceability matrix template (free Excel and Notion): three linked tables
A free requirements traceability matrix template for Excel and Notion. Links business requirements, functional requirements and tests, and calculates coverage.
-
RAID log template: how to keep a RAID log people actually read
A free RAID log template that rates itself: likelihood times impact, a Red, Amber or Green rating, and review dates that flag what is overdue. With an example.
-
Stakeholder register template: build one that tells you who to talk to next
A free stakeholder register template for business analysts that picks an engagement strategy and flags who you have not spoken to recently enough.