Agile culture places enormous emphasis on the team. We talk about collective ownership, shared responsibility, team velocity, and group retrospectives. These are good things. The shift away from heroic individuals and toward collaborative work has made software development more humane and, in most cases, more effective. But somewhere along the way, I started to wonder whether we had inadvertently created a blind spot. In our enthusiasm for teamwork, had we lost sight of individual responsibility?
This was the question I brought to Agila Sverige in 2016, and it is one I have continued to think about since. It is not a comfortable question for the agile community, because it can sound like a step backward — as if advocating for individual accountability means returning to the days of annual performance reviews and stack ranking. That is not what I mean at all. What I am interested in is a more honest reckoning with the fact that teams are made up of individuals, and those individuals bring different levels of skill, commitment, and care to their work.
Collective ownership can sometimes become a kind of diffusion of responsibility. When everyone is responsible, no one feels personally accountable. A bug slips through, and it is the team's problem. A deadline is missed, and the retrospective identifies systemic causes. These are valid observations, but they can also serve as a way to avoid the harder conversation about whether each person is genuinely bringing their best. I do not think this is malicious; it is simply a natural consequence of a culture that emphasizes the group over the individual.
The challenge is to hold both truths at once. Teams matter. Collaboration matters. And individual responsibility matters too. The best teams I have worked with are the ones where each person feels a deep personal commitment to the quality of their work and the well-being of their colleagues — not because a manager is watching, but because they have internalized a sense of craft and care. That kind of accountability does not undermine teamwork; it strengthens it. A team of people who each take their own contributions seriously is far more resilient than one where responsibility is only acknowledged in the aggregate.
I did not offer a neat solution in the talk, and I will not pretend to have one now. This is a tension to be navigated, not a problem to be solved. But I believe it is worth talking about openly. Agile culture at its best is not dogmatic; it is reflective. And reflecting on how we balance the collective and the individual — without swinging too far in either direction — is one of the more important conversations we can have about how we work together.