Stakeholder alignment: agree the problem before you design the answer

Why alignment comes first

A familiar pattern: a design project starts with a brief of a paragraph or two. The team works for weeks. At the review, a senior stakeholder sees the work for the first time and questions the direction - not the details, the direction. The team goes back to the start. Everyone is frustrated, and nobody did anything wrong. The project simply began without agreement on what it was for.

Stakeholder alignment is the work that prevents this. It makes the problem, the goals, the audiences, the constraints and the success criteria explicit - and gets the people who matter to agree them in writing before design starts.

The payoff is well documented. PMI's research found that of the US$135 million at risk for every US$1 billion spent on projects, US$75 million is on the line because of poor communication - and that organisations with highly effective communicators see 80% of projects meet original goals, compared with 52% for minimally effective ones.

Mapping the stakeholders

Alignment starts by knowing who is involved and how. I map stakeholders by their influence over the decision and their interest in the outcome, and agree how each will be involved.

The single most important decision is often who has the final say on what. Agreeing decision rights early ends most circular debates later.

The alignment brief

The main output is a short written brief - usually two or three pages - that everyone involved has agreed:

• Problem - what we're solving and why it matters now, with evidence.
• Goals - what the work must achieve, ideally measurable.
• Audiences - who the work is for, and what they need.
• Scope - what's in, what's out, and what's deliberately left for later.
• Constraints - technical, legal, compliance, budget and time.
• Success criteria - how the work will be judged at each review.
• Decision rights - who decides what, and when.

When feedback arrives later, it is measured against this brief. "I don't like the blue" becomes "does this meet the criterion of feeling calm and credible to procurement reviewers?" - a much more useful conversation.

Alignment as the project runs

Alignment isn't a one-off. Throughout the project I keep it alive:

• Show work early and often - rough work shared at checkpoints avoids big reveals.
• Frame feedback - reviews start by restating the goals and criteria.
• Log decisions - with the reasoning, so new stakeholders can catch up without reopening them.
• Flag scope changes - new requests are weighed against the brief, not quietly absorbed.

On an AI enterprise brand project, this meant six phases - positioning, logo system, colour and type, website UX, applications and governance - each ending with a deliverable agreed before the next began. That structure kept a wide group of stakeholders aligned through a long project.

What you get