12 Day Officers · 除 (Remove)
除 — Remove Day: Cleanups, Cuts, Strategic Exits
Use 除 (Remove) to clear what drags: costs, clutter, stale ties, bad code, and habits. Precision pruning — not demolition.
Clarity
What “Remove” actually favors
●Prune
Cut costs, scope creep, unused seats, zombie features, redundant vendors.
●Clean
Archive dead leads, close stale tickets, delete legacy branches, tidy repos and data.
●Detox
Remove time-wasters and habits; replace with neutral routines. Avoid fresh launches.
Fast decisions
Do / Avoid — 30-second cheat sheet
| Do on 除 | Why | Avoid on 除 | Better Day |
|---|---|---|---|
| Cancel unused tools, renegotiate seats | Instant margin from waste removal | Public launches / PR pushes | 开 / 成 |
| Archive dead leads / close tickets | Declutters pipeline for real wins | Final contract locking | 定 (Settle) |
| Delete legacy code / stale branches | Reduces risk, speeds teams | Hard terminations or teardowns | 破 (Break) |
| Unsubscribe / downgrade tiers | Stop small leaks fast | Grand openings, ceremonies | 开 (Open) |
Execution
Business playbooks (surgical, high-leverage)
1) Cost pruning sprint
- Export SaaS + seats. Cut duplicates, downgrade tiers, remove ex-users.
- Freeze “nice to have” pilots; review on 定 to re-approve.
2) Backlog hygiene
- Close tickets >90 days inactive. Reopen only with new evidence.
- Kill zombie features; remove flags that diverge from current strategy.
3) Quiet exit (script)
We’re simplifying our stack this quarter. Effective {{date}}, we’ll discontinue {{service/feature}}. No further action needed on your side; the handover doc is attached. Thanks for the run.
4) Data cleanup
- Delete or quarantine low-quality segments; fix obvious duplicates.
- Remove “vanity metrics” dashboards; keep decision-critical ones.
Precision
Relationship plays (low friction, high signal)
1) End a stale loop (script)
I’m cutting the back-and-forth on {{topic}}. Let’s drop it and keep momentum on {{X}}. If it matters later, we revisit on a better day.
2) Boundary reset (clean)
I’m removing {{specific behavior/commitment}} from my plate. I’ll keep {{the essential}}, and we’ll review new asks on {{Settle day}}.
3) Habit detox
- Pick one removal: late-night scrolling, junk snacks, reactive messaging.
- Replace with a neutral routine — don’t over-optimize today.
Sequencing
Timing tactics (stacking & sequences)
- Remove → Level: cut first, normalize terms on 平.
- Remove → Settle: prune options, then finalize on 定.
- Remove → Open / Success: declutter, then announce or ship clean.
- Don’t misuse 除: for scorched-earth moves, wait for 破.
Patterns
Real examples
- Finance: cancel 3 unused SaaS tools; annualize savings and report.
- Product: remove a confusing onboarding step; lower friction before 开.
- Personal: unsubscribe from five email lists; delete one social app from phone.
Answers
Quick FAQ
Is Remove the same as Break?
除 is pruning and cleaning; 破 is destruction and teardown. Use the right blade.
Can I launch on Remove?
Avoid launches. Declutter first; push launches on 开 or 成.
What if I must end a vendor today?
Keep it quiet and procedural. Save public/structural teardown for 破.
