Opportunity Framing

Treating customer needs, pain points, and desires as opportunities to be explored in their own right, distinct from any solution, and working that opportunity space before committing to how to address it. It is the discipline of staying in the problem long enough to understand it, rather than jumping to the first idea that comes to mind.

Why it Matters

The instinct is to hear a problem and immediately propose a fix, which locks the team onto one solution before the need is even understood. Framing the need as an opportunity, separate from any solution, keeps the problem space open, surfaces several opportunities to choose between, and lets the team pick which problem is worth solving before arguing about how. A well-framed opportunity is specific enough to act on and solution-free enough not to prejudge the answer.

Signals

• Conversations that leap from a customer comment straight to a feature.
• "Opportunities" that are really solutions in disguise ("they need a dashboard").
• One problem solved repeatedly while more valuable ones are never named.

Benefits

A clearer understanding of the real need, several framed opportunities to choose among, and solutions judged against the problem they serve rather than adopted by default.

Risks

Framing opportunities so broadly they cannot be acted on, or so narrowly they smuggle in a solution; staying in the problem space so long that nothing ships.

Tensions

Exploring the problem competes with the pressure to show progress through solutions, and a need can always be framed at many levels; the skill is choosing one specific enough to act on without prejudging the fix.

Examples

Reframing a request for a specific feature as the underlying job the customer is trying to get done, then considering several ways to serve it.