3.2.1 - The Difference Between Learning and Being Stuck

Name the learning signal: say what question is being answered, what signal will answer it and what decision comes next.

Learning signal

Are we learning something new or just stuck in loops?

The call

Know whether you are learning or stuck. Otherwise AI helps you iterate without evidence and every cycle feels like progress while nothing changes.

Sharpen the learning signal with AI

This is a Launch idea, so there are two AI moves: first Sharpen the learning signal using the prompt below, then Build it with AI, building carefully to carry the decision into the live system. This idea also calls for Run it for real.

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 signal and keep the instruction exactly as visible here. It helps you put your launch/learning-signal.md together by refining your three lines until two people would make the same product decision from them.

You are checking whether this learning signal is clear enough before you move forward.

Constraint:
The learning signal must be specific enough that two people would call the same work progress from it.

Example of the standard:
Vague: "We are iterating and learning as we go."
Sharp: "After each round of testing, we check whether content creators acted on at least one context-shaped result. If they did, the context layer is working and we iterate on result quality. If they did not, we stop and investigate whether the context is shaping the query at all."
The sharp version is specific enough that two people would call the same work progress. The vague one is not.

Working draft:
Learning question: [what question is being answered]
Signal: [what signal will answer it]
Next decision: [what decision comes next]

Task:
Decide whether this learning signal is specific enough that two people would call the same work progress. If it already is, say so. If it is vague, rewrite it to meet the standard in the example above.

Check:
- Would two people interpret this the same way?
- Does it stay concrete enough to guide the next step?
- Can you state what question is being answered, what signal will answer it and what decision comes next?

Return:
- Verdict: clear, or needs work
- The corrected three lines, or the original three if already clear
- What was vague, and the one change that fixed it

Copy this into AI chat. Replace the bracketed parts. Keep the rest unchanged. AI will likely suggest refinements based on what you enter. Use those to sharpen your thinking, not replace it.

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

There are two ways to keep remaking a dish. One is "a little more lemon this time", then tasting to see if it fixed the flatness: each cook answers a question. The other is changing five things at once every night, so you never learn what actually helped and the dish never really improves, however busy you feel.

Telling learning from being stuck is the difference between the purposeful tweak and the endless fiddle. Name the one question each round is meant to answer, the taste that answers it and what you will do next. If a round answers nothing you are stuck and not iterating, however many versions you cook.

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 signal is not a feeling of progress. It is the specific answer that tells you whether the last iteration worked. Until you can name one question being answered, one signal that answers it and one decision that follows, you are iterating blind. AI can help run experiments, but it cannot tell you when to stop.

Make the learning signal concrete

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

Too vague: We are iterating and learning as we go.
Concrete enough to test: After each round of testing, we check whether content creators acted on at least one context-shaped result. If they did, the context layer is working and we iterate on result quality. If they did not, we stop and investigate whether the context is shaping the query at all.

The second version lets two people make the same decision from it.

Learning and being stuck can both feel busy. The signal that tells them apart is simple: in learning, each round brings new information and moves you forward; stuck is the same loop again, so when nothing new is arriving, stop and change the approach.

Check the learning signal

Pass: You can say what question is being answered, what signal will answer it and what decision comes next.
Fail: If learning still means we are figuring it out as we go, the signal is not defined well enough yet.

Do not move into the next iteration 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/launch/learning-signal.md written and sharpened: the learning signal 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-signal.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/launch/learning-signal.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: Iterating without a learning signal, which creates output that feels like progress while the core question stays unanswered.
Mitigation: Define one learning question per iteration and pause when the signal is unclear.

Key takeaway

Do not move forward until you can say what question is being answered, what signal will answer it and what decision comes next.

How to document your learning signal

Write your learning signal 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 signal

## Answer
Learning question: [what question is being answered]
Signal: [what signal will answer it]
Next decision: [what decision comes next]

## 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
Learning question: Does more lemon fix the flatness
Signal: You taste it after that one change
Next decision: Keep the lemon or try one other single change

## Evidence
The times I changed three things at once I never knew which one helped, so one change at a time actually teaches me something.

## Decision
Optimising for a clear lesson from each change. Saying no to adjusting several things before tasting.

## Risk
Tasting too soon, before the lemon is stirred through, gives a false read. Let it settle, then taste.

## AI instruction
Change one thing, more lemon, then taste to learn whether it fixes the flatness. Based on that, keep the lemon or try one other single change, never several at once.

Common questions

I keep asking the AI to fix it and it keeps changing things. Am I making progress?
Not if each try teaches you nothing. Learning moves you closer with each loop. Stuck repeats the same loop faster.
How do I tell learning from being stuck?
Learning changes your next question. Stuck asks the same question again. If you cannot say what the last try taught you, you are looping.
The AI can build anything, so why am I still stuck?
Because building was never the hard part. Knowing what to try next is. That is judgement the AI cannot supply. More in AI can build anything. So why are you still stuck?.
What do I actually do when I am stuck?
Stop looping and get a fresh perspective. Someone not buried in it often shifts the whole thing with one question, as in A different set of eyes makes all the difference.

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.