A vague decision becomes easier to handle when too many floating variables are reduced into a small set of closed questions. Use Choice Throttling when the user needs the decision space narrowed before judgment can work.

The practical version:

  1. Name the variables creating uncertainty.
  2. Turn each variable into a yes/no or closed question.
  3. Answer the questions in order.
  4. Let the answers narrow the decision.

Choice throttling replaces open-ended rumination with a decision path.

When To Use It

Use it for low-to-medium complexity decisions where the main problem is too many options, not lack of values.

Good use cases:

  • choosing between study methods,
  • deciding whether to attend an optional event,
  • selecting a task for a work block,
  • choosing whether to continue or switch,
  • narrowing a list of tools, resources, or plans.

For very simple decisions, a faster filter may be enough: if the option is not a clear yes or clear no, the decision may not matter much.

How To Use It

Start with the uncertainty.

Bad version:

  • “What should I do?”

Better version:

  • “Is this choice high consequence?”
  • “Is the decision reversible?”
  • “Will waiting produce useful information?”
  • “Does this protect the main downside?”
  • “Does this align with the current goal?”

Each question should reduce the decision space.

Why It Works

Open questions create sprawl. Closed questions create movement.

The point is to isolate the variables that actually matter. Some yes/no questions may take time to answer, especially when values or consequences are unclear. That is still progress because the user now knows what information is missing.

Failure Modes

FailureWhat It Looks LikeFix
Fake binaryThe question forces a yes/no where the real variable has degrees.Rewrite the question or add thresholds.
Wrong variableThe answer is clear but does not change the decision.Ask what uncertainty actually controls the choice.
Too many questionsThe method becomes another form of overthinking.Keep only decision-changing variables.
Values are unclearEvery option looks equivalent.Use reflection, Kolbs, or a values check before deciding.
Complexity mismatchThe decision is high-stakes but treated like a quick filter.Move to a complex-decision process.

Sources

  • Justin Sung / iCanStudy basic decision-making materials, paraphrased and synthesized in original language.

Open Questions

  • What are the user’s most common repeat decisions that could become choice-throttling checklists?