The author bases his Strategy on the book Good Strategy, Bad Strategy and in that respect he hits the correct abstraction level imo. I can really recommend the

The author bases his Strategy on the book Good Strategy, Bad Strategy and in that respect he hits the correct abstraction level imo. I can really recommend the book. It basically boils down to how to take Strategy documents from the classic high-flying, bla bla visions, values etc that employees (incl midlevel mgmt) read and forget about again because its too far removed from their actual work, and instead write a Strategy that is both based on what actual problems/threats are, and that communicates in a concrete but not too specific way how to execute the Strategy. Writing Strategy documents that are actionable are important, I think, to try and deal with the old but very true “culture eats Strategy for breakfeast”