A small pebble at the centre of a paper spiral that unwinds outwards, opening wider with each turn.

1of 6

Turn a real customer problem into an open question

Strong ideation begins with a real customer problem, not a solution disguised as a question. Turn discovery findings into open prompts that leave room for different approaches and needs.

Build & Validate
Customer discoveryEvidence-led building

By the EWOR Team2 min read

Two customers may struggle with project handoffs for different reasons. One may lack access to the latest commitments, while another may be unsure who owns each task. Before facilitating an ideation session, identify the discovery finding each prompt is intended to explore. Do not combine distinct problems into one appealing but vague statement.

Put the discovery finding next to the question

Start with a discovery finding that explains who was affected, what they were trying to do, where the difficulty arose and what it cost them. Use that finding to shape an ideation question that explores possible solutions.

For a hypothetical agency team, you might find that incoming project owners spend time asking colleagues which commitments remain outstanding. This supports a question about how to identify unfinished commitments, but it does not yet justify building another dashboard.

Record the finding alongside the proposed question. If the link depends on an additional assumption, make it explicit. If accounts conflict, keep separate questions for the different situations rather than inventing a shared need.

Check the assumptions behind the wording

For the incoming owner, try this question: "How might the new owner identify unresolved commitments without repeatedly interrupting colleagues?" Add an evidence note explaining who reported the handoff problem, which stage caused uncertainty and whether other accounts confirmed the finding.

If you suspect missing information is causing delays, look for cases where the information was available but nobody knew who had the authority to make a decision. Keep that explanation open until the evidence supports it. A prompt that already calls for a dashboard skips the discovery question and jumps straight to a solution.

Preserve disagreements between customers

If one participant needs a reliable history while another needs someone with the authority to make a decision, keep both accounts and develop separate questions. Record who described each situation and what circumstances might explain the difference. Combining them into one elegant question risks steering the team towards a product neither group needs.

Identify which additional interview or observation could help distinguish between these explanations. The workshop can explore both, but its outputs should remain traceable to the differing evidence rather than implying that every customer wants the same outcome.

Give the facilitator context alongside the prompt

Document the selected prompt alongside the participant context, relevant observations, unresolved assumptions and any conflicting accounts. Record fixed constraints, such as safety or legal requirements, separately from the founder's preferred implementation.

Give the group room to explore different approaches within those constraints. Decide what the prompt represents before choosing the workshop format. It should invite participants to explore a specific, evidence-backed finding, not present a solution as already approved.

No comments yet.

Be the first to comment on this signal.

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter

Continue learning

Related modules