The Document That Gets Read
The BRD piece shows one fragment before and after eleven edits. These notes take the document's sections one at a time: the business need, the scope, the measure of success, and what happens to all of it when a change request lands.
Start with the pillar
Eleven Edits That Make a BRD Worth Reading
What a BRD is for, and one fragment of one shown twice: the way it usually arrives, and after eleven edits, with the objection each edit still takes.
The notes, in reading order
A Business Case a CFO Can Argue With
One page of business case, taken apart line by line: where each number came from, what halving it does to the decision, and who may challenge it.
Read →From Change Request to Impact Analysis in One Page
A one-line change request and the six fields of an impact analysis, filled in one at a time: what belongs in each field, and how to tell when one is wrong.
Read →The Context Diagram That Settles the Scope Argument
The scope argument runs on what stays outside and who inherits it. One box, a ring of entities, one line per exchange, and two tables you can copy.
Read →The Success Measure That Makes a Business Case Falsifiable
Five success measures in the wording documents use, put through one question: what result would mean this did not work. Plus the table the survivors go into.
Read →The other two clusters
The Case File · Requirements That Survive Review · All field notes
These notes stand on one worked case, and every figure in that case carries a source tag. What the tags mean.