How the work is actually done
No listicles, no career-change motivation. Each note takes one piece of the job, shows a finished artifact and says what a reviewer would object to.
Field notes, page 2
Gap Analysis Between Two Process Models, Line by Line
Every as-is row walked to its fate in the to-be, then every to-be line walked back. Two residual gaps, one shared verb and one step neither model draws.
Read →Cutting Scope Without Cutting the Point
Eleven cuts a published case made and four it refused, each run through one test: on release day, is the problem the work exists to fix still there?
Read →MoSCoW or WSJF: Prioritising When Everything Is a Must
Five requirements all marked Must, put through MoSCoW's own test and then scored with WSJF: what each method decides, and what it cannot see.
Read →The Feasibility Memo That Recommends Not Building It
A feasibility memo that says no, derived from a worked case: four questions, each answered from the record, and the conditions that would turn it into a yes.
Read →How Long Will the Analysis Take? An Estimate You Can Defend
Three clocks on one published case: thirteen hours of work, seven to nine hours a plan could name in advance, and twenty-eight days of calendar.
Read →A Risk Register With Owners, Dates and a Trigger
A risk register derived from artifacts I already had: eight candidates pulled out of a published case, three thrown out for having no trigger, five rows kept.
Read →Definition of Ready for a Requirement, Not a Ceremony
A definition of ready for requirements: seven conditions a stranger can check from the requirement itself, run backwards over three versions of my own register.
Read →Five Whys Stops Working at Why Number Two
When five whys does not work, and what to do instead: one incident from a published returns case, three honest why chains, three different recommendations.
Read →The Eight Questions in a First Stakeholder Interview
First stakeholder interview questions, built backwards from the six things a case assembled from public sources could not settle, and what each answer changes.
Read →Conflicting Requirements Are an Unmade Decision
Conflicting requirements are an unmade business decision. The one-page card I write instead of mediating, filled in on a 40 EUR refund threshold.
Read →Writing a Use Case: The Main Flow Is the Easy Half
The main flow of a use case writes itself. A worked returns case where the exceptions take three times the space, with the source of each one named.
Read →The Traceability Matrix That Survives a Change Request
What a traceability matrix actually is, one change request walked through it row by row in a quarter of an hour, and the questions it still cannot answer.
Read →Next in the queue: Before the Migration Starts: What the Analyst Must Settle · A Requirements Pattern Library Worth Reusing.
A letter when I have something worth sending
New notes go up on this page as they are written, and the Proof Pack comes when you join. No schedule, no sequence, no webinar funnel.
Subscribe