Analytical Thinking: How Asking Too Many Questions Nearly Ended My Career
Last week I wrote about why organisations say they want analytical thinking and then punish the people who actually do it.
Honestly, it was more autobiography than it was observation.
For most of my career in, I have been person who asked the uncomfortable question. The one who said “I don’t think this is going to work” when everyone else was nodding. The one who looked at a poorly thought-out initiative and couldn’t pretend it was fine.
And I paid for it. Repeatedly. I have been labelled - pessimistic, cynical, “almost impossible to manage” - I have been skipped for projects I should have led. A long history of feedback telling me I’m “too direct.” Not so subtle conversations about my “approach.” The growing sense that I needed to make myself smaller to survive.
I remember sitting in 1:1s with managers whose egos were so fragile that I’d spend the whole morning anxious, rehearsing how to say ordinary things in the least threatening way possible. I find the politics of being honest at work exhausting, and what’s more, I was never very good at it.
Don’t get me wrong, I can be harsh. Blunt. Direct to the point where people feel it. My criticism is never about the person, it’s about the work. If something is poorly thought out or low quality, I’ll call it out. But I’ve learned, painfully, that intent doesn’t matter much when the other person feels attacked. “I was only talking about the work” is cold comfort to someone who just got their idea dismantled in front of their team.
So this piece isn’t “analytical thinkers are victims and everyone else is the problem.” The thinking is only half of it. The other half is knowing how to deploy it without setting yourself on fire. Below, you’ll find the frameworks, prompts, and hard-won lessons that I wish I’d had ten years ago.
Key Takeaways
• Analytical thinking is a cognitive skill. Deploying it at work is a political skill. Nobody teaches the second part.
• Pre-mortems, red team exercises, and structured frameworks aren’t just thinking tools — they’re Trojan horses that make challenge safe.
• AI can be your sparring partner before the room becomes your arena — stress-test your position privately first.
• Sometimes the most analytical conclusion you can reach is “this environment won’t let me do good work.”
• Flourishing after leaving isn’t failure. It’s evidence.
The Skill Nobody Teaches You
I wish someone had told me this at 21. Being right doesn’t mean you’ll be heard. And being good doesn’t give you the right to be an ass.
You can see the flaw in the strategy. You can have the data. You can be completely, demonstrably correct. And you can still lose — the argument, the room, eventually the job — because how you say it matters as much as what you say.
I get this wrong frequently, which is ironic because I train people on communication skills, presentation skills, influencing skills. But nobody sits you down and says: “You’re going to see things other people miss. That’s valuable. But if you don’t learn how to deliver that insight without making people feel stupid, you’ll be the smartest person nobody listens to.”
I spent years thinking the problem was other people’s fragility. And sometimes it genuinely was, there are leaders who cannot handle being questioned, full stop, end of discussion, don’t even try.
But I also had to accept that I was handing people the right answer wrapped in a velvet glove. The content was good. The packaging was brutal. And I kept wondering why nobody was opening the parcel.
If you recognise yourself in any of that, this next section is for you.
Your Analytical Thinking Survival Kit
Over 20 years I’ve collected a set of tools that do two things at once: they make your thinking sharper AND they make it safer to deploy.
The Pre-Mortem: Permission to Be Negative
Most people know what a pre-mortem is. Before you commit to a decision, you ask: “Imagine it’s six months from now and this has failed completely. What went wrong?”
What most people don’t realise is that the pre-mortem is a Trojan horse.
In a normal meeting, saying “I think this will fail because...” makes you the problem. You’re the negative one. You’re not being a team player. You’re “that person.” But in a pre-mortem, saying the exact same thing is the exercise. You’re not being difficult — you’re doing what was asked. The structure gives everyone permission to think critically without anyone having to stick their neck out individually.
This is why I use pre-mortems relentlessly with clients. Not because the thinking technique is revolutionary — it’s straightforward. But because it changes the social dynamics of the room. Suddenly the person who spots the fatal flaw isn’t being negative. They’re winning the exercise.
If you’re someone who sees problems others miss, stop raising them in open discussion where you’ll get labelled. Start suggesting pre-mortems instead. Same insight. Completely different reception.
Red Team Your Own Position First
This one took me far too long to learn.
Before you challenge someone else’s idea, challenge your own. Ruthlessly. I used to walk into meetings ready to take something apart — and I was usually right about the problems — but I hadn’t bothered to ask “what am I missing?” or “what’s the strongest argument against my position?”
So when someone pushed back, I wasn’t ready. I’d get defensive. Double down. Turn it into a fight when it should have been a conversation. Classic stuff, really. Could have avoided about half of my “difficult” labels if I’d just done this first.
Red teaming yourself before the meeting is the fix. Take your position and try to destroy it. Ask:
• What would need to be true for me to be wrong?
• What data am I ignoring because it doesn’t fit?
• What’s the most generous interpretation of the thing I want to challenge?
• If I were defending this decision, what would I say?
If your position survives that, you’ll present it differently. You’ll say “I’ve thought about this from several angles and I keep landing here” rather than “this is wrong and here’s why.” You come across as someone who’s done the work rather than someone who’s picking a fight.
AI as Your Sparring Partner (Not Your Ghostwriter)
Last week I talked about how AI is eroding analytical thinking — a pattern backed by recent Microsoft Research. People offload the reasoning and stop questioning the output. That’s the risk. But there’s a version of AI use that does the opposite — that actually sharpens your thinking. Use AI to argue against you.
Before a meeting where you’re going to challenge something, take your position to an AI tool and say:
“This is what I think. Now argue against me. Find the weaknesses. Tell me what I’m missing. Give me the strongest counterargument.”
Then do it again:
“Now take MY position and make the strongest possible case for it. What am I underselling?”
This isn’t using AI to think for you. It’s using AI to stress-test your thinking before it hits the room. You’re getting your reps in — the same reps I talked about last week — but in a safe environment where being wrong doesn’t cost you anything.
A few practical ways to do this:
Before challenging a decision:
I’m about to push back on [X] in a meeting. The strongest version of my argument is [Y]. What are the three most likely counterarguments I’ll face, and how would you respond to each?
Before proposing something new:
I want to propose [X]. Play the role of a sceptical senior leader who’s seen a lot of initiatives fail. What questions would you ask me? Where would you poke holes?
Before a difficult conversation:
I need to tell my manager that I think [X] isn’t working. I want to be direct without being confrontational. This is what I’m planning to say — how would it land on someone who’s defensive about this project?
The point isn’t that the AI gives you perfect answers. It’s that the process of arguing with it forces you to think harder about your own position. You arrive in the room sharper, more prepared, and you come across as thorough rather than combative. Which, if you’re anything like me, is half the battle.
The Five Whys: Stop Fixing Symptoms
The five whys is simple. When you encounter a problem, ask “why?” five times to get past the surface-level explanation to the root cause.
Project delayed? Why? Because the dev team missed the deadline. Why? Because the spec changed halfway through. Why? Because the stakeholder wasn’t consulted early enough. Why? Because nobody owns stakeholder mapping in our process. Why? Because we skip planning and jump straight to execution every single time.
I include this not because it’s clever — it’s almost embarrassingly simple. I include it because most organisations stop at the first or second “why.” They fix the symptom and move on. The person who keeps asking is, once again, “being difficult.”
The career angle is worth spelling out. The person who can consistently identify root causes rather than surface symptoms is extraordinarily valuable. That’s the person who saves the organisation from solving the same problem six times.
The trick — and this is the survival bit — is framing. “I want to make sure we fix this properly so it doesn’t come back” lands completely differently from “you’ve all missed the point.” One makes you indispensable. The other gets you a quiet word about your tone. Same analytical thinking. Wildly different career trajectory.
When the Environment Is the Problem
Sometimes you can do everything right — frame your challenges perfectly, use structured tools, build allies, present with nuance and humility — and it still won’t work. Because the environment is the problem.
Some organisations don’t just accidentally punish analytical thinking. They structurally cannot tolerate it. The leader’s identity is too wrapped up in being the smartest person in the room. The culture rewards agreement so consistently that genuine challenge is experienced as betrayal. The hierarchy is so rigid that questioning upward is simply not possible.
I worked in environments like that. I tried the frameworks. I moderated my delivery. I picked my battles carefully. And I still ended up being told to stay in my lane. Still ended up smaller than I started.
So I silently excited corporate life too long after the realisation that I was spending more energy managing how I was perceived than doing actual work.
And when I finally went freelance, something changed. I started experimenting, trying new things, working in a way that fitted me best. I picked up writing gigs. Started developing software. I’m currently editing a book for someone. I now do work that would never have been “allowed” in my previous roles because it didn’t fit the box I’d been put in. HR people don’t write code, or build products, or takes risks. HR people stay in their lane.
Now I work in a way that works for me and the feedback and opportunities I get now dwarf anything I ever achieved reporting to someone whose primary concern was whether I’d made them uncomfortable in a meeting.
I’m not telling everyone to quit their job. That would be glib. But if you’ve tried everything in this piece — the structured challenges, the red teaming, the careful framing — and you’re STILL being punished for thinking clearly, you’re not the problem.
Building Your Reps: A Weekly Practice
Last week I talked about analytical thinking being like a muscle — you need reps. A practical weekly routine to keep it sharp, even when your environment doesn’t encourage it:
Monday: Question one assumption. Pick something your team or organisation takes for granted. Don’t raise it publicly yet — just write it down. “We assume X. What if that’s wrong?” You’re not doing anything with it yet. Just noticing.
Wednesday: Red team yourself. Take a position you hold strongly and spend 15 minutes trying to destroy it. Use AI if it helps. If your position survives, you’ll hold it with more confidence. If it doesn’t, you’ve saved yourself from being wrong in public. Either way, 15 minutes well spent.
Friday: Ask “did it work?” Pick one thing your team delivered this week. Not “did we do it?” — that’s output. “Did it achieve what we intended?” That’s outcome. Track the difference. Over time you’ll develop an instinct for the gap between activity and impact that most people never build.
Thirty minutes across the whole week. That’s it. But those are the reps that keep the muscle working. The ones AI is quietly removing from your day. Take them back deliberately.
The Final Thought
If you’ve read this far and thought “this is me” — yeah. I know. I was you. In some ways I still am. I still catch myself being too direct, too fast, too impatient with work that isn’t good enough. I’ve just stopped apologising for the thinking and started taking responsibility for the delivery.
To recap: use pre-mortems to make challenge structurally safe. Red team your own position before you challenge anyone else’s. Let AI sharpen your arguments privately so you arrive prepared. Use the five whys to find root causes, and frame them as thoroughness, not criticism. And if none of that works — if the environment punishes clear thinking no matter how carefully you deliver it — trust the skill enough to act on its conclusion.
The frameworks in this piece aren’t just thinking tools. They’re survival tools. They let you be the person who sees what others miss without becoming the person nobody wants in the room.
And if the room still doesn’t want you after all that? Find a better room. They exist. I’m in one now.
Coming Up
Next week: the other side of this conversation. If you’re a manager or founder, what does it actually look like to create an environment where people can think critically without fear? (Spoiler: it starts with shutting up.)
Been labelled “difficult” for doing exactly what was asked — thinking critically? Reply and tell me about it. I’ll read every one.
One Last Thing
As part of a series I’m writing for The Human Stack I’m building a small mobile app, a kind of career sidekick for people who use AI at work but mostly away from their desks. On the train, between meetings, walking to grab coffee. You know the drill.
But I don’t want to guess what to build. I’d rather just ask you.
I’ve put together a really short survey (genuinely 2 minutes) about how you’re actually using AI day-to-day. Your answers will directly shape what this thing becomes.
As a thank you, everyone who fills it in gets two things:
The Manager’s AI Toolkit — an interactive prompt library I use in my training workshops. 50+ copy-paste prompts for performance reviews, strategic planning, team communication, and more. No sign-up, no data required, just open it and use it.
The 90-Day Influence Micro-App — a tiny app you can install on your phone (inspired by this February’s newsletter series). It sends you one small daily action to build your reputation and influence at work. Again, no data needed, it just works.
Both are completely free.
But really, the survey is what I need most as it will feed directly into April’s newsletter content which I’m so stupidly excited about, I can’t say anything yet but will let you know more soon.