PRODUCTIVITYDays to result

Capture Systems (Not Create Systems)

Record your existing processes as you do them instead of writing manuals from scratch

Problem it solves

low productivity

Best for

Business owners who know they need systems but have been paralyzed by the perceived effort of creating them, anyone who has tried and failed to write traditional SOPs, companies that need to transfer knowledge from one person to another quickly

Not ideal for

Businesses in heavily regulated industries where formal written documentation is legally required, organizations that already have effective SOP processes in place

Overview

Why this framework exists

The Capture Systems framework flips the traditional approach to documentation on its head. Instead of painstakingly writing step-by-step Standard Operating Procedures (SOPs) that take forever to create, become outdated immediately, and are rarely followed, you simply record yourself doing the work using screen recordings, smartphone videos, and voice memos.

The key insight is that you already have every system your business needs; they are just trapped inside your head and the heads of your employees. The goal is not to create systems from scratch but to capture what already exists. As you perform a task, you narrate what you are doing and record it. The video is stored in a shared directory organized by ACDC categories (Attract, Convert, Deliver, Collect) and becomes an instant training resource.

When the process changes (as it inevitably will), the person currently doing the task records a new video. This makes the person who creates the training video both the teacher and the best student, reinforcing their own knowledge while creating transferable documentation. The result is a living library of systems that stays current because the people doing the work maintain the recordings.

Core principles

5 total
  1. You already have every system your business needs; they just need to be captured, not created
  2. The best way to document a process is to record it while you are doing it
  3. The person who makes the training video is the best student because teaching reinforces learning
  4. Traditional written SOPs are almost always outdated by the time they are complete
  5. Organize all captured systems using the ACDC directory structure: Attract, Convert, Deliver, Collect

Steps

4 steps
  1. Set up the ACDC directory structure
    Create a shared cloud drive accessible to your entire team. Create a top-level SYSTEMS folder with four sub-folders: ATTRACT (marketing activities), CONVERT (sales activities), DELIVER (operations and fulfillment), and COLLECT (accounting and cash management). Add sub-directories as needed for specific processes.
  2. Identify the first process to capture
    Start with something small and repeatable that you want off your plate permanently. Good candidates include invoicing, shipping orders, posting to social media, responding to common customer inquiries, or any task that drains your time from the QBR.
  3. Record yourself doing the task
    For computer-based work, use screen recording software and narrate as you go. For physical tasks, have someone hold a smartphone and film you. For communication tasks, use a voice recorder. Do not try to make it perfect; just do the work as you normally would while explaining what you are doing and why.
  4. Delegate and iterate
    Store the recording in the appropriate ACDC folder and assign the task to the new person. They watch the video and perform the task. When they encounter gaps or questions, they record the updated, improved version. The system evolves with each iteration, always maintained by the person actually doing the work.

Checklist

Saved in your browser

Examples

1 cases
Michalowicz's book shipping process

After spending four hours writing a 15-step SOP for shipping books that immediately failed due to missed variables and interface changes, Michalowicz switched to the capture method. He used screen recording software to capture the order processing on his PC and filmed himself packing an order with his iPhone, narrating the details as he went. The whole capture took only as long as actually doing the task.

OutcomeHe never shipped a book again. When the next person took over, they watched the videos and performed the task. When Amazon changed its shipping process, whoever was currently doing the work recorded a new video. The system became self-maintaining and permanently removed the task from Michalowicz's plate.

Common mistakes

2 traps
Trying to make the recording perfect before delegating
Perfectionism with documentation is just another form of procrastination. The initial recording will have gaps and missing steps. That is expected and fine. Delegate the task with the imperfect recording and let the new person improve it. Waiting for perfection means you will never delegate.
Writing detailed manuals instead of recording videos
Written step-by-step manuals are painstakingly slow to create, miss important nuances that video captures automatically, and become outdated almost immediately when software interfaces or processes change. Recording captures far more information in far less time.

Origin story

How this framework came to be

Michalowicz spent years trying and failing to create traditional SOPs for his business. He wrote a 15-step procedure for shipping used books that took four hours to create, only to have it fail immediately when his intern encountered variables he had not anticipated. Then the US Postal Service and Amazon both changed their interfaces, rendering all his screenshots and steps obsolete. After this repeated cycle of failure with written SOPs, he realized the solution was to capture processes by recording them as they were being performed, which both got the work done and created the training simultaneously.

Source

Traced to primary
Source · BOOK
Clockwork
Mike Michalowicz · 2018
Open source →

Related frameworks

Browse all Productivity →