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 🚀💡
I always explain what our software is about, i always talk about why we are implementing that feature and who is going to use it. This leads to sometimes they arguing with me about why should we make such feature and that is just a matter of the user getting used to
But usually this helps motivating them and give them a better picture overall of what we are doing. Sometimes having a meeting talking about the future roadmap of the product itself and how the planned features align to this also helps a lot for them to get the bigger picture and how their work is impacting