1.3.1 - The One Outcome That Makes This Build Worth Doing in the First Place

The earlier files describe the product (user.md, problem.md, promise.md, positioning.md) and what shipping version one means (success.md, risks.md). goal.md is the one outcome that makes the whole build worth doing in the first place: the change in the user's world you are chasing. success.md tells you when version one is done; goal.md tells you why version one was worth starting.

Main outcome

Is this outcome clear enough to guide every decision?

The call

Choose one outcome first. Otherwise AI generates options that pull the product in multiple directions at once.

Sharpen the main outcome with AI

This is a Shape idea, so the AI move is to Sharpen the main outcome: run your draft through the prompt below until two people would make the same decision from it. Build and Launch ideas have their own AI moves, building and running the code.

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 main outcome and keep the instruction exactly as visible here. It helps you put your 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

Ask why you are cooking this particular meal at all. "To give my parents a proper sit-down dinner on their anniversary" is a reason worth the effort, and it quietly decides the menu, the table and the timing. If the only honest answer is "we needed to eat", you would order a takeaway and save yourself the work.

Your main outcome is that reason for cooking. Name the one change in the user world you are chasing, why it matters and the sign you will know it happened. It is not the same as the dish being done, it is why the dinner was worth starting, the thing every other choice quietly serves.

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 main outcome is not a broad aspiration. It is the one result that justifies the work if it actually happens. Until you can point to one user outcome, one reason it matters and one signal that proves it happened, the work is still spread too wide. AI can help explore options, but it cannot choose what matters most.

Make the main outcome concrete

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

• Too vague: This creates more value for users of the AI search tool.
• Concrete enough to test: A content creator completes a search using their saved context and acts on at least one result in the same session, instead of leaving to search elsewhere.

The second version lets two people prioritise the same work from it.

Check the main outcome

• Pass: You can say what changes for the user, why that change matters and what signal will show it is real.
• Fail: If the outcome still sounds like value, impact or improvement without a concrete result, it is not clear enough yet.

Do not move into roadmap, feature or build work until this passes.

What you'll walk away with

You put this into practice with the prompt above. You'll come out with a main outcome clear enough that every later decision flows from it. Scope, priorities, what you cut and the prompts you write to AI all inherit that clarity.

You write the goal before you commit any scope, so every later trade-off is measured against the change you are actually trying to make in the user's world. The file is called goal.md (not outcome.md) because the runner already inserts an "Outcome" heading at the top of every framework post; one short noun keeps the two distinct. The post calls it a "main outcome" because that is the role the goal plays here: the one user-facing change that justifies the whole build.

Write it down

Your 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/shape/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: Letting multiple outcomes compete at once, which creates conflicting priorities and slows meaningful progress.
• Mitigation: Define one measurable outcome signal and defer requests that do not improve that signal.

Key takeaway

Do not move forward until you can say what changes for the user, why that change matters and what signal will show it is real.

How to document your main outcome

Write your main outcome 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.

# Main outcome

## Answer
User outcome: [what changes for the user]
Why it matters: [why that change matters]
Proof signal: [what signal will show it is real]

## 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
User outcome: My parents get a proper sit-down dinner
Why it matters: It is their anniversary and worth the effort
Proof signal: They stay at the table long after the plates are clear

## Evidence
My parents rarely get a proper sit-down meal, and last time they lingered for an hour once one was in front of them.

## Decision
Optimising for a relaxed dinner they linger over. Saying no to anything that rushes them or turns it into a show.

## Risk
I might pour effort into the food and forget the setting that makes them stay. Watch whether they relax, not just eat.

## AI instruction
The outcome that matters is my parents enjoying a proper sit-down anniversary dinner. Judge every choice by whether it helps them settle and stay at the table.

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.