I’ve noticed something interesting about most of the engineers I know—they often lack a deep understanding of the business implications and overall impact of their work. As someone who recognizes the significance of the “bigger picture,” I find myself spending a considerable amount of time explaining and demonstrating the real-world effects of our projects.
I often gather data from various departments, particularly sales & marketing, and present it to the engineers. It’s amazing how engineers who grasp the big picture become more engaged and excel in their roles.
However, I face a challenge in collecting this “big picture” myself. I constantly find myself having to follow artifacts and communication channels from other departments, which can be quite overwhelming.
So, fellow leaders, I’d love to hear your thoughts on measuring the business impact and ensuring that our engineers are aware of it. How do you tackle these challenges in your own organizations 🚀💡
A lot of organizations seem to focus on tailing indicators such as lines of code written, or the number of bugs found, and I think that’s part of what fuels the perception that being an engineering leader is one of the most difficult roles in modern companies because they don’t paint an accurate picture of how things are today.
The first thing is to get data that tracks key performance metrics. Many organizations often start with DORA metrics to create “slides for the board” that show the overall health of the engineering organization. This is a great place to start, but you can take this further by incorporating your project tracking into the data to measure how you allocate resources across the engineering function and whether or not that allocation is enough to meet product delivery timelines. There are a handful of tools out there that make this easy, like Sleuth and LinearB. A quick search should surface other solutions for this too.