Decision Tempo
How long considering takes to become choosing.
- Commitment speed
- Middle is the sweet spot
- Often downstream
- Modulator
Decision Tempo is not how smart your choices are. It is how long your system runs evaluation before it is willing to cross from considering into choosing.
It is visible in the speed and cost of commitment: some systems convert options into decisions almost instantly, others revisit the same material in passes, wanting more certainty before the gate will open.
The range
Saturation curve: the middle tends to work best; both extremes cost something.
Lower
Choices are made rapidly, which supports throughput, responsiveness, and decisiveness in familiar or low-stakes contexts. The cost is under-evaluation when complexity is real: the system can commit before tradeoffs, ambiguity, or second-order consequences have been weighed.
Calibrated (middle)
The sweet spot. Evaluation runs in proportion to what the decision is worth: long enough to weigh what matters, short enough that evaluating never consumes the action itself. Some decisions are fast by design, and the big ones get the passes they deserve.
Higher
Commitment takes time and repeated passes through the same material, which can mean thorough, well-weighed choices. But the system keeps evaluating after the informational value has been extracted, and deciding becomes its own load source. It feels rational from inside, like needing a little more clarity, even past the point where more evaluation improves anything.
It depends
- Fatigue
- Tempo is among the first executive functions to show depletion. Routine decisions suddenly requiring real effort is a leading early burnout signal, often before performance visibly drops.
- Acute stress
- Stress often speeds decisions up, but biases them toward familiar, habitual choices.
- Emotional stakes
- Decisions with emotional consequences have to clear the threat-safety system first, which extends the clock and taxes the very capacity doing the evaluating.
Baseline is the architecture; today's tempo is the state it is running in.
What it is not
- Not Starting Gate
- Decision Tempo is how long it takes to choose. Starting Gate is how hard it is to begin once the choice is made. Slow deciding and slow launching often co-occur, but they are different bottlenecks.
- Not Certainty Pull
- Certainty Pull is the aversive response to incomplete information; Decision Tempo is the duration of the evaluation cycle itself. You can hate uncertainty and still decide fast, or tolerate ambiguity and still take a long time because your evaluation style is slow and exhaustive.
I just need a little more clarity.
the reaction we design for