Executing and evaluating a technical strategy at scale

To paraphrase the Cheshire Cat to Alice, ‘If you don’t know where you’re going, any road will take you there’. What Alice lacked was direction. And that’s where strategy comes in.

I recently wrote a part one to this article (if you haven’t already, check it out here) where we discussed when and why we need a technical strategy, how to develop one using a guiding framework, and how to secure commitment and alignment from key stakeholders, leaders, and users.

So, at this stage, we now have an approved strategy and an outcome that has buy-in from an executive sponsor, which not only provides a North Star but also a map with a prescribed direction.

Join LeadDev.com for free to access this content