Digital strategies fail after approval far more often than they fail on the page. I have read a lot of them and the thinking is usually sound. Someone has done the research, the market makes sense, the recommendations follow from the evidence. Then the document goes into a drawer and the quarter ends with nothing shipped.
The interesting question is not why bad strategies fail. It is why good ones do. In my experience it comes down to three things, and none of them is about the quality of the thinking.
Nobody owns it
Ask who owns the strategy and you usually get a committee. Sometimes you get a name, and when you dig, that person can influence the work but cannot reallocate a budget line or move a person off another project. They have responsibility without authority, which is the least useful combination in an organisation.
A strategy with no owner is a wish. The test is simple: can the named person move money and people without asking permission from three others? If not, they will spend the quarter building consensus rather than shipping, and the quarter will end.
- Weeks 1-3
Kickoff, alignment meetings, and a shared document nobody edits after the first week.
- Weeks 4-7
Waiting. On a decision, on agency access, on a budget code, on someone returning from leave.
- Weeks 8-11
One person delivers the easiest third of the plan around their existing job.
- Week 12
Review. The plan is described as ongoing and the next quarter absorbs it.
The sequence is wrong
Most strategy documents are organised by theme, because themes are how you think. Delivery does not work that way. Delivery works in dependencies, and a plan that reads well by theme often front-loads the hardest, slowest work because it happens to be the most important.
If month one is a data migration and a vendor negotiation, month one produces nothing anyone can see. By the time you have something to show, the organisation has decided the project is quiet, and quiet projects lose their budget to loud ones.
The fix is not to do the easy things first for their own sake. It is to make sure something visible lands early enough to buy patience for the slow work behind it.
The capacity was never there
This is the one that kills the most plans and gets discussed the least. A strategy is approved on the assumption that the team will deliver it alongside everything they already do. Nobody says this out loud because it sounds unreasonable when stated plainly, so it stays an assumption.
Marketing teams are usually running at capacity before the strategy arrives. Adding a transformation programme to a full workload does not produce transformation. It produces a slower version of business as usual and a tired team.
What a survivable strategy looks like
- One named owner who can move budget and people without a committee.
- A sequence built on dependencies, with something visible landing inside the first six weeks.
- An explicit list of what stops, with the same sign-off as the list of what starts.
- A capacity plan that names who does the work, not which team it belongs to.
- A review date early enough that you can still change something, rather than one that only records what happened.
None of that improves the thinking in the document. It just makes the document survive contact with the organisation, which is where strategies actually die. If you want to pressure-test one you already have, the digital strategy reality check is twenty questions built for exactly this, and my approach to strategy work explains how I run it with clients.