Methodology
Build Less. Connect What Matters.
Most automation projects fail because they add complexity — more tools, more workflows, more moving parts. I do the opposite. Find what's redundant, strip what doesn't work, and connect what remains into a system that actually serves your business.
The Core Principle
Most automation strategies fail because they add — more tools, more workflows, more connections. The Subtractive Triad inverts this. I start by removing what doesn't belong. What remains is the architecture.
The Three Disciplines
One principle — subtractive revelation — applied at three scales.
I audit your systems for redundant tools, duplicate workflows, and repeated data entry. If three teams use three different project management tools, that's duplication. If the same customer data lives in four systems, that's duplication. I map it, measure the cost, and design the unified architecture.
Fewer systems, clearer data, lower costs.
Named for Dieter Rams — "Weniger, aber besser" (Less, but better). Every tool, every workflow, every automation must justify its existence. I challenge each component: Does it produce outcomes? Is it used? Would anyone notice if it disappeared? The tools that survive this audit are the ones worth investing in.
A leaner stack where every tool earns its place.
Named for the hermeneutic circle — the principle that every part must serve the whole, and the whole gives meaning to every part. Surviving tools must connect into a coherent system. Data flows between them. Automations bridge them. The architecture becomes a living whole, not a collection of islands.
A connected system where every component serves the mission.
The Process Applied
How the Triad maps to an engagement — eight weeks from audit to architecture.
DRY Audit
Map all systems, identify duplication, measure waste.
Rams Review
Challenge each component, score value vs. cost.
Heidegger Design
Reconnect surviving systems into coherent architecture.
Blueprint Delivery
Complete architecture + implementation roadmap.
Why Three Levels
The triad is coherent because it's one principle — subtractive revelation — applied at three scales.
Most automation reviews stop at Level 1: finding duplicates. That's useful, but incomplete. Deduplication alone leaves you with a tighter stack that still contains tools nobody uses and systems that don't talk to each other.
We go deeper. Removing excess (Level 2) strips the stack to only what produces outcomes. Reconnecting what remains (Level 3) transforms isolated tools into a system that serves the whole.
This is what produces architectures that last — not because they're complex, but because everything that doesn't belong has been removed.
The Three-Tier Framework
Every part of your system does one of three things. Understanding which is the key to building automation that works.
Database
What existsThe foundation — where your data lives, how it's structured, and whether the right information is available to the right systems.
Automation
What happensThe engine — how systems connect, how data moves, and how actions get triggered without manual intervention.
Judgment
What should happenThe intelligence — where human insight meets automated execution. Knowing when to act, what to escalate, and which decisions require a person.
Every component in your automation stack maps to one of these tiers. When tiers are misaligned — when automation makes decisions that should be judgment, or when records aren't available to the systems that need them — the architecture fails. The Three-Tier Framework reveals these misalignments before they become expensive.
Ready to simplify?
Every engagement starts with this methodology. I look at your tools, find what doesn't belong, and build what matters.