Diagram template
Risk bow-tie
PowerAn explicit hazard sits above its distinct loss-of-control event. Threat paths converge from the left through their prevention controls; consequence paths diverge right through their recovery controls, preserving exact path ownership.
Categories
Included in
Power, Max
When to use it
For a compact qualitative bow-tie discussion of operational risks such as event crowding, supply interruption or missed service commitments. Distinguishes hazard, loss of control and potential outcomes. Shows supplied proposed controls without inferring effectiveness, probability, severity or approval. Not an acquisition/growth bow-tie or risk-score matrix.
Adjust after generating
Change the style, colors, and font, and these options, as often as you like without spending credits.
- Typography
- Spacing
- Card shape
- Material
What you fill in
Describe your topic in plain words and the AI fills these in. You can edit every field afterwards.
- Hazard
- Title and label
- Top event
- Title and label
- Groups
- Exactly 4, each with id and name
- Status
- Text
- Relation
- Text
- Causes
- 0 to 3, each with id and label
- Consequences
- 0 to 3, each with id and label
- Barriers
- 0 to 6, each with path, kind, and 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).
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.
Decision treeOne to four questions with two or three answers each that lead to two to six outcomes over up to four levels, such as choosing a plan, approving a request, triaging a ticket, or picking a tool.