What a digital strategy review should actually produce

A digital strategy review costs time and money. Yet at most brands it produces a document that gets shared widely, approved broadly, and then rarely opened again. That is not a problem with the people running the review. It is a problem with what a review is expected to produce.

At Livewall we regularly work with brands that are stuck on their digital product or platform. The question we ask is not 'what does your strategy say?' but 'what decision can you make right now based on what you know?'. That is a different question, and it produces a different approach.

A review is not a report

The difference is in the output. A report describes what exists. A review is aimed at what needs to change. If a digital strategy review does not end in a concrete decision about priorities, budget, or direction, it is just an expensive report.

A good digital strategy review answers three questions:

1. What is not working, and why?
2. What should be different by tomorrow?
3. Who is responsible for making that change?

Without answers to those three questions, you have observations. With those answers, you have an agenda.

What goes wrong in most reviews

The most common mistake is running the review with people who are also responsible for the current situation. That does not produce sharp analysis. It produces conclusions that do not hurt anyone.

Another common failure: the scope is too broad. Everything gets investigated, nothing gets prioritised. After eight weeks there are twenty recommendations on the table, all weighted equally. Nobody knows where to start.

What we at Livewall often find when we step in after one of these reviews: there is no shortage of insight. There is a shortage of choices. The route from insight to decision was never completed.

Three things a good review should produce

A short list of priorities. Not twenty points, but three. What has the most impact in the next six months? That is the question a good review answers. Everything outside those three can wait.

A decision moment, not a recommendation. A recommendation says 'you should consider'. A decision moment asks 'are you doing this, yes or no?' The review must force organisations to make a call, not to reflect indefinitely.

One owner per action. Every priority has a name attached to it. Not a team, not a department. One person who is accountable. Without an owner, nothing happens, no matter how good the analysis was.

In our work on the KLM Scalable Growth case, we saw how a strategic choice for a scalable system made the real difference. Not the insight that scalable was better, but the decision to replace the existing approach.

How the best reviews are structured

A review that leads to action has a different structure than one that leads to insight. Here is what we have learned:

Start with the outcome. Agree before you begin on what a successful review produces. Is it a platform choice? A budget decision? A team structure? If you do not know, the review becomes open-ended research that forces nothing.

Use qualitative and quantitative together. Data tells you what people do. Conversations tell you why. Without that combination you miss half the picture. In our work on the Sportvisunie platform, user research shifted priorities that looked logical on paper but did not hold up in practice.

Rank recommendations by impact and near-term feasibility. Plot everything on two axes: impact and ability to execute in the short term. What scores high on both is your starting point. What scores high on impact but low on feasibility belongs in a later phase, not the current action plan.

Name the cost of doing nothing. What does it cost the organisation if the top three priorities are not addressed in the next six months? That question makes urgency concrete and supports the decision.

When is a review the right move?

Not always. A review is valuable when there is genuine uncertainty about direction or priorities. If you already know what needs to change but lack the political space to decide it, a review will not fix that. You do not need a review. You need someone who will make the call.

A review also has limited value if the organisation lacks the capacity to act on the recommendations. More insight without the ability to execute leads to frustration, not change.

When a review is genuinely useful:

• There is disagreement about digital priorities at board level
• The current platform or product is underperforming but nobody knows exactly why
• A significant investment is being planned and the foundation is unclear
• A new leader has arrived and needs to understand the situation before deciding

In all those cases, the same principle applies: the value of the review is not in the thickness of the document. The value is in the quality of the decision that follows.

At Livewall, every UX/UI design or web application development engagement starts with that same question. What decision are we building towards? Everything else is in service of that.