---
url: /handbook/discovery/work-map.md
description: >-
  How the Work Map shows the flow of work, who owns and does each Task Card, and
  where the gaps are.
---

# Work Map

The **Work Map** shows how work moves through the business: the stages, the Task Cards in each stage, the handoffs between departments, and who owns and does each piece. It does not show who reports to whom. Use it to see what is confirmed, what is a guess, and what to ask next.

Open **Work Map** in the company sidebar.

## How it is built

The Work Map reads the [Company Repo](company-repo.md). It does not keep its own data. Each time the Repo compiles, DutyGraph builds one projection of the work into the generated file `.dutygraph/work-map.json`. Every tab reads that file, so the Work Map and the Repo always show the same state.

The map never invents a hand-off, a time or an owner to fill a picture. A Task Card edit or a confirmed workflow writes records, and the next compile shows the change. Your choices on the map (Not a problem, Mark as the constraint, Not a workflow and the like) are saved with the company and each has Undo.

## The tabs

| Tab | Question it answers | What it shows |
| --- | --- | --- |
| **Process map** | Where does work move, break and wait? | A grid: stages as columns, departments as rows, Task Cards in each cell, with lenses and **What to fix next** |
| **Work flows** | Which chains carry one unit of work? | Each workflow as swim lanes, plus the workflows DutyGraph suggests |
| **Task Cards** | How is each task done? | The Task Card board, with filters and the Repo state of each card |
| **People** | Who holds which work? | People by stage, or the reporting lines |

RACI is no longer a Work Map tab. It is one of the Strategy frameworks.

### Process map

* The **lens bar** counts what the map found: **Breaks**, **Bottlenecks**, **Key-person risk**, **Automation** and **Missing detail**.
* Click a Task Card to see how it links: lines to where its work **arrives from** and **leaves to**, then **How it links**, **The card** and **Findings** below the map. **Back to map**, Esc or **Deselect** returns.
* With nothing picked, **What to fix next** ranks the findings: the possible constraint first, then the cards waiting behind it, then how often it runs.

A hand-off is **Both sides agree** when each card names the other, **One side said it** when only one does, and **Nobody receives it** when a card sends work to a person with no card for it (a dashed card). A value nobody gave reads "not said yet". Hours a week come from the person's own answer and are labelled reported.

On a finding: **Not a problem**, **Mark as the constraint**, **Give it an owner** (a proposal only), **Not real work**, **Record: \<name> confirmed it**, **Add to Opportunities** and **Ask \<name>**. Each has Undo.

**Ask \<name>** sends the question to that person's client app. A question about one Task Card shows on that card under **From your advisor**. Before the person's onboarding starts, it is saved and sent when it starts.

### Mentioned you

When one person's card names another person and that person's own card does not say so, the second person gets a **Mentioned you** check in their app: **Yes**, **Not me** or **Sort of** with a note. A Yes makes the hand-off **Both sides agree**. Not me and Sort of never count as agreement; they show beside the hand-off with the person's words. The person can change the answer, and the advisor can undo a Yes. A card that changes hands or words is asked again.

### Work flows

A **workflow** is a chain of Task Cards, across people, that carries one **unit of work** (an order, an invoice, a supplier) from start to done. If the same unit passes through the Task Cards of 2 or more people, it is a workflow. One person's job is a Task Card.

DutyGraph suggests workflows by following the recorded hand-offs between Task Cards. It keeps a chain only when 2 or more people do its cards and leaves out a chain that a confirmed workflow covers. Each suggestion shows how it was found, the unit of work when the cards share a word for it, how often it runs when a card says so, and where the chain breaks.

The advisor decides: **Confirm workflow**, **Edit steps**, **Split here** or **Not a workflow** (with a reason). A confirmed workflow is documentation only until it has an owner. The Company Repo writes its unit of work in the workflow's file.

### People

* **By stage** (the default) is a matrix of people and stages. A filled dot means the person **owns** work in that stage. An open dot means the person **does** the work of a Task Card there.
* **Reporting lines** shows the reporting chart from the Repo. It is the only reporting chart in DutyGraph.

### DutyGraph Agent on the Work Map

DutyGraph Agent beside the map gets a digest of the page: the Task Cards, hand-offs, workflows, ranked findings and the marked constraint. It works as an operations analyst with the theory of constraints (find the constraint and tell it apart from its symptoms, check policy constraints first, then exploit, subordinate and elevate). Each answer names cards by exact title, cites counted evidence and ends with a **Test it** step. The cards it names are marked on the map. It needs an approved AI connection.

## Owners, performers and AI modes

Each Task Card names two people:

* the **owner**: the person accountable for the work;
* the **performer**: the person who does it today.

Each Task Card also has an AI mode, from "People only" to "AI acts within set limits", or "AI not allowed". See [Task Cards](task-cards.md) for the full list. Every mode other than "People only" is a **proposed** mode. It is not an approved agent. The **Automation** lens marks the Task Cards with a proposed mode.

DutyGraph does not run agents. A proposed mode feeds [Opportunities](../opportunities/opportunities.md). An agent needs the [approval chain](../governance/approval-chain.md) before it gets any access.

::: info
**Status.** **Built:** the Process map, Work flows, Task Cards and People tabs, read from the Repo's Work Map projection; the 5 lenses and **What to fix next**; the decisions on a finding with Undo; **Ask \<name>** to the person's client app and the question on their Task Card; the **Mentioned you** one-tap check; suggested workflows with Confirm, Edit steps, Split here and Not a workflow, and the unit of work on a workflow; DutyGraph Agent's page digest and constraint method (needs an approved AI connection). **Simulated:** the Cobalt Industrial Supply (fictional sample) cards, stages and 2 workflows are fictional. **Planned:** a one-tap check for a hand-off nobody receives, and any agent that runs the work.
:::
