← Part 06: Assemble a prototype
PART 06 · ASSEMBLE · 70 MINUTES
Assemble a prototype
Present slides ▶
Full screen, one slide at a time · 7 slides
From blueprint to build
- Choose one valuable user journey, not the whole product
- Prompt an AI assistant to build one clickable screen for it
- Know which parts are real, which are simulated and which need data
- Improve it through feedback without adding scope
- Test it, and watch a partner try it without help
OUTPUT · A first clickable prototype and an honest review in Blueprint section 10
One journey, start to finish
- TRIGGERThe parent learns that Tuesday’s lesson clashes with a dentist appointment
- OPENTaps the booking link in the tutor’s reminder email
- CHOOSESees the tutor’s free slots this week and picks Thursday at 5pm
- CONFIRMChecks the details and taps “Move lesson”
- DONESees a confirmation; the tutor is told, with no messages swapped
The value happens at one moment. Build towards that moment and nothing else.
Live demo: prompt the booking screen
You are a UX designer and front-end developer. I am testing an idea called TutorDesk, a booking tool for independent tutors. It is fictional and all data is invented. Build one interactive, phone-sized web page, shown as a preview I can click, for this journey: a parent opens a link from the tutor’s reminder, sees their child’s next lesson (Tuesday 4pm, maths, with Sam), picks a new free slot this week from a short list, confirms, and sees a clear confirmation that the tutor has been told. Constraints: one page only, no log-in, no payments, no real data, plain friendly English, large tap targets, readable text and good colour contrast. Use made-up slots and show what happens if the parent picks a slot that has just been taken. Add a small banner saying “Prototype: bookings are simulated”. After the page, list in plain English what is simulated and what a real version would need.
Check the response
- The preview opens and the whole journey can be clicked from start to finish
- Taken slots show a friendly message, not a dead end
- A banner says the bookings are simulated
- The AI lists what is simulated and what a real version needs
Looks real is not the same as is real
In the prototype
- Visual: the screens, buttons, wording and layout
- Simulated: made-up slots that reset when you reload
- Pretend: “The tutor has been told” (nobody was)
In a real version
- Frontend: the same screens, built to work on every phone
- Backend and database: real availability, saved bookings, rules for clashes
- APIs: connections to calendars and email, so the tutor really is told
Know which parts of your prototype are real, simulated or missing, and say so when you show it.
© 2026 MVP Studios Ltd. MVPAI™ and the MVP Studios Academy course materials, including the MVP Founders Programme and MVPAI in a Week, are original works of MVP Studios Ltd. All rights reserved. No copying, redistribution or commercial use without written permission. Course terms