> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kowalah.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Navigating the map

> Move around your operating model by altitude: land in your unit, switch between the map and cockpit views, and zoom from company to step.

The operating model is one dataset seen at four heights. Rather than a single dashboard everyone shares, you land where you sit in the company and move up or down from there.

## You land at your altitude

When you open the operating model, you arrive at the level that matches your **position**:

* **C-suite** land at the company view, the whole tree rolled up.
* **Senior leaders and managers** land in the unit they lead, or their home unit.
* **Individual contributors** land in their home unit and the processes they are part of.

From wherever you land, you can move up to see the wider company or down into a specific process and its steps. The whole map is readable by everyone in your organization. What differs by altitude is where you *start* and what you *own*.

<Note>
  Your position and home unit are set by your organization admin. If you land somewhere that does not match your role, ask your admin to update your position. See [operating model setup](/platform/operating-model/setup).
</Note>

## Zooming through the company

Navigation works like zooming a map. Each level shows a different kind of object, not just a smaller version of the same thing:

<Steps>
  <Step title="Company">
    The whole organization as a tree of units, coloured by AI coverage so you can see at a glance where AI has landed and where it has not.
  </Step>

  <Step title="Unit">
    A single division, function, region, or site: its child units and the processes owned or run there.
  </Step>

  <Step title="Process">
    One process as a sequence of coarse steps, each with its disposition, owner, and platform.
  </Step>

  <Step title="Step">
    The detail of a single step: what it does, how it is done today, where it is heading, and what implements it.
  </Step>
</Steps>

A breadcrumb trail acts as your altimeter, so you always know how high you are and can jump back up in one click.

## Two views of a unit

At the unit level you can switch between two complementary views.

<Tabs>
  <Tab title="Map">
    A visual layout of the unit. At the company level this is a **heat tree**, colouring units by AI coverage so the whole business reads as a heat map. Inside a division or team it becomes a **roads** view that shows how the unit's processes connect. Use the map to orient and to spot where AI is thin. A full-screen mode gives you the map on its own for review sessions.
  </Tab>

  <Tab title="Cockpit">
    A dense readout of the same unit: its AI-coverage strip, the processes it owns with their KPIs and linked initiatives, its child units, the redesign-priority backlog, and a roll-up of opportunities raised in the unit. Use the cockpit to work: it is the highest-leverage screen for a manager or leader.
  </Tab>
</Tabs>

## Reading coverage colour

Across the map, colour is AI coverage. Cooler, greyer regions have more human steps and less AI. Warmer regions have more of their work AI-assisted, automated, or autonomous.

Grey, unmapped regions are not a mistake. They show parts of your company the operating model has not reached yet, which is exactly where there is room to grow. As more of your business is mapped, those regions fill in.

<Tip>
  Coverage tells you *where* AI is, not whether it is working. To see whether a redesign is paying off, open a process and look at its KPIs. See [processes and steps](/platform/operating-model/processes-and-steps).
</Tip>

## What's next

<CardGroup cols={2}>
  <Card title="Processes and steps" icon="workflow" href="/platform/operating-model/processes-and-steps">
    Open a process and read its steps and dispositions
  </Card>

  <Card title="Owning and improving a process" icon="pencil" href="/platform/operating-model/owning-and-improving">
    Make changes to the processes you own
  </Card>
</CardGroup>