> 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/part-two-summary.md).

# Part II Summary

An effective transformation strategy must do more than articulate aspirational statements of ambition. Instead, it has to first diagnose the challenges at hand (see Part I), and then develop guiding policies that not only addresses the challenge, but also creates a source of lasting advantage.&#x20;

Armed with these six pragmatic principles, you can develop a blueprint that your organization will use to guide your transformation efforts. We hope that you’ll see your blueprint as a suggestion, rather than a fixed plan, and commit to being agile in your execution as your circumstances change. Most of all, we hope you’ll see that anticipating change and knowing you’ll adapt your planning to meet it isn’t scary, or indicative of a lack of forethought — it’s a practical judgment call based on the real conditions of the digital world.

In Part III, we’ll explain how to move beyond the planning steps we’ve provided here into action, using a four step model we call Micro-Transformation.


---

# 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:

```
GET https://tbw.rangle.io/the-better-way/02-the-better-way/part-two-summary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
