How do you build systems that run without you?
- Run a bottleneck audit first: tasks like email triage (4 hrs/week), drafting routine replies (2.5 hrs/week), and following up on commitments (1.5 hrs/week) don't require you and are systemable.
- Follow 4 principles: document anything you do more than twice, separate the trigger from the action, design for the 80% and handle the 20% manually, and make the default action the right one.
- Build 5 systems in order: email processing (saves 4-6 hrs/week, 1 hour to set up), then client management, task capture, meetings, and shutdown.
- Build one system at a time over 6-8 weeks rather than all at once; each takes 5 minutes to 1 hour to set up before you move to the next.
The work itself stays variable. It's the repeatable infrastructure around it, like email processing and meeting prep, that gets systematized.
The Bottleneck Audit: What Actually Needs You?
List a typical week's tasks and ask one question of each: does this actually require me? The hours that don't are your system-building territory.
| Task | Frequency | Hours/week | Requires you? | Systemable? |
|---|---|---|---|---|
| Email triage (reading, sorting, deciding) | Daily | 4 | No | Yes |
| Drafting replies to routine emails | Daily | 2.5 | No | Yes |
| Following up on commitments | Daily | 1.5 | No | Yes |
| Extracting tasks from emails | Daily | 1 | No | Yes |
| Scheduling meetings | Daily | 1 | No | Yes |
| Pre-meeting research and prep | 3-4x/week | 1.5 | No | Yes |
| Client strategy and creative work | Daily | 8 | Yes | No |
| Relationship-dependent conversations | Daily | 5 | Yes | No |
| High-stakes decisions | 2-3x/week | 3 | Yes | No |
The 4 Principles of Systems That Last
Most systems die within a month because they depend on memory or willpower. These four principles are what separate systems that stick from systems that quietly stop happening.
If you do it more than twice, write it down
Every process you repeat should have a documented sequence. Not a 20-page manual: a checklist. "When X happens, do Y." This lets your future self (or a tool, or a person) repeat it without your brain.
Example: New client onboarding: (1) Send welcome email (template), (2) Set up project folder, (3) Schedule kick-off call, (4) Send intake questionnaire (template), (5) Add to Monday check-in list.
Separate the trigger from the action
Most systems fail because the trigger is "when I remember." Instead, build explicit triggers: time-based (every Friday at 3), event-based (when a project completes), or threshold-based (when inbox hits 50).
Example: Instead of "follow up with quiet clients," set a trigger: "Every Monday at 10 AM, check the client dashboard. Any client with 5+ days no contact gets a check-in email."
Design for the 80%, handle the 20% manually
Don't try to systematize everything. Build systems for the repetitive 80%. Handle the creative, judgment-heavy 20% yourself. Trying to systematize edge cases makes the whole system fragile.
Example: System handles: routine email replies, task extraction, follow-up tracking. You handle: difficult conversations, creative proposals, relationship decisions.
Make the default action the right action
If your system requires willpower to follow, it will fail. Design defaults that work without motivation. Morning email blocked by default. Calendar buffers added automatically. Follow-ups tracked without manual entry.
Example: Default: email checked at 10:30/2:30/4:30 only. Default: 15-min buffer between meetings. Default: all commitments in a tracked system. Override when necessary, not the other way around.
5 Systems to Build (In Order)
Build these one at a time, in this order. Each lists its components, what it saves, and how long setup takes; the first one alone pays for the rest.
Email Processing System
- Triage rules (who/what gets priority)
- Response templates for top 10 email types
- Follow-up tracking for every commitment
- Batch schedule (3x/day at set times)
Client Management System
- Status dashboard (1 line per client)
- Monday scan ritual
- Proactive check-in triggers (5+ days = outreach)
- End-of-interaction notes (30 seconds each)
Task Capture System
- Single inbox for all inputs (email, Slack, phone, meetings)
- Daily processing (inbox to task list or archive)
- Weekly review to prune and prioritize
- "Top 3" nightly planning
Meeting System
- Scheduling rules (no mornings, 25-min default)
- Pre-meeting prep template (5 questions)
- Post-meeting notes template (decisions + action items)
- Recurring meeting audit (monthly)
Shutdown System
- 15-minute end-of-day ritual
- Brain dump → Top 3 → inbox process → close everything
- "Shutdown complete" trigger phrase
- No email after shutdown
