Saving a Team from Certain Burnout
16 April, 2019
One of the problems that I noticed when I started in my current role is that one of my teams was working 10-12 hour days, and usually six days a week. As a person with a family, I value a good work-life balance and found that you must apply these same principles to your team members. I want them to enjoy coming to the office and not be overworked. Therefore, I knew I had to find the root cause of this problem to ensure that the team didn't burn out.
The first issue that I found was that deliverables to the team were delayed. Not only were they delayed but the team accepted this fact as a given. For example, during a sprint the product team would deliver something on a Wednesday instead of the expected Monday, delaying the work for the team by two days and thus forcing the team to work through the weekend to catch up. Consequently, I made sure that the development teams followed strict guidelines and the necessary scrum process so as to deliver on time.
Another thing that I discovered was that the team was working on very small details even though it was expected that those details would change. Thus, I changed their approach to concentrate on high-level end-user scenarios rather than small details and rare cases. Product, developers, and QA would get together and go through all the user scenarios and establish which were of the highest priority. The result was a product that was satisfying for 95% of the customers rather than delivering on a product that only worked in one particular area. Additionally, we now have more time to test two or three layers, whereas before the team was merely trying to keep up.
- Initially, both of the changes that I made resulted in friction with product management. However, they very soon witnessed increased productivity and turned their opinions around once they saw the results.
- By adjusting a few key aspects I was able to shift the amount of work the team had and subsequently modify the time spent at the office. The attitude of the team changed and people actually now want to come into work. They feel like they are not being pushed too hard and they are willing to apply more to time to deliver something of high quality.
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Based on an awesome book titled "Deep Work" by Cal Newport we provide provide a brief overview of the Rules for Focused Success in a Distracted World.
CEO at Quantum Vision Consulting
Is it possible to be too empathetic? If you overdo it, it can be an energy sucker.
Delivery & Operations / Digital Transformation / People Leader at Marais Consulting Inc
Learn about 10 rules from the wisdom of these long-living residents from Ogimi, a small village in Okinawa, Japan. You could interpret the rules as the lifestyle habits that enable the senior residents of Ogami to live long and enjoy their ikigai.
CEO at Quantum Vision Consulting
Oftentimes Engineers work in silos, developing products to specified requirements, while they remain disconnected from the most important of questions - "WHY are we building this?" We'll explore the consequences of this mindset, as well as how to connect your Engineers to the larger Company Vision.
VP of Engineering at ExecThread
This was not a high point in my career. It's a story of single metric bias, how I let one measure become a 'source of truth', failed to manage up and ended up yelling at one of the most respected engineers in my team.
Chief Technology and Product Officer at Hive Learning