The same executive can make a careful decision on one occasion and rush a similar decision later. That variation may reflect preparation, information, workload or the way the question was presented.
Past success gives a leader a reason for confidence. It does not remove the need for a dependable process.
Define what a prepared decision looks like
For recurring high-consequence choices, agree on a short set of requirements. The question should be clear, credible alternatives should be considered and material assumptions should be visible.
Use those requirements even when the answer feels obvious. They are especially useful when a familiar decision arrives with an unfamiliar complication.
Do not confuse consistency with giving the same answer. A good process should produce a different answer when relevant facts change.
Review the reasoning before the outcome takes over
Record why the choice was made and what would lead to reconsideration. Later, assess that reasoning using information available at the time.
An outcome can be affected by luck and events the team could not reasonably anticipate. Reviewing only the result may reward a poor process that happened to work or punish a sound one that did not.
Look for conditions associated with avoidable errors: unread briefs, missing perspectives, unclear authority or decisions added late to a crowded agenda. Those are arrangements the organization can change. A claim that a wearable score measures judgment is unnecessary when the process failures are already visible.
