How It Works
Subtract first. Control what remains.
First, remove duplicate steps and tools. Then connect what remains. Agree on what AI may do, what needs approval, and when it must stop.
Remove what obscures, then test what survives.
Simplify the work, check how the remaining steps fit together, then build and test the first useful change.
The Core Principle
Extra tools can create more exceptions and handovers to manage. Remove unnecessary steps first, then agree on permissions and checks for the work that remains.
Adding tools can also add work: more exceptions, more handovers, and more things to watch. Our method, the Subtractive Triad, starts by removing duplication and unnecessary steps. Then we connect what remains.
The Three Checks
One principle applies at three scales so the workflow becomes simpler before it becomes faster.
I look for duplicate tools, repeated steps, and data entered more than once. We map the work and remove repetition before adding automation.
Less duplication, cleaner data, lower drag.
Dieter Rams called it “less, but better.” We ask which tools and steps are useful, then remove those the team no longer needs.
A leaner stack where every component earns its keep.
Check how each remaining part serves the work as a whole. Connect the tools so people do not have to carry information between them.
A connected system where every component serves the mission.
- DRY / Implementation
- Rams / Evidence
- Heidegger / System
The Process Applied
Find the repeated work, remove unnecessary steps, agree on approvals, and build the smallest useful change.
Map the manual coverage burden
Name the handoff, owner, systems, exceptions, and current human execution or monitoring burden.
Subtract the noise
Remove duplicated work, excess tools, and disconnected records before adding automation.
Classify the decisions
Define what can auto-run, what needs approval, and what should block with a reason.
Ship the operator path
Deliver the first controlled connection, runbook, operating notes, and operator brief surface.
The method as a map
The map shows which tasks can run, which need approval, and what record is kept.
A workflow becomes trustworthy when the boundary is visible.
One owner, one workflow artifact, and one stop rule. Automation stays inside that boundary, and every run leaves something you can inspect.
1. Map Qualified lead handoff before execution. RevOps owner owns the operating path. The canvas makes the workflow, handoffs, and next decision legible before an agent or system acts. 2. CRM route and notify can run when the rule is clear. CRM route and notify coordinates with Fit and follow-up draft; the map keeps AI assistance bounded to the work it can safely support. 3. Territory or enterprise review stays with a person. Human resolves ownership conflicts, strategic accounts, and unusual requests. 4. Consent and duplicate uncertainty is the stop condition. Stop when consent, restricted domain, or duplicate confidence is unclear. 5. CRM activity receipt shows the receipt. The place an operator sees route decision, owner, draft, and blocked reason. 6. Use the map as booking context for a workflow pilot. The map has enough owner, assistive work, system behavior, and decision context for a first run.
Ready to make the workflow quieter?
Every project starts by simplifying the work. Then we build and test one task, with clear rules for when a person needs to step in.
- Owner
- Workflow owner
- Authority
- One named handoff
- Proof
- Map + subtractive delivery plan
- State
- ready