We're reviewing the same draft, but judging different things

A customer story I am working on has reminded me how easily a review can become a conversation about two different pieces of content. Everybody is looking at the same draft, but that does not mean everybody is judging it against the same idea of what it should do.

I had approached the material as practical advice. The customer experience offered a way to explain how earlier financial information gives a business owner more options: more time to understand what is happening, make decisions and respond before a problem becomes urgent. I wanted the reader to leave with something they could apply.

The feedback pulled towards the person behind those decisions. Where was their personality? What had the worry felt like? What changed when they could switch off rather than carry the business around in their head?

Those were good questions. They also asked for more than a different opening or a warmer sentence. They changed what would lead the article, which evidence would matter most and what the reader would remember.

Two useful readings of the same story

My practical treatment had underplayed something important. A business decision can be easier to understand when you can feel why it mattered to the person making it. The customer was more than an example supporting an advice point, and the review helped me see that.

But the practical route had a purpose too. A reader looking for help with their own business needs more than somebody else’s relief. They need to understand what changed, how that change worked and which part might be useful in their circumstances.

There is room for both approaches. The difficulty is deciding how they relate in this particular piece. Does the human story lead, with advice emerging from it? Does the practical explanation lead, with the customer experience making it credible? Or does the material justify two separate treatments?

That last route is the one we have been working towards: a practical advice article alongside a product video, and a separate article built around the human story and a hero video. It gives the different treatments a clearer job. The work is still in review, so I cannot claim it has produced a better result for readers yet.

What I can say is that the conversation became more useful once we could discuss the purpose of each article. Trying to accommodate everything inside one draft had made the choices harder to see.

When a style comment changes the brief

A lot of editorial disagreement arrives disguised as a comment about style. Make it warmer. Bring the customer forward. Be more direct. Give us more detail. Each request can be reasonable, but each can also imply a different view of the audience and the content’s job.

“Bring the customer forward” might mean that a paragraph feels impersonal. It might also mean that the whole piece should become a portrait rather than an explanation. The writer needs to understand which problem the reviewer is asking them to solve.

This is part of the judgement involved in writing and editing. You cannot improve a piece simply by accepting every suggestion, because individually sensible changes can pull the whole in different directions. Equally, defending every sentence can stop you seeing a weakness that somebody else has noticed.

I find the useful move is to translate the feedback into an editorial choice. If we follow this suggestion, what becomes the centre of the piece? What does the reader gain, and what will we have less room to explain?

That gives the reviewer something more meaningful to respond to than whether their wording has been used. It also requires the writer to make their own reasoning visible. A draft can look self-evident to the person who wrote it while concealing most of the decisions that shaped it.

Ownership needs to mean something specific

Customer stories cross several kinds of responsibility. Someone owns the customer relationship. Someone needs to check that the claims are accurate. Someone understands the channel and its audience. Someone has to judge whether the article holds together.

These people may care about the same outcome while noticing different risks. A customer relationship owner might recognise a portrayal that feels wrong to the person featured. A subject expert might catch an explanation that sounds persuasive but overstates the evidence. An editor might see that the opening promises a different article from the one that follows.

Gatekeeping has a legitimate place here. The work needs people who can say that a claim is unsupported or that a customer has not approved something. The confusion starts when responsibility for a particular risk becomes indistinguishable from authority over every editorial choice.

If all comments carry the same weight, the writer has to infer which are requirements, which are suggestions and which reopen the direction. The document becomes the place where unresolved decisions accumulate. Another revision may make the prose smoother without settling any of them.

I wrote about the wider coordination problem in Stakeholder management is decision design. This experience brings it down to the draft itself. Before asking someone to revise, we need enough shared understanding of what the article is trying to do and who can settle a disagreement about that purpose.

A brief does not have to freeze the thinking. Review should be able to reveal a stronger route. But if the route changes, we need to recognise that decision and give the writer a coherent direction to work from.

AI cannot settle the human decision

This is a problem that AI cannot resolve for us. It can help describe the difference between two treatments, suggest structures and rewrite the article in either direction. It can even produce a plausible compromise.

But a plausible compromise has no authority of its own. It does not decide whose responsibility takes precedence, whether the customer portrayal is acceptable or whether the people approving the work agree that the article now serves its purpose. Those decisions still belong to the people involved.

Producing alternatives faster can be useful once we know what we are testing. Without that clarity, it can also give us more versions to circulate and more opportunities to keep the underlying disagreement open. The difficult work is reaching a decision that people understand and can act on.

For me, the practical response is to establish the article’s main job before another substantial rewrite. Then separate feedback about accuracy and approval from suggestions about treatment, and identify who will make the final editorial call. Where the material supports genuinely different purposes, consider separate pieces with clear roles rather than assuming one article must carry them all.

That is a shared editorial service in its own right: interpreting feedback, exposing the choices underneath it and helping people reach a direction the writer can execute. It takes knowledge of the audience, respect for other people’s responsibilities and a willingness to reconsider your own treatment.

The customer-story review reminded me that a strong draft is still an argument about what matters. Other people can improve that argument, sometimes by challenging its whole shape. Our job is to understand the challenge well enough to decide what the piece should become.