How an idea
becomes
a business.

The hypothetical example

Imagine a small team running paid workshops. Organizers manage bookings through messages and a spreadsheet. Attendees keep asking whether places are available and whether their booking is confirmed.

The question to answer

Where do organizers and attendees lose time or confidence?

A first exercise

As a learning exercise, prepare two short conversation guides, one for organizers and one for attendees. Ask about the last booking, the steps involved, and what was unclear. Listen before suggesting a tool.

What to look for

Repeated questions, awkward handoffs, useful habits, and differences between the two groups.

What to carry forward

A simple picture of the people, their current workflow, and the difficulties worth investigating.

Those observations help narrow the problem in the next stage.

The hypothetical example

In the hypothetical workshop business, repeated booking questions could come from an outdated availability list, an unclear confirmation message, or two people assuming the other has replied. Each explanation points to a different response. Adding a faster way to answer messages could leave the underlying confusion in place.

A sequence for understanding the problem

1. Locate the difficulty.

   Who experiences it, at what moment, and with what consequence? A real example gives the problem boundaries.

2. Trace the workflow.

   Follow an enquiry through availability, booking, and confirmation. Note the information, decisions, and handoffs at each step.

3. Test the explanation.

   Separate the repeated question from its possible causes. What observation would support each explanation, and what would rule it out?

4. Surface the constraints.

   Consider time, budget, responsibility, tools, and habits. Mark what is known, what is assumed, and what cannot easily change.

5. Choose the priority.

   Compare frequency, impact, and feasibility. Pick a specific difficulty to investigate, with a clear picture of what improvement would mean.

The question to answer

What is causing the difficulty, and which part is worth solving first?

A first exercise

Use this sequence to draft a one-page problem brief. Choose one bottleneck, explain the likely cause, and state what evidence would make you reconsider. Keep other possibilities visible.

What to look for

A traceable pattern, a plausible explanation, important constraints, and a consequence that matters to the person affected.

What to carry forward

A problem brief: person, situation, workflow, likely cause, constraints, assumptions, and priority to test.

The resulting brief gives each possible solution a clear job to do.

The hypothetical example

For the workshop example, a clear availability page or a simple booking form might answer most questions. An AI assistant is another possibility, but it would still need reliable information and a way to handle uncertainty.

The question to answer

Which approach makes the complete task easier and more dependable?

A first exercise

Sketch a simple solution and an AI-assisted option using sample workshop information. Compare setup, accuracy, checking effort, cost, and what happens when the information changes.

What to look for

A useful result the person can trust, with manageable errors and a clear way to recover.

What to carry forward

A reasoned choice of approach, with the assumptions and trade-offs visible.

That choice becomes the brief for a small prototype.

The hypothetical example

A first workshop-booking prototype could show available sessions, accept a sample request, and explain what confirmation looks like. It can be a paper sketch or clickable demo before becoming working software.

The question to answer

Does the proposed change reduce the difficulty that made this problem worth solving?

A first exercise

Create one end-to-end path with sample details. Plan a short task-based test, including a full workshop or a changed booking. Keep any simulated behavior visible.

What to look for

Successful task completion, remaining uncertainty, support needed, and whether the change addresses the original problem.

What to carry forward

A prototype, an evidence plan, and a reasoned view of whether the proposed solution creates useful value.

A clearer product makes it easier to define an honest promise for launch.

The hypothetical example

For the workshop tool, the promise might center on clear availability and fewer booking questions. The brand and launch page would need to make that benefit understandable without claiming more than the prototype can do.

The question to answer

Who is this for, what becomes easier, and why should they try it?

A first exercise

Draft a positioning statement and a short launch page for the hypothetical tool. Plan who could try a first version, how they would begin, and where feedback or support would go.

What to look for

A message people can understand and a first experience that matches what the message promises.

What to carry forward

A brand brief, a draft launch page, and a small launch plan.

The next question is how the right people discover the offer and decide whether it fits.

The hypothetical example

Workshop organizers might be the buyers while attendees use the booking experience. A useful message for an organizer would address their workload, and a possible price would need to make sense for the size of their business.

The question to answer

Who values the improvement enough to pay, and can the business deliver it at a sensible cost?

A first exercise

Choose one hypothetical audience and discovery channel. Draft an introduction, role-play a sales conversation, and compare per-event and monthly pricing. Include acquisition, delivery, and support in the cost assumptions.

What to look for

A clear buyer, relevant interest, unresolved objections, and plausible delivery economics. A compliment alone would not establish demand.

What to carry forward

A business hypothesis connecting customer value, buyer, price, route to market, and cost of delivery.

A sale creates a promise to keep. The next stage follows what happens after someone starts using the product.

The hypothetical example

For the workshop example, another event would create a chance to see whether the tool is worth using again. The organizer’s experience would also reveal the support and maintenance needed behind the scenes.

The question to answer

What would make this useful enough to return to, and practical enough to keep running?

A first exercise

Plan a simple record of questions, errors, support effort, and reasons to return. If a test is later run, compare what happened with the original problem and decide what to improve, simplify, or stop.

What to look for

A recurring need, a dependable result, sustainable effort, and specific reasons for changing the next version.

What to carry forward

A learning record and a reasoned decision about the next iteration.

The loop returns to people: listen again and let the new evidence sharpen the problem.