Diagram template
Driver tree
PowerA headline metric card on the left branches by elbow brackets into two to four driver cards per level, over two to four levels. Operator badges (times, plus, minus, divide) sit on each bracket between consecutive drivers, so each branch reads as an expression top to bottom. Every card shows the metric's name, an optional displayed value and an optional change pill colored only by a supplied favorability.
Categories
Included in
Power, Max
When to use it
Use for metrics that decompose into factors or parts: a profit tree (revenue minus costs), revenue as traffic times conversion times basket, unit economics, sales capacity as reps times quota times attainment, cost-to-serve breakdowns, or a productivity metric. Values are shown as supplied, not recomputed. Not for org charts, taxonomies without arithmetic, OKR progress, or causal hypotheses without a combining operation.
Adjust after generating
Change the style, colors, and font, and these options, as often as you like without spending credits.
- Card shape
- Card fill
- Color distribution
- Card border
- Card shadow
- Typography
- Icon fill
- Spacing
- Material
- Connectors
- Line weight
What you fill in
Describe your topic in plain words and the AI fills these in. You can edit every field afterwards.
- Nodes
- 5 to 20, each with id, optional parent, label, optional value, optional change, optional tone, and operator
Related templates
All tree templates
Anatomy: crowned subjectFor explaining what one thing is made of as a primary part, the part that carries it out and a part that spans both: a service offer (scope, delivery, assurance), a product (core function, how it ships, support), a course (content, format, learner support), an event (program, logistics, hosting) or a team charter (mission, ways of working, backing).
Allocation treeA positive common-unit allocation with two to four parts and an exact complete two-to-four-part breakdown of one selected parent.
Comparison: principle seamsFor two to four supplied principles, each owning one exact preferred example and one exact example to avoid: brand voice guides, product interface copy, support reply standards, documentation style, naming conventions, inclusive language or meeting etiquette.
Cycle: causalFor a compact qualitative causal-loop view with exactly five variables and two three-link loops sharing one variable: a referral loop against crowding in a membership plan, workload against hiring in a team, adoption against support load in a product, or demand against price in a market.
Cycle: quarter panelsFor four-step recurring loops where each step produces one named output: service improvement, editorial planning, quarterly operating reviews, product discovery or a study-practice-test-reflect learning cycle.
Cycle: stage ledgerFor 3–5 stage recurring loops with named owners, produced work and an explicit final-to-first feedback artifact: customer learning loops, hiring or onboarding routines, editorial cycles, release reviews and continuous-improvement rounds.