Case study · Solo operator · one working week

Fourteen open loops, one week, three commitments

A fourteen-item week run through The Forced Choice: what got kept, what got parked, and what actually happened by Friday.

A real session run by the person who builds these tools, reproduced here with the list lightly reworded. No client, no invented metrics.

The starting list

Fourteen items, written out in one sitting on a Sunday evening. Four of them were things that had been carried for more than a month. Three were other people's requests. Two were maintenance work that never feels urgent until it is.

Nothing on the list was unreasonable. That is exactly why the list was unworkable: every item had a plausible case for going first, so the week defaulted to whatever arrived loudest.

Why rating it didn't work

The list had already been scored out of ten once. Eleven of the fourteen items landed on seven or eight — a flat wall of near-identical numbers that resolved nothing. Absolute scores ask a question people are bad at answering.

Pairwise comparison asks a question people are good at: if you could only do one of these today, which one? The comparisons were uncomfortable. That discomfort is where the decision happens.

The rest of this case study

Where should I send it?

Enter your email and the full case study opens on this page immediately — no confirmation step, no download.

  • The full fourteen-item list, as written
  • The pair comparisons that flipped the expected order
  • The three that survived, and the confidence score on each
  • The parked list, and what happened to it four weeks later
  • The Friday review: what actually got done

One email address, kept for occasional notes about new tools. No sequences, no sharing, unsubscribe whenever. Already signed in? Your account email unlocks this automatically.

Now run it on your own list

This is the exact tool used in the session above. Ten things you're carrying, eight minutes, three left standing.

The note this came from

Why your to-do list keeps growing no matter how much you finish

A to-do list that only ever grows isn't a discipline problem. It's a design problem: nothing in the system is allowed to say no.