by Terrence Ryan
“Driving Technical Change” is a guide to leading and managing technical change within organizations, focusing on the human aspect of adopting new technologies, tools, and methodologies. The book offers practical strategies and techniques to help technology advocates effectively introduce and promote change within their teams and organizations.
The most valuable points from the book are:
Identifying Skeptics
The book emphasizes the importance of understanding different types of sceptics and their motivations in order to tailor your approach to driving change. It outlines various sceptic archetypes, such as The Hesitant, The Burned, The Time-Crunched, and The Boss.
For example, The Hesitant sceptic might require more information and reassurance about the benefits of the proposed change, while The Boss sceptic might need to see a clear business case or return on investment.
Building Your Case
To drive technical change, it’s crucial to build a strong case for the proposed change. This involves identifying the benefits, potential risks, and impact on the organization, as well as addressing any concerns or objections that may arise.
For example, if you’re advocating for adopting a new programming language, you should be prepared to discuss its advantages, such as improved performance, easier maintenance, or better developer productivity, as well as any potential challenges or risks associated with the change.
Demonstrating Success
The book highlights the importance of demonstrating the success of the proposed change through tangible results, such as prototypes, case studies, or pilot projects. Showing the positive impact of the change on real-world projects can help persuade sceptics and gain support from the team and management.
For example, implementing a small pilot project using the new technology or tool can provide concrete evidence of its benefits, making it easier for others to understand and embrace the change.
Building a Coalition
Building a coalition of supporters is essential for driving technological change. The book offers strategies for identifying potential allies and building relationships with them, as well as leveraging their support to influence others within the organization.
For example, engaging with early adopters or influential team members who are open to the proposed change can help create a network of support and momentum for the change.
Persistence and Adaptation
Driving technical change often requires persistence and the ability to adapt to changing circumstances. The book stresses the importance of learning from setbacks, adjusting your approach, and staying committed to the change, even when faced with resistance or obstacles.
For example, if your initial proposal for adopting a new tool is rejected, you might gather more data, address concerns, or modify your proposal based on feedback and then present it again at a later time.
By focusing on the human aspect of driving technical change and offering practical strategies for overcoming resistance and scepticism, “Driving Technical Change” provides technology advocates with valuable insights and techniques to successfully introduce and promote change within their organizations.
Thanks for reading. If you have feedback, contact me on Twitter, LinkedIn or Github.
Top comments (0)