Contractualism

Thinking Tools5.3 Validating Impact and ExecutionAlso known as Reasonable rejection test

Developed by T. M. Scanlon (Contractualism and Utilitarianism, 1982; What We Owe to Each Other, 1998), in the social-contract line that includes John Rawls.

Tests a rule or policy by asking whether anyone it affects could reasonably reject it, and treats a principle that survives every such objection as justified to all.

Seven objections to an on-call rule, sorted by whether each could reasonably reject it

Each group's objection is weighed two ways: how heavy the rule is on that group, and how heavy the best fix would be on others. The parents' objection is placed as an example. Select each other objection, read its facts, and pick its box; an objection in the bottom-right box, or one that wins the weighing in the top-right, sends the rule back. Illustrative.

Items (select one, then a box)
  • Not placedPlacedReasonable rejectionWeigh the two burdensNot a ground to reject
  • Not placedPlacedReasonable rejectionWeigh the two burdensNot a ground to reject
  • Not placedPlacedReasonable rejectionWeigh the two burdensNot a ground to reject
  • Not placedPlacedReasonable rejectionWeigh the two burdensNot a ground to reject
  • Not placedPlacedReasonable rejectionWeigh the two burdensNot a ground to reject
  • Not placedPlacedReasonable rejectionWeigh the two burdensNot a ground to reject
  • Not placedPlacedReasonable rejectionWeigh the two burdensNot a ground to reject

What the best fix costs others

HeavyLight
Not a ground to reject
Weigh the two burdens
Reasonable rejection
LightHeavy

What the rule costs this group

Parents at night. A parent alone with a toddler cannot answer a page in fifteen minutes at 3 a.m. without paying a sitter. Allowing swaps would cost colleagues almost nothing.Not placed yet.Parents at night. A parent alone with a toddler cannot answer a page in fifteen minutes at 3 a.m. without paying a sitter. Allowing swaps would cost colleagues almost nothing.Reasonable rejection: A heavy burden that a cheap change would lift. The rule goes back for revision until this group could accept it.Heavy on them, light to fix: allow swaps with two days' notice.Parents at night. A parent alone with a toddler cannot answer a page in fifteen minutes at 3 a.m. without paying a sitter. Allowing swaps would cost colleagues almost nothing.Weigh the two burdens: Heavy on both sides. Compare one person's burden under the rule with one person's burden under the fix; the heavier one decides.Parents at night. A parent alone with a toddler cannot answer a page in fifteen minutes at 3 a.m. without paying a sitter. Allowing swaps would cost colleagues almost nothing.Not a ground to reject: A light burden. Note it and accommodate it if that is cheap, but the rule can be justified to this group as it stands.Part-timers' load. Engineers on three-day weeks take the same on-call week as everyone else. Scaling the rotation to hours adds one shift a year to each full-timer.Not placed yet.Part-timers' load. Engineers on three-day weeks take the same on-call week as everyone else. Scaling the rotation to hours adds one shift a year to each full-timer.Reasonable rejection: A heavy burden that a cheap change would lift. The rule goes back for revision until this group could accept it.A full-time burden on part-time pay, lifted at a small cost to others: scale the rotation to hours.Part-timers' load. Engineers on three-day weeks take the same on-call week as everyone else. Scaling the rotation to hours adds one shift a year to each full-timer.Weigh the two burdens: Heavy on both sides. Compare one person's burden under the rule with one person's burden under the fix; the heavier one decides.Part-timers' load. Engineers on three-day weeks take the same on-call week as everyone else. Scaling the rotation to hours adds one shift a year to each full-timer.Not a ground to reject: A light burden. Note it and accommodate it if that is cheap, but the rule can be justified to this group as it stands.Juniors alone. New engineers would be paged alone on payment systems they have never touched. Pairing them with a senior costs each senior two extra weeks a year.Not placed yet.Juniors alone. New engineers would be paged alone on payment systems they have never touched. Pairing them with a senior costs each senior two extra weeks a year.Reasonable rejection: A heavy burden that a cheap change would lift. The rule goes back for revision until this group could accept it.Juniors alone. New engineers would be paged alone on payment systems they have never touched. Pairing them with a senior costs each senior two extra weeks a year.Weigh the two burdens: Heavy on both sides. Compare one person's burden under the rule with one person's burden under the fix; the heavier one decides.Weighed: a junior alone with a payments outage carries more than a senior giving two shadow weeks. The rule goes back.Juniors alone. New engineers would be paged alone on payment systems they have never touched. Pairing them with a senior costs each senior two extra weeks a year.Not a ground to reject: A light burden. Note it and accommodate it if that is cheap, but the rule can be justified to this group as it stands.Customers' wait. Merchants lose sales for every minute payments are down. A five-minute response would keep every engineer on call at their desk.Not placed yet.Customers' wait. Merchants lose sales for every minute payments are down. A five-minute response would keep every engineer on call at their desk.Reasonable rejection: A heavy burden that a cheap change would lift. The rule goes back for revision until this group could accept it.Customers' wait. Merchants lose sales for every minute payments are down. A five-minute response would keep every engineer on call at their desk.Weigh the two burdens: Heavy on both sides. Compare one person's burden under the rule with one person's burden under the fix; the heavier one decides.Weighed: five minutes would cost each engineer far more than the minutes cost each merchant. Fifteen holds, with a status update in five.Customers' wait. Merchants lose sales for every minute payments are down. A five-minute response would keep every engineer on call at their desk.Not a ground to reject: A light burden. Note it and accommodate it if that is cheap, but the rule can be justified to this group as it stands.Seniors' exemption. Senior engineers were never on call before. Keeping them exempt would put each of the others on call one week in four.Not placed yet.Seniors' exemption. Senior engineers were never on call before. Keeping them exempt would put each of the others on call one week in four.Reasonable rejection: A heavy burden that a cheap change would lift. The rule goes back for revision until this group could accept it.Seniors' exemption. Senior engineers were never on call before. Keeping them exempt would put each of the others on call one week in four.Weigh the two burdens: Heavy on both sides. Compare one person's burden under the rule with one person's burden under the fix; the heavier one decides.Seniors' exemption. Senior engineers were never on call before. Keeping them exempt would put each of the others on call one week in four.Not a ground to reject: A light burden. Note it and accommodate it if that is cheap, but the rule can be justified to this group as it stands.One week in six is light next to what their exemption would put on everyone else.Managers' admin. Managers must publish the schedule each quarter. A scheduling tool would do it for them at a small license cost.Not placed yet.Managers' admin. Managers must publish the schedule each quarter. A scheduling tool would do it for them at a small license cost.Reasonable rejection: A heavy burden that a cheap change would lift. The rule goes back for revision until this group could accept it.Managers' admin. Managers must publish the schedule each quarter. A scheduling tool would do it for them at a small license cost.Weigh the two burdens: Heavy on both sides. Compare one person's burden under the rule with one person's burden under the fix; the heavier one decides.Managers' admin. Managers must publish the schedule each quarter. A scheduling tool would do it for them at a small license cost.Not a ground to reject: A light burden. Note it and accommodate it if that is cheap, but the rule can be justified to this group as it stands.An hour a quarter: light. Buy the tool if it is cheap, but it is no reason to drop the rule.Pager dislike. A few engineers would rather not carry a phone app that can ring at night, though they have no one depending on them.Not placed yet.Pager dislike. A few engineers would rather not carry a phone app that can ring at night, though they have no one depending on them.Reasonable rejection: A heavy burden that a cheap change would lift. The rule goes back for revision until this group could accept it.Pager dislike. A few engineers would rather not carry a phone app that can ring at night, though they have no one depending on them.Weigh the two burdens: Heavy on both sides. Compare one person's burden under the rule with one person's burden under the fix; the heavier one decides.Pager dislike. A few engineers would rather not carry a phone app that can ring at night, though they have no one depending on them.Not a ground to reject: A light burden. Note it and accommodate it if that is cheap, but the rule can be justified to this group as it stands.A preference, not a burden: it does not outweigh the cost of the outages the rule prevents.

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.

Reasonable rejection
A heavy burden that a cheap change would lift. The rule goes back for revision until this group could accept it.
Weigh the two burdens
Heavy on both sides. Compare one person's burden under the rule with one person's burden under the fix; the heavier one decides.
Not a ground to reject
A light burden. Note it and accommodate it if that is cheap, but the rule can be justified to this group as it stands.

The sort

  • Parents at night: Reasonable rejection. Heavy on them, light to fix: allow swaps with two days' notice.
  • Part-timers' load: Reasonable rejection. A full-time burden on part-time pay, lifted at a small cost to others: scale the rotation to hours.
  • Juniors alone: Weigh the two burdens. Weighed: a junior alone with a payments outage carries more than a senior giving two shadow weeks. The rule goes back.
  • Customers' wait: Weigh the two burdens. Weighed: five minutes would cost each engineer far more than the minutes cost each merchant. Fifteen holds, with a status update in five.
  • Seniors' exemption: Not a ground to reject. One week in six is light next to what their exemption would put on everyone else.
  • Managers' admin: Not a ground to reject. An hour a quarter: light. Buy the tool if it is cheap, but it is no reason to drop the rule.
  • Pager dislike: Not a ground to reject. A preference, not a burden: it does not outweigh the cost of the outages the rule prevents.

An example

The head of engineering at a payments software company drafted an on-call rule: every engineer takes one week in six, answers any page within fifteen minutes at any hour, and no swaps. Before it went out, she listed every group the rule touched and wrote the strongest objection each could raise. Then she asked of each one whether that group could reasonably reject the rule, given what the fix would cost everyone else.

Three objections held. Parents of young children could not answer in fifteen minutes at 3 a.m. without paying for cover, and allowing swaps cost colleagues almost nothing. Part-time engineers carried a full-time load. Juniors would be alone at night on systems they had never touched. The seniors' complaint about losing their exemption did not hold, because keeping it would push a heavier load onto everyone else. The revised rule allowed swaps with two days' notice, scaled rotations to hours worked, and paired each junior with a senior for the first two rotations.

Why it works

Most policies are tested by asking whether they produce the best total result. Contractualism asks a harder question of each person a rule touches: could this person reasonably refuse it? Reasonable has a working meaning. An objection counts when the rule's burden on that person is heavier than the burden the best alternative would put on someone else. The comparison runs person to person and never adds up a crowd, so a large group's small convenience cannot outweigh one person's serious harm.

The test does two jobs. It finds the people a total-benefit calculation hides, and it disciplines complaints, because an objection that would shift a heavier load onto others fails. A rule that survives every objection is one its author can defend to each person face to face.

The thinking behind it

T. M. Scanlon T. M. Scanlon, a moral philosopher at Harvard, set out contractualism in Contractualism and Utilitarianism (1982), an essay that places his view beside the utilitarian one. On his account an act is wrong when principles that no one could reasonably reject would forbid it. He developed the view fully in What We Owe to Each Other (1998), where reasonable rejection becomes the standard for what people owe one another, and the test this tool runs on a workplace rule.

John Rawls John Rawls, a political philosopher, worked in the same social-contract line. In A Theory of Justice (1971) he asked which principles of justice people would choose in an original position, behind a veil of ignorance that hides their sex, race, abilities, wealth, and place in society. He argued they would choose equal basic liberties and the difference principle, which permits an inequality only when it benefits the worst off. Scanlon's test shares his aim: principles that can be justified to everyone they bind.

How to run it

  1. Write the rule as a principle. State it so it covers every case it will govern, including the ones nobody has in mind yet.
  2. List everyone it touches. Include the people who carry its costs without saying so, such as part-timers, new hires, and customers at night.
  3. Give each group its strongest objection. Write it the way that group's most articulate member would put it.
  4. Find the best fix for each. Name the change that would meet the objection and who would carry the cost of that change.
  5. Compare burdens person to person. An objection stands when the rule's burden on one person is heavier than the fix's burden on anyone else.
  6. Revise and test again. Change the rule to meet every objection that stands, then run all the objections against the new version.
  7. Write down the answer to each group. Keep one sentence per group explaining why the final rule is one they could accept.

Where it goes wrong

The first failure is the strawman: the drafter writes each group's objection weakly, so every one fails. Show the objection to someone from that group and ask whether it is their real complaint.

The second is adding up. A manager concludes that ninety engineers' small gain outweighs three parents' serious problem. That is the summing the test rules out; compare one person's burden with one person's burden.

The third is treating every complaint as a veto. A preference that would shift a heavier load onto others is not a reasonable ground to reject, and a rule held hostage to it never ships. Ask what the objector's fix would cost the next person.

When to use something else

  • Consequentialism. When the decision really does turn on total outcomes, and the job is to compare them across the options.
  • Veil of Ignorance. When the people writing the rule are swayed by their own seat and should choose before knowing which seat they will hold.
  • Ethical Matrix. When many groups and many values need laying out side by side before anyone judges.

Where it sits in SOLVE eX

Go to the source

  • Contractualism and Utilitarianism, Utilitarianism and Beyond (Amartya Sen and Bernard Williams, eds.), Cambridge University Press, 1982
  • What We Owe to Each Other, 1998
  • A Theory of Justice, 1971

Back to the catalog