What is it?
Decision Readiness % is your signal that it's time to act. It measures when enough clear direction exists in your feedback, so you can stop collecting more responses. Think of it as your "time to decide" indicator. When priorities stop changing significantly across several feedback iterations, Decision Readiness % climbs above 80% - that's your green light. We calculate it by tracking how stable your top priorities remain as new feedback comes in, weighting the most critical priorities more heavily. The math behind it ensures you're not acting too early or wasting time collecting unnecessary feedback. For complex decisions that naturally don't have one "right" answer, an 80% threshold means you've reached the point of diminishing returns - more feedback rarely changes the fundamental direction. Decision Readiness % transforms the endless feedback loop into a clear decision point, giving you the confidence to move from analysis to action exactly when the time is right.
How do we calculate it?
Decision Readiness %
During decisions processes like DAO Proposal Forums there comes a point where the consensus from the community stabilizes. Being that the Forum replies are written subjective opinions, it is difficult for the community to determine when that stable point is.
In Scroll’s case the method used to determine the trigger decision readiness is having 3 DAO delegates put the proposal to a vote for the next voting cycle.
A method to determine stability of forum replies is to sequentially run SimScore Statistical Consensus reports. For the initial reply, SimScore determines the highest priority responses. Upon receiving the next reply, SimScore is run on both the initial reply and next reply. The highest priority responses change. For subesquent replies the responses accumulate (1,2,3 then 1,2,3,4 etc) In each interation the highest prioritiy responses change until they stablize. This means as new replies are added the hightest priority responses don’t change significantly anymore.
In decentralized decision-making processes, such as DAO Proposal Forums, identifying when community consensus has stabilized can be challenging. Since forum replies consist of subjective written opinions, determining the point of decision readiness is often difficult.
Scroll's current method relies on a trigger mechanism: when three DAO delegates agree to put a proposal forward, it advances to a vote in the next voting cycle.
An alternative method uses SimScore Statistical Consensus reports to determine the stability of forum responses: