Document 03 of 10

Task Execution

Four tools. One system. This is how work gets done.

Most remote hires are shown a task once, left to figure it out, and judged on an output nobody defined clearly. When the work is wrong the manager blames the hire. When the hire runs out of work they go quiet. Neither problem is the hire's fault. Both are systems failures.

This document gives you four tools that work together as a single execution system. Every task your hire touches from Day One onward runs through it. Learn it once. Apply it to everything.

Use this

For every task you assign

Applies to

All roles and levels

Owner

Assigned Manager

Next doc

Day One

Section 00

How Training Usually Fails

There is a pattern in almost every remote hire that fails. It is not laziness. It is not incompetence. It is the absence of a system.

The hire is shown a task once. The manager shares their screen, walks through it quickly, and moves on. The hire attempts it alone and makes mistakes nobody anticipated. The manager corrects them verbally. The hire tries again. The mistakes change but do not disappear. After a few weeks the manager is frustrated, the hire is uncertain, and neither knows exactly where the standard is or who is responsible for the gap.

Then the assigned work runs dry. The hire has no task. They do not want to bother the manager. They sit idle. The manager cannot see it happening because the hire is thousands of miles away. Idle time compounds. Momentum disappears. Both problems have the same root cause: no system for how work gets transferred, what the quality standard looks like, or what the hire does when work runs out. This document is that system.

If the worker hasn't learned, the instructor hasn't taught.

US War Manpower Commission, Training Within Industry, 1941

Section 01

The Five-Step Training Method

This method applies to every task you introduce, not most tasks, every task. Simple tasks trained incorrectly become compounding errors. It takes longer the first time you use it and saves significant time every week after.

Where this comes from

The five-step method builds on Training Within Industry (TWI), the instructional program created by the US War Manpower Commission between 1940 and 1945 to train millions of unskilled workers to do skilled jobs correctly, quickly, and consistently. Its four steps, Prepare, Present, Try Out, Follow Up, were simple enough to teach any supervisor in hours and precise enough to produce consistent output across thousands of factories.

After the war TWI was taken to Japan and became the backbone of Toyota's training, where its Job Instruction method is still used on the factory floor today. It is widely regarded as a forerunner of lean manufacturing. McDonald's is the archetype of the same idea at global scale: standardized, demonstrate-then-practice training that produces the same result regardless of who is behind the counter.

For remote teams we add one step at the front: the Why. In a physical workplace context is visible. Across time zones it must be stated. The Why is not motivation. It is the context that lets a hire make correct decisions when the SOP does not cover an edge case.

Why

Before touching the task, explain why it exists. Two sentences maximum: what this task produces, and what happens to the business if it is done poorly. A hire who understands why a task matters makes better decisions at every edge case the SOP does not cover.

Prepare

Set everything up before the session begins: the SOP open on screen, the tools ready, the Good Job Library example visible, the task ready to start. McDonald’s does not build the station after the cook arrives. Neither do you. An unprepared session produces an undertrained hire.

Present

Complete the task yourself while sharing your screen. Narrate every decision. Show the SOP followed step by step and the Good Job Library checked before submitting. Do it twice: first pass the main steps, second pass the key points that separate an acceptable output from a correct one. The hire watches and touches nothing.

Try Out

Now the hire does it while you watch. Do not take over or correct in real time unless a critical error is being made. Note every point where they hesitate, skip a step, or deviate. The hire completes the task five times under supervision, each pass building on the last.

Follow Up

Give immediate, specific feedback after the fifth supervised pass. Not “good job.” Name exactly what was correct and exactly what needs to change. Then put them on the task independently while you move to spot checking.

Pass	What the hire does
Pass 1	Completes the task. Manager watches and corrects critical errors immediately.
Pass 2	Completes the task and narrates the main steps out loud as they go.
Pass 3	Completes the task, narrates the main steps, and names the key points.
Pass 4	Completes the task, narrates steps and key points, and explains why each key point matters.
Pass 5	Completes the task in full, narrating everything, with no input from the manager. This is the ownership confirmation pass.

The ownership threshold. A task is owned after five supervised completions with increasing narration, followed by three independent completions audited against the Good Job Library without intervention. Eight completions in total. Before that threshold the manager owns the output. After it, the hire does. This distinction changes every accountability conversation that follows.

Before ownership

The manager is responsible for the output. If the task is done incorrectly, the manager failed to complete the training sequence. This is a training issue, not a performance issue.

After ownership

The hire is responsible for the output. If the task is done incorrectly, it is a performance issue, not a training issue. That distinction gives the manager a clear, defensible position in any accountability discussion.

Step 01

After ownership transfers

Audit one in every five completions against the Good Job Library.

Step 02

After two weeks clean

Reduce to one in ten completions.

Step 03

If quality slips

Return immediately to Try Out. Not a conversation, not a warning. Back to supervised practice.

Section 02

The Good Job Library

The Good Job Library is the quality standard made visible. It is a curated archive of gold standard completed work for every recurring task in the hire's role. Before any hire submits a recurring deliverable they check it against the relevant example, not as a formality, as a genuine self-evaluation.

Without a Good Job Library the quality standard exists only in the manager's head. The hire is being measured against something they cannot see. That is not accountability. That is guesswork dressed as management.

Without the library

The standard lives in the manager’s head. The hire submits and waits to be told if it is right. Feedback is reactive. Errors compound before they are caught. The hire cannot self-correct because they cannot see the target.

With the library

The standard is documented and visible. The hire checks their own work before submitting. Feedback becomes confirmation, not correction. Quality improves without the manager involved in every output.

Save it as you go

Every time a task is completed to an exceptional standard, save it to the library immediately. Do not wait to build it later. Build it as you go from Day One.

Organise by role and task type

A CSR entry looks different from a sales coordinator entry. Keep them separate and clearly labelled.

Note why each example is gold standard

Add a brief note on what specifically makes this the target. The hire should read the note and understand the standard without asking.

Review quarterly

A gold standard from six months ago may no longer reflect current processes or quality expectations. Review and update the library every quarter.

Good Job Library

Customer Support

Perfect ticket resolution with full CRM update
Escalation handoff with complete written context

Sales

Cold outreach message that converted to a booked call
Discovery call notes with next step confirmed

Operations

Completed job schedule with zero gaps
Contractor confirmation sequence fully documented

Non-negotiable

The Good Job Library is only useful if the hire is required to reference it before every submission. Build the habit on Day One. This is not optional and not trust-dependent. It is a professional standard that applies to every hire at every level.

Section 03

Evergreen Tasks

Every remote hire will eventually reach a moment where their assigned task list runs dry. A project is waiting on someone else. A deliverable is pending review. There is nothing in the queue.

In an office this moment is visible. A manager walks past, sees an idle employee, and redirects them. In a remote team it is invisible. The hire sits idle. The manager has no idea. Momentum disappears before either party notices. Evergreen tasks solve this entirely.

Definition

An evergreen task is a productive, role-relevant task with no defined end point. It can be picked up at any moment without briefing or setup. It builds genuine business value every time it is worked on. It never runs out.

The hire does not need to be assigned it. They know what it is, why it matters, and to pivot to it the moment their primary list clears. No manager involvement. No idle time. No momentum lost.

Example: outbound cold calling

A sales coordinator for a commercial cleaning business has an evergreen task: cold calling businesses in the target area to generate quotes. There is no end to it. Every call either books an appointment, adds a prospect to the pipeline, or surfaces objection data that improves the next call. It builds direct business value every time and never runs out of scope.

Find the never-finished task

Ask what task, worked on continuously, would directly grow or improve the business without ever being finished. For a cleaning company that is outbound prospecting. For a home services business it might be reviewing and updating the client database.

Make it role-relevant

An evergreen task for a CSR is different from one for a sales coordinator. Each hire should have one to three evergreen tasks specific to their role.

Train it first

The task must be trained with the five-step method before it can function as a fallback. An untrained evergreen task is just another source of errors.

Make it measurable

Cold calls produce call logs, objection data, and booked appointments. Database review produces an accuracy rate. If you cannot measure what it produces, you cannot manage it.

Trait 01

Always available

No briefing required. No setup needed. The hire knows exactly what to do and pivots immediately without asking.

Trait 02

Always valuable

Every repetition produces something the business can use. Not busywork. Genuine output that compounds over time.

Trait 03

Always building mastery

Repetition against a documented standard using the Good Job Library is how skills deepen. Evergreen tasks are deliberate practice built into the working day.

Section 04

The 10/80/10 Framework

The five-step method applies to every task. The 10/80/10 framework applies to longer, more complex assignments where the risk of going in the wrong direction for an extended period is real.

The 10/80/10 framework is a widely used delegation heuristic, popularised for remote work by Jon Matzner. It addresses the most expensive mistake in remote task management: a hire works on something for days or weeks, submits it, and the manager discovers it is completely wrong. The work cannot be salvaged. The time cannot be recovered. Both parties are back at the beginning. The framework eliminates this by building three mandatory review checkpoints into the task itself, so the hire never works for an extended period without the manager confirming they are on the correct path.

Catching a wrong direction at ten percent costs almost nothing to fix. Catching it at eighty percent costs everything.

Phase 1

The First 10%

The hire completes the first ten percent and stops. This is the planning and direction phase: for a report, the outline and headings; for a database, the structure and first ten entries. They submit it before going further, and the manager checks it against the brief, the SOP, and a Good Job Library example.

Green light. On the correct path. Proceed to the eighty percent.

Redirect. Wrong approach, or the brief was misread. The correction happens now, when almost no time has been wasted. Adjust and resubmit the ten percent before proceeding.

Phase 2

The 80%

With approval confirmed, the hire builds the substantive body of the work, using the SOP and checking against the Good Job Library as they go. When the eighty percent is complete they stop and submit.

Green light. Quality is there. Proceed to the final ten percent.

Redirect. Issues here are addressed before the final polish begins, far less costly than discovering them after submission.

Phase 3

The Final 10%

The hire completes the polish, final formatting, and a quality check against the Good Job Library. When satisfied, they submit the completed work.

The checkpoint is not a lack of trust. It is the most efficient use of both people's time. A manager who reviews ten percent invests minutes to save days. A hire redirected at ten percent loses an hour; redirected at eighty percent, a week. The checkpoint protects both of them.

Use 10/80/10 for

Longer, complex assignments. Building a client database. Producing a first monthly report. Creating an SOP for a new process. Writing and scheduling a month of content. Anything where going the wrong direction for an extended period would be costly.

Use the five-step method for

Short recurring tasks. A CSR closing a ticket. A coordinator updating a job board. A scheduler confirming availability. Tasks repeated daily or weekly that can be owned quickly through supervised repetition.

Section 05

Task Execution Checklist

Use this every time you introduce a new task. For short recurring tasks, run the five-step method. For longer complex tasks, add the 10/80/10 framework after training is complete.

0 / 24

Before training begins

The five-step method

The Good Job Library

Evergreen tasks

The 10/80/10 framework (complex tasks only)

The Expectations Agreement

Day One→