Do Module 1 of Wright, for free, right now

What you ship at the end

One paragraph. About 120 words. It names a real person, describes one painful thing in their life, and ends with a one sentence guess at the thing your kid might build for them. That paragraph is the idea brief, and it is the seed of the next eleven modules. Every later coach either builds on it or sends the kid back to fix it.

Most people skip this step. They start building before they know who they are building for, ship something nobody wanted, and then wonder why nobody wanted it. A brief written by a 14 year old who actually thought about it beats a Stanford MBA's pitch deck about a market the MBA cannot describe in plain language. That is the principle this whole module is built on.

Why customer first, not product first

A real builder thinks at three levels, in this order:

1. The person. A specific human, with a name.
2. The problem. The painful thing in their life.
3. The product. The thing you would build to fix it.

The order is the entire game. Customer first. Problem second. Product third. Skip the customer and you build for nobody. This module trains the customer-first move. Once your kid has done it once, they have it for life. It is the single most reused skill in the whole twelve module program.

What you need before you start

• A notes app or a paper notebook. Your kid will write things down.
• 30 to 90 minutes of real attention. Quiet room, closed door, phone face down. This module does not need any software installed. The building tools come in Module 3. Module 1 is all thinking and watching.

What counts as a real idea

Your kid has had maybe forty ideas in the last year. Where are they now? In the same place everyone's ideas go: a graveyard behind their own eyes they cannot see. The whole game is getting one idea out of that graveyard. Most of what a kid calls an idea right now is not actually an idea. It is a category in a costume.

Category versus idea

Here is what most people mean when they say "I have an idea": "I want to make a fitness app." That is not an idea. That is a category. A category is a shape an idea might one day fit inside. You cannot build a category. You can only build a specific thing, for a specific person. Watch the difference.

The first column sounds bigger. The second column is actually buildable. A real idea answers three questions, in this exact order:

1. Who is the person? Use their actual name.
2. What is the problem? "Spends 40 minutes a day searching for X." Specific.
3. How do you know it is a problem? Did you watch them? Did they tell you? Did you do it yourself?

If your kid can answer all three, they have an idea. If they cannot, they have a category.

The shape of a real idea

Here is what a real idea sounds like on paper:

Sarah is 17 and runs the social media for her dad's gym in San Mateo. She spends about 5 hours a week trying to turn 90 minute Zoom-recorded class footage into 60 second Instagram Reels. She uses CapCut. She gets frustrated because she has to scrub through the entire 90 minute Zoom to find the one moment that would make a good clip. I watched her do it last Saturday for two hours. She muttered "this is so stupid" four separate times.

Count what is actually in there:

• A name. Sarah. An age. 17. A role. Runs social for her dad's gym.
• A specific tool she already uses. CapCut.
• A specific frustration. Scrubbing 90 minutes of Zoom.
• A moment that was witnessed. Last Saturday, two hours, "this is so stupid" four times.

Now the same idea as a category: "an AI app for social media managers to turn long videos into short clips." Zero people. No Sarah, no Saturday, no four mutters. Just a market shape. The 14 year old who can write Sarah's version will out-build the 35 year old who writes the second version. Not because the kid is smarter, but because the kid is thinking about Sarah and the adult is thinking about a market.

A simpler way to think about it

Imagine your best friend is coming over and you are making them a sandwich. You do not make "a sandwich." You think about what they actually like. You remember they do not eat mayo. You remember they said pickles are "the best texture, mathematically speaking." After two minutes of thinking about your specific friend, you know exactly what sandwich to make. Module 1 is the same move. The friend is the customer. The sandwich is the product. The two minutes of thinking is the part everybody skips.

How to find problems in the wild

You have two candidate people circled from Lesson 1. Now your kid needs to figure out what they actually struggle with, which is almost never what you think it is. People are bad at telling you their problems. They are very good at showing you their problems, if you are willing to sit there and watch.

Three ways to look. All work. All uncomfortable in their own way.

1. Watch one person for a week. Strongest signal. Most uncomfortable.
2. Sit in the community where your person already hangs out. Medium signal.
3. Read one subreddit or Discord for two hours. Weakest signal. Lowest discomfort.

The order matters. Method 1 gives you more in three days than Method 3 gives you in three weeks. Most learners default to Method 3 because it takes the least courage. If your kid can do Method 1, do Method 1.

What watching actually finds

Tara, 15, wanted to build something for her older sister Priya, 18, who was applying to college. Tara assumed the problem was "writing the essays" and had a whole AI essay coach in her head. Then she watched Priya for a week. Just watched. Took notes. Did not interrupt. Here is what she actually saw:

Priya did not have an essay problem. Priya wrote essays well. The problem was that Priya was applying to 12 different schools, each with its own portal, different prompt wording, different character limits. Priya was juggling 12 browser tabs and 12 Google Docs and could not remember which essay was for which school. I watched her paste the wrong essay into the wrong school's portal three separate times in one Saturday. She has a spreadsheet to track it. The spreadsheet broke on Tuesday. She rewrote it from scratch. Took her 40 minutes.

Tara's idea was not an essay coach. It was a single dashboard for tracking 12 college essays across 12 portals, with one source of truth for which essay belongs to which prompt. Different product. Much smaller. Much more specific. Priya would have paid for it the moment she saw it. The only reason Tara got there was that she watched.

How to actually do it

• Pick the person. If your kid lives with them, easy. If not, find a reason to be near them.
• Open notes. When you spot friction, type one line, put the phone away. Do not interrupt. The watching is the data. The conversation comes later, with the coach.
• Sunday night, look at the notes. Cluster the ones about the same thing. The biggest cluster is the candidate problem.

If your kid cannot physically watch someone, use Method 2: pick the one online place the candidate actually spends time, read it for 60 minutes sorted by top of the week, and write down the top 5 complaints that start with "anyone else," "why does X always," or "I hate that." Complaints in communities are gold.

How to spot a fake idea

Your kid did Lesson 2. They watched, they took notes, they probably feel good about one candidate. Read this before they fall in love with it. Most candidate ideas that feel exciting after a week of watching are fake. Not because your kid is not smart. Because fake ideas wear a costume that makes them feel real, and you only notice the failure four weeks later, after building the wrong thing. There are four fakes. Each has a 30 second tell. Run your candidate through all four.

A failed candidate at the start of Module 1 is a win. A failed candidate at the end of Module 6 is a disaster. If your candidate fails a fake, that is good news. Your kid just saved two months building the wrong thing.

How to pick between candidate ideas

Your kid probably has one to three candidate ideas now. The next decision is more expensive than it looks: it chooses which one to carry into the next eleven modules. The "exciting" idea is almost never the right one. The right one usually looks slightly boring on Tuesday and quietly compounds into something real by Module 12. You do not pick well by intuition. You need a test. Here it is.

The constraint test (three questions, scored 1 to 5 each)

Score each from 1 to 5. Higher is better. Add the three. Highest total wins.

1. Reach. Can you actually hand the v1 to this person? A 5 is "I live with them and could hand them the v1 by next Saturday." A 1 is "they are a hypothetical type of person I do not actually know."
2. Frequency. How often does the pain hit? A 5 is every day, multiple times. A 1 is once a year. People pay to make daily pain go away, not annual pain. (Concentrated pain counts: college apps is once a lifetime but three intense weeks, and Tara's tracker was a real product.)
3. Buildability. Could you ship the dumbest possible version in 4 weekends? A 5 is "I could sketch it on paper right now and build it in a few hours." If your v1 sentence includes "login," "user accounts," "database," "dashboard," or "AI-powered," you are describing a v3. Strip it.

A worked example

Three candidates, scored:

• Discord moderation bot for kid mods without credit cards. Reach 5, Frequency 4, Buildability 4. Total 13.
• Tara's college essay tracker for Priya. Reach 5, Frequency 5, Buildability 3. Total 13.
• A better Spotify recommendation engine for a cousin. Reach 4, Frequency 5, Buildability 1 (beating Spotify's algorithm is years of work, not weekends). Total 10. Out.

Two tie at 13. The tiebreaker is which idea came out of you fastest, because speed is a signal you actually thought it through. The essay tracker came out in 90 seconds. It wins.

Reading your score

• 8 or lower: not an idea worth shipping yet. Go back to Lesson 2, pick a different person or method. Better to lose a week now than seven later.
• 9 to 11: workable, but scope it down. Ask if there is a smaller version of the same problem that scores higher.
• 12 to 15: ready. Time to write the brief.

Now write the idea brief

This is what your kid ships. One paragraph, about 100 to 150 words, saved in a file called idea_brief.md in a project folder (or a notes app, whichever they will use for the rest of the program). It must contain every one of these, in any order:

1. A customer's first name. A real person, not "people who like fitness."
2. The customer's age.
3. What the customer does (school, work, hobby) that is relevant to the problem.
4. The specific painful moment you witnessed. Where, when, what they did or said.
5. The bad workaround they currently use. A tool, an app, a hand-drawn spreadsheet. Concrete.
6. Why existing tools fail this specific customer. Even one sentence.
7. What you might build (v1). One sentence. Buildable in 4 weekends.

The builder below turns that scary blank page into seven small boxes. Fill them in and it assembles a real paragraph live, counts the words against the target, and tells you honestly which pieces are still missing, the same checks a parent runs. It saves in your browser as you go. When all seven elements are present, copy it into idea_brief.md. The builder never writes the brief for your kid. It just makes the blank page less frightening.

The four things you check

You do not have to be technical. When you read your kid's brief, you are checking for four things. You are not grading their writing. You are checking that they actually thought about the person before they imagined the product.

1. A real, specific person. Not "high school students." A name. "My cousin Maya, 13, who teaches herself piano on TikTok."
2. A painful enough problem that the person already tries to fix it badly. "Maya has 14 tabs open hunting for chord progressions" is real. "Maya wishes she played piano better" is not.
3. A small product guess at the end. One sentence, not a feature list.
4. A real answer to "how do you know that is a problem for Maya?" "I watched her do it three Saturdays in a row" beats "I asked her once."

The rule for the whole program, learned here first: you inspect the work, you do not do the work. Ask one question, then listen. Do not type their answers, edit their idea, or research their market for them. A project can be faked if you do it. The skill cannot.

Is the brief actually done?

Before you call Module 1 finished, run these five questions on the brief. Out loud, honestly. The point is not to pass. It is to catch the gap now, instead of in Module 6 with a half-built product nobody wants.

1. Can you say their name? First name, age, where you know them from. Not "people who."
2. Can you point to a moment? The exact time you saw the pain. When, where, what app was open, what they said. A vibe does not count.
3. Can you name the bad workaround? The tool, the app, the duct tape they use today. "Nothing" means the pain is not real enough.
4. Can you ship v1 in 4 weekends? Describe it in one small sentence. "Platform," "ecosystem," or three stacked features means it is a v3. Strip it.
5. Why this person, not someone else? Name the reasoning: reach, frequency, buildability. "It sounded interesting" does not count.

Five full-credit answers means the brief is solid and your kid is ready for Module 2. Four means go back to the one lesson the missing answer maps to for 30 minutes, then re-check. Three or fewer means do not move on yet. There is zero shame in re-doing Module 1. The fast pass through Module 1 is the slow pass through Module 6. Take the slow pass now.