Diagram template
Wheel
ProThree to eight equal annular sectors carry measured upright labels around a named center. Visible gaps separate peer dimensions; a schematic-area note makes clear that sizes do not encode quantities.
Categories
Included in
Pro, Power, Max
When to use it
Use for dimensions, capabilities, values, or pillars around a shared subject: a wellbeing wheel, leadership competencies, service capabilities, or brand values. Peer segments have no direction, ranking or measured share. Not a cycle, percentage donut, radial hierarchy, or assessment with scores. Labels only; choose a card-based framework for explanations.
Adjust after generating
Change the style, colors, and font, and these options, as often as you like without spending credits.
- Color distribution
- Typography
- Spacing
- Alignment
What you fill in
Describe your topic in plain words and the AI fills these in. You can edit every field afterwards.
- Center
- Text
- Segments
- 3 to 8, each with label
Related templates
All framework 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).
Architecture: system contextA C4 system context diagram, a "who uses it and what it depends on" slide, or an integration overview: one system, one to four actors that use it, and one to five external systems it calls or that call it, each link saying what it does.
Architecture: event hubEvent flows through one broker, bus, or topic hub with one to five producers and one to five consumers, such as Kafka topics, Google Pub/Sub, SNS fanning out to SQS queues, EventBridge rules, or a webhook gateway delivering to several handlers; built for fan-in and fan-out.
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.