Measure Where a Communications Pilot Saves Work and Where It Adds It

The pilot produces a first draft quickly. The account executive then copies its claims into a review sheet, searches for source pages and emails a colleague to ask which attachment is current. The editor sees an apparently finished draft and starts another search. A report that stops at draft completion will miss the work the team now wants to fix.

Once you have a pilot's basic quality and effort measures, add a small record of interruptions and handoffs. The purpose is diagnostic: locate the step that creates avoidable searching, repeated checking or waiting. You need enough detail to choose a repair, without asking participants to narrate every minute of their day.

Create an entry when someone cannot proceed, repeats a completed action or transfers a question to another owner. Record the assignment, stage, time, person, trigger and next action. Use plain reasons such as source inaccessible, current version unclear, fact owner unknown or claim wording changed. Leave room for an explanation that the categories do not capture.

Track active effort separately from elapsed waiting. If two people each spend ten minutes checking in parallel, that is twenty person-minutes within a ten-minute elapsed interval. If a draft waits for two owners at once, overlapping waits should not be added into a fictional longer delay. Keep the event times so another reviewer can reconstruct the sequence.

Attach the smallest useful evidence, such as a version reference or an issue identifier. Do not copy restricted source content into a broadly shared pilot log. The diagnostic record needs to show why the work stopped and how it resumed, while the underlying material stays in its authorized location.

The sequence suggests at least two possible interventions. A clearer passage reference and population definition could reduce the initial search and clarification. A named deputy might change the waiting time when the owner is unavailable. Neither follows automatically from the fact that the draft was generated quickly. Ask the participants which intervention addresses the cause they encountered.

Some added work is valuable. A pilot may reveal that the previous process rarely checked whether a source supported a claim. The new verification effort should appear in the total, with its purpose explained. Removing that check to recover a drafting-time advantage would answer the measurement problem by weakening the workflow.

Other work may simply move between roles. A writer may save time because an account coordinator prepares a cleaner input pack. Count the coordinator's effort and ask whether the preparation is reusable. Keep one-time setup visible separately, and state how it is allocated when comparing subsequent assignments. Avoid assuming future reuse that has not happened.

Logging also costs time and can influence how people work. Try a short set of fields, review them with participants and remove fields that never inform a decision. Ask about unlogged interruptions during a brief debrief, but label reconstructed estimates as estimates. The record should support learning without becoming a ranking of individual colleagues.

Group repeated reasons by assignment type and inspect their traces. A frequent small search and an occasional missed release deadline deserve different discussion. Include unfinished and abandoned tasks. A log of only successful handoffs can hide the friction that caused people to leave the pilot altogether.

Choose one repair, such as sending the exact source passage and scope with each disputed metric. Try it on comparable work while keeping quality checks in place. The resulting decision should name the handoff to keep, revise or stop, with the event records that explain why.