· 2 min read
Why briefings, and not decks?
A note on the form of this practice's output, and what the choice of prose over slides does to the quality of the thinking underneath.
#method#writing
Reviews
9 articles
· 2 min read
When is a diagram a liability?
The architecture diagram is the only document everyone believes. A short briefing on the specific ways that belief goes wrong.
#reviews#documentation
· 3 min read
How do you review an agent platform?
The first production agent platforms have published enough detail to steal from. A briefing on what changes in review practice when the operator is software.
#agents#reviews#governance
· 2 min read
What does the incident history say?
The postmortem folder is the most honest architecture document an organization owns. How we read a year of incidents before we read a single diagram.
#reviews#incidents#evidence
· 2 min read
What does the diagram leave out?
Every architecture diagram is a claim about what matters. The review is not about the boxes you drew; it is about the arrows you did not.
#reviews#diagrams#evidence
· 2 min read
What did 2025's public incidents agree on?
A grid, a cloud, and everything between them. The year-end read of the incidents that published enough detail to learn from.
#incidents#reliability#dependencies
· 5 min read
What would have to be true?
The five-word question our whole practice runs on. A long briefing on using it to audit claims, size risks, and end the meetings that should not have started.
#reviews#method#decision-records
· 2 min read
How do you read a latency histogram?
The average is a fiction and the p99 is a person. Reading latency distributions the way the review reads them, shape first.
#reviews#latency#observability
· 3 min read
What makes an architecture reviewable?
Some systems can be reviewed in a day; others resist a month of workshops. The difference is a property of the architecture, and it can be designed in.
#reviews#design#decision-records