Last month I facilitated a panel at Lead Dev Live about how to build an effective tech strategy.
The panel were absolutely excellent: Randy Shoup, VP Engineering and Chief Architect, eBay, Anand Mariappan, VP Engineering, Impira, Nimisha Asthagiri, Engineering Director and Chief Architect, edX and Papanii Nene Okai, Director of Engineering and Architecture, Venmo.
They all had a lot of great experience and insight to share. We talked about what a good tech strategy looks like, how to craft one, how to articulate and communicate it, and how to adapt it as times change. We also discussed the tricky problem of how to make sure people are following it. I could have talked to them for ages.
I made several notes during the session. Nimisha had fascinating insights and models about how to collaborate on a strategy with a distributed team, as she oversees an open source platform with a global community. Randy had brilliant thoughts on what a tech strategy should be, including actionable, pragmatic and falsifiable. Anand had great explanations of the importance of showing, rather than telling, to get buy-in for your tech strategy; and Papanii shared the extremely useful CBTI paradigm (Customer, Business, Team, Individual) for the order in which you think about whether something has value.
I asked the panel to summarise at the end what the most important thing for a tech strategy was, and we agreed:
The discussion afterwards in the LeadDev Slack was also really interesting. Someone asked for recommended reading on how to create a good strategy, and the following suggestions were made, all worth a read:
You can watch the panel here (you need to register with LeadDev to access; this is free).
If you’d like to be notified when I publish a new post, and possibly receive occasional announcements, sign up to my mailing list: