Ales Nosek - The Software Practitioner

Helping you navigate the world of Kubernetes.

Jul 4, 2016 - Comments - reading

What I Learned From the Open Organization

Red Hat is one of the most successful software companies that makes billions of dollars selling open source software. The book The Open Organization written by Jim Whitehurst, CEO of Red Hat, provides a great insight into the company culture and how things get done at Red Hat. This blogpost lists some of the ideas I learned from this book.

Motivating and inspiring

  • A company should have a purpose. The purpose is not a goal a company wants to achieve but the reason why it exists. For instance, Red Hat’s mission statement says: To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. This statement enables Red Hat to attract the most talented people that share the belief that open source is fundamentally good for the world.

  • It’s important to hire passionate people. When interviewing, ask the candidates what they are passionate about and think how it resonates with the purpose of your company.

  • Admitting mistakes builds your credibility and authority to lead.

  • As a manager, if you want to have engaged employees, you need to share context and knowledge. Be prepared to explain your decisions.

  • As an employee, if your manager is not providing the appropriate context, ask for it. Most bosses are happy to share. They just haven’t yet figured out that it belongs to what they should be doing.

Getting things done

  • The Open organization embraces meritocracy where the leaders are chosen based on their contributions to the project, not based on their titles or longevity within the company.

  • If your intention is just to stick your nose into every little thing so you can be front and center, people see it. At Red Hat, one of the greatest insults to your ego comes when you put something on one of the internal discussion threads and receive nothing back - neither positive nor negative. That means the team is likely ignoring you, which means you’ve failed in some way.

  • In the discussions, people argue and criticize not because they are trying to be difficult, but because they are so passionate about the subject. A debate involving multiple views from different people leads to better decisions made than a meeting where the goal for everyone is to be nice to each other, and every idea is treated as a good one.

Setting direction

  • The decisions that came from top down are typically harder to turn into real actions. The more open you make your decision-making process, the easier is to execute the decisions you made.

  • Encourage your team to bring up ideas and proposals. Discuss the ideas, regardless of whether you move forward with them.

Deploying Kubernetes on Openstack using Heat Red Hat Summit 2016

comments powered by Disqus