Autonomy doesn’t mean doing whatever you want

We talk a lot about the virtues of autonomous teams. In fact, the whole point of a microservices architecture to enable team autonomy.

But autonomous teams still follow the overall mission and standards. It’s precisely following the mission and standard that make autonomy possible.

One of the pivotal moments in military doctrine history was the realization that units didn’t have to run every change in condition through their central command. Armies that required this couldn’t react fast enough to changing conditions and so units were empowered to react.

This only worked because the units were keyed into the commander’s intent. You couldn’t have units running off carrying out their own missions.

You’ve achieved autonomy when anyone at the org would make the same decision given the same circumstances. Autonomy is born out of unity in purpose and practice.


Like this message? I send out a short email each day to help software development leaders build organizations the deliver value. Join us!


Get the book!

Ready to learn how to build an autonomous, event-sourced microservices-based system? Practical Microservices is the hands-on guidance you've been looking for.

Roll up your sleeves and get ready to build Video Tutorials, the next-gen web-based learning platform. You'll build it as a collection of loosely-coupled autonomous services, developing a message store interface along the way.

When you're done, you'll be ready to contribute to microservices-based projects.

In ebook or in print.