From purpose to a specific answer
Before searching for a solution,
make the problem smaller.
Work through purpose, the essential obstacle, the type of solution and the smallest specific action — in that order.
The product name appears at the end. It will cope.

The order used on this site
Four stages from purpose to action
Starting with a product tends to produce requirements that justify the product. This is efficient if the purpose was purchasing. It usually was not.
Worked example
Five people need to share appointments and notice double bookings.
Purpose
Describe the changed state without a product name.
Introduce an AI scheduling platform with advanced permissions, external integrations and analytics.
Specification, not purpose.
Who uses the analytics?
State whose situation changes, by when, and how success is observed. If the sentence needs a product name, remove it and see whether the purpose survives.
Delete Test
Remove conditions and see whether the purpose still works.
The useful question is not whether a feature would be nice. It is what fails when the feature is absent.
Route
Choose the type of solution before the specific product.
Once the obstacle is clear, consider the routes in a deliberately unglamorous order.
StopIs the work itself needed?
OrganiseChange the sequence, owner or input
LearnIs missing knowledge the obstacle?
PersonIs this judgement better assigned?
ExistingCalendar / spreadsheet / manual
ToolIf still required, search here
In this example, the first route is one shared place for appointments.
Choice
Test the smallest action that meets the must-haves.
Use an existing shared calendar for one week before comparing dedicated scheduling platforms.
| At enquiry | After the test | |
|---|---|---|
| Purpose | Introduce a powerful tool | Notice clashes early |
| Conditions | Seven desirable features | Two Must + one Should |
| Route | New software | Process change + existing tool |
| First action | Product comparison | One-week trial |
Try the shared calendar first.
If it fails, turn the failure into a product requirement.
Use this order
- PurposeWhat changes, for whom, and how is success visible?
- ObstacleWhat currently makes the purpose difficult?
- RouteProcess, learning, person, existing method or tool?
- ActionTest the smallest option that meets every Must.