One of the key challenges in any change programme or strategy implementation is connecting an overarching organisational strategy with the departmental strategies and tactics needed to make it happen and all head in the same direction. And then there is the oft forgotten required conditions, environment and culture that not only supports but enables the strategy to be delivered.
One approach to mapping this out that I like is the Agile Strategy Map, originated by the people at Agile42. I like it since it maps not only success factors, but dependencies and necessary conditions for success around a central goal or vision. It's pretty straightforward (and explained in full here).
The success factors might be possible success factors (in other words hypotheses that you want to test), or critical success factors (that you know now require investment in resources or time). The necessary conditions might be dependencies (so important and yet not many mapping frameworks enable you to set these out effectively) or cultural enablers. The map allows you to track progress against multiple experiments or success factors at the same time, and so is better than a linear backlog or roadmap.
It draws on Goldratt's Theory of Constraints, and also strategy and tactic trees, recognising the need for layered strategy and related tactics, and interpretations (perhaps at a functional or team level) of that overarching strategy. Useful.