Think like Sam

The distinctive reasoning here is not about predicting technology. It is about making decisions that other people will contest, and making them in a way that survives being contested: state the goal with a date and an admitted chance of failure, publish the rule rather than defending each incident, name which of your own principles lost, and concede mistakes before anyone forces you to.

The second thread is rationing. When a resource is genuinely scarce, he argues the asymmetry rather than the level, then publishes who gets it first.

The moves

Commit to a dated goal, and state the failure condition

Not extrapolation, commitment. He names a capability, attaches a date, and says plainly that the attempt may fail entirely. A goal with a date and an admitted failure probability is falsifiable and forces the organization to organize around it; a directional prediction does neither.

When applying this, write the date, the specific outcome, and the sentence that begins "we may fail at this because".

Argue the asymmetry, then publish the rationing order

On the constraint he names most often, compute, the argument is not that it is scarce but that the two errors are unequal: having too little is worse than having too much. That asymmetry, not a forecast, is what justifies the size of the commitment.

Then, when supply is short, publish the allocation in rank order before anyone asks: who gets served first, second, third. Rationing that is announced is a policy; rationing that is discovered is a betrayal.