Clear decision rights: what the team decides itself and when leadership becomes involved.
self-organisation
Self-organisation: responsibility where the work is
Self-organisation is not an end in itself
Well-organised teams know what needs to be done and do not have to wait for a decision. The customer notices first – the external customer who needs a commitment, and the internal customer waiting for the neighbouring department’s work. If every query must first reach a manager, the customer loses time that nobody can recover later. In the end, it comes down to a simple question: who may decide so that the work can continue?
Self-organised teams decide on sequence, allocation and approach within a clear framework. They need goals, boundaries, metrics and escalation paths. The manager sets and maintains that framework instead of taking every individual decision. This means everyone knows what to do – including at the interface with the neighbouring department.
Whether this is called agile or Lean is secondary. Both have the same roots: short cycles, visible work and responsibility within the team. Kanban boards and shop floor boards create transparency; retrospectives and CIP cycles both learn from what did not work.
Sound familiar?
Responsibility is meant to move into the team, but decisions still land higher up.
What you get
Teams that take responsibility, and managers who allow them to do so:
Shorter paths for customer issues: clarity on who in the team may decide directly when time matters – towards the customer and the neighbouring department.
A pilot team that tests the new way of working with support.
Managers who set and maintain the framework instead of making every individual decision.
Frequently asked questions
Self-organisation: common questions
Does self-organisation mean the manager no longer decides anything?
No. The manager still decides, but decides different things. They set the goals, define the boundaries within which the team may work and determine when they need to be involved. Within that framework, the team decides.
How do we know which decisions belong in the team and which do not?
We review the decisions that actually arise in daily work and sort them into three groups: the team decides alone; the team decides and informs; leadership decides. The guiding question is simple: who bears the consequences and can correct them? That person or team should also be allowed to decide. The result is recorded in writing; otherwise, the first conflict starts the negotiation all over again.
Is it enough simply to give the team the decision?
No. Authority without resources is an empty promise. Information, clear boundaries and time – if any one is missing, the decision moves back up the hierarchy.
What if the team does not want the responsibility?
That happens, and there is usually a reason. Responsibility may have been delegated before and taken back after the first mistake – in that case, caution is a sensible response. We first clarify what lies behind it and start where the team already makes decisions without calling it that. Once people experience that their own decision stands, they take the next one voluntarily.
Does this work in production in the same way as in the office?
Yes, but the decisions differ. In production they concern sequence, staffing within the shift, responses to disruptions and smaller material issues. In the office they concern prioritisation, responsibility for customer enquiries and coordination with other departments. The framework is therefore defined separately for each team.