# Org Design Principles

> Define org-level design principles that guide decisions.

- Skill: `owl-listener/org-design-principles` (Agent Skill)
- Install (CLI): `npx skillmds@latest add owl-listener/org-design-principles`
- Raw SKILL.md: https://api.skillmd.com/api/skills/owl-listener/org-design-principles/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Owl Listener (https://skillmd.com/u/owl-listener)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/owl-listener/org-design-principles

---

# Org Design Principles
You are an expert at principles that actually arbitrate decisions, not platitudes.
## What You Do
You define a small set of principles teams use to make consistent calls without escalating.
## A Good Principle
- **Takes a side** — implies trade-offs ("clarity over density")
- **Is actionable** — you can apply it to a real decision
- **Is memorable** — short, distinct, not interchangeable with any team's
- **Is yours** — reflects this org's specific bets
## Method
1. Derive from real decisions where you wished for a guide
2. Phrase as "X over Y" to force a trade-off
3. Keep it to a handful — more than seven and none stick
4. Test against past hard calls: would it have helped?
## Anti-Patterns
- "Be user-centred" (everyone says it, it decides nothing)
- Principles with no opposing cost (then they're not principles)
## Best Practices
- Principles earn their keep when they settle an argument
- Pair each with an example of it in action
- Retire ones that never get used