Product Learning Lab
Skill · Execution

Reframing stakeholder asks

Convert an urgent request into the underlying problem and a defensible next step.

An ask names a solution. Your job is to recover the problem it's a solution to.

Scenario

The VP of Sales messages you: "We're losing deals because we don't have a Salesforce integration. Can you get it on the roadmap this quarter?" It's phrased as urgent and revenue-linked.

What's the strongest first move?

The method

Getting behind an ask without stonewalling

  1. 01

    Acknowledge the urgency

    Signal you take the stake seriously. Reframing lands as partnership only if the person feels heard first.

  2. 02

    Ask for the incident, not the opinion

    "Which deals? What happened in the room?" Specifics surface the real blocker; generalities repeat the ask.

  3. 03

    Separate the problem from the proposed solution

    State it back: "So the problem is reps can't X. The integration is one way to solve that." Now the solution is optional.

  4. 04

    Offer the problem, plus a next step

    Don't return empty-handed. Bring the reframed problem and one defensible action — a spike, a smaller fix, a decision date.

Same pattern, different asks

The solution on top, the problem underneath

"Add a dark mode"

Stated ask

Users keep requesting dark mode.

Underlying problem

People use the app late at night and the bright UI strains their eyes.

Defensible next step

Confirm the usage pattern, then weigh dark mode against dimming and contrast fixes.

"We need a mobile app"

Stated ask

Leadership wants a native mobile app.

Underlying problem

Field users can't complete one specific task away from a desk.

Defensible next step

Ship that task as a mobile web flow first; validate demand before a native build.

"Make the report exportable to Excel"

Stated ask

A customer insists on Excel export.

Underlying problem

They don't trust the in-app numbers and re-check them by hand.

Defensible next step

Export helps, but the deeper fix is transparency in how the numbers are computed.

Takeaway

Never just accept or refuse an ask. Return the problem behind it and one credible next step — that's the move that keeps trust and keeps you from building the wrong thing well.

Keep going
Skill · Execution

Writing sharp problem statements

Turn the recovered problem into a sentence the team can act on.

Skill · Analytical

Problem vs Symptom

Tell what you observed from what caused it.

Skill · Product judgment

Prioritizing under uncertainty

Decide what the reframed problem is worth against everything else.