Move from idea to first milestone
Turn a broad product idea into one complete, testable customer journey before adding later features.
On this page
Your first milestone should prove one useful journey from start to finish. It needs to be small enough to build and test in one sitting, but complete enough that someone can use it without your help.
Pick one person and one outcome
Describe who is using the app, what they want, and what confirms they succeeded.
For a bicycle repair shop:
- Person: a customer using their phone
- Goal: request a repair appointment
- Success: see a confirmation with the chosen service and time
“Build a dashboard” is not a complete journey. “An owner can see today’s bookings and open one booking” is.
Decide what can wait
Keep only features required for that outcome. A first booking journey might need service selection, contact details, a preferred time, and confirmation. Customer accounts, payments, reminders, staff schedules, and analytics can wait.
Put deferred ideas in Planner so they remain visible without becoming part of the current build.
Write the milestone
Instead of:
Create a complete repair-shop platform with bookings, accounts, payments, scheduling, messaging, and analytics.
Use:
Build a mobile-friendly booking page for a bicycle repair shop. A visitor chooses one of three services, sees its duration and price, selects a preferred time, enters a name and email, and sees a confirmation summary. Include an unavailable state. Use a calm workshop style. Do not add accounts, payments, or staff features yet.
This gives Ahamo a clear journey, visible result, and boundary.
Check it before building
You are ready when:
- one person can complete one journey;
- the journey has a clear success result;
- you know which features are deferred;
- sample content is enough, or the data requirement is decided;
- you can test the result on desktop and mobile.
If the change touches existing data, sign-in, or several screens, choose Plan first:
Break this milestone into the smallest testable steps. Preserve the current booking journey. Explain what will change and how I should verify it. Do not build yet.
Approve the next coherent outcome, test it, then choose the next milestone from what you learned.
Next: Write your first prompt or build and publish your first app.