Decision Lattice
A fifteen-to-twenty-five-minute protocol for decisions with multiple interdependent variables and competing outcomes. Maps options as a lattice, assigns probabilities and values, runs mental simulations, and forces a clean commit. For decisions where gut feeling is not enough and the stakes are too high to go with the first plausible answer.
Contributed by Grok (xAI), built with the Framework Builder skill
Download .framework.jsonLayer 1 · Principles
- Gut fails under multi-variable pressure. Intuition is excellent at single-variable problems where a pattern matches a past situation. It degrades quickly when three or more independent variables interact, because the mind cannot hold their interactions in parallel. For those decisions, structure beats intuition.
- Probability times value is more honest than either alone. People routinely overweight high-value-low-probability outcomes or high-probability-low-value ones. Forcing both numbers to appear side by side, even rough estimates, reveals which options are actually competitive and which just feel competitive.
- Lattices make trade-offs visible; visible trade-offs become actionable. An unarticulated trade-off keeps you stuck. An articulated one is a choice. The framework's real output is not the decision; it is the named trade-off that made the decision inevitable.
Layer 2 · Systematic Approach
Build, score, simulate, choose
- Map core variables. List the three to seven variables that actually matter for this decision. Not everything matters. Cut ruthlessly. If you have more than seven, you are confusing variables with considerations.
- Build the outcome lattice. For each option, write the outcomes across each variable. Arrange as a grid. Options on one axis, variables on the other. The grid is the lattice.
- Assign probabilities and values. For each cell, estimate the probability that this outcome happens and its value if it does. Rough numbers are fine. The point is not precision; it is forcing the comparison to be explicit.
- Run mental simulations. For each option, imagine you chose it and a year has passed. What does success look like? What does failure look like? How much regret does each outcome carry? The simulation catches second-order effects the grid missed.
- Select and commit. Pick the option. Write one sentence naming the specific trade-off you are accepting. If you cannot name the trade-off, you have not decided; you have postponed.
Layer 3 · Force Multipliers
- Transferable pattern recognition Once you build a few lattices, you start seeing them everywhere. Career moves, product bets, hiring choices, even arguments. The habit of asking 'what are the variables, what are the outcomes, what is the trade-off' becomes automatic. Grok identified this as the most compounding skill in the meta-cognition set. Users typically report feeling significantly more decisive on complex choices within a month, not because decisions get easier but because the structure is no longer intimidating.
- Reduced post-decision regret Naming the trade-off before the decision makes the downside predictable. When the downside arrives (and one always does), it is already on the grid. Regret drops because the surprise dropped.
- Calibration log as long-term asset If you write down your probability estimates at decision time and check them after, you build a personal calibration record. Over years, you learn exactly how much to trust your own estimates on different types of questions. The log becomes more valuable than any single decision.
Layer 4 · Success Metrics
Leading indicators
- Variables list is three to seven items, not more.
- Every cell in the lattice has a probability and a value, even if rough.
- The final step produces a named trade-off in one sentence.
Lagging indicators
- Post-decision regret decreases over a period of months of consistent use.
- Probability estimates, tracked over time, become measurably more accurate.
Failure modes
- Variable bloat
- Analysis as avoidance
Do not use when
- The decision is simple or reversible at low cost. Use gut and move on.
- Time pressure makes a twenty-minute structured process more expensive than a slightly suboptimal call.
- The decision is fundamentally values-based rather than outcome-based. Lattices compare outcomes, not values.
Layer 5 · Implementation
Required to start
- A specific decision with two or more real options.
- Three to seven variables that meaningfully differentiate the options.
- Fifteen to twenty-five uninterrupted minutes.
- Willingness to commit at the end.
Works best with
- A trusted advisor to pressure-test the variable list and probability estimates.
- A calibration log from previous decisions, so you know your personal over- and under-estimation tendencies.
You are done when
- A scored lattice.
- A mental simulation for each option.
- A selected option.
- One sentence naming the specific trade-off being accepted.
Where to use it
- Career moves Job offers, role changes, sabbatical decisions. High stakes, multi-variable, irreversible on any short timeline.
- Investment choices Any bet where probability and value both matter and both are uncertain.
- Big life changes Relocation, relationship, education, health. Framework does not make the choice easier emotionally but makes it clearer analytically.
- Advising others Running this with someone else walking them through the steps is often more useful than doing it alone. The external voice catches variables the decision-maker missed.
Built with the Framework Builder methodology. Get the skill →