Home/ Volume 06/ Chapter 8
Show menu button
The Golden Rule

You cannot hire for, train toward, or measure against a job that was never written down.

Recruitment, training, and performance management all trace back to the same document: the role description.

RecruitmentHire against the description, not a gut feeling.
TrainingVerified by testing, not just watching someone nod along.
PerformanceReviewed against KPIs, on a predictable rhythm.

Match the hire to the role

Charisma for a Task Role, or technical skill alone for a Supervisor role, misfires.

"Shown" isn't "trained"

Training ends only when performance is verified, unsupervised.

Feedback in the moment

Patterns belong at the review; new information never should.

A surprise is a broken habit

Any review with a surprise means in-the-moment feedback broke down.

1

Definition

Imagine a tailor quietly misses a stitch-quality target for two months. If nobody says anything until the quarterly review, that review turns into an ambush, the tailor blindsided by criticism he never had a chance to fix in real time. Now imagine the supervisor mentioned it plainly each time it happened. The quarterly review becomes something else entirely, a calm conversation about why the pattern is happening and what to do about it, because nothing said in the room is news.

Recruitment

Choosing who joins the business.

Training

Making sure they can actually do the job to the documented standard.

Performance Management

The ongoing, honest answer to "are they doing it well?"

Recruitment

is choosing who joins the business. Training is making sure they can actually do the job to the documented standard. Performance management is the ongoing, honest answer to "are they doing it well?" All three fail without Chapter 7's role description, you cannot recruit for, train toward, or measure against a job that was never actually written down.

In One Sentence

Hire against the role description, not a gut feeling. Train against the documented systems (Volume 02), verified by testing, not just by watching someone nod along. Review performance against the role's own KPIs, on a predictable rhythm, with no surprises at review time because problems were already raised when they happened.

2

Recruitment: Hiring Against the Description

StepWhat It Checks
Write the role description first (Chapter 7)Are we even clear on what we need?
Screen against the purpose and KPIs, not just a CVCan this person plausibly do this job, not just "a similar job"
Test the actual skill (a practical cutting test, a mock customer call)Talk is cheap; a demonstrated skill isn't
Check references for pattern, not just a good wordDoes their history match what the role actually demands
Common Mistake

Hiring on charisma alone for a Task Role (Chapter 5) that mostly needs precision and consistency, or hiring on technical skill alone for a Supervisor role (Chapter 4) that mostly needs judgment and people management. Match the hire to what the role, not the interview, actually rewards.

Once someone is hired, formalize it with an Employment Contract and work through the New Employee Onboarding Checklist, never start someone on an informal, undocumented understanding.

3

Training: Verified, Not Assumed

Training has one job: closing the gap between "has been shown the SOP (the written step-by-step procedure)" and "can reliably perform the SOP without supervision." Volume 02, Chapter 3's stranger test applies directly here, a new hire is that stranger, and training isn't complete until they've actually performed the task correctly, unsupervised, at least once.

StageWhat It Looks Like
ObserveWatch a competent person do the task
Co-doPerform it together, with correction in real time
Solo, supervisedPerform it alone while being watched
Solo, verifiedPerform it alone; a supervisor confirms it meets the standard
Signed offThe role description's checklist is marked complete, with a name and date

This directly answers Chapter 5's apprentice story, a documented, verified training stage replaces "seemed talented" with a repeatable standard anyone can check.

4

Performance: A Rhythm, Not an Ambush

Performance reviews should never contain a surprise. If a problem is worth mentioning at a quarterly review, it was worth mentioning the week it happened. The review's job is to step back and look at the pattern, not to introduce new information for the first time.

RhythmPurpose
In the momentImmediate, specific feedback, praise or correction, tied to a real event
Monthly check-inA short conversation against the role's KPIs, on track, or not?
Formal review (quarterly/annual)Pattern review, documented, tied to development and (where relevant) pay
Memory Trick

Feedback in the moment; patterns at the review. A review that only ever delivers feedback for the first time is a sign the in-the-moment habit is missing.

Use the Performance Review Form for the formal stage, and a Warning Letter whenever an in-the-moment correction needs a written record, never as a surprise substitute for the conversation itself. When a role changes for the better, confirm it with a Promotion Letter; when someone leaves, a Resignation Letter and an Exit Interview close out the record, the latter doubling as one last chance to capture any tacit knowledge (the know-how they carry in their head that was never written down) before it leaves with them.

5

Example Story: The Review With No Surprises

Here's the full version of the stitch-quality story from the start of this chapter.

A tailor at MANIAC MINDZ had been quietly missing the stitch-quality KPI for two months. Because his supervisor had mentioned it plainly each time it happened, not as a formal warning, just an honest, specific correction, his quarterly review contained nothing he hadn't already heard. It became a conversation about why the pattern was happening (an unfamiliar new fabric type) and a concrete fix (extra practice time with that fabric), not a confrontation. Compare this to Volume 04, Chapter 5's story, the difference between documented, timely feedback and one that only surfaces at the worst possible moment.

6

Common Mistakes

Common Mistake #1: Hiring Without a Written Role Description

Impossible to know what "good" looks like for a role no one has defined, see Chapter 7.

Common Mistake #2: Treating "Was Shown" as "Is Trained"

Training isn't complete until the new hire has performed the task alone and been verified, not merely watched it once.

Common Mistake #3: Saving All Feedback for the Formal Review

Guarantees surprises, resentment, and reviews that feel like ambushes instead of pattern conversations.

7

Quiz Yourself

Quiz 1
Why must recruitment, training, and performance all trace back to the role description?
Because you cannot hire for, train toward, or measure against a job that was never clearly written down, the description is what defines "good" for that role.
Quiz 2
What is the actual difference between "was shown the task" and "is trained"?
Being trained means having performed the task alone and had it verified against the standard, not just having observed or been walked through it once.
Quiz 3
Why should a quarterly review never contain a surprise?
Because feedback belongs in the moment it happens; the review's job is only to step back and examine the pattern, not introduce new information for the first time.
8

Practice Exercise

  1. For your next hire, write the role description first (Chapter 7), then design one practical test tied directly to its core task.
  2. For one current employee, map their training against the five stages in Section 3, where are they, honestly?
  3. Recall your last formal review with someone. Did it contain anything they were hearing for the first time? If so, that's this chapter's fix to apply going forward.
9

Quick Summary

Quick Summary

  • Recruitment hires against the role description's purpose and KPIs, not charisma alone, and not technical skill alone where judgment is what the role needs.
  • Training moves through observe → co-do → solo supervised → solo verified → signed off, not complete until performance is verified, unsupervised.
  • Performance review is a rhythm: feedback in the moment, patterns at the formal review, never the reverse.
  • A review with a surprise in it is a sign the in-the-moment habit broke down somewhere along the way.