Services / Practice 06 / Six · The operating layer
Lightweight, tech-led process redesign. Sharper performance, lighter org. Quarterly cadence.
Transformation vs. improvement
They produce a roadmap, a transformation office, and a slide deck. Then they require a separate implementation budget. Then the original team is rotated off before the first fix lands. Two years and seven figures later, the actual operating performance has barely moved.
The reason is structural. Transformation has been weaponized into a multi-year revenue stream by the firms that sell it. The longer the program, the larger the fee. The more workstreams, the bigger the team. The output is the program, not the improvement.
Operations excellence is the discipline of shipping specific operational fixes, in specific quarters, with specific outcomes. A practice, not a program.
A framework
Every quarter, dozens of operational improvements compete for attention. We use three tests to choose what gets fixed.
Which fix moves the most material business outcome? Revenue, margin, NPS, retention, time-to-market. Pick the lever, not the visible thing.
Which fix can ship without rewiring everything else? The narrower the scope, the faster the deployment, the cleaner the measurement.
Which fix pays for itself within the quarter? If payback is multi-year, it's a transformation, not an improvement.
What we won't do
We won't run multi-year transformation programs. Transformation rents the firm; quarterly improvements compound for the client.
We won't take on workstreams that don't pass the three tests. Saying no is the discipline.
We won't deliver against vendor incentives. We don't have any.
We won't bring junior consultants.
Related practices
Discuss operations
FAQ
