The first conversation in content design is not about content

The most predictable failure I see in government content design has nothing to do with writing ability. It happens before anyone writes a word.

A content practitioner reviews a page, identifies the problems, and sends recommendations. The subject matter expert responds defensively. Progress stalls. The project develops a reputation for being difficult. Nothing gets improved.

The problem is not the content. It is the sequence.

Stakeholders grieve their content

When someone has spent months getting content through internal review, legal clearance, and executive sign-off, they are attached to it. Not irrationally. It represents real work, real authority, and real accountability. In government, where clearance processes are long and stakeholders are professionally exposed, the emotional investment is real.

When a content designer arrives and says the page needs to change, that does not feel like improvement. It can feel like being told the work they produced is not good enough.

I have worked across seven ACT Government directorates. The pattern is consistent. The stakeholders who resist content changes most strongly are often the ones who worked hardest to get the content approved in the first place. They are not obstructing progress. They are protecting something they believe in.

Understanding this does not mean lowering your standards. It means you treat the resistance as information about what the first meeting needs to address.

The right first move

Content design stakeholder management in government is not a soft skill that comes after the real work. It is the real work, at the start of any project.

Before you touch a word, you need a direct conversation with the person who owns the content. That conversation has a specific shape.

Explain what you are trying to do, and why it matters. You are not trying to take over their content or second-guess their expertise. You are trying to make sure their audience can actually understand it, and act on it.

Name the obligation. WCAG 2.2 Success Criterion 3.1.5 sets a standard for text that exceeds the lower secondary education reading level. Where content cannot be made simpler, agencies can provide a plain language version alongside the original. Framing the conversation around accessibility requirements changes its register from personal critique to shared obligation.

Reduce the ask. Tell the stakeholder what you actually need: not redrafting, not debating, just approval. Commit to documenting every decision and explaining the rationale. A clear process reduces anxiety considerably.

Why documentation matters here

Decisions about how to simplify or restructure government content will be contested again. When the subject matter expert moves on, when a minister changes, when the policy updates and the page needs revising. Without a record, you start from scratch every time.

A decision log does not need to be complicated. A shared document that records what changed, why, and who approved it is enough. It turns "we changed this" into "we changed this, with this rationale, with this person's sign-off."

That documentation protects the stakeholder as much as it protects you. It means nobody can come back later and claim the content was changed without oversight or rationale.

What this changes in practice

Once the stakeholder understands the process and the purpose, and has committed to being the approver rather than the gatekeeper, the content work moves faster.

Not always without friction. There will still be disagreements about specific changes. But the dynamic shifts from adversarial to collaborative, because you have established that you are working toward the same thing: content that serves the audience.

The Australian Government Style Manual is clear that plain language is a standard for all government content. WCAG 2.2 sets accessibility criteria that content should meet. But neither of those things will get your content published if the person who owns it does not trust the process.

The conversation is not overhead. It is the thing that makes the rest of the project possible.

If your content design projects are stalling at the stakeholder stage, ask yourself: did you start with the relationship, or with the recommendations?