> For the complete documentation index, see [llms.txt](https://tbw.rangle.io/the-better-way/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tbw.rangle.io/the-better-way/02-the-better-way/principle-four-divide-and-conquer/what-good-looks-like.md). # What good looks like * Defensive, disruptive and innovation have the right talent composition * The organizational portfolio can be easily visualized as a [Lean Value Tree](/the-better-way/glossary.md) * The relationship between initiatives in the LVT can be easily understood * Outcomes are customer-focused missions to achieve a clear business result * Bets are short-term cross-functional initiatives with measures of success designed to “move the needle” on their parent outcomes * A “hypothesis” is a rapid experiment designed to test the riskiest assumptions related to a bet in order to determine its viability * Outcomes and bets are incrementally funded based on the success of each hypothesis experiments --- # 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://tbw.rangle.io/the-better-way/02-the-better-way/principle-four-divide-and-conquer/what-good-looks-like.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.