Why being helpful is a trap

One question, asked at one moment, that saves quarters of work.

The difference between somebody thinking strategically and somebody running on autopilot shows up in a single moment. It’s the moment right after they’re asked to do something, and it tells you whether the next six weeks are going to be useful or wasted.

Most people say yes immediately, because saying yes is how you appear helpful and easy to work with. A smaller group says no and acquires a reputation for being difficult.

There’s a third response, and the people who use it tend to be the ones I want in the room when something consequential is being decided.

They ask what problem we’re trying to solve.

Three things compressed into one question

They questioned the request at all. Most people don’t. Somebody says “build a dashboard” and work begins, because the request came from someone senior and questioning it feels like friction, and friction feels like a career risk.

To be precise about the scope, I’m talking about requests that are solutions in disguise. Build a dashboard. Change this process. Add a field to the form. Those aren’t requirements, they’re somebody’s proposed answer to a problem you haven’t been told about yet, and the proposal usually arrived in the first ninety seconds of them thinking about it.

They asked about the problem rather than the request. Behind every request for a dashboard is a real difficulty, and it’s frequently something like “I keep getting surprised when things go wrong” or “I have to justify this number in a meeting every Thursday and I hate it”. Once that’s on the table, you often find they don’t need a dashboard. They need an alert, or a conversation with a different team, or one number in an email every Thursday morning.

That’s how weeks of work get saved before they’re spent, which is a form of value nobody ever sees, because the wasted quarter that didn’t happen leaves no trace.

They said “we”. Not “what do you need”. What are we trying to solve.

That single word changes the temperature of the entire exchange. Asking about the underlying problem can easily land as obstruction, as the analyst being difficult again, as somebody creating process where none was wanted. Framed as something the team is working out together, the identical question becomes collaboration. Same information sought, completely different reception.

The thing this framework doesn’t resolve

Here’s where I’ll be honest about the limits, because the advice above works better in the abstract than it does at three o’clock on a Tuesday.

Sometimes the person asking knows exactly what problem they’re solving and simply doesn’t want to explain it to you, because explaining it would require disclosing something political. The dashboard exists to give a director cover in a meeting. Asking what problem we’re solving, in that situation, is asking someone to say out loud a thing they’ve decided not to say, and no amount of collaborative framing makes that comfortable.

And sometimes the honest answer is that there’s no underlying problem worth solving, and the request exists because it exists. Surfacing that can be genuinely unwelcome, because now somebody has to either defend it or drop it, and both are worse for them than if you’d just built the thing.

So I’d stop short of claiming this always makes you look strategic. It reliably surfaces information. What happens to you afterwards depends on the organisation.

What to actually do

Next time somebody brings you a solution, ask what problem we’re trying to solve.

Just the question. No framework, no discovery workshop, no template. One sentence, asked with real curiosity rather than as a challenge, and then listen properly to the answer instead of preparing your next point while they talk.

There’s a lot of pressure at the moment to say yes to everything, particularly anything with AI attached, because nobody wants to be the person slowing it down. The whole industry is optimising for speed at a moment when direction matters considerably more, since moving quickly in the wrong direction is just an efficient way to be wrong.

Being helpful was never really about saying yes to everything, however much moving fast gets celebrated. It’s about making sure the thing everyone’s about to spend a quarter on is the right thing.

Although I’d be interested to know, in your company, whether asking this makes you strategic or just annoying. I don’t think that’s a rhetorical question. The answer tells you something important about where you work.