The words that box you in

I’ve been noticing something about how business analysts get stuck.

It’s not a skills problem. Most BAs I know can run circles around their stakeholders when it comes to actually understanding what’s broken and how to fix it.

But we stay stuck anyway. In the “tactical helper” box. The “can you document this for us” box. The box that gets smaller every budget cycle.

I think I finally figured out why.

It’s the language we speak.

By that I don’t mean whether you can “communicate effectively” or “speak to executives.” Everyone knows that matters.

It’s specific words that keep us trapped in the process role when we’re trying to move into the strategy one.

Here are five words that signal:

I help execute

Instead of:

I help decide.

I still slip into them. You’ve probably heard (or read?) me do it too. But once you start hearing the difference, you can’t unhear it.

A problem is something to fix.

An outcome is a destination worth the investment.

Leaders care about destinations.

When you walk into a room and say, “the problem is X,” you’re positioning yourself as the fixer. And fixers are expendable. There’s always another BA, another contractor, another AI tool that can “fix problems.”

But when you say “the outcome we need is Y”… suddenly you’re talking about value. About whether this is even worth doing. About strategic choices.

Same insight. Different altitude.

A solution sounds finished. Certain. Safe. Which means when it doesn’t work, guess who takes the heat?

A bet is an investment with risk attached. It opens up the conversation you actually need to have:

Is this worth putting money behind at all?

No wonder banks and financial firms love to come up with banking and investment solutions. They would never call anything a bet, even though every investment is one. They frame their offers as solutions so that it sounds unquestionable.

You’re not trying to sound unquestionable, but you’re trying to make people think.

Constraints sound like complaints from IT. Reality is non-negotiable.

That’s it.

When you ask for requirements, you’re asking people what they want. When you ask for evidence, you’re asking them to justify why it matters.

One makes you a documenter. The other makes you a filter.

And filtering, that is, protecting the team’s focus from every half-baked idea that floats through a planning meeting… that’s strategic work.

You don’t have to say this one out loud, but you should hear it in your head.

Not every stakeholder request deserves your energy or a spot on the roadmap.

Most of it is noise.

When you can hear the difference between signal and noise (and hold that line without apologizing for it), people start trusting your judgment differently.

Your words teach people how to see you.

Change the label, and you change the expectation.

Change the expectation, and you change where you sit in the room.

I’m not saying this is easy. Old habits die hard. I still fall back into my old conditioning and start talking about problems, solutions, and constraints. But now I hear myself when I do it. I know what I’m signaling.

Once you start hearing it too, you’ll know exactly when you’re speaking like someone who executes process... and when you’re speaking like someone who manages value.

That’s the shift that gets you out of the box.