Problems Triangle Solves
A decision architecture for leaders who believe structure matters more than charisma.
1. One person carries too much
Problem: Key decisions concentrate on one leader. They burn out, or they are wrong and nobody tells them.
Solution: Three-person triangle. One facilitator runs the process. Authority is shared by design, not by goodwill.
2. Dissent goes silent
Problem: People disagree but say nothing. The decision passes unanimously. Six months later it fails — the dissent was there but unrecorded.
Solution: Consensus-first voting. Genuine dissent is extracted, recorded, and travels with the decision. Disagreement is information, not noise.
3. Circular re-litigation
Problem: Decisions get reopened endlessly. Nothing is ever final. Teams stall because the same arguments repeat.
Solution: Lock & Forward. Once Frame → Vote → Record → Move completes, the decision is locked. The team moves to the next decision. No going back — except by challenge (two non-originating triangles) or authorized override.
4. Cross-team dependencies are invisible
Problem: Team B waits for Team A to decide. Team A does not know they are blocking. Email chains replace accountability.
Solution: Decision Requests with timeout. Team B sends a request. Team A receives it as a pending dependency on their Map. Timeout = locked. Blockers become visible. Escalation is built in.
5. No institutional memory
Problem: Why decisions were made gets lost. New members repeat old arguments. The organization learns nothing from its own history.
Solution: Every decision is recorded with reasoning, dissent, and follow-up results. The log is the Map. New members read past decisions during onboarding.
6. AI rubber-stamping
Problem: AI makes a recommendation. Humans rubber-stamp it without real evaluation. Accountability blurs.
Solution: AI is advisory only. The triangle consciously affirms or overrules. Everything is logged: AI recommendation + human vote + dissent. Six months later you can see who overruled AI and why.
7. Decisions are flat
Problem: All decisions get treated equally. Some depend on others. Some can run in parallel. Nobody can see the sequence.
Solution: Decision Map — a directed acyclic graph. Nodes are decisions. Arrows show dependencies. The Map makes the sequence visible.
8. No way to challenge bad decisions
Problem: A locked decision is wrong. One person cannot reopen it. The team is stuck.
Solution: Challenge rule. Two non-originating triangles can challenge a lock. Biblical witness pattern — by the mouth of two or three witnesses.
9. Facilitator has too much power
Problem: The person running the meeting could override the group. Minority views get suppressed.
Solution: If the facilitator is in the minority (two others disagree), the facilitator must represent the majority — not override it. When the triangle is requested to support other triangles, the majority decision binds the external position.
10. Scale breaks the rules
Problem: What works for three people does not work for thirty. Every level needs different rules.
Solution: Fractal architecture. A department is a triangle. A division is a triangle. The board is a triangle. Same rules apply at every scale. A team of five uses the same architecture as a corporation of five thousand.
Cite This Framework
If you reference Triangle in your work, please cite:
Beyst, M. (2026). Triangle: A Framework for Structured, Accountable, Humane Decision-Making. Retrieved from https://dynamictrilateral.org/
Released under CC BY-NC 4.0.