Why Your Brain Overcomplicates Problems in Consulting (And the One Mental Move That Fixes It)

You just got asked a straightforward question in a team meeting. Something like: "Why did client revenue dip last quarter?"

And instead of answering, your brain immediately starts cataloguing every variable you've touched in the past two weeks. Macro headwinds. Sales cycle lag. Pricing pressure. Competitive dynamics. Channel mix. You want to be thorough. You want to show you've done the work. So you start talking — and thirty seconds in, you can feel the energy in the room go flat.

You're not bad at this job. Your brain is just running the wrong operating system for the environment you're in.

The Overcomplication Trap Is Not a Character Flaw

Here's the mechanism nobody explains at orientation: everything that got you hired is actively working against you right now.

In school — even in a rigorous undergrad or a competitive graduate program — you were rewarded for comprehensiveness. Leaving out a variable lost you points. Showing your full reasoning chain was the whole assignment. Gaps were penalized. Gaps meant you didn't know something.

Consulting inverts this completely. In consulting, comprehensiveness is a liability when it buries the answer. Your manager doesn't want to know everything you considered — they want to know the one thing that changes what they do next. The gap you leave out intentionally, because it doesn't move the needle, is called judgment. That's the thing they're trying to develop in you and also the thing they're grading you on before you know the test exists.

Your brain hasn't caught up yet. It's still in exam mode. That's not a character flaw — it's a conditioned response to a decade of incentives that just got flipped overnight.

The Anatomy of an Overcomplicated Answer

Here's how it plays out in practice. A junior consultant — call him David, eight months into his first engagement — gets asked by the project lead: "Why did market share drop in the Northeast region?"

David has been living in this dataset. He knows it cold. So his brain immediately starts constructing a complete picture: he's thinking about the macro environment, about three competitor moves he flagged last week, about a pricing anomaly in one SKU, about distribution gaps, about a promotional calendar mismatch, and about a customer satisfaction score trend he noticed in the appendix of a report from two months ago.

He builds a 12-variable analysis. It takes four hours. The slide is dense and technically correct. He sends it.

What the data actually showed, visible in the very first cut he ran, was this: one large regional distributor churned in Q2 and accounted for 60% of the share loss on its own. Everything else was noise.

David wasn't wrong about the other variables. He was wrong about what his manager needed. The cognitive trap was that his brain treated "why did market share drop" as an academic question requiring a complete answer, when it was actually an operational question requiring an actionable answer. Those are different questions. Consulting runs on the second kind.

The 'So What' Compression Drill

This is the one mental move that breaks the pattern. It takes less than ten minutes once you've practiced it a few times, and it will change the quality of almost everything you send or say.

Step 1: Write your full answer. Don't skip this. Get everything out of your head and onto the page. All the variables, all the nuance, all the caveats. This is your brain doing what it was trained to do — let it finish. This draft is for you, not for anyone else.

Step 2: Write one sentence that captures the only thing a senior person needs to act on. Not a summary. Not a headline. The one thing. The sentence that, if they only read this and nothing else, gives them enough to make a decision or take a next step. In David's case, that sentence would have been: "Market share loss in the Northeast is driven almost entirely by the Q2 churn of [Distributor X], which we should prioritize recovering before diagnosing anything else."

Step 3: Rebuild your answer starting from step 2. Lead with that sentence. Then, and only then, add supporting context — but only the context that defends or sharpens that lead sentence. Everything that doesn't serve the lead gets cut or moved to an appendix. What you're left with is a consulting answer. Tight, directional, and useful.

Run this drill on your next piece of analysis before you send it. Ask yourself: did my answer change? Did it get shorter? If the answer is yes to both, you just did something most first-year consultants take 18 months to figure out.

The Communication Version: Compressing in Real Time

The drill above works great for written deliverables. But what about when you're in a meeting and you feel the urge to over-explain building in real time — that pressure in your chest when someone asks you a question and your brain starts serving up everything at once?

The verbal version is about sentence starters that signal you've already done the compression internally, even if you're still nervous. These phrases buy you a half-second to find your lead sentence and they communicate confidence before you've said anything of substance:

• "The short answer is..." — forces you to find the short answer before you speak it.
• "The thing that matters most here is..." — signals judgment, not just data recall.
• "Bottom line up front: [sentence]. Happy to go deeper on any piece of that." — this is the consulting handshake. It shows you know the difference between the answer and the backup.

What you want to avoid is the filler that signals you're still sorting: "So there are a few things going on here..." or "It's actually pretty complicated because..." — those phrases tell a senior person that you haven't compressed yet, and they will mentally check out or cut you off before you get to the point.

The goal isn't to sound slick. It's to get out of your own way so the actual thinking you've done gets heard.

If this pattern — the over-engineering, the vague feedback, the feeling that you're working constantly but somehow still missing the target — sounds familiar, you're not alone and you're not broken. The rules of this job are real, they're learnable, and almost no one explains them explicitly.

The First-Year Consultant's Field Manual: What They Expect But Never Explain is a dense, practical PDF guide built specifically for analysts and associates in the first 0–18 months at MBB or tier-2 firms. It decodes the fifteen most common pieces of vague feedback you'll receive — including "be more 80-20," "think hypothesis-led," and "be more proactive" — into concrete, observable behaviors with worked examples. It also includes a self-diagnosis tool to help you tell the difference between normal imposter syndrome and genuine performance gaps, because those two things require completely different responses and most people can't tell them apart when they're in the middle of it.

It's $97. No fluff, no cheerleading — just the translation layer the job doesn't come with. You can find it here.

But first: try the So What Compression Drill on your next piece of analysis before you send it. Did the answer change? Did it get shorter? Reply and tell me what happened.