Design Strategy Consultant

Most companies do not have a design execution problem.

They have a design direction problem.

The work gets done. Screens get made. Workshops happen. Research appears in slides. But when you zoom out, the bigger question stays fuzzy:

What is design actually helping the business do?

If that question does not have a clear answer, design becomes expensive activity. Useful in places, frustrating in others, and too easy to push aside when pressure rises.

That is the point where a design strategy consultant becomes useful.

Design strategy is not a trend deck

The phrase gets stretched to mean almost anything. Vision decks. moodboards. operating models. brand narratives. workshop language.

For me, the job is simpler and more demanding:

Design strategy is the work of deciding where design creates leverage, what problems are worth solving, and how that should change the way the team operates.

If the answer does not affect decisions, it is not strategy yet.

That means the work usually touches:

• product direction
• research priorities
• design team responsibilities
• collaboration with product and engineering
• leadership expectations
• capability building

In healthy teams, these pieces reinforce each other. In weaker systems, they drift apart.

What the gap feels like inside a company

It often sounds like:

• “We are doing a lot, but it is hard to say what moved the needle.”
• “Design should be more strategic, but nobody agrees what that means.”
• “Research is useful, but it rarely changes the roadmap.”
• “The team is stretched across too many priorities.”

These are strategy symptoms.

Not because nobody is smart. Because nobody has created a clean enough frame for how design effort should connect to user problems and business decisions.

The Visma Sign journey is a good example of what the opposite looks like. Over a long engagement, design was not limited to interface work. It influenced enterprise feature evolution, onboarding, product direction, and eventually the team’s own internal capability. That is design operating strategically. Not as a service desk. As a contributor to the company’s trajectory.

Where design strategy consulting becomes valuable

Usually in one of three situations.

1. The company has grown past intuition

What worked when the team was smaller no longer works now. Informal alignment breaks down. Decisions get slower or more political. Design influence becomes inconsistent.

2. Leadership wants more from design

But the team has not been set up for that. There is no shared language for what “strategic” means in day-to-day work.

3. The team is busy but not focused

There is activity, but no sharp prioritization. Important work gets mixed with urgent noise. Design effort becomes spread across too many directions.

In each case, the core need is the same: better judgment upstream.

What the work usually involves

Not a giant strategy project detached from reality.

The useful version is grounded in live decisions and operating patterns.

That may include:

• reviewing current initiatives and where design is truly influencing them
• identifying recurring failure modes in research, prioritization, or collaboration
• defining what design should own, influence, or stay out of
• helping leadership connect user insight to business priorities
• coaching the team so strategy shows up in practice, not just vocabulary

This is also why I do not separate design strategy from how a team works. If the operating behavior stays the same, the strategy will decay quickly.

The engineering-company example proves this from the negative side. The absence of strong strategic product direction meant years of output piled up without the right validation. Once user-informed methods entered the system, the team’s operating model changed. That is strategy becoming behavior.

Why outside perspective matters here

Because companies are bad at seeing their own gravity.

What feels normal internally may be exactly what is limiting the team:

• design brought in too late
• leadership using design language without decision change
• research disconnected from prioritization
• teams protecting old assumptions because too much has already been invested

An outside strategist can name those patterns faster because there is no need to defend them.

The value is not fresh buzzwords. It is pattern recognition plus enough distance to call the real issue.

That is especially important now, when AI tools are making output cheaper and faster. If direction is weak, faster output just means you can move in the wrong direction more efficiently. Strategic design matters more, not less, in that environment.

What you should get from the engagement

You should leave with more than a clearer narrative.

You should see:

• sharper priority decisions
• a more credible role for design in leadership conversations
• clearer expectations for the design team
• better use of research and validation
• less wasted effort around the wrong bets

This work is for companies that already know design matters. They just need it to matter in the right places, with more consequence.

That is what design strategy consulting is for: not making design feel important, but making it useful where the business actually moves.