Autonomy and management: why is an autonomous team not always self-managed?

For weeks I have been facilitating and accompanying the work of teams as Project Manager at Lab9. We add up hours, deliverables, boards, meetings, but what I really observe—like someone calibrating a fine instrument—is when a team begins to move on its own. Not out of inertia, not out of abandonment of leadership, but out of shared conviction.

Not every autonomous team is a self-managed team. Sometimes there are tasks in progress, boards in motion, and deliverables on the way… but that does not guarantee that there is a healthy, conscious or aligned dynamic. Real self-management is something else. It's when a team doesn't need to wait for directions to move forward, but still chooses to communicate. It is when each member knows what they have to do, but also why they do it and for what purpose.

From my role, I am not a passive spectator. I am a facilitator, interpreter, and, many times, mirror. Because there is no self-management possible without certain conditions: clarity, focus, sense of purpose, structure and —yes— follow-up.

A self-managing team is not a team without direction. It is a team that learned to make aligned decisions, with shared criteria. Who knows his limits, but does not confine himself to them. That acts autonomously, not from disconnection, but from commitment to a common purpose. Who knows when to resolve it on his own and when to clearly escalate a problem.

In an environment in which the urgent threatens to devour the important, the greatest act of professional maturity that we can cultivate is this: create clear ways of working that allow teams to make decisions autonomously, without losing direction.

Behind products and services, there are values

Sometimes we focus so much on deliverables that we forget that what a team really delivers is value through a framework.

A product or service may be well made technically, but if it was developed in an environment of wear, isolation or mistrust, sooner or later it will show. Not in the interface, but in the dynamics. Not in the deliverable, but in the equipment that is disassembled inside.

For this reason, in my experience of all these years that I have had to collaborate with different teams, I always return to the same thing: the underlying values—those that are not displayed in the backlog but are lived in each daily decision—are those that determine whether a team advances or only survives and with them the organization.

I mean simple, but deeply strategic things:

• Know how to ask for help, even if we are afraid of appearing untechnical.
• Trust in the expertise of the other, even if that means ceding control momentarily.
• Escalate a decision, not for convenience, but because we understand that its impact transcends the individual.
• Delegate leadership in a meeting, when someone tells their peer—without the need for hierarchies—: “today you will lead”

In my experience, values are not soft skills: they are hard conditions for work to happen in a humane, sustainable and impactful way.

When teams understand that collaborating is not about looking good, but about empowering themselves; Communicating is not about filling Slack with messages, but about knowing what to say, when and for what; When that becomes natural in the team... then yes, true self-management appears.

In each of these daily gestures culture is built. It's not a slogan, it's a practice. And it is that practice that moves organizations forward, much more than any tool, framework or methodology.

And that is why I never tire of repeating it: behind every project that works, there is an invisible network of sustained values. And someone, often silently, who took care of supporting them.