Work and people
A company other people can run
Make standards clear, teach the judgment behind them and give people the information and authority to finish the work.

A company can have capable people and still send every difficult question to the same person. Sometimes the missing piece is information. Sometimes it is permission to act, time to learn or a commitment nobody has been given the means to finish.
These readings stay with the work. What does an instruction leave unexplained? Which record would show that a promise was kept? Can the person who receives the handoff do anything useful without asking its author to return?
The aim is not to make every employee behave like the founder. It is to give people enough shared understanding to make reasonable choices, recognize an exception and carry the work through. A good procedure should also be open to correction by the person closest to the problem.
Make the work understandable
A standard and an explanation do different jobs. Both need to survive contact with the person using them.
Being good at it and teaching it are different jobs
An explanation has to cross the distance between what you can see and what another person knows to look for. More detail is useful only when it closes that distance.
Read onChoosing what to learn nextThe skill your work still needs
The next improvement may belong between what you do well and the person who needs it.
Read onJudgment about the finished pieceWhen a good addition gets in the way
An accurate paragraph can be worth keeping and still belong somewhere else. Read its contribution alongside what it interrupts or delays.
Read onPeople and responsibilityStandards without micromanagement
A standard has to be clear enough for someone else to use. Otherwise the founder remains part of every decision.
Read onService and executionA promise needs an operation
What a customer buys may take a sentence to describe. Providing it can require a sequence of work they will never see.
Read onReachable, with a workable arrangementWhat your reply promises
The first reply should tell the person waiting what they can actually rely on.
Read onAn original practice caseThe session you can confirm: a discussion case
Twelve people have paid, eight have asked and a machine might be available. Decide what can actually be confirmed before the next person makes plans.
Read onLet judgment reach the problem
Examine the account, the handoff and the objection before adding another approval.
Trust needs a record another person can follow.
A company can give people room to act and retain enough knowledge to understand what happened. Those aims belong together.
Read onPeople and operating responsibilityCould the next decision happen without the founder?
A covered inbox is not the same as a covered responsibility. Follow one unfinished situation all the way to its outcome.
Read onResponsibility and communicationAn update should not hand the problem back
An owner can understand a problem without becoming the person who must solve every part of it. Make the decision and the continuing responsibility clear.
Read onMaking a proposal strongerHow to disagree with a promising plan
An objection earns its place by showing what might fail, why it matters and what could change the judgment. Enthusiasm deserves the same test.
Read onAccuracy and the momentMake the correction useful in the room
The fact matters. So does what the listener needs to do with it now.
Read onKnowledge before commitmentAsk while an answer can still change the plan
Make clear what remains open, who decides and when an answer can still affect the choice. Then return with what happened to the contribution.
Read onWhen the problem changesOne incident can contain many bills
A modest daily charge can become a larger commitment while each invoice still looks ordinary. Keep the incident together as the proposed solution changes.
Read onThe result worth pursuingWhat would resolving this dispute change?
A payment can settle a cost while leaving the disputed record unchanged. Decide which result the next conversation needs to produce.
Read onReading the choice before the endingA principle can have a cost
A later reward can make an earlier choice look easier than it was. Keep the standard, its cost and the eventual outcome visible as different judgments.
Read onThe overlap before reliefFunding the weeks before a manager can take over
A manager can start getting paid weeks before the old work and costs can move. Put the handover evidence beside the cash dates.
Read onThe instruction before the paymentBefore you change where a supplier payment goes
The invoice can be valid while the proposed destination remains unverified. Keep the request, its confirmation and permission to act separate.
Read onTest the intended operation
A tidy plan can hide a dependency that only appears at the next scale or at the busiest hour.
Test the business you actually plan to run
A successful trial can justify a useful smaller operation. It supports a larger launch only to the extent that it has tested the larger launch’s difficult assumptions.
Read onCapacity on the day it is neededBusy days and quiet averages
An empty Tuesday room cannot accommodate a Saturday guest. Before adding up demand and capacity, keep the dates attached.
Read onThe work behind customer growthThree more customers can mean nine new setups
The customer count can rise by three while the team sets up nine. Keep the starts and departures with the target.
Read onEvidence and responsibilityA decision before a report
A short decision brief connects the choice, the commitment, the current evidence and the question still open. Write it before commissioning another report.
Read onAfter the error is foundA correction needs somewhere to go
The original record can be right while the next person still acts on the old answer. Follow the correction to the decisions that depend on it.
Read onThe finding after the warningWhat has a screening flag actually established?
A useful warning starts a check. What follows depends on what the system examined, what remains unknown and the evidence needed before acting.
Read onThe people behind the openingHiring for a shift people can reach
Interested applicants do not yet supply a workable shift. Follow the journey in both directions before deciding whether to change the job, the service or the transport.
Read onInventory and serviceWhen a bulk discount costs more
A cheaper pack can make a more expensive order. Start with how many you can use and when you need them.
Read onReading a controlled comparisonDid the new instructions make the difference?
Twelve volunteers, two instruction sheets and one shared task show why assigning the versions matters as much as calculating their averages.
Read onReading a marketing measureConversion rate: what is being counted?
Six sessions can contain eight paid orders from five recorded IDs. Those counts support different rates; none should silently become a count of people.
Read onNotice what a useful relationship depends on
See the customer, the recurring task and the work that remains after a promising result.
What repeated complaints should change
A pattern becomes useful when someone changes the work behind it and checks what happens next.
Read onLearning from completed serviceAsk the customers your inbox never shows you
A useful follow-up has a defined group, a question worth asking and an honest account of whose experience remains unknown.
Read onThe weight of one relationshipWhen one customer matters too much
A large customer can make a company stronger and leave it more exposed at the same time.
Read onThe work after the first answerDid the faster process actually save time?
A result produced in seconds can leave hours of work behind it. Count the whole job.
Read onTechnology, livelihood and the transitionWhat happens between the old job and the new economy?
A faster operation and a secure living are different outcomes. Chapter 16 asks who carries the interval between a changed job and the benefits people hope technology will bring.
Read onThe people affected by the decisionWhose story does the turnaround tell?
An owner’s reason, an employee’s changed position and a later return to work answer different questions. Keep each one in the account.
Read onWork that reaches a finishWhich unfinished work is moving?
Thirty-six requests finished. Half of the opening queue is still waiting.
Read onService and executionA promise needs an operation
What a customer buys may take a sentence to describe. Providing it can require a sequence of work they will never see.
Read onAfter the ownership changeWhat comes with the customer relationships?
A company can change hands before every relationship that supports it is ready to follow.
Read onReading an origin storyWho supplied what at the beginning?
Money, advice and practical help can appear in the same beginning. Describe each contribution before turning the account into a single label.
Read onReading a recurring business100% net revenue retention does not mean every customer stayed
Expansion in one account can replace revenue lost elsewhere. Follow the original customers before adding the new ones.
Read onReading a stock planA reorder point is not the quantity to buy
Fifty units can trigger an order for eighty. The shelf, open order and delivery calendar explain why.
Read onRead alongside the book
Return to the full account.
The restaurant work, the recovery chapters and the technology chapter look at responsibility from different positions. Read Chapters 3, 8, 10 and 16 together to see what changes when someone else needs to carry the decision.
Open the chapter companion