Plan: Think, Design, Organize
Strategic analysis and opportunity sizing, blueprinting the architecture, and structuring the team and roadmap needed to execute — grounded in your real workflows, not a template.
Every firm now claims a methodology. The real question is whether that methodology is a straight line that ends at handoff, or a loop that keeps running after launch. Ours is a loop.
The classic model treats Plan, Build, and Operate as three sequential phases, often run by three different teams — sometimes at three different firms. Strategy hands off a deck. A build team hands off a system. An internal team inherits whatever's left to run.
That works when the technology and the environment stay still long enough for a handoff to make sense. They do not. A production system surfaces new use cases, failure modes, and opportunities within weeks of shipping — information a strategy team six months removed from the build will never see.
So we don't split Plan, Build, and Operate across separate teams or separate engagements. We run all three as one continuous loop.
There are two ways to structure an engagement.
Strategy defines the roadmap, a build team implements it, and the relationship ends at go-live. Whatever the system learns in production never makes it back to the people who designed it.
What we learn running a system in production — what broke, what got used constantly, what a client actually needed instead of what they asked for — becomes the input for the next planning cycle, not a lessons-learned doc nobody reads.
The best systems do not ship once. They get better every week they run.
Here's what each phase actually involves, not just what it's called.
Strategic analysis and opportunity sizing, blueprinting the architecture, and structuring the team and roadmap needed to execute — grounded in your real workflows, not a template.
Deploying the tools and infrastructure, developing the custom systems, and driving the organizational change needed for people to actually use what we ship.
Keeping systems reliable day to day, resolving issues fast, and continuously tuning performance — feeding what we learn back into the next Plan cycle.
This isn't a knock on any of them. It's just where their business model naturally stops.
Excellent at the Plan phase — vision, roadmap, org design. The engagement usually ends at the deck, well before anything ships.
Strong at the Build phase — shipping a model or a pilot. Less built for the ongoing Operate work of keeping it reliable once it's live.
Good at the Operate phase — running and maintaining systems. Rarely involved in the Plan or Build decisions that shaped what they're now running.
Close to the Operate reality, but often under-resourced to Plan or Build at the pace the rest of the organization needs.
Looking across the market, keeping a system "up and running" is becoming table stakes — uptime monitoring, basic support, patching. That's necessary, but it's not where the value is.
What matters is whether the system gets better while it runs: whether usage data improves the next version, whether a recurring failure mode gets designed out instead of just patched, and whether its scope expands as trust grows.
That's the orientation behind every engagement we run. Operate isn't the end of the loop. It's the phase that makes the next Plan cycle smarter.
The structural advantage of a loop over a line-item engagement accrues over time. Every Operate cycle hands the next Plan cycle better data about what's actually worth building next.
Six months into a real loop, we (and your team) understand your constraints, your data, and your risk tolerance in a way no new vendor starting from a blank slate can replicate. That's not lock-in. It's compounding context — the same dynamic we cover in more depth in Momentum.
Whether you need Plan, Build, Operate, or all three running together, Ali plugs in and keeps the loop moving.
Save it, print it, share it, or bring this page into an AI tool for follow-up questions.