> For the complete documentation index, see [llms.txt](https://docs.theoutcomeminds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theoutcomeminds.com/framework/editor.md). # Define the Outcome Learn how to articulate outcome and constraint for the users that anchor the map. Start with a person, not a product. The first job is to define the outcome that matters to them. ### Outcome formula Write the outcome like this: `[User] needs to achieve [Result] given [Conditions], because [Reason].` Good examples: * A first-time founder needs to validate demand in 30 days with limited cash, because building without validation risks wasting scarce resources and running out of runway. * A local merchant needs to restock faster without tying up working capital, because locked capital limits inventory turnover and directly impacts sales and cash flow. Weak examples: * Build an AI platform * Improve the product * Grow faster ### What a strong outcome includes * A clear user * A specific result * A real constraint * A reason the result matters now ### Questions to ask * Who is the user? * What triggers the need? * What counts as success? * What does failure cost them? * What happens before and after this moment? {% hint style="info" %} If the outcome cannot be measured, it is still too vague. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.theoutcomeminds.com/framework/editor.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.