🎯 Training ·

Accountability
& Ownership

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.

Agenda

What we'll cover today

01Why this matters — building a shared languageTheory
02Definition of Ownership: Knowledge + Mandate + ResponsibilityTheory
036 Archetypes of Broken OwnershipTheory
04Pulse check + BreakBreak
05How to fix it — Circles of Control, Influence & ConcernTheory
06Quiz — identify the patternQuiz
07Group exercises: The Impossible SLO · The Roadmap TensionExercise
Why

Why This Matters

🗣️
Shared terms, different meanings
"Ownership" means something different to every team. Without alignment, every handoff is a risk.
🚫
Raise the bar
Avoid the "not my problem" mindset. Every gap in ownership costs someone — usually the customer.
📈
Compounding reliability
Going beyond your lane creates reliability that compounds across the organisation. One team's ownership becomes everyone's foundation.

This is ownership you need to practice — and ownership you need to demand from others.

Objectives

Course Goal

1
Align on ownership, accountability, and "you build it, you run it"
Build a shared vocabulary that works across disciplines and teams.
2
Recognise broken ownership patterns and apply practical remedies
Learn to diagnose which element is missing — Knowledge, Mandate, or Responsibility — and pick the right fix.
3
Use real-world scenarios to build data-driven, trust-centered habits
Theory is only useful if it changes how you work tomorrow. We'll practice with real situations.

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.

Definition

What is Ownership?

Ownership means you have the decision rights, resources, and accountability for a specific domain.
All three — or it's not ownership. You = the team.

🧠
Knowledge
You understand your domain — the system, the users, the trade-offs. You can make informed decisions.
🔑
Mandate
You have the authority to act — access, approvals, decision rights. You can change things, not just observe.
⚖️
Responsibility
You are accountable for the outcome — on-call, incidents, SLAs. You feel the consequences of your decisions.

Missing one element → broken ownership. Missing two → the system fails silently.

Framework

Why Ownership is Broken — 6 Archetypes

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
Archetype 1

🔫 Monkey with a gun — Only Mandate

🧠 Knowledge 🔑 Mandate ⚖️ Responsibility
Symptoms
Top-down decisions without ops context
Little or no exposure to production
Experts ignored in key calls
Impact
Micromanagement and rework
Demoralized engineers
Decisions that don't survive contact with reality
Fix
Add Responsibility: on-call rotation, incident ownership
Build Knowledge: reviews, observability, ops pairing

Power without context and without skin in the game → dangerous decisions made with confidence.

Archetype 2

💤 Coma — Only Knowledge

🧠 Knowledge 🔑 Mandate ⚖️ Responsibility
Symptoms
Smart people sidelined
No levers or stakes
Advice that's never acted on
Impact
Slow decisions — experts not in the room
Wasted expertise and frustration
Knowledge walks out the door
Fix
Give bounded Mandate: put them in decisions
Add Responsibility: shared outcomes, pilots with skin in the game
The expert who is consulted but never decides. The architect who designs but never runs on-call. The analyst whose findings go unread. All Coma.
Archetype 3

👶 Babysitter — Only Responsibility

🧠 Knowledge 🔑 Mandate ⚖️ Responsibility
Symptoms
Cleaning up without context or control
Always the one paged, never the one who designed it
Dependent on others for every change
Impact
Firefighting as a full-time job
Passive ops; fragile systems
Burnout without authority to improve things
Fix
Grant Mandate: access, approvals, change rights
Build Knowledge: embed with builders, design reviews

Accountability without authority is not ownership — it's a trap. The Babysitter suffers it every day.

Archetype 4

🧒 Teenager — Mandate + Knowledge, no Responsibility

🧠 Knowledge 🔑 Mandate ⚖️ Responsibility
Symptoms
Autonomy without consequences
Finger-pointing when things go wrong
No SLAs tied to decisions
Impact
Risky bets with no skin in the game
Trust loss — mandate later revoked
Fix

Attach SLAs/OKRs, on-call rotation, and incident accountability directly to decisions made. Consequences must follow choices.

Real example
In a weekly business review, the team detects an issue with tracking metrics. They wait for the PM to prioritize the fix. A senior leader outside the team steps in and begins fixing the problem on the spot.
Why broken ownership
The team did not take the wheel. They relied solely on their PM's prioritisation and didn't demonstrate agency within their area of responsibility.
How to fix it
Understand stakeholder needs and act proactively. Look at the impact of systems gaps beyond the roadmap plan.
Archetype 5

🪖 Foot Soldier — Responsibility + Knowledge, no Mandate

🧠 Knowledge 🔑 Mandate ⚖️ Responsibility
Symptoms
Experts handle incidents
Can't change what's broken
"Management by escalation"
Impact
Burnout
Slow improvements
Fragile systems that nobody can fix
Fix

Delegate change rights, access, and time/budget to those responsible. Authority must match accountability.

Real example
A team needs to configure a 3rd party tool for customer-facing notifications (NPS impact) but requires approval from a team with no business domain or impact knowledge.
Why broken ownership
Unclear mandate. The domain-owning team lacks authority for critical tool decisions, creating dependencies on teams without relevant expertise.
How to fix it
The domain-owning team must gain mandate over the configuration system. Demonstrate agency — take responsibility for domain-impacting tools instead of accepting inefficient approval processes.
Archetype 6

🎲 Gambler — Mandate + Responsibility, no Knowledge

🧠 Knowledge 🔑 Mandate ⚖️ Responsibility
Symptoms
Gut decisions, partial data
Devs excluded from ops
Business claims without evidence
Impact
Costly incidents
Productivity drag
Trust breakdown over time
Fix

Build shared Knowledge: post-mortems with devs, golden metrics, pairing between business and engineering.

Real example
A business team insists on adding an unvalidated feature to an MVP, claiming partners "might stop using our platform." The team agrees, introduces the functionality, and misses the original delivery deadline.
Why broken ownership
Insufficient knowledge. The team failed to demand supporting data, didn't assess actual impact vs the deadline, and lacked domain knowledge to make informed trade-offs.
How to fix it
Establish clear criteria for scope changes. Demand evidence-based justifications. Develop domain knowledge to challenge unvalidated requests.
Pulse Check

Which pattern do you recognise most
in your day-to-day?

0 votes
🔫
Monkey with a gun
Mandate without knowledge or skin in game
💤
Coma
Knowledge with no power or stake
👶
Babysitter
Responsibility without context or control
🧒
Teenager
Autonomy without consequences
🪖
Foot Soldier
Experts who can't change anything
🎲
Gambler
Decisions without domain knowledge

Share one example. No names required. Focus on the pattern, not the person.

Break

☕ Break Time

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.

Recap

One-Slide Recap

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

1 Diag
Ask "Which element is missing — Knowledge, Mandate, or Responsibility?"
2 Fix
Add the missing element with the lightest-weight intervention possible first
3 Loop
Validate outcomes: fewer escalations, less toil, faster & safer changes

Fix by adding the missing element — with explicit enablement and clear criteria for success.

Framework

What can you do now?

The Circles of Control, Influence, and Concern — three zones that define where your energy belongs.

🎯
Circle of Control
Your domain, your ownership. Act here. Be proactive. Be transparent. Apply the full K+M+R.
🤝
Circle of Influence
Other teams, stakeholders. Show up consistently. Make boundaries explicit. Build trust through commitments you keep.
🌀
Circle of Concern
Things you can't change. Don't camp here. Complaining about what you cannot control is energy that doesn't compound.

Start with the Circle of Control. Expand outward as you build trust.

Based on Stephen Covey, The 7 Habits of Highly Effective People (1989).

Circle of Control 🎯

Your ownership, your domain

Be Proactive

→
Communicate before being asked. Don't wait for your manager to notice the risk.
→
Take action to fix what's broken in your scope. If you can see it, you own it.
→
Don't wait for the roadmap to tell you what needs attention in production.

Be Transparent

→
Share context — what you're doing, what's blocked, and why.
→
Make your data and KPIs publicly available. Visibility is a form of trust.

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

Circle of Influence 🤝

Building trust with your stakeholders

→
Show ownership consistently and repeatedly to build influence. Trust compounds.
→
Make sure ownership boundaries are shared and explicit with all partners.
→
Only make commitments you can meet. Explicit the assumptions you're working with.
→
Don't surprise your partners. A late warning is infinitely better than a late delivery with no warning.

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.

Circle of Influence

The Art of Saying No

Saying yes and delivering late or with poor quality destroys trust. This is the framework for a No that builds trust.

1
Acknowledge the request
"I understand this is important for the Q4 launch." — show you heard them, not that you're dismissing them.
2
Explain the constraint
"Our team is at capacity with reliability work after last month's incidents." — be specific, not vague.
3
Make the trade-offs explicit — let them choose
"We can deliver in Q1 · or descope X to fit it in · or partner with Team Y who has more capacity." Escalate if requests conflict. Let the people asking choose the trade-off together.
4
Document the decision and its context
Write it down. Six months later, nobody remembers the conversation — but they'll remember who owned it.
Circle of Concern 🌀

What you cannot change

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.

CONCERN
INFLUENCE
CONTROL

Focus energy inward.
Expand the inner circle over time.

Quiz

Identify the pattern

For each scenario: identify which broken ownership archetype it represents, and name the missing element(s).

👁️
Step 1 — Read
Read the scenario silently. What do you see?
🔍
Step 2 — Diagnose
Which element is missing? Which archetype?
💬
Step 3 — Reveal
Discuss with the group, then reveal the answer.

Some scenarios have more than one pattern. Name the most dominant one — and discuss what that means for who acts first.

Quiz · Scenario 1
Read & discuss — which archetype?
Team A has a dependency on Team B's domain in a shared platform. Instead of helping Team B extract their domain, Team A starts working directly on it, hoping to get things done faster.
Quiz · Scenario 2
Read & discuss — which archetype?
Your team member with knowledge of a configuration stack changes team. Their new team has dependencies on his previous one — but they don't have ownership on the configuration domain.
Quiz · Scenario 3
Read & discuss — which archetype?
You just joined a team. The manager of this team is leaving — but before they do, they make a decision that will significantly impact your team's future.
Quiz · Scenario 4
Read & discuss — which archetype?
Orders are down in one of your markets due to a bug that went undetected in your team for a week.
Quiz · Scenario 5
Read & discuss — which archetype?
Your team has 5 pending post-mortem actions that are beyond their SLA — and nobody has closed them.
Quiz · Scenario 6
Read & discuss — which archetype?
An intern has deployment rights to production.
Quiz · Scenario 7
Read & discuss — which archetype?
You are paged while on-call during the night. You have identified the fix — but you don't have access to deploy, and there's no obvious escalation path. So you decide to go back to sleep.
Exercises

Group Exercises — Goal

⏱ 12 minutes per group · then share back
Work through a real ownership challenge in small groups. Use the framework from today — diagnose, fix, validate.
1
Discuss and diagnose the problem using the K+M+R framework
2
Call out the archetype you identified
3
Define actions, who needs to be involved, and possible solutions
4
Write down the outcome of your discussion
5
Share with the group — and challenge each other's approaches

Write down your outcomes and share them with the wider group.

Exercises

Your groups

Group 1
The Impossible SLO
Your team owns an SLO that is regularly breached, but the root causes live in a dependency you don't control. You have Responsibility but not Mandate. Diagnose: which archetype? What's the fix?
Apply: K+M+R · Circles · Art of Saying No
Group 2
The Roadmap Tension
A stakeholder is pushing a feature onto your Q3 roadmap citing business urgency, but your team has no supporting data and the deadline is already tight. Diagnose: which archetype? What's the fix?
Apply: K+M+R · Art of Saying No · Trade-offs

12 minutes → share back → challenge each other → align on one concrete next action per group.

🎯

We are counting
on you.

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 ·

← → · T pause · R reset · ? help
--:-- | total --:--
Keyboard Shortcuts
Navigate← →
Pause / Resume timerT
Reset timersR
This panel?