Diagram - Metric Tree.

Best for: ARR decomposition in a B2B SaaS growth review, pinpointing the growth lever in a fundraising deck, a value driver tree in a consulting proposal, sharing the metric hierarchy in an OKR design workshop

Use: When one slide has to prove which formula a north star metric decomposes into, and which term moves the number above it. Use it when you also need to descend to level 2, the inputs a team directly controls. The operators are printed, so the figures have to actually add and multiply up.

Avoid: Use problem-root-cause for a causal narrative where causes converge on a problem, diagram-decision-tree when conditions branch to mutually exclusive conclusions, diagram-layered-stack for categorical stacked tiers, and diagram-pyramid-hierarchy when area encodes the hierarchy. For an additive bridge between two points in time use chart-waterfall-bridge, and for three unrelated parallel figures use content-stat-typescale. Beyond five drivers, or more than three leaves per driver, the type drops under the legibility floor, so split the levels across two slides.