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 🚀💡
Hi friend, sounds like you should join us over in [email protected] :)
It is important, and effective, to properly track and show to teams what effect their code changes have to the system and what “their team’s process” looks like to an outsider with meaningful data.
More here https://programming.dev/post/80365