Start with subtraction when you are improving a process: ask whether each requirement and step should exist. Use regret minimization when you are weighing a consequential personal choice: consider the decision from your future perspective, including the possibility of failure. Each framework clarifies a different kind of problem.
A framework is a way to organize attention. It helps you notice a part of the problem that may be easy to miss. It does not remove uncertainty or make a decision for you.
Two released Frameworks episodes offer different tools: Musk's operating sequence for questioning a system, and Bezos's regret minimization for examining a consequential choice. This guide adapts those episode ideas into small exercises. Choose the tool that matches the problem rather than forcing every decision through the same lens.
When the problem is a process: start with subtraction
A recurring meeting, approval, or report can become familiar enough that its existence stops being questioned. Improving its speed may preserve an unnecessary task. The Tesla episode explores an order of operations: question requirements, delete, simplify, accelerate, and automate.
Consider a weekly status report. Before automating it, identify who uses it and which decision it informs. If nobody can name that decision, investigate whether the report is needed. If it is needed, examine whether a shorter format would serve the reader better.
Deletion needs context. A step may protect safety, comply with an obligation, or preserve customer trust. Check with the people who depend on it before removing it. The exercise is to understand the requirement, not assume that every constraint is waste.
Pick one recurring task and name its purpose.
Ask who relies on it and what would happen without it.
Test a bounded change with the affected people.
Simplify what remains before considering automation.
When the problem is a life choice: examine future regret
Regret minimization asks you to view a decision from further ahead in your life. The Bezos episode uses that perspective to examine trying, failing, and never trying. A useful extension is to ask whether you would still respect a choice if the hoped-for outcome did not happen.
Imagine two options: keep your current role, or test a new business alongside it. Write the tradeoffs in ordinary language. One option might protect stability while delaying exploration. The other might produce learning while consuming scarce time. Neither description tells you what to choose; both make the choice more honest.
Do not let an imagined older self erase present responsibilities. Money, relationships, health, and other people's needs belong in the decision. Ask what you can test at a smaller scale before treating the choice as all-or-nothing.
Write two concrete options, including staying where you are.
Describe a plausible good and bad outcome for each.
Ask which decision you would still respect if it failed.
Look for a reversible experiment that reduces uncertainty.
A five-minute decision note
Record the decision, your assumptions, the downside you are accepting, and when you will review it. This creates a record of what you knew before the result arrived. You can then learn from the process without rewriting the story around success or failure.
Choose one decision for this week. If it is about an inefficient system, try subtraction. If it is about a direction you might regret never exploring, try future regret. If neither fits, use a different tool. A useful framework earns its place by clarifying the decision in front of you.
Sources and further listening
Show descriptions use the official pages below. Comparisons and exercises are Frameworks editorial assessments. Other shows and hosts are not affiliated with or endorsing Frameworks.