Skip to main content

Experience or Leadership, what is more important

Look across your teams and the people you are trying to hire.  Where are you struggling?  Which teams look just like they did 2 years ago?  Which teams are excelling and providing the most value to your customer?

I bet you have a few teams that have very smart, experienced leaders that work hard.  They have been with you for years and your teams or tech would fail without them.  This is great right?

I propose that your teams are not the real problem.  The problem is the leadership of the teams.  Your team or organizational leaders should change every year or two.  Teams need to be pushed toward new tech, fresh ideas and improved processes.  Teams must be energized and motivated. 

I know an organization that has the same leadership from the top executive down to the team leads for over 10 years.  They now their customer and systems very well but very little innovation or improvements have come in years.  They are falling behind and are starting to lose business, quickly.  Their customers have lost confidence in them and their, "this is how we have always done it", mind set. 

It is changing rapidly.  Do your teams have SREs, are you doing the DevOps, are they using advanced monitoring solutions, are they very agile, are they embracing containers and cloud native architectures?  If not, bring in new tech leads that can help the leaders or even better, hire new leaders to bring that experience to your organization.

You will have to pay these new leaders well but the cost will pay off quickly.  If you not familiar with Good to Great, you should stop everything you are currently reading and read the book.  You need the right people on the bus and the Level 5 leaders to take you to the next level. 

In the end, leaders are going to grow your company (NetFlix).  Experience is going to make you fade away.(Blockbuster)

Comments

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  

Manage IT by Johanna Rothman

I just completed this book. I think it is a really good book which covers a whole lot of software development. This book could possibly be the best book for first time project managers. I believe many of the PMs understand PMM but do not understand software development. This book gives a view of each project role. The only one that it does not cover is Business Analyst or requirements documentation. It does cover QC, development and of course PMs. It gives a PM a view into development processes like TDD, CI and estimation. Many PMs that are new to SD can read this book and get a great start to manager an SD project. If you are a PM or know some, read this book. http://www.jrothman.com/

Matrix Organizations are bad for Software Dev

Development teams need to be teams first and company people second. What happens when your team wants to start using user stories and index cards, but your analyst team manager thinks Use Cases are the best way to document requirements? How about when your QA process is not mature and you keep releasing with defects but the QA manager does not do anything about it? How about your project manager never buys into the team and only cares about being on time and on budget because their review is based on it. Maybe the tech lead wants requirements that never change and never lets the client change their mind. The technical manager taught your tech lead and agrees with everything the tech lead says. Agile or what I like to call "Successful Teams" are teams. They do what it takes to do what the customer wants, deliver features. I am not saying only agile teams are successful but successful teams are agile. If your organization is matrix, get your leadership buy in to override...