Snippets of Text

Snippets of Text

246: From Burnout Charts to Measurable Success

Incident management and measuring productivity for engineers

Snippets Press's avatar
Snippets Press
Sep 15, 2023
∙ Paid

Thank you for reading Snippets of Text. Snippets from media about tech, programming, parenting, and more. This is a preview of a post available exclusively to paying subscribers. You can get unlimited access to all articles by purchasing a subscription.

an aerial view of a lake surrounded by mountains

Off Topic: Prevent Incident Chaos

A lack of proper incident management can lead to issues. The aim is to take small steps and limit the scope while ensuring systems are back online. Focusing on fixing bugs instead of developing new features can impact product sales.

Consider implementing a hands-off policy on Fridays to give your team a break. Remember, it's all about the people on your team. Automated systems can help keep track of unique alerts and ensure a fair rotation. When establishing on-call rotations, keep time zones in mind. Although it may not be everyone's favorite task, it is a learning process. To ensure success, maintain a flexible and cohesive process. Incident responders should have a "jump bag" containing critical information to avoid delays. During an emergency, any organization must provide quality services. You can take advantage of on-call rotations as a learning opportunity. Schedule regular hands-off cycles to ensure everyone has a chance to learn.

Thank you for reading Snippets of Text. This post is public, so feel free to share it.

Share

Current Work: From Burnout Charts to Measurable Success

The only proof of progress is in the working software, not any burnout chart. Measuring effort becomes even more complicated when dealing with bugs. Using activity metrics to assess progress creates the wrong incentives for prioritization. While activity metrics can help check team collaboration, they cannot reflect progress. 

If the team cannot provide the expected functionality, it could be due to a dependency or rule they lack. In such cases, it should be removed from the backlog or sprint, as those stories won't impact the business. A cross-functional team comprises members with expertise across various technical domains. 

Thank you for checking out the free preview of Snippets of Text. Please consider subscribing to the paid version if you find my work helpful. This will allow me to dedicate more time to developing new ideas to share with you.

Snippets of Text is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

Keep reading with a 7-day free trial

Subscribe to Snippets of Text to keep reading this post and get 7 days of free access to the full post archives.

Already a paid subscriber? Sign in
© 2025 Rafael George
Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture