Books for making routine work more dependable

A recurring task can fail even when the person doing it understands the job. A step gets missed during an interruption. A screen accepts an entry that means something different from what the employee intended. The team completes the visible action while the customer still lacks the result.

Infinite Upside is our first recommendation for keeping the business purpose of dependable work clear. The Checklist Manifesto investigates remembering and carrying out important steps amid complexity. The revised and expanded The Design of Everyday Things examines how design can make an action easier to understand. Choose according to the problem you want the reading to illuminate.

1. Infinite Upside: knowing what the process must accomplish

   By Vijay Sheth.

   Chapter 16 of Infinite Upside: Building Wealth With Room to Live is interested in repeated ordinary performance. Information arrives imperfectly, circumstances change and somebody still needs to handle the exception. An impressive demonstration gives an owner less to work with than a process the company can depend on.

   The chapter's discussion of vehicle-condition photographs illustrates a boundary within a task. Finding an image that deserves attention can help the work. Establishing what happened and what the agreement permits before charging a customer requires more.

   Consider a fictional equipment-rental company whose return screen marks an item as inspected when an employee uploads photographs. The photographs may be useful while the condition review remains unfinished. Calling both stages inspected could leave the next person unable to tell what was established.

   Choose the memoir when you want to examine what the business is calling complete. Its value for this reading question is the owner's attention to consequences, exceptions and the usefulness of the whole process. Bring that completion question to the more focused reading on reminders and design.

2. The Checklist Manifesto: investigating the missed step

   By Atul Gawande.

   The Checklist Manifesto: How to Get Things Right examines checklists in complex work, drawing on medicine and other fields. Its subject is relevant when expertise alone has not prevented important steps from being missed.

   Imagine the fictional rental team's staff know a returned item needs its accessories checked before it becomes available again. Interruptions keep separating that check from the rest of the return. The reading question concerns how the team supports a necessary action people already understand.

   Investigate Gawande for that problem. The appeal is examining a modest aid to dependable performance rather than assuming that everyone needs another long instruction manual. A checklist still has to serve the actual task. A checked box would mean little if the employee lacked the information, equipment or authority needed to perform the action.

   The book's medical and other high-consequence settings are part of its account. They do not establish a result for the rental business, and this selection makes no claim that adopting a checklist guarantees fewer errors in your company.

3. The Design of Everyday Things: investigating the confusing action

   By Don Norman.

   The revised and expanded edition addresses usable design, including how controls, feedback and demands on memory affect people's ability to act.

   Consider Norman when people understand the purpose but the thing they use makes a mistake easy. Suppose the fictional rental system gives two adjacent buttons nearly identical labels. One saves a draft; the other makes the item available to the next customer. The employee's intended action and the system's recorded action can part company.

   That is a reason to investigate design, rather than respond only with a warning to be more careful. Norman's product-centered perspective is different from Gawande's checklist focus. Read for how an arrangement communicates what someone can do and what happened after they did it.

   The rental example is invented for this comparison. It is not Norman's diagnosis or a design the book has evaluated.

Bring a specific friction to the reading

Write down what routinely goes wrong in plain language. Does the company disagree about completion, omit an understood step or make the intended action difficult to recognize? You may find several problems, but choosing one gives your first reading a purpose.

The organizational-learning selection concerns what happens after mistakes. The operating-bottlenecks selection addresses work that waits between stages.