The approach
The Alexandria Method
A nine-step cycle for building systems that outlast the engagement. It is how every project runs, whether the subject is an operating model, a learning function, or a community vision.
The nine steps
Capture
Gather the information, context, and voices that matter.
Organize
Give the information structure so patterns can surface.
Analyze
Find the patterns, tensions, and root causes.
Challenge
Test assumptions instead of inheriting them.
Design
Build better systems, not quick fixes.
Operationalize
Turn the design into clear documentation people can use.
Institutionalize
Convert the work into reusable assets and shared memory.
Automate
Remove friction where technology genuinely helps.
Reflect
Learn from the work and improve continuously.
Philosophy
The philosophy underneath
Systems thinking over isolated fixes. Root causes over symptoms. Long-term capability over short-term productivity. Institutional knowledge over individual memory. Reusable assets over one-off deliverables. Evidence over assumption. Clarity over complexity. And people-centered design throughout, because the people living inside a system deserve a say in how it works.
Where this practice uses human-centered design, it draws on IDEO.org's Design Kit as a facilitated practice, with gratitude and attribution. It is a method I facilitate, not a framework I claim.