Fostering technical leadership
What helps foster and nurture technical leadership?
Key Points
Create and promote autonomy, mastery & purpose, setup an environment for accountability
Trust matters and is at the heart of nurturing and growing high performing people
Companies need to leverage intrinsic motivation of technologists by complementing with appropriate extrinsic motivators
Focus on the people and environment before being concerned with the technology aspects
Software is continuing to play a dominant role in driving business innovation and growth. In fact, its role is expanding and spawning innovation which is the lifeblood of success and growth. While many business leaders continue to consider software and technology a cost that should be actively reduced or 'the problem' should be transferred elsewhere, a recurring question from more progressive or technology-native business leaders is,

how do we best leverage software and technology to grow, compete and win?

One critical action is that of identifying and nurturing technical talent, those who possess both deep technical expertise and the ability to guide and inspire others. However, achieving this presents unique challenges for leaders and the businesses they work for. How is this best done and what strategies can be executed to cultivate an ecosystem that natures and fosters technical leadership?
Success requires fostering individuals who possess both deep technical expertise and those with the ability to inspire and guide others. However, achieving this ideal balance presents unique challenges. So below I'll cover some conditions that I've found to produce high quality, capable technology leaders and technologists alike. Interestingly, at this point there is little that is specific to technology. Why? Without these factors, the technical uplift aspects become at worst redundant and at best a distraction.
Motivation
Building, running and operating technology is a non-trivial, high-complexity, mentally challenging and creative activity, and during my career I've rarely found someone that doesn't enjoy the core aspects of their craft - there is no shortage of intrinsic motivation. However, nurturing talent requires supporting people beyond their own desires and satisfactions, their intrinsic motivation must be enhanced and leveraged into a business and commercial context. Dan Pink (Drive: The Surprising Truth About What Motivates Us) explains the concepts of Autonomy, Mastery & Purpose and putting these concepts into practice from a form AND substance perspective will deliver returns.
The Crucial Trio: Autonomy, Mastery & Purpose
Software engineers thrive when given the ability to make decisions about how to execute their work, experiment with solutions, and take ownership of projects. The autonomy to own and drive to an outcome not only boosts job satisfaction but also ignites intrinsic motivation, crucial for tackling complex challenges in coding and problem-solving.
The journey to mastery in an ever and fast-changing landscape is never-ending. Whether learning new languages, architectures, tooling, diving into sophisticated frameworks, or refining coding techniques, the pursuit of mastery not only fuels professional growth and supports a drive to continuously "do better".
Beyond crafting code, software engineers find purpose in understanding the impact of their work on users and society. Contributing to strategically critical projects that have impactful, validated goals drive a strong sense of purpose, motivating engineers to go beyond routine tasks and strive for impactful outcomes that resonate with their values. Engineers want to see value and impact in the eyes of users from their efforts. It's the high of the profession, solving that problem that really matters.
Trust
Building a foundation of trust is essential for effective leadership. Research in the "Journal of Applied Psychology" suggests a direct correlation between trust and team effectiveness. Fostering psychological safety, as emphasized by Amy Edmondson, creates an environment where collaboration and open communication thrive. Leaders who trust their teams empower individuals to take ownership and contribute meaningfully to their work. Trusting engineers to develop the best solution with the context and constraints they are provided, while supporting them with appropriate resources brings out the best professional growth for a technologist.
The Challenge
It is easy to form a view that these steps are a pathway to chaos and an environment of low accountability. It's easy, and unfortunatelly a common view, to think that technologists simply want an open reign with no accountability to deliver, that they do not care about delvierables or outcomes. I've found the opposite is true and that the organisation and its leaders have failed to effectively design and support a business that enables the attributes outlined above and this is where improvement and senior leadership is required.
Guardrails and operating rules and procedures must be appropriately designed and put in place, embedded by the organisation and ideally become cultural norms and values of the organisation. These guardrails should foster the safety for failure, provide clarity on decision-making and drive clarity around accountability. The values of the organisation must move the organsiation away from traditional 'command and control' from the [https://en.wikipedia.org/wiki/Ivory_tower] Ivory Tower, realising they can generate true leverage and power from the expertise of the people they've employed.
Closing
For those businesses who believe in the power of technology and software, focus on creating an environment where technologists are empowered, guided, enabled and trusted to do their best work. Make sure that work matters to both the organisation and where possible, society. Setup simple, focused systems of work to ensure accountability, doing this through the provision of clear guardrails that support a culture of safety.
Author
Andrew Todd
These are my personal views based based on practical experience, influenced by aspects of my professional life, work engagements and often curious discussions with those I see as software, technology, leadership and strategy experts.
Initially published on 07 March 2024