The Product Question

Raise your hand if you’ve ever shipped something on time, on budget, technically clean — and nobody used it.

Yeah. Me too. And here’s the thing — that’s not a delivery failure. That’s a product thinking failure.

Most of us were trained to ask: Can we build this?

Product thinking asks a different question: Should we build this, and for whom?

Three mental shifts that change everything #

Shift 1 — From features to outcomes #

A stakeholder says: “I need a dashboard with 14 charts.”

Product thinking hears: “I need to make a decision faster and explain it to my boss.”

The dashboard is the solution they imagined. Your job is to find the actual problem.

Shift 2 — From users to jobs #

Clayton Christensen said people don’t buy a drill — they buy a hole in the wall. They hire your product to do a job.

GOAL: Identify the customer problem you are trying to solve by focusing on the outcomes that customers want to achieve, not on the product that you want to sell to them.

Eg: When I go running I want to be able to listen to my music and be entertained by my run (situation, motivation and expected outcome)

So instead of asking “Who are my users?” ask: “What job is someone hiring this for, and what does success look like for them?”

That one question kills more bad ideas in the room than any slide deck.

Shift 3 — From launch to loop #

Products aren’t projects. A project ends. A product loops — build, measure, learn, repeat. Thinking like a product means you’re never done. You’re just at the next iteration.

If your work has no feedback loop, it’s not a product — it’s a deliverable.

You don’t have to be the PM #

Here’s the part I want you to take back to your desk: Product thinking isn’t a role. It’s a lens.

You’re an engineer? Before you estimate a ticket, ask: What decision does this unlock?

You’re a PM? Before you write a PRD, ask: What does success look like to the person using this at 2pm on a Tuesday?

You’re in data or analytics? Before you build a report, ask: What action does this enable that couldn’t happen before?

The people who move fastest aren’t the ones with the best execution. They’re the ones who figured out early which hill was worth climbing.

One question to take with you Next time someone asks you to build something, before you open Jira or Confluence or your IDE — ask one question:

“What does the person who needs this actually need to do next?”

Krish Ram is a member at the Austin CTO Club.