Knowledge is power

There are a lot of different books and blogs that cover a range of different aspects of the DevOps movement, but there are few and far in between where you can find a good concentration (a hub) of different approaches, an all-inclusive collection of tools and techniques to route your company into the successful DevOps tack. I’d like to be very blunt and explicit that when I talk about tools, in fact, I mean the “human” tools and not the technical/technology ones.

People don’t want to talk much about human interactions because it is tough, fluffy and hard to measure. It is hard to find people that know how to execute this properly and hard to get a reasonable and valuable feedback on your own progress.

Over the last two decades there has been a surge in understating the human nature in depth. Now we’re have the technology that allows us to peek into the human brain, explain and understand human psychology and behavior on the physical and chemical levels. We’ve accumulated years of scientific research that proves that this knowledge becoming essential to the success of the companies and organizations. Without understanding these “human tools” and without introducing them into the organizations — it’s impossible to succeed. It is important to understand organizations on macro and micro levels. It’s important to understand people as well as the teams, what drives them and what motivates them. All the successful organizations are applying this knowledge in some sort or fashion (to name the view: Netflix, Amazon, Facebook, Hubspot).

It looks simple and obvious to many of us, but there is a lot of science that support all these initiatives. I feel passionately and strongly that it is very important to put a lot of effort and emphasis on making this knowledge as widely adopted as possible.

Usually when we start to “work on human interactions” we use the tools like workshops and team building. Notice the words we use refer to it as work. It still sounds like a hard work. And there are a very good reasonz for that. It is very hard indeed.

So without further adieu and within DevOps’y spirit of Kaizen (continuous improvement), I’ll start flushing my thoughts and experience into the series of articles about a range of interrelated topics and themes about building successful software companies.

I’ll show different approaches for both changing teams’ culture and development processes. What are the relations between them and how all these techniques and approaches related and lead to one another.

Credit for cartoon: