LN: Carpenter (2025) — Work the System
Bibliographic Reference
Citation: Carpenter, S. (2025). Work the system: The simple mechanics of making more and working less (5th ed.). Greenleaf Book Group. URL: https://www.workthesystem.com/the-book
Pass 1 — Bird’s Eye View (5 Cs)
| C | Assessment |
|---|---|
| Category | Practical business methodology / systems manifesto |
| Context | Written by Sam Carpenter, founder of Centratel (24/7 telephone answering service). After 15 years of 80-hour weeks and near-bankruptcy, he adopted a pure systems-thinking mindset and transformed his business into a self-managing operation in 2.5 years |
| Correctness | Practitioner case study; not peer-reviewed but backed by Carpenter’s documented business turnaround and widespread adoption by small-to-midsize business owners |
| Contributions | (1) The “systems mindset” as a fundamental perceptual shift; (2) Three-document framework (Strategic Objective, Operating Principles, Working Procedures); (3) Distinction between primary aim and strategic objective; (4) Concrete SOP documentation methodology |
| Clarity | Excellent. Narrative-driven with concrete examples; accessible to non-technical business owners. |
Relevance: ⭐⭐⭐⭐
Work the System provides the philosophical and operational foundation for the SmartPMO vision: a PM organisation that runs as a self-managed system with autonomous agents handling routine tasks and humans engaged in strategic decisions only.
Pass 2 — Content
The Systems Mindset
Carpenter’s central insight is a perceptual shift, not a technique: most business owners see their organisation as a single organism reacting to chaos. The systems thinker sees a collection of separate, independent processes — each of which can be designed, documented, and improved in isolation.
“Your business is not a single entity. It is a collection of systems, and your job is to work on those systems, not in them.”
This reframing eliminates the firefighting mentality. Problems are not crises to be endured; they are evidence that a specific system needs improvement. The owner’s job becomes designing and maintaining systems, not executing them.
The Three Primary Documents
Carpenter’s framework organises every business into three foundational documents:
| Document | Purpose | Scope |
|---|---|---|
| Strategic Objective | Defines what the business is, what it stands for, where it is going, and how it operates at the highest level | Company-wide, rarely changed |
| Operating Principles | A set of 15–30 rules that guide decision-making and behaviour across all systems | Company-wide, reviewed annually |
| Working Procedures (SOPs) | Step-by-step instructions for executing every recurring task in the business | Per-task, updated continuously |
The Strategic Objective is not a mission statement. It is a detailed, functional description of the business: what it does, who it serves, what quality standards it maintains, and how it sustains itself financially. Operating Principles are the company’s ethical and operational DNA — they resolve ambiguity without requiring management input. Working Procedures are the atomic unit of the system: if a task recurs more than once, it needs a written procedure.
Working ON vs. Working IN
Carpenter shares the same core distinction as Gerber (E-Myth): the owner must shift from executing tasks (working in) to designing and improving the systems that execute tasks (working on). The difference in outcomes is dramatic:
- Working in: Owner is the bottleneck; business cannot function without daily intervention; owner works maximum hours, business scales minimally
- Working on: Owner improves systems; staff execute documented procedures; owner’s hours decrease as business quality improves; scaling becomes mechanical
Process Documentation as Leverage
Every documented procedure is a form of leverage. A well-written SOP allows:
- Delegation: Any sufficiently trained person can execute the task to standard
- Consistency: Outcomes are repeatable regardless of who performs the task
- Improvement: Each iteration identifies where the procedure can be refined
- Onboarding: New staff can become productive faster; institutional knowledge does not leave when individuals leave
Carpenter’s documentation standard: procedures must be clear enough that a competent new hire could follow them without asking questions. Ambiguous procedures are incomplete procedures.
The Manager’s Role in a Systems Business
When working procedures are documented and trusted, the manager’s role shifts:
- Monitor systems for performance deviations
- Update procedures when deviations reveal gaps
- Hire and train staff to operate systems
- Design new systems as the business expands
This is not management-by-exception (react when things go wrong). It is management-by-design (prevent failure by designing robust systems upfront).
Applying the Systems Mindset to Personal Life
Carpenter extends the framework to personal productivity: defining a personal Strategic Objective (life goals), personal Operating Principles (values in action), and personal Working Procedures (routines for health, relationships, learning). The same logic applies: chaos is the symptom of absent or broken personal systems.
Why Most Businesses Fail at Documentation
Carpenter identifies three failure modes:
- Procrastination: Documentation is viewed as overhead, not investment. Owners defer because they are too busy executing.
- Perfectionism: Owners wait for the “perfect” procedure before writing anything. Result: nothing gets written.
- Lack of trust: Owners believe no one else can execute tasks to their standard. This becomes a self-fulfilling prophecy.
The solution is to start documenting imperfectly. A 70%-quality procedure that exists is infinitely more valuable than a 100%-quality procedure that is never written.
PUMA Integration
SmartPMO as a Systems Business
The SmartPMO vision (PUMA Stage 5) is precisely the systems business Carpenter describes: an autonomous PM operation where AI agents execute documented procedures (issue triage, effort estimation, sprint planning) while human PMs work on improving the system and handling exceptional cases.
| Carpenter’s Framework | SmartPMO Equivalent |
|---|---|
| Strategic Objective | SmartPMO Vision document |
| Operating Principles | PUMA Constitution §§ |
| Working Procedures (SOPs) | PUMA skill files + agent prompts |
| System monitoring | Automated metrics dashboard |
| Owner working on the system | PM reviewing agent performance + improving prompts |
SDD as Systematic Documentation
Spec-Driven Development (SDD) in PUMA is the engineering equivalent of Carpenter’s Working Procedures: every agent behaviour is specified before implementation, documented for reproducibility, and improved iteratively. The CLAUDE.md file is PUMA’s Operating Principles document.
Related Notes
- Smart-PMO-Vision — SmartPMO: the systems business vision for automated PM
- PN-SDD-Framework — SDD: specification as systematic documentation
- PN-PARA-GTD-Zettelkasten — GTD as a personal systems framework
- LN-Gerber-2009-EMythRevisited — complementary: the E-Myth makes the same working ON/IN distinction
- LN-Wickman-2012-Traction — EOS provides the execution framework for the systems business
- LN-Harnish-2022-ScalingUp — Scaling Up as the next layer: scaling the documented system
- SP-PUMA-Constitution — PUMA Constitution as Operating Principles