Name every system and team, give each an owner, and say which system is right when they disagree.
3c · map the teams and systems
Assign ownership across teams and systems
Start with the example, then try it yourself. The last case is optional practice.
Meet Samir.
Samir follows what happens after a decision. He helps name the next owner, check permission to act, and confirm that work reached its destination.
Samir · Workflow operator
The case
A dashboard with no memory
Different systems own different facts. Name each source of truth and what another system may only observe.
Every panel
A live call to somebody else’s API
When the provider is slow
The page is slow
When the provider is down
The page is blank
"What changed since yesterday?"
Unanswerable, because nothing was recorded
What is missing
A local copy of what the other system thinks is true
Your task
Choose an owner for each system. Then choose which system has authority over each fact.
Need a little guidance?
You’re done when: Every important fact has one authoritative owner and every system has a bounded job.
Cross-system reliability starts with knowing who owns what.
Need a reminder? Reopen the worked example
Watch one example first
The calendar owns booking evidence; the CRM owns account assignments. An integration copies selected facts without becoming the authority for every domain.
Why this follows from the evidence
Source of truth is scoped to a fact. When systems disagree, identify the fact’s authority and integration owner before choosing a repair.
GTM Lab
Saved locally
Cross-System Operating Plan · 0 of 8 sections started
Saved locally to your browser.
Case evidence
A dashboard with no memory
Every panel
A live call to somebody else’s API
When the provider is slow
The page is slow
When the provider is down
The page is blank
"What changed since yesterday?"
Unanswerable, because nothing was recorded
What is missing
A local copy of what the other system thinks is true
Four systems carry this workflow. Give each an owner, then answer the harder question: which one is right when they disagree?
Map each fact to its source system and owner
These systems contain overlapping information. Assign an accountable role to each system, then give each fact one authority. A system may be managed for one purpose and only observed for another.
Systems needing an operating owner
Drag a card into a bucket, or tap a card and then tap a bucket.
Facts needing one authority
Drag a card into a bucket, or tap a card and then tap a bucket.
Compare two different facts: the CRM decides whether someone should enter a cadence; the sequencing tool records how far they have progressed after enrollment.
Restoring this case draft…
Optional: compare the original decision choices
The case workbench above records completion. These choices are optional review and do not create the activity receipt on their own.
Work the case · 0 of 2 sections drafted
Draw the map
Compare these alternatives one section at a time. Check a choice to see its consequence; the draft summary below keeps the proposed changes together.
Step 1 of 2
How should ownership be assigned across the four systems?
This is a proposed draft until the chapter check runs. Selecting a choice alone does not complete the chapter.
