Interactive guide
Carry the Work Across Teams and Tools
Cross-system work adds questions about identity, authority, and delivery that a single-screen view can hide. This guide makes those questions explicit.
A connected system may use different definitions, so a rule that crosses the boundary needs an explicit enforcement point. When people or processes can change either side independently, values can drift; a workflow should make those differences visible before it proposes a repair. A change can also affect remote state that is not obvious from the current screen. You will build a Cross-System Workflow Map and Operating Plan. The lab saves your progress in this browser.
Keep the handoff intact with Samir.
Trace a request across teams and systems. Investigate retries, disagreements, and missing acknowledgments while preserving the operation’s identity and its next owner.
Start with a broken answer
Map the Teams and Systems
Chapter 1 of 8 · 14 min
The learning path
The order here is not a preference. You cannot write a handoff contract until you know which system owns the fact being handed over, and you cannot repair a disagreement until you can see one. Every chapter assumes the one before it is already done.
The map and the machinery
- 01Map the Teams and SystemsName every system and team, give each an owner, and say which system is right when they disagree.~14 min · exercise
- 02Define What Each Handoff CarriesWrite the six things every boundary crossing carries, and derive routing rather than maintaining it.~16 min · exercise
- 03Read Job State, Freshness, and Last SuccessSeparate the current run from the age of its output, and keep the last successful result inspectable.~14 min · exercise
- 04Choose a Retry or Repair PathMatch retries, repair and escalation to the failure cause and the named owner.~16 min · exercise
Staying correct, and closing the loop
- 05Reconcile Systems That DisagreeDesign a repair loop you can preview before it runs and measure after.~18 min · exercise
- 06Notify and Escalate to the Right OwnerGive each alert a named owner and next action; monitor the signals that reveal whether the escalation path works.~14 min · exercise
- 07Confirm the Business OutcomeClose the loop back to the workflow specification, and learn the build order.~16 min · exercise
- 08Capstone: Follow One Record End to EndTrace one record across every boundary as the person on call, validate the plan, and approve version 1.0.~20 min · exercise