Simon Wardley Portfolio
Creator of Wardley Mapping, a value-chain visualization technique developed from his own experience running cloud infrastructure at Fotango, since applied by architects and executives to reason about multi-cloud and platform strategy decisions.
Location
Location: classified. Send a pigeon.
Skills
What makes it work
A breakdown of the choices that make this portfolio stand out.
A named methodology traceable to real operational experience
Wardley Mapping is not presented as abstract theory — it grew out of decisions he had to make running cloud infrastructure at his own company, which is why the framework focuses on practical build-vs-buy and platform tradeoffs.
A multi-year public archive refining one core idea
Instead of a new framework every year, the blog returns repeatedly to the same mapping technique, sharpening and simplifying it over time.
Willingness to publicly critique his own prior work
One post explicitly argues for removing complexity from earlier versions of his own method, which is a rarer and more credible move than continuously promoting a framework without qualification.
What Cloud Architects can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
If you've developed a genuine methodology from real experience, say where it came from — a framework tied to an actual decision you had to make is more credible than one presented as pure theory.
Return to and refine one core idea over years rather than publishing a new framework with every post — depth on one idea builds more authority than breadth across many.
Publicly critique or simplify your own earlier work when it's warranted — it signals that the goal is a useful tool, not defending a personal brand.
Case studies
One idea, refined in public for twenty years: a free, openly licensed book on mapping, the org-design essay that grew from it, and a new book on software engineering written with Tudor Girba. Simon Wardley's portfolio is an archive of 1,000+ writings rather than a gallery.
Wardley Maps: Topographical Intelligence in Business
Wardley's 19-chapter book on strategic mapping. It covers building a map from users and needs down a value chain, placing components on an evolution axis, universal 'doctrine', gameplay, and using climatic patterns to anticipate change. Each chapter is readable free on his site.
It is a complete, openly licensed method for build-vs-buy and platform decisions. Architects can apply it straight to cloud and vendor strategy.
19 chapters, from 'On being lost' to scenario planning
Free EPUB and PDF downloads
The mapping method is licensed CC BY-SA 4.0
The only structure you'll ever need (Pioneers, Settlers, Town Planners)
An essay describing the PST organization model he used as CEO of a Canon subsidiary from 2004. The business is mapped, split into small autonomous cells (under 12 people), and staffed by Pioneers, Settlers or Town Planners depending on how evolved each component is. Later groups take over and 'steal' work from earlier ones as it matures.
It ties architecture (components on a map) to team structure (who owns them at each stage), which is the Conway's-law problem platform teams face.
Grew out of his own time as CEO of a Canon subsidiary from 2004
Cells under 12 people with fitness functions, coordinated via Kanban
Credits Cringely's 'Accidental Empires' and admits it 'might just be a fluke'
Rewilding Software Engineering
A book in progress arguing that software engineering is decision-making about systems too large to read. Teams should build contextual tools to understand legacy code instead of reading it line by line. It opens from Dijkstra's software crisis and compares a core banking system (tens of millions of lines) with Apollo's 130,000.
Legacy modernization is where most architecture budgets go. The book gives a specific method for understanding a system before deciding to refactor or replace it.
Co-written with Tudor Girba of feenk
Frames engineering as decision-making, not code-writing
Six chapters out, including 'Myths we tell ourselves'
More Cloud Architect portfolios
Ready to build your portfolio?
Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.