Stakeholder management is decision design

The more my work moves upstream, the more I think stakeholder management is becoming part of editorial judgement.

I used to think of stakeholder management mainly as communication: keep people informed, make sure nobody is surprised, gather feedback and create enough alignment for the work to move.

All of that still matters. But I am becoming more interested in a different question.

What decision is this person here to improve?

That changes the shape of collaboration. Instead of assuming that important work needs more people in more meetings for longer, you start thinking about the point at which somebody’s knowledge can still materially change the outcome.

Sometimes that is much earlier than we involve them now. Sometimes the involvement can be much shorter. And sometimes the useful decision is that another meeting is not needed at all.

Content crosses too many boundaries for vague collaboration

Editorial work rarely belongs to one team anymore.

A campaign can involve content, brand, performance, SEO, GEO, PR, product marketing, customer marketing, subject-matter experts, designers, web teams and external agencies. Those functions are not unnecessary bureaucracy around the content. They often hold information the work genuinely needs.

The difficulty starts when involvement is confused with ownership.

Everybody can have a legitimate interest in the work while still having very different roles in the decision. One person may own the campaign objective, another the customer relationship, another the channel, another the technical accuracy and another the editorial judgement about what the audience actually needs.

If those roles are not clear, collaboration becomes additive. Another person joins the meeting, another comment appears in the document, and another approval stage gets created because nobody is quite sure whether the previous approval counted.

The writer or editor then becomes the place where all of those competing signals are reconciled. That can look like stakeholder management. Often it is just unresolved governance being absorbed by the person closest to the deliverable.

Bring people in at the point of leverage

One of the clearest lessons for me has been that the timing of stakeholder involvement matters more than the volume of it.

There is limited value asking editorial to contribute strategically after the campaign premise, format, evidence, channels and deadlines have already been decided. At that point the opportunity is mostly to make the words better inside somebody else’s architecture.

The same applies elsewhere. Asking performance how success should be measured after publication is late. Asking a customer team for proof after the story has already been written is late. Asking GEO or search specialists what questions matter after the content plan is fixed is late.

The useful intervention often happens before there is much to look at. What is the audience problem? What evidence would make the answer credible? What do we already know, and what do we still need to ask? Which channel has a real job here? What are we expecting somebody to do differently after seeing this?

These questions are editorial, commercial and operational at the same time. That is why the right stakeholder can change the work disproportionately when they arrive early enough.

Then they do not necessarily need to stay for every later conversation.

Good collaboration can mean bringing somebody in earlier and letting them leave earlier.

The decision ask is underrated

I have also become much more conscious of the difference between presenting thinking and asking for a decision.

It is easy, particularly when you have done a lot of work, to bring the whole intellectual journey into the room. Here is the research. Here are the patterns. Here are the possible frameworks. Here are the seven things we might do next.

That can be useful context. It can also move the burden of synthesis onto everybody else.

A stronger recommendation usually has a clearer shape: here is what I found, here is what I think it means, here is what I recommend, and here is the decision I need.

I do not think every conversation should be reduced to a binary approval box. Complex work sometimes needs genuine exploration. But even exploratory conversations benefit from knowing what they are trying to make clearer.

Are we testing the premise, trying to find the missing evidence, choosing between two routes, deciding who owns activation, or working out whether the idea is worth pursuing at all? The answer changes who needs to be there.

More meetings can be a symptom

I dislike meetings for meetings’ sake, but I do not think the lesson is simply that meetings are bad.

Some problems are much easier to resolve in 20 minutes of live conversation than through three days of messages and comments. Relationships matter. Trust matters. People sometimes need to hear uncertainty in somebody’s voice rather than receive a polished recommendation that makes the situation look more settled than it is.

The problem is not synchronous conversation. The problem is using a meeting as a substitute for deciding what kind of conversation is required.

A status update can often be written; a genuine disagreement may need a room; a decision with three clear options may need 15 minutes. An unresolved strategic question may need longer because the purpose is to discover something together rather than approve a pre-written answer. Treating all of those as the same 30-minute calendar object is where the waste begins.

Visibility, contribution, decision and ownership are different

I increasingly want to distinguish four reasons somebody might be involved in a piece of work. They may need visibility because the work affects them, contribute expertise because they know something the team does not, make a decision because they own the relevant risk, budget or direction, or own the next step because the work moves into their area.

Those are different relationships, and treating them as interchangeable is where a lot of unnecessary coordination begins.

Someone who needs visibility does not necessarily need to attend the working session. Someone contributing expertise may be essential for 20 minutes and irrelevant for the next three weeks. Someone with decision authority should probably be involved before the team spends a fortnight perfecting a route they cannot approve.

This is not about excluding people from collaborative work. It is about respecting the difference between being interested in an outcome and being required to shape it.

That distinction can reduce coordination without reducing collaboration.

Editorial people can accidentally become the coordination layer

There is a particular risk here for people whose editorial role is moving upstream.

Editors are trained to connect things. We notice inconsistencies between research and claims, gaps between what customers say and what a campaign wants to say, repeated questions across different sources and places where one asset could strengthen another.

That connective instinct is valuable, but it can also turn you into the human middleware between teams. You spot the dependency, so you create the tracker. You notice that three teams need to coordinate, so you organise the meeting. You see that the customer evidence is missing, so you chase it.

Then you build a useful process and become the person who maintains it indefinitely. At some point the ability to see the system can result in serving the system.

I wrote about a related version of this in AI can connect the silos. You still have to learn how people work. Tools can make information move more easily across organisational boundaries, but they do not remove questions of ownership, incentives or authority.

The same is true of editorial integration.

Seeing the connection is not the same as owning every task required to maintain it.

A good process should need less coordination over time

This gives me a useful test for stakeholder management.

If a process is working, it should gradually require less active coordination.

The audience should become clearer. The evidence standard should become understood. People should know when they need to enter the work. Routine execution decisions should stop escalating. Approval should become proportionate to risk rather than habitual.

In other words, good stakeholder management should create enough clarity that people can work without continuously synchronising.

That is why I like thinking of it as decision design.

You are not simply trying to make everybody feel aligned. Different teams may never evaluate the work in exactly the same way, and that is fine. Performance, PR, brand and editorial have different jobs.

The aim is not perfect agreement.

It is sufficient clarity to make the next good decision.

There is a risk in over-designing collaboration too

Decision design can become its own kind of process theatre.

Not every useful conversation has a predetermined output. Serendipity matters. Informal relationships matter. A stakeholder can surface something nobody knew to ask. An exploratory discussion can create a better question rather than answer the original one.

If every interaction is forced into a decision matrix, the organisation can become efficient at executing assumptions it never properly challenged. So the goal is not to eliminate ambiguity; it is to be deliberate about where ambiguity is useful.

Early exploration can be open. Once the work moves into execution, ownership should become clearer. A team should be able to tell the difference between a conversation designed to discover and one designed to decide. That alone would improve a lot of meetings.

The upstream editorial job

I think this becomes more important as editorial roles change.

If the writer only enters after the brief is complete, stakeholder management is mostly about delivering against agreed requirements.

If the editor is involved earlier, helping decide what evidence is missing, what narrative is credible, which audience question matters and how several assets should connect, then the work increasingly depends on influencing people who own different parts of the system.

That does not mean editorial should own the whole strategy. It means editorial judgement now includes knowing whose expertise is required, when it matters and what decision the work needs next.

That is a different skill from keeping everybody updated. The version of stakeholder management I want to get better at is simpler: fewer conversations whose purpose is simply involvement, and more moments where the right person can still change something.