By Divya Jyoti Munjal

The survey closed.

The report was circulated.

The action plan was created.

The tracker is fully updated.

Every month, the author survey is reviewed as part of the author experience improvement project. Feedback is discussed. Themes are identified. Actions are assigned. Progress is noted.

Three months later, when results are evaluated again as part of quarterly Key Performance Indicators (KPIs), the numbers have barely shifted.

No one understands the reason.

In many publishing organisations, author survey projects do not fail because teams lack discipline. They fail because everyone completed their tasks and no one owned the outcome.

This is not a performance gap but a systems gap.

The monthly review versus the quarterly KPI

Monthly reviews create operational rhythm. They encourage teams to remain attentive to feedback comments shared by authors in the survey. Simple problems are identified early. Email templates are refined. Survey questions are reworded. Turnaround times are monitored.

On the surface, the system appears responsive.

The quarterly KPI, however, introduces a different dynamic. When performance is formally measured every three months, the focus subtly shifts. Attention moves from understanding feedback to demonstrating progress.

The conversation changes from:

“What are authors experiencing?”

to

“Why has the score not improved?”

Under KPI pressure, activity increases. New templates are introduced. Additional reminders are sent. Extra checks are added. The tracker is filled quickly.

However, visible activity does not always translate into perceptible improvement.

When monthly reflection turns into quarterly justification, projects drift away from experience and towards measurable display.

The illusion of progress

Survey projects often follow a familiar pattern:

• • Feedback is summarised.

• • Themes are identified.

• • Actions are assigned.

• • Deadlines are set.

• • Managers monitor completion.

On paper, everything looks structured.

Yet the central question is rarely asked: “Did this change what the author feels?”

When activity replaces purpose, progress becomes administrative rather than meaningful.

How misalignment quietly develops

Tasks become detached from goals

An author survey may receive comments such as:

• • “The process is unclear.”

• • “Proof corrections are not incorporated correctly”

• • “Response times are inconsistent.”

The intended goal might be: “Reduce author uncertainty during production.”

What gets implemented by publishing teams:

• • Update the proof email template.

• • Add a line about timelines.

• • Create a new FAQ page.

These actions are not wrong. The problem is that no one checks whether uncertainty has actually reduced.

Although the task is completed, the friction may still remain.

Stakeholders optimise their own area

• • Editorial refines communication.

• • The time to publication improves turnaround by two days.

• • Customer support standardises responses.

Each team delivers within its scope. However, the author journey does not operate in segments. It is experienced as a whole.

When every stakeholder focuses on their assigned column in the tracker, fragmentation persists. Authors do not evaluate departments. They evaluate the overall experience.

Survey projects fail when responsibility is divided, but perception is shared.

Managers measure completion, not impact

Project updates often focus on:

• • Were actions implemented?

• • Were deadlines met?

• • Is the tracker complete?

These are just operational checks.

Strategic improvement requires different questions:

• • Are authors emailing less for clarification?

• • Has the tone of author comments shifted?

• • Are repeat complaints reducing?

• • Do authors seem more confident about the next steps?

If these questions are not discussed, the organisation may confuse activity with real improvement.

The real problem: No one owns the outcome
In many survey initiatives:

• • Teams own tasks.

• • Managers own reporting.

• • KPIs measure percentages.

But no one explicitly owns the behavioural change the project was meant to produce.

Without outcome ownership, effort disperses. The tracker reaches 100% completion. The experience remains largely unchanged.

What needs to change

Improving survey outcomes does not require more urgency. It requires sharper alignment.

Define the outcome in observable terms

Instead of saying: “improve communication,” define: “authors should understand the production timeline without needing to email for clarification.”

Observable outcomes prevent vague action. They connect every task to a real behavioural shift.

Link every task to a specific friction point

Each action should answer a simple question:

“Which author frustration does this directly reduce?”

If the link is unclear, the action may be procedural rather than strategic.

Clarity at this stage prevents activity that looks productive but feels invisible to authors.

Assign ownership of the experience, not just deliverables

Alongside task owners, appoint one outcome owner.

Their responsibility is not to rewrite templates or shorten timelines. Their responsibility is to monitor whether combined actions are changing perception.

They ask consistently:

“Is the author feeling the difference?”

This single shift reduces fragmentation and strengthens accountability.

Replace status updates with impact conversations

In review meetings, move beyond: “Is it done?”

Instead ask:

• • What has changed since implementation?

• • What are authors no longer confused about?

• • What questions are appearing less frequently?

If nothing has shifted, the solution needs to change, not the timeline.

Make improvement visible

Authors rarely know what changes were made because of their feedback.

A brief message such as:

“Based on recent author feedback, we have clarified our proof guidance to make next steps clearer.”

signals responsiveness. It reinforces trust. It makes the survey meaningful.

Trust influences survey responses as much as operational efficiency does.

From task completion to experience change

Survey projects fail when:

• • Monthly reviews become routine.

• • Quarterly KPIs create reactive urgency.

• • Task completion receives more recognition than actual impact.

• • Completion is mistaken for improvement.

They succeed when different departments in an organisation move from:

“I completed my part.”

to

“Did the author experience improve?”

When all tasks are done and nothing changes, the issue is not effort. It is alignment, ownership and impact verification.

Before closing your next quarterly review, pause. Ask one final question:

“What is genuinely different for the author this time?”

If the answer is unclear, the project is not yet complete.

Call to action

If you work in journal publishing or author experience, I would genuinely value your perspective. Have you seen survey initiatives stall despite visible activity? What shifted the outcome in your organisation? Let us move this conversation from reporting metrics to improving experiences.