What it means to truly own your domain
Opening question
Describe accountability in your own words.
Take 60 seconds — write it down before we start.
This is ownership you need to practice — and ownership you need to demand from others.
A note before we start
Ownership is a practice. It's also a demand you place on others. Both require honesty about where things stand today.
Ownership means you have the decision rights, resources, and accountability for a specific domain.
All three — or it's not ownership. You = the team.
Missing one element → broken ownership. Missing two → the system fails silently.
Heavily inspired by Alex Ewerlöf — "6 Archetypes of Broken Ownership". Each archetype is missing at least one of the three elements.
| # | Nickname | 🧠 Know | 🔑 Mandate | ⚖️ Resp | Core problem |
|---|---|---|---|---|---|
| 1 | 🔫 Monkey with a gun | ✗ | ✓ | ✗ | Top-down decisions, no ops exposure |
| 2 | 💤 Coma | ✓ | ✗ | ✗ | Smart but sidelined; no levers or stakes |
| 3 | 👶 Babysitter | ✗ | ✗ | ✓ | Cleaning up without context or control |
| 4 | 🧒 Teenager | ✓ | ✓ | ✗ | Autonomy without consequences |
| 5 | 🪖 Foot Soldier | ✓ | ✗ | ✓ | Experts who can't change anything |
| 6 | 🎲 Gambler | ✗ | ✓ | ✓ | Gut decisions; devs excluded from ops |
Power without context and without skin in the game → dangerous decisions made with confidence.
Accountability without authority is not ownership — it's a trap. The Babysitter suffers it every day.
Attach SLAs/OKRs, on-call rotation, and incident accountability directly to decisions made. Consequences must follow choices.
Delegate change rights, access, and time/budget to those responsible. Authority must match accountability.
Build shared Knowledge: post-mortems with devs, golden metrics, pairing between business and engineering.
Share one example. No names required. Focus on the pattern, not the person.
10 minutes
Back at :xx. Come ready to talk about how to fix it.
While you're up: think of one area in your work where the DRI is genuinely unclear. We'll apply the circles framework to it.
Ownership = Knowledge + Mandate + Responsibility
All three, or it's not ownership. Missing one element creates a named archetype — a predictable failure mode with a known fix.
Broken ownership → High WIP, waste, burnout, poor ops
The symptoms are always visible. The root cause requires diagnosis.
How to fix it
Fix by adding the missing element — with explicit enablement and clear criteria for success.
The Circles of Control, Influence, and Concern — three zones that define where your energy belongs.
Start with the Circle of Control. Expand outward as you build trust.
Based on Stephen Covey, The 7 Habits of Highly Effective People (1989).
Be Proactive
Be Transparent
Full K+M+R applies here
The Circle of Control is the only place you can apply all three ownership elements simultaneously. If you're not doing that here — nowhere else will work either.
Signals you're doing it right
✓ No one has to chase you for status
✓ You surface risks before they escalate
✓ Your dashboards are always live
✓ Post-mortem actions are closed on time
Trust = doing what you say, repeatedly.
Not perfectly. Repeatedly — and transparently when you can't.
It's about all your stakeholders and partners
Influence is not about selling — it's about reliability. The teams that depend on you are watching whether your words match your actions.
The Art of Saying No
Saying yes and delivering late or with poor quality destroys trust faster than saying no ever could. The next slide covers how to do it right.
Saying yes and delivering late or with poor quality destroys trust. This is the framework for a No that builds trust.
The trap
Spending energy complaining about what you cannot change: org structure, company strategy, other teams' decisions, macro context.
It feels like engagement. It's actually displacement — productive-feeling energy that produces nothing.
The alternative
Name it once. Make it visible. Then return to the Circle of Control and do what you can do.
Focus energy inward.
Expand the inner circle over time.
For each scenario: identify which broken ownership archetype it represents, and name the missing element(s).
Some scenarios have more than one pattern. Name the most dominant one — and discuss what that means for who acts first.
Write down your outcomes and share them with the wider group.
12 minutes → share back → challenge each other → align on one concrete next action per group.
Knowledge · Mandate · Responsibility
Ownership is not a title. It's a daily choice.
The team next to you is counting on you to make it — every single day.
Accountability & Ownership ·