Disconnected workflows
What are Disconnected workflows?
A recurring job spans tools, systems or people that fail to carry the necessary information and context across their boundaries.
How Disconnected workflows work
Manual transfers, duplicated records and missing context consume time or cause errors. The condition supports several possible product responses; it does not prescribe one architecture.
Case studies tagged with Disconnected workflows
Each link opens the passage tagged with this concept.
- Adobe
- athenahealth
- Blue Apron
- Braze
- Brex
- CareBridge
- Compass
- Confluent
- Cursor
- Datadog
- Datavant
- Dayforce
- Doximity
- Figma
- Flatiron Health
- GitLab
- HipChat
- Inovalon
- InVision
- Iterable
- Jobber
- Klaviyo
- LiveRamp
- Mastercard
- Navan
- New Relic
- PagerDuty
- Palantir
- Paylocity
- Practice Fusion
- Procore Technologies
- Revel Systems
- Sabre
- Samsara
- ServiceTitan
- Slack
- Sprinklr
- Sprout Social
- Tempus
- Toast
- Uber
- Visa
- Weave Communications
- Xero
The question to ask of a company
Which handoff loses context or requires reconciliation, and what does that cost the customer?
Examples
- Figma: separate files and feedback channels complicated design review.
- Weave: patient records did not supply context during ordinary telephone calls.
Who names it
| Author | What they call it / where it appears |
|---|---|
| Strategy Canon + | Editorial pattern label derived from the company entry studies |