Over the last months, I've witnessed firsthand the transformation of my team from a basic operation provider to an internal service provider.

As someone who has spent years navigating the complexities of engineering leadership, I can tell you that transparency is one of the most critical elements of effective leadership. If you're aspiring to take on a leadership role, understanding the importance of transparency and how it contributes to a healthy chain of command is essential.

Dear readers, I am back. It has been a few “interesting” months in my life that have made me reflect a lot on some topics that before I thought were trivial, and one-sided. I will try to share some thoughts over the next few posts. So let's start with a subject that is really fresh in my mind, as it's what has been affecting me over the last few months.

Hello Everyone, I want to apologize for this hiatus that I had to take as writer of leads horizons. I have delayed most of the posts and ideas I had to share with all of you. I will resume my writing activities next week, so I am looking forward to any feedback you can/what give me. To give some context, the hiatus was to handle my mental health, and make some changes that will help me move toward my goals and personal happiness. I would like to personally thanks my wife for being a great support all this time 🙏. I want to also say thanks to everyone who is subscribed to the newsletter or reads independently in substack for your support. To show my appreciation, I will add a complimentary subscription to everyone. Thanks again for your support & reading this newsletter, Regards, Alvaro

Have you ever considered the various types of tasks within a team? Why do we often separate tasks into 'technical' and 'product' categories? Is this division a reality, or is it simply a reflection of our difficulty in articulating the value of non-functional behavior?

Last week, we discussed the importance of managing 100% utilization within the team to maintain their well-being. As individuals, we each react differently to experiences, which can have long-term consequences.

It has been almost a year since McKinsey released their developer productivity approach. While I fully disagree with their ideas, it highlights the ongoing interest of companies in continuously improving per-developer productivity.

Ever found yourself in engineering departments where tools and practices are adopted and discarded rapidly?

Have you noticed a broad spectrum of aspirations among your team members?

We all continuously hear about high-performance teams and the importance of becoming one. But there is actual no real definition of it. Is it?