Stan Tscherenkow
Wrong-engagement pain

I Don't Know If My Consultant Is Even Solving The Right Problem

The slides look beautiful. The methodology is sound. The fees keep arriving. And somewhere quiet you cannot shake the question: is this even the right problem?

This page is for the owner deep into a consulting engagement, surrounded by deliverables, and unable to feel that the work is changing anything that matters. The work is real. The match between the work and your actual problem is what stays uncertain.

Short answer

If you cannot say in one sentence what business outcome will be different ninety days after the engagement ends, the engagement is not solving a problem you can verify. That is not always the consultant's fault. The brief you wrote, the layer you scoped, and the question you handed over decide whether the work can land.

Research signal

The hot language is polite. Then quiet.

Owners do not say this out loud while the engagement is running. They say it when the invoice arrives.

Clean deliverables

Slides, frameworks, dashboards. Visible work. Real work.

Vague outcome

If the work succeeds completely, you cannot say what specifically will be different.

Layer mismatch

The consultant is solving in one layer. The cost is sitting in another.

Quiet unease

You have not said it to anyone yet. You will not until the bill is paid.

Infographic

The brief decided most of this before the consultant arrived.

Consulting engagements rarely fail because of the consultant. They fail because the brief defined the wrong problem to solve, and the work was excellent against the wrong problem.

Pattern visualBriefyou wrotedefined the problemEngagementconsultant ranagainst the briefRealitythe actual costin a different layerIf columns one and three do not match, column two cannot fix anything.
The work landed where the brief pointed. The brief did not point at the cost.
Jump map

Fifteen questions you actually ask at 11pm.

"The work is impressive."

"I am not sure it is the work we needed."

"I cannot point to what will actually change."

"Maybe I scoped this wrong."

"I cannot say that out loud yet."

Each answer is short enough to finish here and sharp enough to make the deeper page worth opening.

01

How can I tell if my consultant is solving the right problem?

Write one sentence.

'If this engagement succeeds completely, X will be different in the business.'

If you cannot fill in X concretely, the engagement is not solving a problem you can verify.

Fast read

If you cannot name what will be different, the engagement cannot prove it worked.

What concrete looks like

X is not 'we will have better processes.' X is 'our average time to close a sales decision will drop from 14 days to 5.' Specific. Measurable. Dated. If your X is vague, the engagement was scoped vague.

AtlasReal Target DisciplineAtlasConsultant For Decision ProblemCompareAdvisor vs Consulting
02

Is this the consultant's fault?

Usually not.

The consultant ran the brief.

The brief is what you handed them.

If the brief named the wrong target, the consultant did not get to choose otherwise without violating their scope.

Fast read

Excellent work against the wrong brief still arrives as the wrong work.

Where the responsibility splits

The consultant owns execution against the brief. You own the brief. Most engagements fail at the brief layer, then get blamed at the execution layer.

AtlasThree Proposals, Three Different ProblemsAtlasAgency vs AdvisorCompareAdvisor vs Consulting
03

Did I write a bad brief?

Maybe not bad.

Maybe just brief.

Most owner-written briefs name the symptom, not the structure. The consultant accepted the symptom as the target. The work followed.

Fast read

Brief named the symptom. Engagement worked the symptom. The structure underneath stayed.

What a strong brief includes

The business outcome you want. The current state in numbers. The hypothesis about what is causing the gap. The decision you will make based on the work. If your brief did not include all four, the consultant did not have what they needed.

AtlasDecision Architecture ExplainedAtlasHow To Choose Outside HelpManualRead Your Own State
04

What does a good brief actually look like?

Three to five pages.

The business outcome named.

The current numbers attached.

The hypothesis about cause.

The decision you will make from the work.

The hard constraints (budget, time, people).

Fast read

Five elements. None optional. Most briefs miss three of them.

Why each element matters

Outcome anchors the engagement. Numbers make success verifiable. Hypothesis prevents wandering. Decision ensures the work routes to action. Constraints prevent the engagement from becoming a project on top of a project.

AtlasReal Target DisciplineAtlasHow To Choose Outside HelpCompareAdvisor vs Consulting
05

Why does this feel off mid-engagement?

Your gut sees the layer mismatch before your head names it.

The work is real.

The work is in one layer.

The cost is in a different layer.

Your gut feels the gap.

Fast read

The feeling is faster than the analysis. Trust it enough to investigate.

What to do with the feeling

Not panic. Not silence. Schedule one meeting with the consultant and bring one question: 'What is the one decision in this business that, if I closed it tomorrow, would make most of this work unnecessary?' Their answer tells you whether they understand the layer.

AtlasWrong Help Feels ProductiveAtlasRole Bias ExplainedManualRead Your Own State
06

Can I redirect them mid-engagement?

Yes.

Most senior consultants would rather redirect than ship a deliverable the client does not value.

The conversation costs you ego.

The redirect costs you less than the engagement landing in the wrong layer.

Fast read

Redirect costs ego. Wrong-layer landing costs the engagement.

How to open that conversation

'I want to make sure we are solving for the right outcome. Help me get clearer on what specifically will be different in the business when this work lands.' That sentence opens the door without burning the relationship.

CompareAdvisor vs ConsultingAtlasHow To Choose Outside HelpApplyApply
07

Should I stop the engagement?

Only after the redirect conversation.

If the redirect lands and the work pivots usefully, finish.

If the redirect lands and the work continues in the same direction, the engagement was always headed there. Stop.

Fast read

Stop after one honest conversation, not before.

What stopping cleanly looks like

Pay for work completed to date. Take the interim deliverables. Document what was learned. Most consultancies will work with you on this if the conversation is professional.

CompareAdvisor vs ConsultingAtlasHow To Choose Outside HelpApplyApply
08

Why are the slides so beautiful?

Because slides are what consulting firms can control.

The deliverable craft is high.

The deliverable craft is also independent of whether the work mattered.

Beautiful slides do not prove the right problem was solved.

Fast read

Slide craft is a downstream signal. It does not validate the problem definition upstream.

What to read for, not look at

Skip the design. Read the recommendations. Ask: which of these would change my business behavior next week? If the answer is none, the work is presentation, not decision.

AtlasWrong Help Feels ProductiveAtlasReal Target DisciplineCompareAdvisor vs Consulting
09

What is layer mismatch?

The consultant is operating at the layer where their methodology works.

Your cost is sitting in a different layer.

They produce excellent work in their layer.

It does not touch the layer where the cost lives.

Fast read

The work is real. The level is wrong.

How layers stack

Surface layer: messaging, design, copy. Execution layer: process, ops, team. Authority layer: who decides, how, with what right. Most consulting engagements live in surface or execution. Most owner pain lives in authority.

AtlasBusiness Help HierarchyAtlasThree Proposals, Three Different ProblemsAtlasConsultant For Decision Problem
10

How do I know what layer my problem is at?

Ask one question.

If everything in the recommendation was already true, would the business be different?

If yes, the layer is right.

If no, the layer is wrong.

Fast read

Imagine the work is done perfectly. If the business still has the same problem, the layer is wrong.

What this test reveals

Most engagement disappointment comes from imagining the work is done and realizing the underlying problem is untouched. The test is faster done in your head than at the end of the engagement.

AtlasNeutral Triage Before Role ChoiceAtlasOutside Help Market MapAtlasHow To Choose Outside Help
11

What if they cannot work at my layer?

Then they are the wrong role.

Not because they failed.

Because the role is defined.

Consultants execute against scoped work. They do not redefine the layer the work happens in.

Fast read

Some roles cannot work some layers. Not a failure. A definition.

What role does work your layer

If the cost is authority-layer, you need advisory before consulting. If the cost is execution-layer, consulting fits. If the cost is mindset-layer, coaching fits. The role is downstream of the layer.

AtlasTraining vs Coaching vs Consulting vs AdvisoryCompareAdvisor vs ConsultingCompareAdvisor vs Coaching
12

Is this scope creep in reverse?

Sometimes.

Reverse scope creep is when the engagement keeps narrowing toward what is easy to deliver, away from what was hard to solve.

The deliverable gets cleaner.

The original problem stays open.

Fast read

Engagements drift toward the deliverable they can finish.

How to spot it

Look at the original brief. Look at the current scope. If the current scope is smaller, cleaner, and further from the original outcome, the engagement narrowed away from the problem.

AtlasReal Target DisciplineAtlasWrong Help Feels ProductiveAtlasHow To Choose Outside Help
13

Will the final recommendation actually move the business?

It depends on whether the recommendation routes to a decision you will close.

Beautiful recommendations sit on the shelf if there is no named decision-maker on the receiving end.

The deliverable does not move the business.

The decision after the deliverable does.

Fast read

Decks do not move businesses. Decisions after decks move businesses.

Who closes the post-engagement decision

Name them now, before the deliverable lands. If you cannot name who in your business will receive the recommendation and close on it, the engagement will end with a binder, not a change.

AtlasDecision Closure Before PeaceAtlasOperator Before Authority ReleaseApplyApply
14

Why am I afraid to say something?

Because the bill is large.

Because the firm is reputable.

Because saying it out loud might mean admitting you scoped the engagement wrong.

None of those reasons change what your gut is telling you.

Fast read

The price of saying nothing is the engagement landing exactly as you fear.

What to say first

To yourself, not to the consultant: 'I think the layer is wrong.' Sit with that. Then write the redirect question. Then have the meeting.

AtlasWhy This Decision Is StuckAtlasDecision Delay CostApplyApply
15

When should I bring outside help?

Before you sign the next engagement.

Or right now, if the current one feels off and you have not had the redirect conversation.

A short, paid read on the layer fit costs a fraction of the consulting bill.

Fast read

The cheapest read is before the next contract. The next-cheapest is right now.

What that read looks like

Two hours. The brief, the current state, the recommendation in progress. Output: a written read on whether the engagement is in the layer your business needs. Not a sales call. A read.

AtlasHow To Choose Outside HelpWork pathWays to WorkApplyApply
Second visual

The brief. The work. The reality. Three things that should match.

When the brief and the reality do not line up, the work is excellent in the wrong direction.

Pattern visualBrief writtenwhat you askedforWork deliveredwhat they shippedagainst the briefRealitywhat the businessactually neededIf column one does not match column three, column two cannot fix anything.
The bill does not care that the brief was wrong.

If you cannot say what will be different ninety days after the engagement ends, the engagement is not solving a verifiable problem.

The cheapest move is naming the layer before the next contract.

Apply when the pattern is active