> 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-three-choose-product-teams-over-project-teams/final-thoughts.md).

# Final thoughts

At Rangle, the majority of the transformation work we do is brought to life through product teams. Through product teams, we are able to single-mindedly focus on the customer and bring [Principle One](/the-better-way/01-the-big-picture/part-one-introduction.md) (*CVA),* and [Principle Two](/the-better-way/02-the-better-way/part-two-introduction.md) (*technology as strategy)* to life.

In effect, product teams are the bridge between strategy and execution. But product teams can only be effective when they are focused on creating long term value for customers. In order to do this, they must be as unconstrained as possible with strong leaders in place — ready to unblock them, lobby on their behalf within the organization, and trust them to make the best possible decisions in support of the customer.

In [Part III](/the-better-way/03-micro-transformation/part-three-introduction.md), we’ll explore the practical application of product teams as a pragmatic way to turn the transformation vision into action, and hopefully spur your enthusiasm for starting your transformation journey by demonstrating that it is possible!


---

# 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-three-choose-product-teams-over-project-teams/final-thoughts.md?ask=<question>&goal=<endgoal>
```

`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.