2.1.3 - What This Build Is Meant to Teach You, Not Just to Ship

Learning goal

Is this build teaching one clear lesson?

The call

Name the lesson before you build. Otherwise AI helps you ship fast without learning anything you can act on.

Sharpen the learning goal with AI

This is a Build idea, so there are two AI moves: first Sharpen the learning goal using the prompt below, then Build it with AI, vibeCoding the thinnest working code that tests the decision.

New here? Let your AI do this with you. Paste your problem into Guide me and it builds a prompt that walks you through this in ChatGPT or Claude. You do not need to know how to prompt.

Prefer to drive the AI yourself? Give ChatGPT or Claude this page and ask it to help. For skill.txt, the Claude Code plugin and other ways in, see how to use vibe2value.

Or copy this prompt into AI chat, replace the bracketed lines with your real learning goal and keep the instruction exactly as visible here. It helps you put your build/learning-goal.md together by refining your three lines until two people would make the same product decision from them.

There are six ways to work with AI across a build. This idea's AI moves are noted above. See Working with AI for all six and where each fits.

The same idea on a recipe card

Picture trying a new recipe to learn one specific thing. "I am making this curry to find out whether the kids will eat more vegetables when they are spiced" is a question the dinner can actually answer. "I felt like cooking something different" teaches you nothing you can use next week.

Your learning goal is that one question on the plate. Before you build, name the thing you are trying to find out, the build that tests it and the sign that answers it. A meal cooked to answer a question teaches you something, the same as a build aimed at one lesson rather than just more output.

The recipe card is just a simple example, using everyday cooking ideas everyone understands, to make the concept clear. See the recipe card.

What it really means

A learning goal is not a loose hope that the build will teach something. It is the exact question the build is meant to answer. Until you can name one hypothesis, one question and one signal that answers it, the build will collect noise instead of evidence. AI can help generate experiments, but it cannot decide what counts as learning.

Make the learning goal concrete

Compare the broad version with a version you can actually test.

• Too vague: This build should help us learn what users want from AI search.
• Concrete enough to test: This build should tell us whether a content creator gets more relevant results when their saved context shapes the search than when it does not.

The second version lets two people collect the same evidence from it.

Check the learning goal

• Pass: You can say what you believe, what the build needs to answer and what signal will prove or weaken that belief.
• Fail: If the build is still meant to teach something useful without a clear question, the learning goal is not sharp enough yet.

Do not move into implementation or prototype work until this passes.

What you'll walk away with

This post is about the framing decision: the words that pin down what this idea actually means for your build, before any code. You'll come out with your own knowledge-base/build/learning-goal.md written and sharpened: the learning goal pinned down as a decision, three worked examples to map against your own surface and an AI prompt that pressure-tests it until two people would make the same call.

Write it down

Your learning-goal.md is a real file in your project. The AI forgets everything between sessions. It reads this file each time to pick up what you already decided, on this idea or another part of the build. Write it down once instead of explaining it again.

knowledge-base/shape-build-launch/build/learning-goal.md is just a suggested name and place for this information. The name and the location are just how we organise this type of documentation, not something you have to follow. Call the file and put it wherever suits your project. What matters is that it is written down in a format that is easily understood by both people and the AI.

The .md ending is markdown, a plain text format often used for documents kept in a code repository like GitHub. It is just the common way people store this kind of writing alongside their code.

Writing it down is how you keep good context for your AI. See Keep the signal, not the noise for why this matters across a whole build.

Risk and mitigation

• Risk: Expanding the build before the lesson is clear, which creates output but hides whether anyone learned anything useful.
• Mitigation: Define one learning signal for each iteration and pause new scope when that signal is still unclear.

Key takeaway

Do not move forward until you can say what you believe, what the build needs to answer and what signal will prove or weaken that belief.

How to document your learning goal

Write your learning goal up in full so your AI has the whole picture: the answer, why you believe it, what you are optimising for, where you might be wrong and the standing instruction it should follow. Keep it in a file with your project like this.

# Learning goal

## Answer
Hypothesis: [what you believe]
Question: [what the build needs to answer]
Signal: [what signal will prove or weaken that belief]

## Evidence
Why you believe this. Conversations, examples, tickets, your own experience.

## Decision
What you are optimising for and what you are saying no to.

## Risk
Where you might be wrong and what would tell you.

## AI instruction
The standing note your AI reads on this project.

Here is one filled in so you can see what good looks like, grounded in the recipe card idea from earlier.

## Answer
Hypothesis: The kids eat more vegetables when they are spiced
Question: Will they eat more of this curry than plain veg
Signal: Their plates come back empty

## Evidence
The kids left plain vegetables untouched last week but cleared a mildly spiced dish the week before.

## Decision
Optimising for learning whether spice gets them eating veg. Saying no to changing three things at once and losing the lesson.

## Risk
They might eat it for a reason other than the spice, like hunger. Compare it against plain veg on a similar night.

## AI instruction
This dish is a test of whether the kids eat more vegetables when spiced. Watch whether their plates come back empty compared with plain veg, and change one thing at a time.

What now?

Apply it. Guide me turns what you are building into a prompt that walks you through this idea.

Get all 27. The guide is a free coffee-length read with the whole method. Join free and it is yours to download.

Get a hand. Work with me and we will work out together what is worth doing. The first conversation is free.