What does it mean that one framework per decision type?

Create a specific framework for each recurring decision type.

Example: You use the same agonizing deliberation for choosing a database as you do for choosing lunch. One decision shapes your architecture for years. The other is reversed by walking to a different restaurant tomorrow. When you apply a single generic process to both, you either over-invest in trivial choices or under-invest in consequential ones. The fix: build a specific framework for each type of decision you encounter repeatedly, so the right level of rigor activates automatically.

Try this: List every decision you made in the past two weeks. Group them by type: hiring, purchasing, architectural, scheduling, prioritization, relationship. For each type, write down the process you actually used. Now compare: did the process match the stakes? Pick the one type where the mismatch is largest and draft a one-page framework — criteria, sequence, kill conditions — specific to that decision type. Use it for the next three instances.