Bottom-up system building for small teams

Executive overview

Standard systemising advice is built for large organisations with dedicated operations staff. Small teams follow it, produce process maps and policy binders, then change nothing.

The fix is reversing the order: start with what is already happening at the front lines, not with leadership vision. Build systems from the bottom up — tasks first, procedures last.

Why the top-down approach fails small teams

• Starts with the CEO mapping a full vision before any work is observed
• Produces process maps, policy binders, and Loom libraries that take months to create
• Outputs a shared vision but rarely changes day-to-day behaviour
• Relies on the most senior people's time; if they're busy, nothing moves
• Mistakes fiction for infrastructure — the plan rarely becomes reality

The tactical (bottom-up) approach

• Step 1: Task management — what is happening, who is doing it, when
• Step 2: Purpose and storage — why it's happening and where it lives in software
• Step 3: How — SOPs and checklists, only once high-impact tasks are identified
• Data from step 1 shows where time actually goes, so improvements target real bottlenecks
• Anyone on the team can participate; no systems expertise required

Division of labor in the new model

• Front-line team members optimise their own slice of the work
• Operations leaders focus only on bottlenecks and overdue handoffs — not every box in the chart
• Skill and attention of senior people is spent where it changes throughput, not on theorising
• Scales across technophobes and non-process people alike