The loop real product teams use
Design thinking is a 5-step loop. Companies pay designers a lot of money to run it. You can run it at your kitchen table.
It is a loop, not a line. Great builders go around it many times. Bad apps happen when someone jumps straight to step 4 and never leaves.
Steps 1 and 2: find a problem worth solving
An app is a gift you make for a specific person. So start with people, not technology. Grab paper and answer with real names: your brother, your netball team, your grandmother, the tuck shop line.
👀 Questions to find the WHO
- Who do I see struggling with something small every week?
- Who always asks me for help with the same thing?
- What group am I part of (team, class, church, family) that shares one annoyance?
😤 Questions to find the PAIN
- What do they do the slow way (paper, memory, shouting across the house)?
- What do they forget, lose, or repeat every single week?
- What makes them say "somebody should fix this"?
📱 Questions to check "why an app?"
- Would a screen actually help here, or would a sticky note do?
- Will they use it more than twice?
- Can I explain the help it gives in one breath?
A Kingston teen notices her football coach keeps match details in a battered notebook, and parents call HER every Friday asking where the game is. WHO: the coach and the parents. PAIN: match info lives in one notebook. That is an app waiting to happen.
Now compress everything into one sentence. This is your promise, and you will paste it into every AI builder in this course:
Example: "My app helps my football team's parents see every match's time and venue without calling anyone."
Step 3: imagine badly, on purpose
Your first idea is rarely your best one. Set a 5-minute timer and write 10 app ideas for your problem, including silly ones. Quantity beats quality here: idea number 8 is often the winner. Then circle the ONE that is smallest and most useful. Small is a superpower: a tiny app that works beats a giant app that never gets finished.
Steps 4 and 5: build it on paper first
Professional designers sketch screens on paper before anyone codes. You will too, because tomorrow you will describe these screens to an AI, and a sketch turns a vague wish into clear instructions.
- Draw 3 rectangles on your paper. Each rectangle is one screen of your app.
- Screen 1: the home screen. What is the FIRST thing a user sees? Draw boxes for it. Label the buttons.
- Screens 2 and 3: what happens after they tap the main button? Draw it. Arrows between rectangles show the journey.
- Test on a human. Hand the paper to someone at home. Say "tap with your finger, tell me what you expect to happen". Watch where they hesitate. That hesitation is free product research.
- Fix the sketch, not their behaviour. If they tapped the wrong thing, the design was unclear. Redraw it. That is one full lap of the loop, done in 20 minutes with zero code.
Sketching first works with how teenage brains learn: it makes the idea concrete, gives instant feedback from a real person, and keeps the creator in charge of decisions before a machine starts making them. Learners who plan on paper give the AI clearer instructions and get dramatically better apps in Lessons 3 to 5.
Your friend says "I want to build an app with AI tonight!" What is the FIRST design-thinking question to ask them?
Finishing this opens Lesson 2: What is vibe coding?