Set out by Donald A. Norman (The Psychology of Everyday Things, 1988).
Builds the desired action into the structure of the work, so the right step becomes unavoidable or the wrong one impossible, without relying on memory or willpower.
Seven ways to make sure a payment has its signed approval, sorted by what they rely on
Auditors found one payment in twelve going out without its signed approval. The reminder email is placed as an example. Select each other setup, read how often the step was still skipped under it, and pick what it relies on: only the right-hand box takes memory and attention out of it. Illustrative.
Items (select one, then a box)
Not placedPlacedMemoryNoticingThe work
Not placedPlacedMemoryNoticingThe work
Not placedPlacedMemoryNoticingThe work
Not placedPlacedMemoryNoticingThe work
Not placedPlacedMemoryNoticingThe work
Not placedPlacedMemoryNoticingThe work
Not placedPlacedMemoryNoticingThe work
Setups tried
Payments team
Memory
Noticing
The work
Someone rememberingSomeone noticingThe work itself
What keeps the step from being skipped
Reminder email. Every Monday the controller emails the payments team: attach the signed approval before paying. Still skipped on 1 payment in 12.Not placed yet.Reminder email. Every Monday the controller emails the payments team: attach the signed approval before paying. Still skipped on 1 payment in 12.Memory: Works when people are calm and have time, which is exactly when they would have remembered anyway.Nothing changed but the information, and the team already knew the rule.Reminder email. Every Monday the controller emails the payments team: attach the signed approval before paying. Still skipped on 1 payment in 12.Noticing: A person checks before or after. Better than memory, but checkers get busy too, and an after-the-fact catch comes once the money is gone.Reminder email. Every Monday the controller emails the payments team: attach the signed approval before paying. Still skipped on 1 payment in 12.The work: The next step cannot happen until this one is done. Watch for the workaround, and close it.Wiki checklist. A six-item checklist on the team wiki, approval first. Skipped on 1 payment in 14.Not placed yet.Wiki checklist. A six-item checklist on the team wiki, approval first. Skipped on 1 payment in 14.Memory: Works when people are calm and have time, which is exactly when they would have remembered anyway.A checklist helps someone who opens it. On a busy Friday nobody does.Wiki checklist. A six-item checklist on the team wiki, approval first. Skipped on 1 payment in 14.Noticing: A person checks before or after. Better than memory, but checkers get busy too, and an after-the-fact catch comes once the money is gone.Wiki checklist. A six-item checklist on the team wiki, approval first. Skipped on 1 payment in 14.The work: The next step cannot happen until this one is done. Watch for the workaround, and close it.Handbook policy. Section 4.2 of the finance handbook, signed by every new hire. Skipped on 1 payment in 12.Not placed yet.Handbook policy. Section 4.2 of the finance handbook, signed by every new hire. Skipped on 1 payment in 12.Memory: Works when people are calm and have time, which is exactly when they would have remembered anyway.A rule on paper is a reminder people read once.Handbook policy. Section 4.2 of the finance handbook, signed by every new hire. Skipped on 1 payment in 12.Noticing: A person checks before or after. Better than memory, but checkers get busy too, and an after-the-fact catch comes once the money is gone.Handbook policy. Section 4.2 of the finance handbook, signed by every new hire. Skipped on 1 payment in 12.The work: The next step cannot happen until this one is done. Watch for the workaround, and close it.Second sign-off. A second clerk reviews each payment over $10,000 before release. Skipped on 1 large payment in 40.Not placed yet.Second sign-off. A second clerk reviews each payment over $10,000 before release. Skipped on 1 large payment in 40.Memory: Works when people are calm and have time, which is exactly when they would have remembered anyway.Second sign-off. A second clerk reviews each payment over $10,000 before release. Skipped on 1 large payment in 40.Noticing: A person checks before or after. Better than memory, but checkers get busy too, and an after-the-fact catch comes once the money is gone.A person catching it, most of the time. The reviewer skims when the queue is long.Second sign-off. A second clerk reviews each payment over $10,000 before release. Skipped on 1 large payment in 40.The work: The next step cannot happen until this one is done. Watch for the workaround, and close it.Monthly audit sample. Internal audit samples fifty payments a month and flags any without approval. Finds about a third of the misses, weeks later.Not placed yet.Monthly audit sample. Internal audit samples fifty payments a month and flags any without approval. Finds about a third of the misses, weeks later.Memory: Works when people are calm and have time, which is exactly when they would have remembered anyway.Monthly audit sample. Internal audit samples fifty payments a month and flags any without approval. Finds about a third of the misses, weeks later.Noticing: A person checks before or after. Better than memory, but checkers get busy too, and an after-the-fact catch comes once the money is gone.Notices after the payment has gone. It measures the problem; it does not stop it.Monthly audit sample. Internal audit samples fifty payments a month and flags any without approval. Finds about a third of the misses, weeks later.The work: The next step cannot happen until this one is done. Watch for the workaround, and close it.Form blocks the send. The payment form will not submit until a signed approval is attached. Skipped on no payment for three weeks, then a clerk attached a blank page.Not placed yet.Form blocks the send. The payment form will not submit until a signed approval is attached. Skipped on no payment for three weeks, then a clerk attached a blank page.Memory: Works when people are calm and have time, which is exactly when they would have remembered anyway.Form blocks the send. The payment form will not submit until a signed approval is attached. Skipped on no payment for three weeks, then a clerk attached a blank page.Noticing: A person checks before or after. Better than memory, but checkers get busy too, and an after-the-fact catch comes once the money is gone.Form blocks the send. The payment form will not submit until a signed approval is attached. Skipped on no payment for three weeks, then a clerk attached a blank page.The work: The next step cannot happen until this one is done. Watch for the workaround, and close it.Forces the step, until the workaround appears. The fix was to accept only files from the e-signature system.Bank file check. The bank upload rejects any payment line without an approval ID that matches the signing log. Skipped on no payment in six months.Not placed yet.Bank file check. The bank upload rejects any payment line without an approval ID that matches the signing log. Skipped on no payment in six months.Memory: Works when people are calm and have time, which is exactly when they would have remembered anyway.Bank file check. The bank upload rejects any payment line without an approval ID that matches the signing log. Skipped on no payment in six months.Noticing: A person checks before or after. Better than memory, but checkers get busy too, and an after-the-fact catch comes once the money is gone.Bank file check. The bank upload rejects any payment line without an approval ID that matches the signing log. Skipped on no payment in six months.The work: The next step cannot happen until this one is done. Watch for the workaround, and close it.Built into the last step the payment must pass, so there is no path around it.
Your sort matched 0 of 7.Your sort matched 1 of 7.Your sort matched 2 of 7.Your sort matched 3 of 7.Your sort matched 4 of 7.Your sort matched 5 of 7.Your sort matched 6 of 7.Your sort matched 7 of 7.
Memory
Works when people are calm and have time, which is exactly when they would have remembered anyway.
Noticing
A person checks before or after. Better than memory, but checkers get busy too, and an after-the-fact catch comes once the money is gone.
The work
The next step cannot happen until this one is done. Watch for the workaround, and close it.
The sort
Reminder email: Memory. Nothing changed but the information, and the team already knew the rule.
Wiki checklist: Memory. A checklist helps someone who opens it. On a busy Friday nobody does.
Handbook policy: Memory. A rule on paper is a reminder people read once.
Second sign-off: Noticing. A person catching it, most of the time. The reviewer skims when the queue is long.
Monthly audit sample: Noticing. Notices after the payment has gone. It measures the problem; it does not stop it.
Form blocks the send: The work. Forces the step, until the workaround appears. The fix was to accept only files from the e-signature system.
Bank file check: The work. Built into the last step the payment must pass, so there is no path around it.
An example
Internal auditors at a food distributor found that one payment in twelve went out without its signed approval. The controller had tried what controllers try: a Monday reminder email, a checklist on the team wiki, a refresher on the handbook policy. None of them moved the number much, because the clerks already knew the rule. They skipped it on busy afternoons, when a supplier was calling about a late payment.
The controller stopped telling people and changed the form. The payment screen would no longer submit until a signed approval was attached. Skips fell to zero for three weeks. Then a clerk under pressure attached a blank page, and the form accepted it. The second version accepted only files that came from the e-signature system, and the bank upload began rejecting any payment line without an approval ID that matched the signing log. Six months later the audit sample found no payment without an approval.
Why it works
Memory and willpower fail under load, and they fail most at the moments when skipping a step does the most harm: the rush, the interruption, the end of the quarter. A reminder adds information, and people who skip a step usually have the information already. A forcing function changes the path instead, so the wrong action is not available and the right one is the only way forward.
The mechanism is sequence. When the next step cannot begin until this one is done, no one has to remember it, choose it, or be checked on it. The design does the remembering. That is also why every forcing function invites a workaround: it puts friction exactly where people are in a hurry. A good one is tested by trying to get around it, and then closed again.
The thinking behind it
Donald A. Norman Donald A. Norman, a cognitive scientist and usability engineer, argued in The Psychology of Everyday Things (1988), later retitled The Design of Everyday Things, that when people make mistakes with everyday objects the fault usually lies in the design. The book shows how constraints can be designed in to prevent errors, and a forcing function is a constraint of that kind taken to its limit: a design that will not let the action go forward until the right step has been taken. The same reasoning carries from door handles and car keys to forms, approvals, and payment runs.
How to run it
Pick the step that keeps getting skipped. Choose one with a real cost, measured by how often it is missed and what a miss costs.
Find out when it is skipped. Look at the misses for a pattern, such as a time of day, a queue length, or an urgent caller.
Find the next step it must come before. Name the action the skipped step should be a condition of, such as submitting, releasing, or shipping.
Make the next step wait for it. Change the form, the system, or the physical setup so the later step cannot start without the earlier one.
Try to get around it. Have someone in a hurry attempt the obvious workarounds, such as a blank file or a reused ID.
Close the workarounds. For each route around it, check the substance of the condition as well as its presence.
Give people an escape that leaves a trace. Allow a logged override for real emergencies, so the force never stops urgent work in silence.
Where it goes wrong
The first failure is forcing the wrong step. A required field that people fill with "n/a" forces typing, not judgment. Force only steps whose presence can be checked for substance.
The second is the blocked emergency. A system that refuses to release a payroll run because one approval is missing will be switched off by the end of the day. Build a logged override, and review every use.
The third is believing the problem is solved. Workarounds appear within weeks, and a forcing function that has been bypassed is worse than none, because everyone assumes it holds. Check the misses again after a month, and keep checking.
When to use something else
Poka-Yoke. When the error is physical, on a line or a bench, and a fixture or sensor can make it impossible.
Implementation Intentions. When the step belongs to one person's habits and cannot be built into any system.
Jidoka. When the right response to an abnormality is to stop the process and fix the cause on the spot.