The past few weeks have given me time to reflect on what technical leadership truly means to me. As with so many aspects of life, there isn’t a one-size-fits-all solution or a definitive answer. Instead, I’ve observed recurring patterns in how I’ve approached leadership across multiple companies and diverse teams over the years. Rather than writing yet another guide on what technical leaders ought or ought not to do, I want to share a collection of personal reflections on what it means to me to be a technical leader:

• Make Decisions at the Last Responsible Moment

This concept, borrowed from Toyota’s Lean Product Development System, emphasizes delaying decisions for as long as responsibly possible. The goal is to consider as much emerging information as possible before making a choice. While this sounds simple, it’s often challenging in business environments where early and decisive decision-making is seen as a premium skill. Human nature tends to favor a false sense of clarity over the discomfort of uncertainty, even when that uncertainty is inconsequential at the moment.

• Emergent Strategy Over Top-Down Strategy

This approach aligns with the decision-making process above. In many organizations, the seeds of a successful tech strategy often exist as puzzle pieces scattered across the team. That’s why it’s crucial not to rush to judgment or impose a false sense of clarity. By carefully listening and observing, you can allow a technical strategy to emerge from the interplay between business strategy and existing product development.

An emergent strategy synthesizes past efforts and aligns them with future objectives. It feels almost obvious once articulated, as it respects the past while creating a realistic path forward. This kind of strategy is resilient because it builds upon what has already been done rather than invalidating it.

• Autonomy Through Alignment

This principle forms the foundation of high-performing teams. Good developers know what they’re doing and don’t want to be micromanaged. This idea isn’t new; it traces back to concepts like “mission command” and Clausewitz’s reforms of the Prussian army after its defeat by Napoleon.

To manage skilled developers and teams effectively and at scale, leaders must provide context and alignment — and then should step aside. Clear objectives, aligned with the overall mission, empower teams to make decisions independently while staying on course.

• Context Shapes Value

When working with strong individuals or teams, my focus is on adding value by removing obstacles and ensuring they have the space to thrive. Conversely, when working with teams that are ramping up or under pressure to deliver, I try to make it a priority to step in and assist wherever needed, even if it means stepping out of my comfort zone.

• Strong Opinions, Weakly Held

This principle is one of my favorites, though it’s harder to live by than it sounds. I am opinionated and outspoken, but I recognize that my perspective isn’t always the best one. In my first meeting with my team of architects at Haufe, I presented a slide that said, “I don’t ask you to follow my opinion but to have your own. Otherwise, you’re stuck with mine.”

Often, voicing a strong opinion in the right setting sparks discussions that lead to better decisions. That said, I’ve had moments where I’ve failed to live up to this principle. For example, I once pushed for rolling out a product to a different user base earlier than planned. When challenged, I grew frustrated and resorted to the weakest argument: “trust me.” In the end, we didn’t proceed with my suggestion, and I’m glad we didn’t.

Admitting mistakes is not a sign of weakness but a demonstration of growth. However, I’ve also learned that flexibility and pragmatism can sometimes be perceived as inconsistency. For example, I worked with someone who was highly process-driven and felt uneasy when I quickly changed my stance based on new information. What helped in that situation was relentless communication and goodwill from both sides.

Closing Thoughts

These reflections are not definitive answers but some guiding principles that have picked up on my journey as a technical leader. Leadership in tech is an evolving practice that requires adaptability, humility, and a commitment to learning. I hope some of these ideas resonate with you.