If you want the index, start here: Value Multipliers.
The issue this taxonomy solves is that people talk about output as if it is only effort. In practice, effort is necessary, but it is not the whole model. What actually gets delivered is shaped by multipliers: trust, reliability, access, judgment, timing, coordination, and tool leverage, among others.
The mechanism is compounding. When several multipliers are strong, value stacks. When one is weak or missing, the whole system flattens no matter how much effort is applied. This is why two people with similar effort can produce radically different outcomes over time.
The trade-off is that multipliers are easy to talk about and hard to operationalize. The point of breaking this into individual pages is to make each multiplier clearer over time: what it is, what it looks like in practice, what it costs, and what tends to break if you ignore it.
The Big Buckets
The taxonomy is a working framework (not a finished ontology). The terms generally fall into a few clusters:
- Human qualities: traits and deeper capacities that shape value before tactics, tools, or credentials even enter the picture.
- Execution and operating qualities: the discipline layer — consistency, planning, responsiveness, and working well with real constraints.
- Strategy and leverage: choosing well, shaping leverage, and understanding why some work compounds more effectively than others.
- Relationships and markets: interaction, positioning, customer understanding, and fit between capability and real-world demand.
To browse all terms alphabetically (and click into any one), use the taxonomy page: Value Multipliers.
How To Use This Section
Read this as a working framework, not a finished taxonomy. The goal is not to label everything. The goal is to make the limiting factor visible so you can choose a better next move.
So the next step is:
- Identify the multiplier that is currently limiting your output (or your team’s output).
- Read that term page with one question in mind: “What has to be true for this multiplier to become reliable?”
- Define a concrete “done condition” for improvement (a behavior, a cadence, an output, or a constraint removed).
If you want the broader context around why these ideas matter, pair this section with Ideas & Writing and Systems Across Domains.