Free · No signup
The Architecture Pattern Pack
Seven artifacts from a full TOGAF engagement — each one a blank template with the worked example beside it.
25-page PDF · no email required · nothing to unsubscribe from · also as editable Markdown (.zip)
Most architecture templates hand you an empty grid and leave you to guess what belongs in it. A capability map with nothing in it teaches nothing. So every artifact here comes with the filled-in version from a real engagement, plus the reasoning for what went in — and what was deliberately left out.
What's inside
- 1
Stakeholder map & concerns matrix
Phase AWho can sink this, and what they actually care about — including the concerns that conflict, and who ruled on them.
- 2
Architecture principles as decision filters
Phase APrinciples that rule something out. If you can't name a decision it forbids, it's a value, not a principle.
- 3
Statement of Architecture Work
Phase AThe scope fence — where the "explicitly out" section is longer than the "in" section, on purpose.
- 4
Business capability map
Phase BWhat the business does, independent of who does it — and the contested capabilities that are the whole point.
- 5
Data duplication audit
Phase CNine systems, one customer, no agreement about which is right. Turns "our data is a mess" into fundable work.
- 6
Architecture contract
Phase GBidirectional. Delivery commits, and architecture commits back — with a consequence when architecture is the blocker.
- 7
Dispensation register
Phase GScoped, expiring exceptions. Governance with no escape hatch doesn't produce compliance, it produces invisibility.
Where it comes from
These are the actual deliverables produced across the TOGAF 10 in Practice series, run end to end on Karoo Retail Group — a fictional composite retailer built from patterns common to mid-size retail estates. The company is invented. The problems are not.
Each artifact names the episode that builds it, if you want the reasoning rather than just the shape.
Get new packs as they ship
The pack above needs no email. This is a separate thing: one message when a new pack lands, and nothing else.