Every consulting practice has a way of working. Most keep it vague on purpose, because vagueness is flexible and flexibility bills well. I would rather show you the whole machine.
The Alexandria Method is a nine-step cycle: capture, organize, analyze, challenge, design, operationalize, institutionalize, automate, reflect. It is how every engagement runs, whether the subject is an operating model, a learning function, or a community's vision for its next decade.
The first four steps earn the right to design
Most failed projects fail before the design starts. Someone skipped straight to solutions, and the solutions solved the wrong problem beautifully.
Capture gathers the information, context, and voices that matter. Not a survey blast: real conversations, real artifacts, the informal knowledge that lives in hallways. Organize gives that raw material structure so patterns can surface. Analyze finds the patterns, tensions, and root causes. And challenge, the step most practices skip, tests the assumptions everyone inherited. The org chart says five teams. Is five right? The intake process assumes requests must queue. Must they?
By the time design begins, the problem has been earned, not assumed.
The middle steps build the thing
Design builds better systems, not quick fixes. The distinction is practical: a quick fix optimizes inside broken constraints, a better system changes the constraints. Operationalize turns the design into clear documentation people can actually use, because a design that lives in a slide deck is a rumor, not a system.
The last three steps are where the value compounds
Here is the part I care about most. Institutionalize converts the work into reusable assets and shared memory: playbooks, templates, decision logs, the things that survive turnover. Automate removes friction where technology genuinely helps, which is a narrower territory than the software industry suggests. And reflect closes the loop: what did we learn, what would we do differently, what does the system need next?
Most engagements end at step six. The deliverable ships, the invoice clears, and two years later the organization cannot remember why the process works the way it does. The last three steps are the difference between renting an outcome and owning a capability.
Why a cycle and not a checklist
Because organizations are alive. The reflection step feeds the next capture. The system you institutionalized this year becomes the assumption you challenge in three years. That is not a flaw in the method, it is the method: continuous, honest, and built for the long life of the mission it serves.
If you want to see the cycle pointed at your organization's hardest problem, that is what a discovery call is for.