From Clusters to How Might We: Writing Clean Opportunities

Clusters of insights identify where problems exist. Opportunities define what the problems are asking for. The transition from cluster to opportunity is a specific act of framing — one that requires enough specificity to guide creative response and enough openness to avoid locking into a predetermined solution.

The "How Might We" question is the standard mechanism for this transition, and it works well when it is written with precision.

What a Good Opportunity Statement Does

An opportunity statement does three things simultaneously.

It represents the cluster accurately. The opportunity should be traceable to the evidence: anyone reading it should be able to see how it was derived from the specific pains, needs, gains, and pressures that form its cluster. If the connection is not clear, the statement is too abstract.

It stays in problem space. A well-written opportunity does not contain a solution. "How might we help customers feel safer when paying online?" is an opportunity. "How might we add a security badge to the checkout page?" is a solution phrased as an opportunity. The difference matters: the first invites multiple creative responses, the second shuts them down.

It is specific enough to generate useful responses. "How might we improve the experience?" is an opportunity in name only — it is too vague to guide ideation. "How might we help customers stay informed about their order status without relying on support contacts?" is specific enough that a team knows what successful responses would look like.

"Each cluster becomes a classic 'How Might We...?' question. These become the first Opportunities."

Common Failure Modes

The solution already embedded. A stakeholder proposes an opportunity that is actually a feature request in disguise: "How might we build a better notifications system?" This sounds like an opportunity but is already a solution. The underlying need — customers want to stay informed without effort — has not been articulated. Rewriting it means stepping back to the cluster and asking what the customer is actually trying to accomplish.

The cluster not yet complete. Sometimes a "How Might We" is written before the clustering is finished — before enough insights have been gathered to see the full shape of the problem. Premature opportunity statements tend to be narrow, addressing one facet of a problem without acknowledging the others. The test: can you trace the opportunity back to at least three distinct insights from different sources?

The opportunity too broad. "How might we make the entire experience better?" is not an opportunity — it is a strategic aspiration. Opportunities need boundaries. They should be locatable in a specific stage of the journey and should address a specific type of customer difficulty.

Clustering Opportunities Into Themes

Once individual opportunities are written, they should be clustered in turn. Groups of two or three related opportunities often reveal a broader theme that gives the Big Solution its shape.

For example:

• "How might we help customers feel confident about product quality before purchase?"
• "How might we help customers find the right product faster without expert knowledge?"
• "How might we reduce the cognitive effort required to compare similar products?"

These three opportunities cluster into a theme: customers need better knowledge and confidence at the discovery and acquisition stages. This theme becomes the brief for a Big Solution — a unifying direction that multiple emerging solutions can contribute to.

The cluster-to-opportunity transition is where insight becomes design brief. It is the moment the journey map stops describing the past and starts orienting toward the future. The quality of the opportunities determines the quality of the solutions that follow — which is why precision in this step pays dividends through every subsequent phase of the program.