Free · no emailPDF · 4 pages · A4
Stop nodding along in architecture discussions.
What it gives you
Enough to let a product manager hold their own in an architecture discussion — every term they will hear, what it actually costs in time and money, and the one question to ask next.
What is inside
- The twenty terms that come up most, in plain management language.
- What each one implies for cost, time and reversibility.
- The question to ask when you hear it — the one that turns a statement into a decision.
- The four phrases that usually mean something is being avoided.
Who it is for
- Product managers who have learned to nod.
- New engineering managers translating upward.
- Anyone who has approved an architecture decision they did not understand.
Get it
Download it
No email, no form, no sequence. Take it, use it, forward it to whoever needs it more than you do.
PDF · 4 pages · A4
If you want the next one
One practical artefact a month, and a short note on what I got wrong recently. That is the whole newsletter.
More resources
Available now
Programme Overview
The programme overview: the approach, the buyer roles, the five tracks and how an engagement is assembled.
Get it →
Available now
The One Pager
The single-page summary of The Bridge: the claim, the numbers, the three flagship days and the five tracks.
Get it →
On request
The Full Curriculum
The complete 58-page catalogue: all 34 modules and 236 lectures with durations and outcomes.
Get it →