I learned the hard way that first, one has to get the facts right; second, understand the overarching story; and then, and only then, share that narrative with the team. Sometimes, the problem is not what you said but what you didn’t say

The business world is filled with this type of theater, where teams adopt the latest best practices that work within a very specific context, and then behind the curtains, we all tell each other what a waste of time it was. Most of the time, teams have no power to change the fact that OKRs are part of their organization; perhaps we should push harder.

I have worked with many teams that got along well but moved very slowly or lacked a sense of purpose, motivation, or even pride in execution. These teams smiled every day, but deep down, they knew that things could be better; however, avoiding conflict is the default mode. These environments may yield friendships but not career satisfaction.

The truth is that most productive engineers normally look like they are not working much.

This is a brave post. It takes a lot to share this with the world. I truly hope the right partner comes along and makes the best use of all the hard work you put into this. Respect

thanks sofia :)