Build with AI
How to design an MVP without a dedicated designer
Define one complete user journey, choose useful references and build the states needed to test a small product with real users.
Choose one journey to learn from
Start an MVP design with one complete user task. For a booking product, that could be finding an available time and receiving confirmation. Sketch the information needed at each step before deciding how many screens to build.
A homepage alone will not tell you whether the workflow works. Include the ordinary complications: no available times, a missing required field, a failed request and a user changing their mind. Keep the first version small enough to try with someone.
Collect references for the difficult decisions
Find examples of the interaction you are unsure about. You might need a service picker, a compact calendar and a confirmation summary. Save them in a Taste collection and write what each example solves. Do not assemble an entire app from unrelated attractive screens.
Use the same typography, controls and spacing rules across the journey. If the project already has a component library, start there. New visual treatments should have a reason beyond making individual screens stand out.
A brief for a small first version
This hypothetical booking flow is a starting point you can adapt. It is not a tested customer result.
Build the smallest complete booking flow for this project: choose a service, choose an available time, enter contact details and see confirmation. First inspect the existing components and my Taste collection named Booking references. Use the notes to explain the design direction. Include no availability, invalid contact details and a failed submission. Keep backend assumptions explicit. Show me how to run and review the flow.
Watch someone use it
Give a person the task without explaining the interface. Notice where they pause, what they click first and whether they understand the confirmation. Ask what they expected when something surprises them. Those observations are more useful than asking whether they like the colors.
Revise the largest obstacle, then try again. Keep a short record of what changed and why. Taste can hold the references and notes; the product still needs working behavior, accessibility review and appropriate engineering checks before release.