3.2.1 - The Difference Between Learning and Being Stuck

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.

Why it matters

The difference between learning and being stuck is whether each iteration answers a question or just produces more output. AI can generate variations quickly, but human judgement decides whether the latest change moved the needle or just moved the work. The difference is between focused iteration and expensive repetition.

Explainer

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.

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.

The code that brings these decisions to life lives in the build-in-public repos (subCancel, ghostMarketingFlow and flowRun), which are works in progress growing alongside the writing. We work through the code together each week in the free weekly workshops; that is where these ideas get put into practice with hands on the keyboard.

If you sign up, this idea continues with how it all fits together, a worked example, how to use it with AI, how to evaluate it on a real change, the risks worth naming and how to mitigate them, the key takeaways and a copy-paste AI prompt you can drop straight into your next chat. Examples are shown on the Cloudflare Workers stack with AI-assisted coding tools; the ideas apply equally on any other platform.