Skip to main content

Why ESOP Consulting Firms Can’t Afford AI Theater

Why ESOP Consulting Firms Can't Afford AI Theater graphic on ESOP AI adoption

In employee-owned firms, bad AI adoption doesn’t just create tool confusion. It weakens trust, judgment, and enterprise value.

AI is already inside most consulting firms.

Maybe it is showing up in proposal teams. Maybe in meeting summaries. Maybe in research support. Maybe in project documentation. Maybe quietly, unofficially, in ways leadership does not fully see yet. We've seen the results in recent headlines with McKinsey.

That is no longer the interesting question.

The real question is this:

Will your firm use AI to strengthen the business—or will you accidentally create AI theater?

By AI theater, I mean the pattern I keep seeing across professional services firms: visible AI activity at the top, uneven AI behavior in the middle, unclear judgment at the project level, and hidden risk inside the actual work.

It looks modern from the executive deck. It feels messy everywhere else.

For ESOP consulting firms, that risk is even more serious.

Because in an employee-owned firm, AI is not just a technology issue. It is a trust issue, a quality issue, a margin issue, a utilization issue, a client confidence issue, and ultimately, an ownership culture issue.

The biggest mistake ESOP firms are making right now

Many leadership teams are still asking:

How fast can we scale AI?

That sounds decisive. It sounds strategic. It sounds like leadership.

But in most employee-owned consulting firms, it is the wrong first question.

The better question is:

Where can AI improve the work without weakening professional judgment, delivery quality, or client trust?

That is the real leadership test.

Because consulting firms do not sell technology. They sell expertise, judgment, credibility, trusted execution, and the confidence that clients can rely on your people when the work matters.

That means the risk is not simply “using the wrong tool.”

The real risk is this:

Leaders confuse speed with capability.

A faster first draft is not the same thing as better consulting. A polished output is not the same thing as sound professional judgment. A tool rollout is not the same thing as firm readiness.

And in an ESOP, that distinction matters even more—because the people using the tools are not just employees.

They are the future owners.

In an employee-owned firm, bad AI adoption compounds differently

In many companies, weak AI adoption creates operational noise.

In an ESOP consulting firm, it can distort the exact behaviors that make the business valuable.

Here is the pattern I see:

leadership approves tools centrally practices adopt unevenly some principals push hard others quietly resist managers invent local rules junior staff use unofficial tools because the “approved” guidance is too vague proposal speed improves before delivery discipline does quality review gets murkier utilization looks better before margin quality is actually proven leadership reports progress before the firm has built real confidence

That is not transformation.

That is AI theater.

And in an ESOP, AI theater is especially dangerous because it erodes the things employee ownership depends on:

trust between leadership and delivery teams consistency across offices and practices clarity about what “good work” looks like the apprenticeship model for younger professionals and confidence that leadership is protecting long-term enterprise value—not chasing short-term optics

Employee ownership amplifies behavior.

That is one of its strengths. It is also why bad AI adoption can spread faster than leaders expect.

The right rule: AI should improve the work before it changes the story

This is the simplest discipline I would put in front of any ESOP consulting leadership team:

AI should improve the work before it changes the story.

Too many firms do the reverse.

They announce AI capability before they define where it belongs. They talk productivity before they clarify review. They celebrate faster proposals before they address delivery risk. They push experimentation without giving managers usable decision boundaries.

That is how firms create adoption without trust.

And trust is the real threshold.

Not licenses. Not logins. Not training completions. Not “number of users.” Not the fact that the innovation committee is excited.

For consulting firms, the real question is much simpler:

Would you trust this use of AI in front of a client, inside a deliverable, or under professional scrutiny?

If the answer is unclear, you are not ready to scale it.

The best early AI use cases are usually not the flashiest ones

This is where a lot of firms get pulled off course.

The best early AI use cases are rarely the ones that make the boldest slide in a partner retreat.

They are the ones where:

value is real risk is bounded mistakes are survivable review is clear and trust can compound

That is what I call a high-value / low-regret starting point.

For ESOP consulting firms, that often means starting with:

proposal structuring and boilerplate assembly internal meeting summaries internal research organization project kickoff note consolidation lessons-learned capture repetitive internal documentation cleanup internal knowledge retrieval from non-sensitive repositories admin and coordination support that reduces friction without blurring judgment

Notice what these have in common: they help the firm, reduce waste, and improve speed—but they do not casually outsource the core professional judgment the client is actually paying for.

That matters.

The goal is not to start where AI is most impressive.

The goal is to start where AI helps the firm learn how to absorb the tool without weakening the work.

A policy no one can apply is not a guardrail

A lot of firms already have some kind of AI policy.

That is fine. But let’s be honest: a PDF in SharePoint is not an operating model.

If your PMs, principals, proposal leaders, or technical reviewers still have to ask:

Can I use this for this client? Can I use it on this deliverable? Can I use it to draft this section? Can I use it if I review it? What kind of review actually counts?

…then you do not have a usable guardrail.

You have governance theater.

The strongest firms are getting more practical. They define four kinds of AI guardrails:

  • Access Guardrails

What tools are approved? What environments are restricted? What client data is absolutely off limits?

  • Use Guardrails

What tasks are allowed? What is allowed only for internal drafting? What is prohibited?

  • Review Guardrails

What must be checked? What requires senior, licensed, or designated review? What counts as real review—not ceremonial review?

  • Decision Guardrails

Where can AI support judgment? Where must judgment remain unmistakably human? What can never be delegated just because the output looks polished?

This is the line I keep coming back to:

Guardrails only work if people can use them in the flow of work.

If your managers cannot apply the rule in real time, it is not a guardrail.

It is paperwork.

In ESOP firms, the manager layer decides whether AI becomes capability—or chaos

This is where many executive teams misread the real point of leverage.

AI adoption in consulting firms does not succeed or fail in the CIO’s office.

It succeeds or fails in the manager layer:

project managers discipline leads regional office leaders proposal leaders studio or Branch heads practice leaders client account leaders

These are the people who decide, every day:

what good use looks like what must be reviewed what gets escalated what stays internal what becomes client-facing what shortcuts are acceptable and what professional standards still apply

If they are unclear, your adoption will be uneven no matter how sophisticated the enterprise policy sounds.

And in an ESOP, this matters even more.

Because those managers are not just enforcing process. They are teaching ownership behavior. They are showing younger professionals what stewardship looks like.

So if AI gets introduced as a shortcut, younger staff will learn shortcut behavior.

If it gets introduced as a disciplined tool that supports quality, trust, and judgment, they will learn something much more valuable:

how to use new technology without weakening the firm.

That is a strategic advantage.

What I would tell ESOP consulting firm leaders to do next

If I were sitting with an ESOP consulting leadership team right now, I would push five practical moves:

  • Stop asking, “How do we scale AI?”

Start asking:

Where can we responsibly rely on AI today—and where are we still learning?

That is the better leadership question.

  • Pick 3–5 high-value / low-regret use cases

Start where:

value is visible review is manageable client risk is low managers can coach good use clearly

  • Create role-based guardrails

Not just firm policy.

Define what:

junior staff can do PMs can do principals can do proposal teams can do technical reviewers can do and what requires escalation

  • Train managers to coach judgment—not just compliance

The real question is not:

Did they follow the rule?

It is:

Did they understand where professional judgment still mattered?

  • Measure capability—not just activity

Do not over-index on:

user counts logins tool usage training attendance

Also measure:

review burden rework reduction proposal cycle quality delivery consistency manager confidence client-facing error avoidance adoption consistency across practices and whether the work actually got cleaner, not just faster

Because this is still true:

What you measure is what you scale.

The real leadership challenge for employee-owned firms

The real question is not whether your firm will use AI.

It will.

The real question is whether you will adopt AI without eroding the exact things that made the firm worth owning in the first place:

trust judgment quality mentorship accountability and long-term enterprise value

That is the leadership standard.

And honestly, I think ESOP firms should hold themselves to a higher one.

Because employee-owned firms are supposed to think longer-term. They are supposed to care more about stewardship. They are supposed to resist short-term theater in favor of durable value creation.

That is exactly the posture AI requires.

The firms that win here will not be the ones that moved first.

They will be the ones that learned where AI belongs, where it does not, and how to strengthen the business without weakening the work.

Build trust before scale.

A closing challenge for ESOP leaders

If you lead an employee-owned consulting firm, do not ask whether AI can make your teams faster.

It probably can.

Ask whether you are using AI in a way that makes the firm:

more trustworthy more consistent more coachable more scalable and more valuable over time

Because in an ESOP, you are not just deploying technology.

You are shaping the future behavior of owners.

And that means the real goal is not AI adoption.

It is responsible capability.

Final question for your leadership team

Here is the conversation I would have in your next executive meeting:

Where are we using AI today in ways that strengthen trust, quality, and judgment—and where are we still creating AI theater?

If that question gets uncomfortable, it is probably the right one.

Contact Dana Houston Jackson for AI Adoption help.

Written by Dana Houston Jackson, Founder and Principal Change Architect of Change – With a Coach Approach, LLC and former ESOP member

Quick Answers

What is AI theater?

Visible AI activity at the top, uneven AI behavior in the middle and unclear judgment at the front line. It looks modern in the executive deck and feels messy everywhere else.

Why is AI adoption riskier for ESOP consulting firms?

In an employee-owned firm, the people using the tools are the future owners. Poor adoption erodes trust between leadership and delivery teams, consistency across practices, quality standards and the apprenticeship model that make the firm worth owning.

Where should ESOP consulting firms start with AI?

With three to five high-value, low-regret use cases such as proposal structuring, internal meeting summaries and lessons-learned capture. Back them with role-based guardrails, managers trained to coach judgment and measures of capability, not just activity.

Originally published on LinkedIn on April 22, 2026. Read it on LinkedIn.

Dana Houston Jackson

Dana Houston Jackson is the founder of Change With A Coach Approach, LLC and the author of The AI Adoption Traps. She started in manufacturing, spent 10 years in construction, taught K-12 and university students, and ran technology projects as a scrum master and project manager. As a consultant she has stood up project management and change management offices and trained clients across industries, including work with the Department of Energy. She’s a speaker, advisor and executive coach with 30 years in the work, now focused on helping leaders turn AI activity into lasting capability.

    Comments are closed