The Axis Method is a five-stage fractional COO methodology designed for $10M–$100M operators, particularly post-acquisition situations. It is the engagement structure underneath every fractional COO retainer at Obsidian Axis Group. The stages are sequential, the deliverables explicit, and the exit criteria visible, the engagement is over when the company runs the operating system without us.
The methodology, in detail.
01 / Diagnose Weeks 1–4
Operational due diligence with three concurrent threads. (1) A value-stream walk of the primary process, end to end, on paper, with value-add and non-value-add steps marked. (2) A waste inventory across SaaS spend, decision latency, and process bloat. (3) A team diagnostic against Edmondson's safety-accountability quadrant and Tuckman's stages, identifying whether the leadership team is in the Learning zone, the Comfort zone, the Anxiety zone, or stuck at Norming-via-suppression. The output is a written diagnosis the leadership team can argue with, and the leverage points are identified before any work begins.
02 / Stabilize Weeks 4–10
Fix the highest-leverage broken thing first. Not all of it. Not in parallel. The single piece whose stabilization makes the rest of the work possible. Almost always this is a hand-off (the gap between sales and ops, the gap between fulfillment and accounting), and almost always the underlying issue is part process and part team. We apply Lean's variation-reduction discipline to the process side. We surface the buried disagreement that's been suppressing real coordination on the team side. Interim SOPs go into use immediately, not perfect, just running. Stable beats elegant in this phase.
03 / Document Weeks 10–16
Now the SOPs become permanent. Toyota's standard work, written by the people who do the work. KPI definitions with formulas, data sources, and owners. Decision trees that route decisions to the lowest responsible level. Role-by-role responsibilities, escalation paths, blameless incident-review templates. The team-performance practices get codified alongside the process documentation: public mistake-of-the-week, devil's-advocate rotation, calibrated leader reactions to bad news. The output is the operating system in writing, the smallest set of documents that produces predictable execution. We do not write 200-page manuals.
04 / Hand-off Weeks 16–22
Transfer ownership. The in-house team runs the documented system; we shadow. Visual management and pull-based work flow get installed in the workspace. We verify by absence, what breaks when we are not in the standup, in the review, on the email thread, in the incident response. Whatever breaks, we patch the documentation or the team practices until it doesn't. The hand-off is not over until the team has run the system through one full operating cycle without us being essential to anything, including the decisions that previously routed to us by reflex.
05 / Compound Quarterly
The discipline persists. Continuous-improvement cadence, baked into the daily standup, produces small accumulating gains the way Toyota's actual genius worked. Quarterly check-ins, optional. Most engagements end here, the company runs the operating system on its own and growth doesn't require us. Some sponsors retain us to install the same discipline at the next portfolio company. Either way, the company we just left is no longer dependent.
Diagnose before stabilizing. Stabilize before documenting. Hand off before compounding.
Most operations consulting reverses these. The pattern is: deliver a strategy deck, identify a list of changes, then leave. The team is supposed to execute. They don't, because the muscle for execution wasn't built. The work decays.
The Axis Method puts hand-off at the center. Diagnose, stabilize, and document are setup for hand-off. Compound is what you get if hand-off succeeds. Reverse the order and you get the same outcome as every other engagement: a deck that gets shelved, a team that resents the consultants, and a sponsor who quietly writes off the line item.
Operating principle: if the engagement is still essential at month twelve, we did the job wrong. Hand-off is the deliverable.
Process discipline. Team performance. Both, sequenced.
The Axis Method is not just a process-improvement engagement and not just a leadership-team intervention. It is both, deliberately sequenced because each one gates the other. Process discipline without team performance produces SOPs that get bypassed; team performance without process discipline produces a high-trust team running on tribal knowledge. The five stages install both, layered.
The process layer
Lean and Six Sigma principles applied without the methodology overhead. No belts. No multi-month DMAIC projects. No kaizen events as deliverables. Value-stream mapping during Diagnose, variation reduction at high-cost hand-offs during Stabilize, Toyota-style standard work during Document, visual management and pull-based flow during Hand-off, daily continuous-improvement cadence during Compound. The principles do their work; the labels do not. See the post on what to keep and the glossary entry.
The team layer
Tuckman's stages as diagnostic. Edmondson's safety-accountability 2x2 as destination. Most LMM leadership teams arrive at us stuck in Norming-via-suppression, calm because the disagreements got buried, not because they got resolved. The Stabilize and Document phases install the practices that move a team into the Learning zone, where high safety AND high accountability coexist. That is where documented operating systems actually run, where bad news travels fast, where the team improves itself without leadership memos. See the post on the practitioner intervention and the psychological-safety glossary entry.
Why both, sequenced
Process before team produces brittle systems. Team before process produces a culture with nothing to coordinate around. The right order is Diagnose both, Stabilize the highest-leverage process problem first (because a quick win builds team-level trust in the engagement), then layer the team-performance practices alongside the documentation work. By Hand-off the company has both an operating system and the cultural muscle to use it. That combination is operational excellence, the destination underneath the methodology.
The four situations this is for.
- Post-acquisition. The seller-operator leaves. The new owner inherits a business that runs on tribal knowledge. The Axis Method installs the documented system in 90 days, before the muscle memory walks out.
- Lower-middle-market growth stall. A $25M–$50M operator stuck below the next inflection. Usually because operations don't scale to the next stage. We install the discipline that supports it.
- Sponsor-led ops install. A PE portfolio company. The sponsor wants documented operating discipline before the next round, before the auditor, before strategic-acquirer diligence. We produce it and exit.
- Operational due diligence pre-sale. 12–18 months from sale. We write the operating system properly before the data room opens, instead of frantically during it.
What the Axis Method isn't.
- Pre-revenue or early-stage operators. Documenting an operating system before you know what the operating system is wastes the engagement. Come back at $5M+ revenue.
- $500M+ enterprise transformation. At that scale you need a different shape of engagement, a team, not a fractional embed. We will refer you elsewhere.
- Single-issue tactical work. If you need a one-time fix to a specific process, hire a consultant for that process. The Axis Method is whole-system installation; it is overkill for tactical scope.
How we know we're done.
The hand-off is verified by absence. We stop attending the standup. We stop being copied on the operations thread. We stop running the weekly review. Whatever breaks in that absence is what hand-off didn't cover, we patch the documentation until nothing breaks.
When the in-house team has run one full operating cycle (typically a month, sometimes a quarter for slower-cycle businesses) without us being essential to anything, the engagement is over. We stay available for quarterly check-ins; the company runs without us.
The methodology, compounded.
The Axis Method is built on Cedric Corbett's decade of enterprise operations across Amazon, International Paper, Spirit Halloween, Maersk, and Levi Strauss, $3B+ in operational impact, then compressed into a methodology any $10M–$100M operator can run. It was stress-tested inside DefaultFail, the operator community where every system was proven by real business owners before it became a consulting engagement.
The Axis Method, answered.
What is the Axis Method?
The Axis Method is a five-stage fractional COO methodology, Diagnose, Stabilize, Document, Hand-off, Compound, designed for $10M–$100M operators, particularly post-acquisition. It is the engagement structure underneath every fractional COO retainer at Obsidian Axis Group.
Why five stages instead of three?
Three-stage methodologies skip the parts that matter. Most consulting frameworks compress hand-off and compounding into "completion," which is why their work doesn't survive the engagement. Hand-off and compound are the entire point, the prior three stages are setup for them.
How is this different from McKinsey or Bain post-merger work?
Top-tier consulting produces decks. The Axis Method produces running systems and trained operators. We sit in your standups, write the SOPs your line managers actually use, and verify the hand-off by absence. The cost difference is roughly 10x lower; the deliverable difference is operational rather than strategic.
Why is the hand-off the actual product?
Because if we're still essential at month twelve, we did our job wrong. The deliverable is not the SOPs or the diagnostic, it's the company's ability to run without us. Everything before hand-off is preparation; hand-off is the test.
How do you measure operational waste during diagnosis?
Three measurements. (1) SaaS spend vs. utilization, what you pay for vs. what your team actually uses. (2) Decision latency, how long it takes a decision to route from origin to resolution. (3) Founder-bottleneck count, how many decisions per week route through the principal that shouldn't. The audit produces a number for each.
What does the stabilize phase typically include?
One process, fixed completely. Usually a hand-off, the place where work crosses team boundaries and information goes missing. We don't fix everything in stabilize; we fix the thing that, once fixed, makes the rest of the operating system buildable.
What's in the documentation deliverable?
SOPs for every recurring workflow. KPI definitions with formulas and data sources. Role-by-role responsibility maps. Decision trees for the highest-volume decisions. Escalation paths. The smallest possible set that produces predictable execution, not the largest possible set that proves we did the work.
How long does a typical Axis Method engagement run?
Three to nine months end to end. Most engagements settle around six months. The diagnose phase takes 4 weeks; stabilize takes 4–6 weeks; document takes 4–6 weeks; hand-off takes 4–6 weeks. Compound is open-ended and quarterly.
What does compounding look like 12 months out?
The team running operations without us. SOPs being maintained, not by us, by them. New hires being onboarded into a documented system rather than learning by osmosis. The discipline visible in the next investor's diligence as a positive signal rather than a liability.
How do you involve the sponsor or deal team in the engagement?
Monthly written reports to the sponsor, the same format as our internal review. Quarterly on-site if desired. We coordinate with whatever PortCo monitoring already exists; we don't replace it. The sponsor sees the same diagnostics the operator sees.
Do you work alongside an internal COO or replace one?
Both patterns work. With an internal COO present, we focus on operating-system installation while they run day-to-day. Without one, we run interim COO functions until hand-off. The engagement structure is the same; the daily allocation differs.
What happens if the company is acquired again mid-engagement?
The documented operating system is the deliverable a strategic acquirer wants. We coordinate with the new sponsor, usually the engagement either completes on schedule or extends slightly to integrate the new ownership's reporting requirements. We've worked through this twice.
Thirty minutes. No pitch deck.
If the methodology fits where you are, we'll scope an engagement. If it doesn't, we'll tell you that, and probably point you at someone who does fit.