think-dialectical-bootstrapping
Produces a dialectical estimate that improves a single committed number by polling the inner crowd, make a first estimate, assume it is wrong and list why, read whether that pushes the answer too high or too low, make a second estimate from those changed assumptions, then mechanically average the two. Use when a hard, one-off, bounded-scale numeric estimate (a year, a percentage, a count, a forecast) is about to be committed and no second judge, no real reference class, and no better data are available. Not for easy questions, not for unbounded order-of-magnitude unknowns, and never a cherry-picked single number in place of the average.
product-on-purpose · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add product-on-purpose/thinking-framework-skills --skill think-dialectical-bootstrappingAbout this skill
name: think-dialectical-bootstrapping description: Produces a dialectical estimate that improves a single committed number by polling the inner crowd, make a first estimate, assume it is wrong and list why, read whether that pushes the answer too high or too low, make a second estimate from those changed assumptions, then mechanically average the two. Use when a hard, one-off, bounded-scale numeric estimate (a year, a percentage, a count, a forecast) is about to be committed and no second judge, no real reference class, and no better data are available. Not for easy questions, not for unbounded order-of-magnitude unknowns, and never a cherry-picked single number in place of the average. license: Apache-2.0 metadata: id: thinking-framework-skills.dialectical-bootstrapping family: decision-and-option-evaluation evidence-tier: "M" version: 0.1.0 standard: "0.8"
Dialectical Bootstrapping
A single estimate of a hard quantity is an anchor: the first number that comes to mind quietly fixes the answer, and merely staring at it again does not move it. Dialectical bootstrapping breaks that anchor by simulating a second opinion from inside one head and then harvesting it the way a crowd is harvested - by averaging. The durable move is to poll the inner crowd and force the synthesis to be arithmetic: make a first estimate, deliberately assume it is wrong and generate a second estimate that draws on at least partly different knowledge, then take the plain arithmetic mean of the two numbers as the committed answer. The statistical reason it works is the wisdom of crowds in miniature - averaging two estimates cancels random error, and when the two bracket the truth (one too high, one too low) it eats into systematic error too. The "dialectical" name is literal: thesis (first estimate), antithesis (the contrarian second estimate), synthesis (the average). The output is a dialectical estimate artifact, not prose: the applicability check, both numbered estimates with the assumed-wrong reasoning that produced the second, and the non-negotiable average.
When to Use
- A one-off numeric estimate is about to be committed on a genuinely hard question - a date, a percentage, a count, a forecast - where being off matters.
- No second human judge is available or consultation is impossible, so the only "second opinion" obtainable is a second pass from the same mind.
- No genuine reference class of comparable past cases exists to anchor an outside view, so reference-class forecasting is not an option.
- The quantity lives on a familiar or bounded scale (a year, a share, a percentage), where a deliberately different second guess can plausibly land on the other side of the truth.
When NOT to Use
- Do not use it on an easy question or one well within competence. The strongest pre-registered evidence on the modern variant found a forced-different second estimate helps on difficult questions and actively HARMS accuracy on easy ones (Van de Calseyde and Efendic, 2025). When the first estimate is already close, the contrarian second mostly adds error that the average then bakes in.
- Do not use it on an unbounded, order-of-magnitude unknown. Muller-Trede (2011) found the gains vanish for general numerical questions whose answers range over orders of magnitude. That is
think-fermi-estimation's home regime - decompose the magnitude into factors instead of re-sampling a holistic guess. - Do not use it when a real second judge or real data is available. Your own second opinion is worth about half of someone else's (Herzog and Hertwig, 2009); and if a genuine reference class exists,
think-reference-class-forecasting(the outside view) dominates simulating a crowd from one mind. The method is a fallback, and it must say so. - Do not use it when the error is one shared load-bearing assumption. Averaging two estimates from the same mind cannot remove a bias both estimates share; the inner crowd tops out near the value of only 1.5 independent judges (van Dolder and van den Assem, 2018). If the whole estimate hangs on one assumption, test that assumption instead of averaging over it.
- Do not make the average optional. The discipline IS the mechanical average. Left free, most people cherry-pick the estimate they now prefer or extrapolate outside their own two numbers, and the realized gain disappears (Muller-Trede, 2011). The final answer is the mean of the two estimates - never a single number you liked better, never a value outside their range.
- Do not use it on a qualitative judgment. The move is defined for quantitative point estimates only. There is no arithmetic mean of two opinions, so there is nothing to average.
Instructions
When asked to firm up or pressure-test a single numeric estimate, follow these steps:
- Run the applicability check first, before touching any number. Confirm all four gates: the question is genuinely hard (not easy or routine); the quantity is a point estimate on a bounded or familiar scale (not an order-of-magnitude unknown); it is a one-off commitment; and no real second judge, no reference class, and no better data are available. If any gate fails, stop and route to the right tool (an easy question needs no method; an unbounded magnitude routes to fermi-estimation; available data routes to reference-class-forecasting; a single load-bearing assumption routes to assumption-testing).
- Make the first estimate. State the single best point estimate of the quantity, with its units and the scale it lives on. This is the thesis.
- Assume the first estimate is wrong and say why. Deliberately suppose the first number is off the mark. List the assumptions and considerations behind it that could have been mistaken, and what different knowledge a skeptic would bring. The goal is a genuinely different basis, not a