Many companies have started searching for self-organisation. That ideal or nirvana where teams can figure out how to work together effectively with limited or little direction to solve problems.
Many, including some of my colleagues, believe that this search for self-organisation is ultimately fruitless. While many of our customers don’t initially believe in its existence because they have never seen it my colleagues think it impossible because they see company after company fail to achieve it. This is mostly as companies that call use are not ding so because they are awesome but instead because they see that they have some problem that needs looking into. These companies, while realising the need to change, tend to have an organisational structure and culture that presents an anti-pattern for self organising teams to ever exist. Oh, you will occasionally find small pockets of self-organisation within an organisation but if anyone tries to roll this dynamic out, it is ultimately demonstrated as unworkable due to those anti-patterns and those required traits and patterns are then ground out of people.
Realism dictates that we need to move slowly towards self-organisation in a way that will build up the self esteem of teams and create an environment for them to thrive. But the organisation also needs to have courage and conviction in order to realise it as the path to agility is a bumpy one and long, depending on how traditional they are to begin with.
Why self-organisation at all?
If we don’t have self-organisation then don’t we have our least skilled and appropriate individuals (project managers) determining how, when and were any work should be completed. Should we not have the knowledgeable and skilled professionals that we hired to do the job of developing the product decide on the how, when and where?
If we don’t have self-organisation then how can we hope to hold the Development Team accountable for delivering the work? They can always blame the organiser!
If we don’t have self-organisation then how do we know how much time should we spend on training of new individuals? Do we guess at their current skills or evaluate them with standardised tests that have done so well for our school system? Or should we not rely on their peers to make sure that each team member has the skills and knowledge required to help the Development Team deliver…
Without self-organisation how do we effectively encourage individuals to work as a team and be responsible for the results?
Encouraging self-organisation
There are many thing that can impact your ability to get to self-organising teams. Here are a few items to ponder:
- Team Accountability – Moving from Individual accountability for tasks, to collective accountability can improve both the team dynamics and the management of those teams. Peer-pressure within teams and a clear but slight pleasure to deliver can reduce any concerns around collective under performance.
- Team Identity – Although related to accountability, organisations wants to aspire to achieve high-performing teams which is impossible without a team identity. This identity is the same ideal that sports teams strive for and results in a camaraderie that is part of any high-achieving team. Team should be expected to move through Tuckman’s stages of group development (Forming | Storming | Norming | Performing).
- Small Teams – Creating dedicated teams of 6+-3 people will allow you to manage the complexity of the work and the people more effectively. A team should work from a single ordered backlog so that they get good at working together, understanding the backlog, and delivering. You may need multiple teams to work through the backlog at a rate that is acceptable to the customer but you should see significantly better results with many small teams than fewer large teams.
- Consistent Teams – If you are forever inter-changing team member then you will be forever re-forming and never even enter storming let alone getting to performing. If you cant get to performing then high-performing is totally out of reach. Stop thinking in individual allocation to projects and start thinking about team allocation to projects. This will also help reduce your management overhead and improve your communication by removing layers between the customer and the team.
Remember that the biggest killer of self-organising teams is a manager who just needs to make sure…
Conclusion
Without self-organisation, no matter how much we try, all we can ever have is a glorified collection on individuals that think and operate as individuals. Just like with sports teams we want to have those individuals identify as a team, to work together as a team and function as a team. The only way to achieve this is to have them be a team. You would not want the coach to swap out players on football game for every match? How effective would that be? So don’t do it to your teams…
If you get really good at self-organising teams you may find your organisations formula to high-performing teams…
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Everyone loves the idea of self-managing teams
Explains how self-managing teams thrive with autonomy balanced by structure, highlighting the need for clear goals, accountability, and …
There is no "do agile" there is only "be agile"
Explores the difference between adopting agile practices superficially and truly embracing agile values, highlighting the need for deep …
Does your company culture resemble Survivor?
Explores how individualistic, competitive company cultures hinder collaboration and agility, and highlights the benefits of fostering …
We hear self-managing teams so often it become a cliché
Explains how true self-management in Scrum requires active, disciplined effort from Product Owners, Scrum Masters, and Developers, not chaos …
The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie
Explains why true Scrum requires real team agency, not just self-management in name, and how lacking agency leads to ineffective, …
Unlocking Naked Agility: How Happy Teams Drive Exceptional Products
Explores how team happiness, autonomy, mastery, and purpose drive engagement and lead to higher-quality, more impactful products in agile …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Getting Started with Objectives & Key Results
Learn how to successfully implement OKRs by aligning clear strategy, fostering transparency, empowering teams, focusing on outcomes, and …
Futureproof Leadership: How CTOs Can Cut Through the Noise and Lead with Clarity, Confidence, and Culture
Struggling with tech change? Discover how clarity, evidence, and culture can futureproof your team, no chasing trends, just smart …
From Burnout to Breakthrough: How CTOs Can Lead with Clarity, Resilience, and Real Innovation
Feeling overwhelmed as a tech leader? Discover how to shift from chaos to clarity and build resilient, future-ready teams, without burning …
Human and AI Agency in Adaptive Systems: Strategy Before Optimisation
Explores the distinct roles of human and AI agency in adaptive systems, emphasising human-led strategy and accountability versus AI-driven …
Stop Chasing Trends: How Real Agility and DevOps Build Resilient, Adaptable Teams
Stop chasing trends, build real agility. Discover how DevOps and agile create resilient teams, smoother delivery, and sustainable …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.