Systems, Not Processes
Create repeatable playbooks while preserving skilled human judgment
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 98%
Systems, Not Processes distinguishes a flexible operating playbook from a rigid sequence of prescribed actions. A system names the desired result, essential roles, handoffs, constraints, and feedback loops so work can be repeated reliably. It does not dictate every example, format, or judgment call. Skilled contributors remain free to adapt their method to context while staying aligned with the shared outcome. The hosts illustrate the mechanism through HubSpot's SEO engine: analysts performed keyword research, writers transformed it into content, and technical requirements ensured discoverability, but writers could reframe dull topics and analysts could challenge questionable findings. When leaders feel compelled to prescribe every move, the model prompts them to examine whether the actual problem is unclear accountability, inadequate capability, or insufficient trust.
Origin
Extracted from Marketing Against The Grain through Kipp Bodnar's comparison of HubSpot's organic-search system with rigid organizational processes.
Core principles
- 01Define repeatable outcomes without prescribing every action
- 02Give teams a shared understanding of responsibilities and handoffs
- 03Preserve autonomy for context-sensitive judgment
- 04Use systems to focus capable people rather than control them
- 05Diagnose excessive rigidity as a possible talent or leadership problem
How to run it
- 1
Define the outcome
State the repeatable result the system must create and how success will be recognized. Keep the outcome separate from a preferred method.
Pro tip Use a measurable result that all participating roles can understand.
Watch out A vague outcome invites inconsistent interpretations.
- 2
Map essential contributions
Identify the roles, inputs, outputs, and handoffs required to produce the result. Assign clear accountability without scripting every activity.
Pro tip Design around responsibilities rather than job titles.
Watch out Too many handoffs can turn the system into bureaucracy.
- 3
Set necessary guardrails
Specify technical, legal, brand, or quality constraints that contributors cannot ignore. Explain why each guardrail matters.
Pro tip Keep only constraints that protect the outcome or prevent material harm.
Watch out Preferences disguised as guardrails recreate a rigid process.
- 4
Preserve judgment zones
Explicitly identify where contributors may challenge inputs, change framing, choose examples, or adapt execution. Match discretion to demonstrated skill.
Pro tip Give examples of acceptable variation without making them mandatory templates.
Watch out Autonomy without clear accountability can produce drift.
- 5
Install feedback loops
Measure results and let each role flag weak assumptions or broken handoffs. Update the shared playbook when recurring evidence supports a change.
Pro tip Review the system with practitioners rather than only with managers.
Watch out Do not respond to every isolated error by adding another rule.
- 6
Diagnose control pressure
When leaders demand greater rigidity, determine whether the root cause is unclear expectations, weak talent, poor execution, or lack of trust. Fix that cause instead of automatically expanding the procedure.
Pro tip Ask what decision the leader believes the team cannot make safely.
Watch out Micromanagement can conceal a leadership problem while reducing ownership.
In the wild
HubSpot's SEO team researched keywords and handed findings to a content team. Writers received topic direction and basic technical formatting requirements so Google could discover and crawl the work. Within those constraints, analysts could challenge questionable keyword choices and writers could reframe boring topics or choose stronger examples.
→ The organization repeatedly produced search-aligned content without eliminating the judgment that made each piece useful.
Common mistakes
Prescribing the entire method
Mandating exact article structures, examples, or other creative decisions removes the flexibility that lets skilled contributors improve the work.
Adding rules after every error
Accumulating controls around isolated mistakes gradually converts a useful system into bureaucracy.
Using process to avoid talent decisions
Leaders sometimes impose rigid procedures because addressing capability, accountability, or trust would require a harder decision.
Is it for you?
Best for
Skilled teams that need consistent outcomes across recurring work while retaining flexibility and initiative.
Not ideal for
Safety-critical or legally regulated procedures where exact compliance must override individual discretion.
From the transcript
“we build systems we don't build processes”
“we had a system that said hey this is how this should work to achieve this result in a repeatable way so we have a…”
“if you have rigid processes they will kill you if you have systems that provide Clarity and rigor to grind out things that you know…”
From the episode
6 Marketing Mistakes Holding You Back From 10Xing Your Business (#164)