> 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/03-micro-transformation/step-one-design-effective-cross-functional-teams/why-it-works.md). # Why it works Empowered cross-functional teams aligned by shared principles outcomes and measures of success are the best way to navigate uncertain and unpredictable environments. Through shared outcomes, cross-functional teams and pods are better able to collaborate with a common purpose and mission, which enables them to continuously identify, prioritize, and break down risky assumptions, and then use their collective capabilities to “swarm” both opportunities and challenges accordingly. The success of this approach is predicated on a culture change and mindset shift: One where everyone in the organization believes that those closest to the work and to the customer — aka, the product teams or the pods — are best suited to make decisions for the product and on behalf of the customers’ experience. In traditional command and control environments, the executive leadership are thought to “know best”. Part of shifting to the pod approach will be to ensure the most senior stakeholders in the process can relinquish (at least some) control to the collective wisdom of the pods. --- # 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/03-micro-transformation/step-one-design-effective-cross-functional-teams/why-it-works.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.