Leader
We serve. We enable. We coach.
For the short version, click here.
Leadership happens at all levels.
Product Owners lead desired outcomes. Customer jobs to be done. Struggling moments.
Product Developers lead craft and engineering toward those outcomes.
Adaptiveness Guides lead change toward those outcomes.
They all lead.
But quite often, there's also a distinct Leader role.
Organizational managers. Executives. Those who create the organizational context within which the other roles operate.
This philosophy is both:
The foundation. The container. The principles that underpin all leadership.
And the specific capabilities of those in formal leadership positions.
Leadership is service. At all levels.
We serve the team.
Not the other way around.
We exist to help them succeed.
But service means knowing when help is welcome.
Not inflicting help. Offering it.
This is true whether you're a Product Owner leading outcomes, a Product Developer leading craft, an Adaptiveness Guide leading change, or a Leader creating organizational conditions.
Leadership is not authority. It's service.
On Leadership as Service
Leadership is service.
We serve those who build the product.
We lead from the front. The sides. The back.
Depends on the situation.
Sometimes we clear the path ahead. Sometimes we support alongside. Sometimes we follow and protect.
We remove obstacles. We provide clarity. We create conditions for success.
We don't lead from authority. We lead through service.
Our job is to make their job possible.
When they succeed, we succeed. When they struggle, we help.
But we don't inflict help on people.
We offer it. We make it available. We ask if it's wanted.
Unless it's a negative chaos situation. Then we act.
This isn't soft. It's essential.
Empowered teams need enabling leaders.
Leaders who clear the path. Who provide resources. Who protect focus.
We work for the team. They don't work for us.
This is the foundation.
On the Distinct Leader Role
Leadership happens at all levels.
Product Owners lead. Product Developers lead. Adaptiveness Guides lead.
But quite often, there's also a distinct Leader role.
What makes it distinct?
Organizational scope. We create the context within which all roles operate.
Budget authority. We allocate resources across teams and initiatives.
Hiring and succession. We build the organizational capability for the future.
Strategic alignment. We connect work to business outcomes and market realities.
Policy and process. We establish organizational norms and remove organizational impediments.
Broad engagement. We work across the organization, not just within teams.
Culture gardening. We shape the environment. The climate. The conditions.
This is different from leading product outcomes. Different from leading craft. Different from leading change.
But it depends. Some leaders do both.
It's creating the organizational container within which those forms of leadership thrive.
We don't do their jobs. We make their jobs possible.
Product Owners need clarity on strategy. We provide it.
Product Developers need protected time for craft. We protect it.
Adaptiveness Guides need organizational support for change. We create it.
The distinct Leader role is about organizational conditions.
But the principles? Service. Enablement. Coaching.
Those are universal. Those apply to all leadership.
At all levels.
On Removing Obstacles
Obstacles block progress.
We remove them. The ones beyond the team's control or influence.
When requested. When needed.
Not all obstacles. The team can handle many themselves.
But some require organizational authority. Budget. Policy. Politics.
These are ours.
Technical obstacles beyond the team's reach. Organizational obstacles. Political obstacles.
Slow processes they can't change. Unclear decisions they can't resolve. Missing resources they can't acquire.
Dysfunctional meetings they must attend. Conflicting priorities from above. Communication breakdowns across departments.
We identify them when the team asks for help.
Or when we see the team blocked by things beyond their influence.
We remove them. We prevent new ones.
We don't wait for someone else. This is our job.
The team shouldn't spend energy fighting organizational battles they can't win.
They should spend energy building great products.
We handle the organizational friction.
We clear the path.
But we don't assume every problem needs our intervention.
We ask: "Is this something you need help with? Or something you can handle?"
We offer help. We don't inflict it.
Unless it's negative chaos. Then we act.
On Understanding the Work
We understand the work.
Not just "what" the team builds. But "how" they build it.
The code. The design. The architecture. The testing. The deployment.
The tools. The practices. The constraints. The trade-offs.
We know how the work works. And we know how the customer works.
Not just what customers want. But how they actually work. Their workflows. Their context. Their constraints.
We don't need to be the best coder. But we need to understand coding.
We don't need to be the best designer. But we need to understand design.
We pair with the team. We read the code. We review the designs.
We understand the technical decisions. The architectural constraints. The quality practices.
We know enough to ask good questions.
"Why this architecture?" "What's the trade-off here?" "How does this scale?"
Not to second-guess. To understand. To learn. To coach better.
When we understand the work, we can:
Identify real obstacles. Not imagined ones.
Coach on actual challenges. Not generic advice.
Remove meaningful blockers. Not superficial ones.
Recognize good work. Not just completed work.
We stay technical. We stay current. We stay curious.
The work changes. We learn with the team.
We can't lead what we don't understand.
On Providing Clarity
Ambiguity paralyzes teams.
We provide clarity.
What are we building? Why does it matter? How do we know we're succeeding?
We quantify what success looks like. Tom Gilb style.
Not vague aspirations. Specific, measurable, testable statements.
"Improve performance" becomes "Reduce page load time from 3s to 1s by Q3."
"Better user experience" becomes "Increase task completion rate from 60% to 85%."
Quantification creates clarity. Numbers make ambiguity impossible.
We translate strategy into action. Ambiguity into direction. Complexity into simplicity.
We communicate context constantly.
Not once. Not in a document. Constantly.
In conversations. In decisions. In questions we ask.
We connect today's work to tomorrow's vision.
We help the team understand what matters and what doesn't.
We align stakeholders so the team doesn't have to.
We navigate organizational politics so they can focus on building.
Clarity enables focus. Focus enables excellence.
But clarity doesn't mean fixed.
Strategy is continuous adaptation. Not a fixed plan.
We learn from evidence. We adjust strategy.
What are customers telling us? What are competitors doing? What's changing?
What are we learning from experiments? From releases? From failures?
Strategy adapts based on evidence.
We provide direction with clarity. But we nurture emergence.
The team discovers how to get there. Solutions emerge from the work.
We don't prescribe every step. We clarify the direction of travel.
We adapt strategy frequently. Not just annually. Continuously.
Small adjustments weekly. Larger pivots when evidence demands.
We make adaptation visible.
"Here's what we learned. Here's how strategy adapts. Here's why."
Not "I changed my mind." But "evidence changed, strategy adapted."
We balance clarity with responsiveness.
Too much rigidity kills adaptation. Too much fluidity kills focus.
Clear direction. Emergent solutions. Adaptive strategy.
On Coaching
We help people to grow.
Not by telling. By asking.
Not by solving. By developing capability.
We coach when it's welcome. When it's appreciated.
We offer coaching. We don't force it.
We ask: "Would it be helpful if we talked through this?"
We create space for coaching. We don't impose it.
When coaching is welcome, we coach.
"What do you think?" Not "Here's what to do."
"What did you learn?" Not "Here's what you should have done."
"What will you try next?" Not "Try this."
We ask questions that develop thinking.
We give feedback that accelerates growth.
We create learning opportunities. We pair people for knowledge transfer.
We provide challenge and support.
Challenge without support is cruel. Support without challenge is comfortable stagnation.
We provide both.
But only when it's wanted.
We also help people become more coachable.
Awareness of how they receive feedback. How they respond to questions. How they engage with challenge.
Coachability is a skill. We help develop it, in ourselves and others when needed.
Forced coaching isn't coaching. It's control.
We develop skills through practice, feedback, and reflection.
We make people better. Better technical skills. Better collaboration. Better thinking.
But only if they want to grow. We can't force growth.
Growing people grows outcomes.
On Customer Engagement
We engage with customers directly.
Not just through reports. Not just through product owners.
We watch customers use the product. We hear their problems firsthand.
We understand their context. Their constraints. Their workarounds.
We see what delights them. What frustrates them. What they actually need.
This isn't the product owner's job alone. It's ours too.
We join customer interviews. We observe user sessions. We read support tickets.
We talk to customers at conferences. We visit customer sites. We use our own product.
We understand their needs and their limits.
What they can't do. What they won't tolerate. What they'll pay for.
When we understand customers, we can:
Provide better strategic clarity. Grounded in reality, not assumptions.
Help the team make customer-informed decisions.
Identify value opportunities. Not just build requests.
Recognize when we're drifting from customer needs.
We don't filter customer knowledge through others.
We acquire it firsthand. Continuously.
Customer engagement isn't delegation. It's leadership.
On Climate Gardening
We garden the climate.
Not command it. Not decree it. Garden it.
Like a garden, climate requires continuous care.
We tend it daily. We nurture growth. We protect from harm. We prune what damages.
We look after how it feels to work here.
This is our most important work.
We foster humane performance climate.
Not just high performance. Humane performance.
Performance that sustains people. That respects limits. That values humans.
High performance that burns people out isn't performance. It's extraction.
We watch for signs of climate degradation.
People stopping speaking up. Fear replacing trust. Blame replacing learning.
Overwork becoming normal. Shortcuts becoming standard. Quality becoming optional. Building faster than we can go live.
We act immediately when we see these.
Not "we'll address it later." But "we address it now."
Teams need safety to perform.
Not comfort. Safety.
Safety to speak up. Safety to disagree. Safety to fail. Safety to learn.
We create this.
We listen without judgment. We respond to dissent with curiosity.
We normalize failure as learning. We talk about experiments that fail, and learnings from those. We're not naive.
We model vulnerability. We admit our own mistakes.
We call out behavior that threatens safety. Blame. Mockery. Dismissiveness.
We protect voices that need protecting. Quiet team members. Junior people. Dissenters.
We don't punish honesty. We reward it.
When someone says "I don't know," we say "let's learn together."
When someone says "I disagree," we say "tell me more."
When someone says "I failed," we say "what did you learn?"
We protect the climate from toxicity.
Blame culture. Hero culture. Crunch culture. Perfectionism. Burnout.
We remove people who damage the climate. Even if they're productive.
One toxic high performer damages the whole climate. One person offering only "lip change" to change can do the same. We don't tolerate it.
We nurture climate through small actions.
Celebrating learning from failure. Recognizing collaboration. Protecting focus time.
Saying "take time off" and meaning it. Modeling work-life balance. Respecting boundaries.
Asking "how are you?" and listening to the answer.
Climate compounds.
Small positive actions daily create healthy climate.
Small negative actions daily create toxic climate.
We're deliberate about which we're compounding.
Psychological safety enables truth. Truth enables improvement.
Without safety, teams hide problems until they explode.
With safety, teams solve problems before they grow.
We measure climate. Psychological safety surveys. Turnover. Energy levels. Team health.
Climate is our most important work.
Products can be rebuilt. Climate once damaged is hard to restore.
We protect it. We nurture it. We garden it.
Every. Single. Day.
On Systems Thinking
We think in systems. Not just tasks.
We see the whole. The connections. The feedback loops.
We optimize for flow, not utilization.
We measure what matters, not what's easy to measure.
Work Item Aging. At every flowing level. How long is work sitting?
The older work gets, the more likely it will get older.
Age—how long it's been since in-progress work started—is a leading indicator for elapsed time to finished.
Old work could be a signal of a problem. Helps observers notice issues before they get out of hand.
We track it. We interpret it. We act when it's signal, not noise.
Customer and other stakeholder sentiment. How do people feel about the product? The experience? The relationship?
Value. Are we creating it? Capturing it? Sustaining it?
We have more specific measurement recommendations depending on the context.
Different teams. Different products. Different stages. Different measures.
What matters for a new product differs from a mature one. What matters for platform differs from customer-facing.
We measure what helps us learn and adapt.
We understand that local optimization often creates global dysfunction.
A team at 100% utilization has no capacity to respond. No slack for learning. No space for improvement.
We create slack. Deliberately.
Slack enables responsiveness. Enables learning. Enables excellence.
We make work visible. What's in progress? What's blocked? What's waiting?
We limit work in progress. Focus finishes things. Multitasking creates delays.
We identify bottlenecks. We don't add capacity everywhere. We add it where it matters.
We see second-order effects. This change helps here but hurts there. Is the net positive?
We think long-term. Quick wins that create long-term pain aren't wins.
Systems thinking prevents us from solving problems in ways that create bigger problems.
On Waste & Anti-patterns
We understand waste.
Not just obvious waste. All non-value-add waste.
Waiting. Handoffs. Rework. Partially done work. Over-production. Over-processing.
Motion. Transportation. Defects. Skills underutilization.
We study waste in our organization.
Where do things wait? Where do handoffs create delays? Where do we rework?
Where do we build things nobody uses? Where do we over-engineer?
Where are talented people doing work below their skill level?
We make waste visible.
Not to shame. To improve.
We recognize anti-patterns.
Hero culture. Depending on individuals, not systems.
Crunch mode. Chronic overwork as normal.
Analysis paralysis. Studying forever, deciding never.
Premature optimization. Optimizing before understanding.
Death marches. Impossible deadlines creating predictable failure.
Meeting culture. Discussing work replacing doing work.
We name these when we see them.
"This is hero culture. Here's why it's harmful. Here's what we'll do instead."
We teach the team to see waste and anti-patterns.
Not just us seeing them. The whole team seeing them.
Waste and anti-patterns become common language.
"That's partially done work piling up." "That's hero culture emerging."
When everyone can name it, everyone can address it.
We eliminate waste systematically.
Not randomly. Systematically.
Measure it. Prioritize it. Address it. Verify improvement.
We don't tolerate recurring anti-patterns.
If we see the same pattern repeatedly, we change the system.
Pattern: "We always rush at the end." System change: "We limit work in progress and protect slack."
Pattern: "Quality suffers under pressure." System change: "We make quality non-negotiable and adjust scope."
Understanding waste and anti-patterns is fundamental leadership knowledge.
Can't improve what we can't see.
On Team Autonomy
Autonomy drives motivation.
We give teams autonomy over how they work.
Not what they achieve. Not why it matters. But how they get there.
They choose their practices. Their tools. Their processes.
They decide how to split work. How to collaborate. How to improve.
We provide guardrails, not recipes.
Outcomes matter. Methods are negotiable.
We trust the team to figure out how.
When we see problems, we ask questions. We don't impose solutions.
"What's blocking you?" Not "Do it this way."
"What have you tried?" Not "Here's what worked for me."
"What would help?" Not "I'll tell you what to do."
Autonomy requires competence. We build competence through coaching.
Autonomy requires clarity. We provide clarity through context.
Autonomy with competence and clarity creates ownership.
Ownership creates excellence.
On Evidence-Informed Leadership
We lead with evidence.
Not just intuition. Not just experience. Evidence.
We acquire knowledge empirically.
What actually works? What actually creates value? What actually matters?
We test our assumptions. We measure our impacts. We learn from data.
We identify where value can be harvested.
Where is value being created but not captured?
Features built but not used. Improvements made but not noticed. Waste removed but value not realized.
Opportunities seen but not pursued. Customer needs known but not addressed.
We make this visible.
"Here's where value exists. Here's how we harvest it. Here's what we learn."
We study behaviors and habits.
Team behaviors: What creates flow? What creates friction?
Customer behaviors: What drives adoption? What causes churn?
Organizational habits: What enables speed? What creates delay?
We don't assume. We observe. We measure. We learn.
We experiment deliberately.
Hypothesis: "If we [change], then [outcome] because [reason]."
We test. We measure. We learn. We adapt.
We share evidence transparently.
Not to prove we're right. To learn what's true.
"Here's what we thought. Here's what we learned. Here's what changes."
Evidence-based leadership means:
Admitting when we're wrong. Changing approach when evidence contradicts us.
Testing before scaling. Learning from failures. Building organizational knowledge.
We don't lead by gut. We lead by evidence.
But we act on evidence, not just collect it.
Insight without action is waste.
On Organizational Alignment
The team doesn't exist in isolation.
We connect them to the organization.
We align stakeholders. We manage dependencies. We communicate upward and outward.
We translate between the team and the organization.
From team to organization: "Here's what we're learning. Here's what we need. Here's our progress."
From organization to team: "Here's the strategy. Here's the context. Here's what matters."
We represent the team in meetings they shouldn't attend.
We shield them from organizational dysfunction.
We amplify their voice to leaders.
We ensure their good work is visible.
We fight organizational battles they shouldn't fight.
Budget battles. Priority battles. Political battles.
They build the product. We handle the organization.
On Broad Engagement
We engage broadly.
We are outside-in and inside-out change agents.
Outside-in: We bring market forces, customer needs, industry trends into the organization.
Inside-out: We build organizational capability, culture, and change from within.
Both matter. Both required.
Not just our team. Customers. Colleagues. Partners.
We engage with customers. Directly, as noted earlier.
We engage with colleagues across the organization.
Other teams. Other departments. Other functions.
Engineering. Product. Design. Marketing. Sales. Support. Operations.
We build relationships. We understand their work. We identify collaboration opportunities.
We don't wait for formal processes to connect.
We reach out. We ask questions. We offer help.
"What are you working on? What's blocking you? How can we help?"
We facilitate cross-team collaboration.
Our team needs something from another team? We don't just send email.
We connect people. We facilitate conversations. We remove organizational friction.
We identify systemic opportunities.
Problem we see repeated across teams? We bring teams together to solve it once.
Practice working well in one team? We help spread it.
We engage externally.
Conferences. Communities. Open source. Industry groups.
We learn from outside. We bring ideas back. We share what we learn.
We make engagement visible.
"Met with Team X, learned Y, opportunity Z."
We model broad engagement for the team.
They see us engaging widely. They engage widely too.
Engaged leaders create engaged teams create engaged organizations.
We don't lead in isolation.
We lead in connection.
On Continuous Improvement
We help teams get better at getting better.
We walk the gemba with curiosity, empathy, and a desire to help.
What's working? What's not? What will we change?
We make it safe to surface problems. We ensure changes actually happen.
We track improvement over time. Not just "we discussed problems." But "we solved problems."
We encourage people to experiment with new approaches.
Try pair programming. Try mob programming. Try different ceremonies.
Measure the impact. Keep what works. Discard what doesn't.
We spread good practices.
Team A discovers something useful? We help Teams B and C learn from it.
We measure what matters.
Cycle time. Lead time. Deployment frequency. Quality. Team health. Stakeholder sentiment (including but not limited to customer).
Not story points. Not hours worked. Not lines of code.
We optimize for outcomes, not outputs.
We improve systems, not just fix symptoms.
Bug rate high? Don't just fix bugs. Fix what creates bugs.
Deployments risky? Don't just deploy carefully. Make deployments safer.
Meetings ineffective? Don't just run them better. Eliminate unnecessary ones.
Continuous improvement compounds.
Small improvements weekly create massive change yearly.
On Responsiveness
We develop responsiveness.
The ability to respond quickly to change. To new information. To customer needs.
Responsiveness is competitive advantage.
Responsiveness requires capability.
Technical capability: Can we deploy quickly? Change safely? Test rapidly?
Organizational capability: Can we make decisions fast? Pivot when needed? Learn quickly?
We remove barriers to responsiveness.
Approval delays. Handoff friction. Dependency bottlenecks.
Long release cycles. Manual processes. Unclear authority.
Complex product organization. Bloated workflows. Over-engineered processes.
We descale. We simplify. We declutter.
Like descaling a kettle with vinegar. Remove the buildup that slows everything down.
Product organization. Workflows. Processes. Systems. Organization designs.
Remove what slows us down. Simplify what remains.
We create slack for responsiveness.
Teams at 100% utilization can't respond. They can only execute the plan.
We protect slack. Twenty percent minimum. For learning. For responding. For adapting.
Time to learn. Time to experiment. Time to help each other. Time to innovate.
We enable flow across value networks.
Not just within our team. Across teams. Across departments. Across the value chain.
Where does work get stuck between teams? We fix it.
Where do handoffs create delays? We eliminate them.
Where do dependencies block flow? We resolve them.
We make flow visible.
Value stream mapping. Lead time tracking. Bottleneck identification.
We optimize the whole, not the parts.
One fast team in a slow system doesn't help customers.
We improve flow end-to-end.
Responsiveness means:
Deploying when we learn, not when the schedule says.
Pivoting when evidence changes, not when the plan allows.
Responding to customers quickly, not eventually.
Adapting strategy continuously, not annually.
We measure responsiveness:
Lead time. How fast from idea to customer?
Deployment frequency. How often can we release?
Time to restore. How fast can we fix?
Decision speed. How fast can we adapt?
We are responsive leaders in responsive organizations.
Not just stable. Responsive.
On Growing People
Our most important work is growing people.
Better people create better outcomes.
We develop technical skills. Coding. Design. Testing. Architecture.
We develop product skills. Discovery. Prioritization. Metrics. Customer understanding.
We develop collaboration skills. Communication. Facilitation. Conflict resolution. Feedback.
We create growth opportunities.
New technologies. Different roles. Leadership chances.
We give feedback frequently. Not just in reviews.
Feedback on what's working. Feedback on what to improve. Specific. Actionable. Kind.
We recognize growth publicly. We coach development privately.
We help people understand their strengths. Their growth areas. Their potential.
We support career development.
Not everyone wants to be a manager. Some want deep technical expertise. Some want product thinking. Some want breadth.
All paths are valuable. We support all paths.
We don't hoard talent. We grow people even if they'll eventually leave.
Better to have someone great for two years than someone mediocre forever.
Growing people is our legacy.
The products we build will be replaced. The people we grow will grow others.
On Succession Planning
We plan for succession. Deliberately.
Not because we're leaving. Because it's essential.
We identify potential successors. Multiple, not just one.
We grow their capability. We give them opportunities. We delegate real authority.
Not token delegation. Real ownership.
Not just delegation. Devolution. Distributed leadership.
Like the UK Parliament devolving power to the parliaments of Wales and Scotland.
Not delegation where Westminster can take it back. Devolution where they own it.
Leadership distributed across the team. Not concentrated in one person.
Multiple people leading in different areas. Different decisions. Different contexts.
They run retrospectives. They facilitate alignment. They remove obstacles.
They make decisions. They represent the team. They coach others.
We create space for them to lead while we're still here.
Not "wait until I leave." But "lead alongside me now."
We teach what we know. We share our networks. We expose our thinking.
"Here's why I made this decision. Here's what I considered. Here's what I learned."
We document our work. Not to control from afar. To enable continuity.
We protect the climate through succession.
Successors who understand humane performance. Who value psychological safety.
Who know the difference between pressure and support.
Making ourselves replaceable isn't a threat. It's the goal.
Irreplaceable leaders create fragile organizations.
Replaceable leaders create resilient ones.
When we can be replaced, we can:
Take vacations without guilt.
Move to new challenges.
Scale our impact. Multiple teams. Multiple products.
Know the team will thrive without us.
We measure success by the leaders we grow.
Not just the products we ship.
Succession planning protects everything we've built.
The culture. The practices. The values. The performance.
We don't wait until we're leaving to think about succession.
We build succession capability every day.
On Problem Space Understanding
We understand the problem space.
Not just solutions. Problems.
What problems do customers face? What problems does the organization face? What problems does the team face?
We resist jumping to solutions.
"What's the real problem?" comes before "What's the solution?"
We study problems deeply.
What causes this? What makes it hard? What have others tried? What didn't work? Why?
We distinguish symptoms from root causes.
Symptom: "Deployments are risky."
Root cause: "We lack automated testing and deploy large batches infrequently."
We solve root causes, not symptoms.
We identify opportunities in the problem space.
Problems are opportunities. Unmet needs are opportunities. Friction is opportunity.
We make opportunities visible.
"Here's a problem customers face that we could solve."
"Here's inefficiency in our process we could eliminate."
"Here's capability we could build that would unlock value."
We help the team understand problems before building solutions.
Not "build this feature." But "solve this problem."
Feature thinking creates feature factories. Problem thinking creates value.
We validate problem understanding.
Do customers actually have this problem? How big is it? How often? What's the impact?
We don't assume problems. We verify them.
Understanding the problem space means:
Knowing customer problems deeply.
Recognizing organizational problems clearly.
Identifying opportunities systemically.
Validating before solving.
Teaching teams to understand problems first.
We lead in the problem space.
Solutions emerge from understanding.
On Knowing When to Quit
We know when to quit ideas.
Not missions. Not people. Not values.
Ideas that aren't working.
Strategies that evidence shows are failing.
Initiatives that consume resources without delivering outcomes.
We don't confuse persistence with wisdom.
Persistence on a failing approach wastes energy and opportunity.
We help teams see when to pivot. When to stop. When to redirect.
The sunk cost fallacy is real. We resist it.
What we've already invested doesn't justify continued investment.
We assess: is this still the right path? Does evidence support continuing?
If not, we change course.
We make it safe to abandon approaches that aren't working.
We treat pivots as learning. Not failure.
Quitting the wrong thing at the right time creates space for the right thing.
This requires courage. Judgment. Honesty about what's not working.
We model this ourselves.
When our own ideas fail, we let them go.
We show teams: changing your mind when evidence changes is strength.
On What We Don't Do
We don't command. We coach.
We don't control. We enable.
We don't hoard information. We share context.
We don't protect our authority. We give it away.
We don't solve every problem. We build capability to solve problems.
We don't blame the team for organizational dysfunction.
We descale, simplify, and declutter workflows, processes, systems, and organization designs.
We don't shield leadership from reality. We go to the gemba with a spirit of empathy and curiosity.
We don't create work for ourselves by taking away team autonomy. We ask teams how can we help.
We don't measure what's easy. We measure what matters.
We don't optimize for our comfort. We optimize for team success.
We don't create dependencies on ourselves. We build self-sufficiency.
We don't lead from behind closed doors. We lead in the work.
These are choices.
Daily choices.
The Work
This is leadership in empowered teams.
Not heroic leadership. Leadership as service.
Not commanding. Enabling.
Not controlling. Trusting.
We look after how it feels to work here. We garden the climate.
We acquire knowledge on the work, customers, waste, anti-patterns, evidence.
We understand how the work works. We engage customers directly. We engage broadly.
We adapt strategy continuously from evidence. We nurture emergence with direction.
We develop responsiveness and flow across value networks.
We remove obstacles. We provide clarity. We coach.
We build humane performance climate. We think in systems.
We give autonomy. We align organization. We drive improvement.
We grow people. We grow successors.
We lead with evidence. We understand problems before solutions.
This is harder than traditional leadership.
It requires more humility. More listening. More trust. More knowledge. More engagement.
But it's better.
Better for the team. Better for outcomes. Better for sustainability. Better for humans.
This is what empowered means.
Not that teams do whatever they want.
But that we create conditions for them to do their best work.
We remove obstacles. We provide resources. We give clarity.
We acquire knowledge. We engage broadly. We adapt continuously.
We trust them to solve problems. We grow their capability to solve harder problems.
This is the work.
This is what we do.
This is who we are.
In Closing
We're leaders.
We serve.
We measure our success by their success.
We look after how it feels to work here. We garden the climate daily.
We acquire knowledge. On the work. On customers. On waste. On evidence.
We engage broadly. Customers. Colleagues. Stakeholders.
We adapt strategy continuously. From evidence. With direction.
We develop responsiveness. Across value networks.
We grow people. We grow systems. We grow successors.
We remove obstacles. We understand problems. We lead with evidence.
We create clarity from ambiguity.
We build capability through coaching.
We enable autonomy through trust.
We foster humane performance culture.
Everything serves the team.
Their growth. Their success. Their impact. Their wellbeing.
This is the work.
This is what we do.
This is who we are.
Anyone can be a leader.
A Product Owner should be a leader of the product.
People doing the work should lead in how they do it.
Managers should be leaders.
So if you see overlap between this and other roles, we're glad you see that.
But it also means we expect more.
The superset of your role and leader.
It's a big ask.
We are raising the bar.
We are going for it. Really going for it.
Are you?
Leaders. Servants. Enablers. Coaches. Climate gardeners. Knowledge acquirers. Customer engagers. Evidence-informed practitioners. Succession planners. Responsiveness developers. System thinkers. People developers.
Share:
Leader –– The foundation for all leadership. At all levels. And the distinct role of organizational leaders.
Roles and How They Work Together –– Leader, Stakeholder, Product Owner, Product Developer, Adaptiveness Guide