Appearance
Work Map and workflows
This page is for: advisors and forward-deployed engineers, who work in the advisor dashboard.
Built
The Work Map shows how work moves through the company: which Task Cards hand work to which, where it breaks, and where it waits. It reads only the company's records. It never invents a hand-off to fill a picture.
Open Work Map in the company sidebar. It has four tabs: Process map, Work flows, Task Cards and People.
Two words to keep apart
| Word | Meaning |
|---|---|
| Task Card | One person's repeatable job: what arrives, what they do, where it leaves to. |
| Workflow | A chain of Task Cards, across people, that carries one unit of work (an order, an invoice, a supplier, a support email) from start to done. |
The rule: if the same unit of work passes through the Task Cards of 2 or more people, it is a workflow. One person's job is a Task Card, not a workflow.
Process map
The Process map is a grid. Stages run left to right, departments top to bottom, and each Task Card is a chip in its cell.
- Lenses along the top count what the map found: Breaks, Bottlenecks, Key-person risk, Automation and Missing detail. Pick one to mark those cards.
- Data formats, beside the lenses, draws every hand-off with the format each side uses and lists the format breaks under the map. See Data formats and conversions.
- Click a Task Card to see how it links. Lines show where its work arrives from and leaves to. Below the map you see How it links, The card and Findings for that card. Back to map scrolls back up. Press Esc, click empty space or select Deselect to clear it.
- With nothing picked, the section under the map is What to fix next: the findings ranked by the likely constraint first, then by how many cards wait behind it, then by how often it runs.
A hand-off shows one of three states:
| State | Meaning |
|---|---|
| Both sides agree | The sender's card names the receiver and the receiver's card names the sender |
| One side said it | Only one of the two cards names the other |
| Nobody receives it | A card sends work to a person who has no card for it. The map shows a dashed card. |
A missing "how often" or "how long" reads not said yet. Nothing is guessed.
What you can do on a finding
Each choice has Undo.
| Choice | What it does |
|---|---|
| Not a problem | Hides the finding |
| Mark as the constraint | Marks this card as the place the work is held up |
| Give it an owner | Proposes an owner. The Task Card itself does not change. |
| Not real work | Marks the card as not a real task |
| Record: [name] confirmed it | Records that a person confirmed the hand-off to you, for example on a call |
| Add to Opportunities | Puts the card on Opportunities › Your team, under "Picked on the Work Map" |
| Ask [name] | Sends a question to that person's client app (see below) |
Ask a person, and see the answer
Ask [name] sends the question to that person's client app. When it is about one Task Card, it shows on that card under From your advisor. It also shows on their Home. The chip on the map reads Sent to their app, then Answered in their app.
If the company's onboarding has not started, or does not list the person yet, the question is kept and the chip reads Saved until their onboarding starts. Start the onboarding in Discovery and it is sent.
"Mentioned you": one tap from the other side
When one person's card says they hand work to someone, and that someone's own card does not say so, the other person gets a Mentioned you check at the top of My work in their app. They answer Yes, Not me or Sort of (with a few words).
- A Yes makes the hand-off Both sides agree.
- Not me and Sort of never count as agreement. They show beside the hand-off on the map, with the person's words.
- The person can change their answer. You can take back a Yes given in the app. If either card changes hands or words, the person is asked again.
A dashed "Nobody receives it" hand-off has no one-tap check yet. Use Ask [name].
Work flows
Work flows shows one workflow at a time as swim lanes: one lane per person, the chain in order. The list on the left has three groups:
- Confirmed: workflows you confirmed.
- Suggested: chains DutyGraph found by following the hand-offs between Task Cards. The tab shows a count, for example 4 suggested.
- Not workflows: suggestions you turned down, with Hide and Bring back.
What counts as a workflow? at the top of the list gives the rule in one box.
How DutyGraph finds a suggestion
DutyGraph joins Task Cards by their recorded hand-offs. It keeps a chain only when 2 or more people do its cards. A chain that a confirmed workflow already covers is left out. Each suggestion shows:
- its first and last card, the people on it, and "Follows N hand-offs from X to Y" under How DutyGraph found it;
- the unit of work, when a word from the first card is also on 2 or more people's cards. Otherwise you pick or type one;
- how often it runs, from the first card that says so, else "not said yet";
- Where does it break?: each hand-off on the chain that does not hold.
Decide on a suggestion
The Is this a workflow? panel has four choices:
| Choice | What it does |
|---|---|
| Confirm workflow | Saves it as a workflow. It is documentation only until it has an owner. |
| Edit steps | Take a card out or put the steps back as DutyGraph found them |
| Split here | Pick the card where part 2 starts. It becomes two suggestions. |
| Not a workflow | Turn it down, with a reason: one person's job, not the same unit, already covered, or other |
Each choice has Undo. After the Undo note is gone, a workflow you confirmed from a suggestion still has Take back confirm, until it is reviewed. A confirmed workflow lets you Edit unit (or Add the unit) at any time. On a break, Ask sends the question to the person's app and Edit steps changes the chain.
DutyGraph Agent on the Work Map
The DutyGraph Agent™ beside the map sees the page as you do: every Task Card, every hand-off, the workflows, the ranked findings and the card you marked as the constraint. Its starter questions follow what you picked, for example Where is the biggest constraint?, Where does the chain break?, Who should own this? or Why did you suggest this?.
It works like an operations analyst, with the theory of constraints:
- List the candidates and tell the constraint apart from its symptoms.
- Look for a policy constraint first (a rule or an approval), then the physical one.
- Exploit it: get more from the constraint as it is.
- Subordinate: line the other work up behind it.
- Elevate: add capacity only when the first steps are done.
Each answer names Task Cards by their exact title, gives the counted evidence, ends with a Test it step, and adds what to Also check. When no times are recorded it ranks from the structure of the map and says so. It suggests workflows only from hand-off chains.
The names in its answer ring green on the map and the rest dims. Clear highlight removes the marks.
When the Agent lists questions for people, Ask [name] and Ask everyone under its answer add unsent drafts to Discovery › Asks. The row says "Waiting in Discovery › Asks. Not sent yet." Nobody gets them until you review them and press Send there. This is not the same as Ask [name] on a finding, which goes straight to the person's app.
The Agent needs the company's AI connection. Without one it says so.
Fix it: send the fix to the people involved
When an answer names a Task Card nobody owns, a Fix it box shows under it. The same choice is on the card itself (Fix this). Pick a way:
- Let the people involved decide (recommended): 2 or 3 ways to fix it go to the people on each side of the step and to whoever a way names. Each way comes from the map: the manager of the people who do the steps before it (with the person who does most of them as backup), the person who sends the work in, the person who takes it out.
- Assign an owner now: you pick the owner; they and the people on each side accept it.
- Test it first: one question to each person. Nothing on the map changes.
The fix is drafted under the map and nothing is sent until you press Send. The Task Cards it changes are numbered on the map, matching What would change (Now and Proposed). Who it goes to is picked from the map: add or remove people. How it gets locked in sets the rule: 2 agree and the decider confirms (the default), the decider decides after reading the answers, or everyone must agree. The decider is the workflow's owner, else the top of the reporting line. What they see in their app shows each person's card exactly as their app will.
In each person's app it is an alert at the top of Home and a card: they pick a way (or A different idea, or Not mine to say), say why by talking or typing, and then see what the others picked. They can change the answer until the decider picks. If nobody agrees by the date, the decider gets it anyway.
After Send the pane follows it: Sent, In their app, Answers in, Locked in, Constraint resolved. You can send it to the decider early, or lock in the decider's pick for them when they told you. Once locked in, the new owner gets New step on your Task Cards in Mentioned you. Their Accept names them on the Task Card; then the people on each side accept, which confirms both sides of each hand-off. This isn't mine sends it back to the decider with their reason. Take it back at any step removes it from their apps and undoes the owner and the confirmations it wrote.