> For the complete documentation index, see [llms.txt](https://book.cpj.fyi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.cpj.fyi/operating-models/introduction.md).

# Introduction

## How should we think about Organizations?

Before we get into the work of improving organizations, we should have a collective understanding of what an organization i&#x73;*.*

Here’s my definition.

> *The organization is an economic device and embodied idea for achieving a shared purpose that requires the work of many people.*

An organization’s boundaries are best defined by **purpose and participation.** While important, W-9s do not define who is in and out of the organization: shared purpose and active participation do a better job of this task. An organization is fueled by the time, attention and/or money provided by the people who perform or make use of the organization’s work. I’d argue that this even includes customers, suppliers, and stakeholders! Lastly, it is structured by the relationships between the organization and its participants, and within the participant group.

To use a framing from D’Arcy Thompson, **an organization is a diagram of the forces that surround it.**

## How should we think about Operating Models?

Summarizing Amy Kates – one of the most important thinkers in the org design world – an operating model is a **shared idea** that helps “shape human behavior at the group level.” In Kates’ world, an operating model is made up of three interlocking elements: **Ambition, Blueprint, and Integration.**

## Ambition

{% tabs %}
{% tab title="Strategic Choices" %}

{% endtab %}

{% tab title="Distinctive Capabilities" %}

{% endtab %}

{% tab title="Case for Change" %}

{% endtab %}

{% tab title="Business Configuration" %}

{% endtab %}
{% endtabs %}

## Blueprint

{% tabs %}
{% tab title="Organization Model" %}

{% endtab %}

{% tab title="Enterprise Roles" %}

{% endtab %}

{% tab title="Governance & Performance" %}

{% endtab %}

{% tab title="Work & Technology" %}

{% endtab %}
{% endtabs %}

## Integration

{% tabs %}
{% tab title="Teams & Networks" %}

{% endtab %}

{% tab title="Experiences & Processes" %}

{% endtab %}

{% tab title="Data & Tech Architecture" %}

{% endtab %}

{% tab title="Talent & Workplace" %}
&#x20;
{% endtab %}
{% endtabs %}


---

# 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://book.cpj.fyi/operating-models/introduction.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.
