When Clear Questions Feel Like Threats

There’s a saying we all know: don’t shoot the messenger.

People think it’s about tone. Or delivery. Or tact.
I don’t think it is.

It’s about what happens when someone asks the questions that make it impossible to keep pretending everything is fine.

I’ve learned this through experience, not theory.

I’ve given feedback and been quietly shut out afterwards.
I’ve named things early and been told I’m “not a good fit”.
I’ve worked with founders who hired me, paid me, then recoiled when I asked the questions that came before the work they thought they wanted.

And every time, the pattern is the same.

The issue is never the question itself.
It’s what answering it would force.

When I become the problem instead of the question

One of the clearest examples happened with a marketing client a few years ago.

They hired Qallann Marketing Agency for a logo and a website.

Simple brief. Paid upfront.

My team and I went for the discovery meeting.

In the room were two people: one who built the product, and another who worked in legal and positioned himself as the marketing voice. He spent most of the meeting explaining to me how disruptive their product was.

The product itself was built around a real national issue. Big vision. Big names. Government-level ambition. Lots of references to ministers and institutions.

The problem was simpler.

They were now trying to sell this to small and medium businesses. Private companies. People who would have to pay real money.

And everything they were saying was about Kenya. Or Africa.

Nothing was about the buyer sitting across from them.

So I asked the obvious question.
Why would a small business pay for this?

The room shifted.

They explained the vision again. Louder this time. With more name-dropping.

I reframed the question.
What problem does this solve for small businesses, specifically?

That’s when the defensiveness showed up.

They told me the space was regulated.
They said they couldn’t talk about the product openly.
They said people would need to sign NDAs first.

So I asked the next obvious thing.
How do you expect people to sign up for something they’re not allowed to understand yet?

That’s when I stopped being their marketer partner and became “difficult”.

At one point they asked me, genuinely offended, whether I was asking them to rebuild their whole business model.

I wasn’t.
I was asking them to listen to the people they said they wanted money from.

By the end of the meeting, it was clear: they wanted output, not interrogation. A website. A logo. Something to point at.

The questions made them uncomfortable because answering them would mean admitting something wasn’t ready yet.

The moment the room tightens

I’ve watched this happen across organisations, teams, and client meetings over the years. 

At first, the conversation flows.
People talk confidently about vision, disruption, impact.

Then I ask something simple.
Who exactly are you trying to reach here?

There’s a pause.

Someone answers with a category instead of a person.
Or with a value instead of a reason.
Or with words like “premium”, “quality”, or “innovative”.

So I ask the next obvious thing.
What does that mean to them?

That’s usually where the mood changes.

These are not clever questions. They’re not abstract. They’re not confrontational.
They’re basic.

And yet, I’ve watched rooms tighten when they’re asked.

Not because people don’t understand them. Most people do. Instantly.
But because once the question is on the table, the answers are no longer optional. The answer can’t stay theoretical.
It has to connect to how real people make decisions with their money, time, or attention.

How this shows up in organisations too

This isn’t just about clients.
I’ve seen the same thing inside teams of five, nine, twenty.

You raise something early. Gently. Clearly.

A lack of ownership.
Moving targets.
Decisions being deferred instead of made.

At first, people nod.

Then the energy shifts.

The conversation stops being about the issue or your feedback and starts being about you.

Your tone.
Your timing.
Your “approach”.

You’re told to soften. Or reduce. Or “be careful”.

And slowly, the feedback loop closes.
Because what it implied was inconvenient, not because you were wrong.

Why this keeps happening

Most people are top-down thinkers.

They start with what they want to build, then work backwards. There’s nothing wrong with that. It’s common. It’s not a flaw.

The problem comes when someone like me, a bottom-up thinker, asks questions from the other direction.

From the buyer.
From the executor.
From the consequence.

Those questions feel disruptive because they slow things down at the exact moment people want momentum.

And when someone can’t produce the answers quickly or answer them cleanly, the discomfort needs somewhere to land.

So it lands on the person asking.

What I’ve learned from being on the receiving end

I no longer assume that being hired means people want the truth.

Often, they want progress without friction.
Movement without interrogation.
Output without discomfort.

I’ve learned that when I ask basic questions and the room goes quiet, that silence is information. It tells me exactly where things are fragile.

It tells me what’s being protected.
It tells me what can’t yet be examined.
It tells me whether the work ahead will be honest or cosmetic.
And it tells me whether I’m about to be positioned as the problem.

Why my work feels different

I don’t arrive at the first meeting with answers or pre-packaged solutions.
I don’t rush past the basics or assume everything is in place.

I ask questions. And those questions that reveal whether the thing you’re building can actually stand in the world you’re trying to put it in.

Sometimes that helps people clarify and leads to sharper work.
Sometimes it leads to hard decisions.
Sometimes it leads to silence or makes people realise they are not ready.
Sometimes it makes me unnecessary.
And sometimes, it makes me unwelcome.

All these outcomes are fine.

Because at the end of the day, I’m not interested in being liked for delivering output that avoids reality.
I’m interested in helping them see where things don’t yet add up, while there’s still time to change them – before they spend more money, more time, or more trust pretending they do.

The cost people underestimate about my questions

Every organisation, every founder, every team pays for avoidance.

They just choose when.

Up front, in discomfort and adjustment.
Or later, in rewrites, rehires, pivots, and exits.

I’ve been on both sides of that cost.

And I’ve learned to trust the moment when a simple question changes the air in the room or start to feel like an attack.

That moment tells you exactly where the real work is.

If this resonates, you already know why.
And if it doesn’t, this probably isn’t the work you’re looking for.

Both are fine.