Management Frameworks and the Proximity to Snake Oil
Many management frameworks operate close to the snake oil line — selling beliefs and process models rather than verif...
What CTOs Need From Consultants and Hands-On Experts
5 min read
The Category Error
01.06.2026, By Stephan Schwab
The mistake is not hiring consultants. The mistake is expecting the same person to align stakeholders, improve execution, stabilize how changes go live, clean up ownership, and turn AI ambition into daily working practice. Those are different jobs. Some consultants are valuable because they stay above the operating mess. Hands-on experts are valuable because they step into it. That applies whether your company sells software, runs internal platforms, or depends on a knot of custom systems and vendor integrations. CTOs get burned when they pay for one and quietly expect the other.
What Consultants Actually Give You
"Good consultants create clarity around decisions. They do not magically remove execution friction."
A good consultant is useful when the problem is political, structural, or strategic.
They can bring an external benchmark that cuts through local mythology. They can package a difficult message so a board, CEO, or investor group actually hears it. They can force decisions that have been politely avoided for months. They can map a portfolio, challenge a vendor story, or show where the organization is lying to itself.
That is real value. It is just not the same value as changing how technology work gets done inside the business.
If the work is mostly about priority, governance, funding logic, executive alignment, or choosing between competing paths, a consultant may be exactly the right hire.
What Hands-On Experts Actually Give You
"Hands-on experts work where the embarrassment lives: releases, ownership, architecture, and feedback loops."
A hands-on expert is useful when the problem sits inside the actual flow of work.
By hands-on expert, I mean someone close enough to the system to work inside it, not just talk about it from the conference room.
That means changes take too long to move. Releases are brittle. Teams depend on too many approvals. Ownership is blurred. The architecture turns every change into a small archaeological dig. Integrations fail in predictable places. The AI initiative looks impressive in slides and invisible in daily work.
Hands-on experts do not mainly sell interpretation. They trace friction to concrete causes and remove some of it. They make the path to production more reliable. They clarify ownership. They reduce handoffs. They help teams build practices that survive after the workshop glow wears off.
That is why hands-on experts can feel inconvenient. They make the conversation less theatrical and more testable.
Where CTOs Waste Money
"Trouble starts when strategic framing gets sold as operational change."
The expensive mistake is not hiring consultants. The expensive mistake is hiring consultant-shaped help for hands-on problems.
If getting changes live is chaotic, another alignment deck is not a rescue plan. If your ERP or platform migration is stuck, a maturity model is not movement. If your internal teams and vendors cannot deliver changes without drama, a facilitation expert does not magically become the person who fixes how the work runs.
This is where many technology organizations drift into the kind of abstraction theater behind management frameworks and snake oil. Nobody is technically lying. The work is just happening one layer above the place where the pain is produced.
When a Consultant Is the Right Hire
"Buy a consultant when you need leverage, framing, or executive movement."
A consultant is often the right choice when:
- the board needs an outside benchmark before making a structural decision
- a merger, carve-out, or vendor reset needs neutral framing
- the CTO needs help turning technical reality into business language
- senior leadership is stuck in circular discussion and needs sharper decision pressure
- critical business systems depend on too many outside providers and nobody agrees where responsibility sits
- the organization needs someone to challenge assumptions from outside the hierarchy
That is not second-class work. It is just different work.
When a Hands-On Expert Is the Right Hire
"Buy a hands-on expert when the constraint is inside the system and the system needs touching."
A hands-on expert is usually the right choice when:
- getting changes live is slowing everything down
- teams cannot own work from start to finish
- architectural coupling keeps spreading delays across teams
- brittle integrations keep breaking the flow between internal systems and vendors
- priorities change faster than the organization can absorb them
- AI is being discussed at length but has not changed daily execution
Those are not messaging problems. They are operating problems.
When You Need Both
"The clean setup is simple: consultants frame, hands-on experts prove."
The strongest outside help often combines both roles without pretending they are the same.
A serious consultant knows when the work now needs a hands-on expert. A serious hands-on expert knows when executive alignment, board language, or political air cover has to happen first. The healthy pattern is not territorial. It is complementary.
That matters for firms like ours too. Sometimes the right consultant creates the conditions for hands-on work to land. Sometimes the hands-on expert exposes facts that let the consultant drive a cleaner leadership decision. That is collaboration. The problem is only when one role gets dressed up as the other.
The Questions Worth Asking
"Do not buy by title. Buy by job."
If you are evaluating outside help, ask questions that force the distinction into the open.
- What decision will you help leadership make in the first 30 days?
- What concrete constraint will you help remove in the first 30 days?
- Who will work inside the real flow of work, not just report on it?
- What evidence will exist after six weeks that did not exist before?
- If the answer is “we need more alignment first,” what specifically becomes true afterward?
Weak advisors hate those questions because they collapse ambiguity. Strong ones answer them without flinching.
The CTO Test
The grown-up position is not anti-consultant. It is anti-category error.
Consultants can be valuable. Hands-on experts can be valuable. Some firms can do both. The only part worth fighting is the lazy fiction that they all create the same kind of progress.
If you need executive clarity, buy that. If you need system change, buy that. If you need both, make the handoff explicit.
Anything else is how organizations spend six figures learning that slides do not unjam a release process, an ERP rollout, or the integration chain behind it.
Contact
Let's talk about your real situation. Want to accelerate delivery, remove technical blockers, or validate whether an idea deserves more investment? I listen to your context and give 1-2 practical recommendations. No pitch, no obligation. Confidential and direct.
Need help? Practical advice, no pitch.
Let's Work Together🎭 This Week's Episodes
Telenovelas show what we can't say in client meetings. The drama is heightened, but the patterns are real.
The Trunk-Based Experiment
Katja puts a new DORA baseline beside Navigator's weekly synthesis and finds the same diagnosis from two directions: long-lived branches, rubber-st...
Technical Consultancy
Embedded Delivery Partner
Embedded into your team as an active contributor, reducing delivery friction and helping important work move cleanly.
Technical Advisor
Peer-style technical assessments before far-reaching decisions; reduce architectural and product risk early.
Product & Delivery
Ship working software to real users earlier. Measure impact and adapt based on evidence rather than assumption.
Custom Software Development
High quality, maintainable software. Short-term augmentation that leaves lasting capability in your own team.
Recent Articles
- What CTOs Need From Consultants and Hands-On Experts (01.06.2026)
- AI Coding Agents Need XP (29.05.2026)
- Children of the Magenta Line (25.05.2026)
- The Invisible Nature of Software (22.05.2026)
- AI Won't Run Your Company by Itself (18.05.2026)