The Product SystemThe Vault
The Product Manager Interview Question That Shows If a Team Is Really Empowered, the infographic in this PDF

Career development

The Product Manager Interview Question That Shows If a Team Is Really Empowered

One interview question shows whether a product team is really empowered or just says so: when did evidence last change something already decided?

Want this as a PDF?

You'll also get The Product System, my weekly note on leading product in the AI era. Unsubscribe anytime, and I'll never sell your email. How I handle your details

1

The full infographic, as a PDF

The exact one from the post, sized to print or keep within reach.

2

A copy in your inbox

The download link lands in your email too, so it's there when you need it. No follow-up campaign.

3

The Product System, weekly

My note on leading product in the AI era. One idea a week that compounds. Unsubscribe anytime.

Same interview. Three years. Two completely different careers.

Two product companies can run the same pitch. Empowered teams, outcomes, ownership. You'll own the roadmap. We follow the evidence here. Only one of them can back it up, and from the outside they look identical. Except in one room: the interview.

One question, asked before you sign, tells you which job you are actually being offered.

Ask for an event, not a principle

The people who get this right don't ask about empowerment. Ask about empowerment and you'll get a description of the culture the company wants to have. Instead, they ask for a single event.

The question is this: "When did evidence last change something the company had already decided?"

Then test it across three situations. A solution Sales had already promised. A roadmap item that was already approved. A date already given to a customer. For each answer, ask who made the decision, what the trade-off was and what happened next.

Each situation tests something different. A solution Sales already promised shows whether product can push back on a commercial commitment. An approved roadmap item shows whether approval means the thinking stops. A date already given to a customer shows whether the company will move an external promise when the evidence says it should. A team can be flexible on one and rigid on the other two, so ask about all three.

The reason this works is simple. Changing course costs a company something real. Teams that do it can name the cost. Teams that don't will answer you with a principle.

When you get a principle, ask again

When the answer comes back as a value statement, ask again, warmly. "That makes sense. What's a recent example?"

Then ask a future peer the same thing. The hiring manager tells you how decisions are meant to work. The person who'll sit next to you answers it differently, because they live with how decisions actually get made.

This doesn't make you look difficult. Asking how decisions get made is the job you're interviewing for.

And if nobody can name one event, that's your answer. Empowerment is the plan there, not the job.

Why the answer matters more now

The illustration with this piece shows the gap. The top half is the job they sell you: a bright meeting room, a whiteboard saying you decide the solution, the roadmap and the evidence. The bottom half is the job they give you: Sales already promised the solution, the dates were set in March, and the data never changes anything.

AI is making output cheaper. The wrong job trains you on the part it's replacing: taking a decided solution and shipping it. The right one trains the part it can't touch: deciding what to build and changing course when the evidence says so.

Three years pass either way. Only one version is worth turning up for. The question you ask in the interview is a small cost. Finding out in month six is a much bigger one.

An aspirational culture is a different job, not a bad one

None of this means a company that fails the test is a bad company. An aspirational culture does not make it a bad company. But joining one is a different job.

If the team is not empowered yet, you may be being hired to build that, not to work inside it. That can be a good job too, if you know it going in and the authority and the backing come with it. The point of the question is to find out which job is on the table before you say yes.

Find out if you are joining an empowered team or being hired to build one. If you could only ask about one of the three situations, which would it be?

More free product resources are in the vault at martongaspar.com/vault.

Questions people ask

What is the best question to ask in a product manager interview?
Ask "When did evidence last change something the company had already decided?" It asks for a specific event rather than a description of the culture. Teams that change course based on evidence can name when it happened and what it cost. Teams that don't tend to answer with a principle instead.
How can you tell if a product team is really empowered?
Ask for examples where evidence changed a decision that was already made, such as a solution Sales promised, an approved roadmap item or a date given to a customer. For each, ask who decided, what the trade-off was and what happened next. If nobody can name one real event, empowerment is an aim there, not how the job works.
Should I ask a future peer the same interview questions?
Yes. The hiring manager tends to describe how decisions are meant to work. A future peer, the person who would sit next to you, often describes how they actually get made. Comparing the two answers tells you more than either answer alone.
Will asking hard questions in a product interview make me look difficult?
It shouldn't. Understanding how decisions get made is the core of a product manager's job, so asking about it shows you take the role seriously. Ask warmly, and if you get a principle rather than an example, follow up with "That makes sense. What's a recent example?"
Is it bad to join a company where product teams aren't empowered yet?
Not necessarily. A company with an aspirational culture is not automatically a bad company, but the job is different. You may be hired to build an empowered team rather than work in one. That can be a good role if you know it up front and the authority and backing come with it.