Ask the future editor to complete routine tasks
Ask the future editor to change a test item, replace its image, update hours, recover a mistake and preview the result. Record assistance, permissions and recovery separately. The handoff passes when the agreed routine work can be performed at the intended responsibility level, not when a developer finishes a demonstration.
Worked example — illustrative data.
| Task | Observe | Issue/register field |
|---|---|---|
| Change a test product description | Can the editor find and update the right item? | Task, assistance and result |
| Replace an image | Correct product and useful crop | Asset/source and validation |
| Update exceptional hours | All intended destinations affected | Source owner and scope |
| Recover a mistaken change | Supported undo/restore route | Recovery steps and help needed |
| Preview before publishing | Editor understands preview versus public state | Permission and confirmation behavior |
Use synthetic content in a safe environment and ask the editor to narrate their choices. Give the goal without pointing at the control. Note unclear labels, missing permissions and unsafe defaults separately from knowledge that a short runbook can address. After the task, provide guidance and repeat a meaningful action if needed. Keep the issue register with owner, severity, proposed change and retest condition.
Separate permission failures from editing confusion
Give the editor a test task under the role they will actually use. If they cannot replace an image, first check whether the control is unavailable or merely hard to find. Log the two causes separately: changing permissions may solve one, while labels or a short procedure may solve the other.
After guidance, use a different test item to check whether the editor can repeat the action independently.
Facilitator assistance can conceal an unfinished editor task
An editor may complete a task only because the facilitator corrected several steps. Mark it assisted rather than successful without qualification, and decide whether the interface, permissions or instructions need improvement.
Accept handoff when agreed routine tasks and recovery can be completed at the required responsibility level. Preserve unresolved tasks explicitly rather than calling a recorded training call proof of readiness.
Should the editor practice on a live product?
Use an unpublished duplicate or another approved safe environment. Preview the result and demonstrate the supported recovery route before making a public change. Keep learning mistakes separate from production content.
Continue with Guides for stores, software teams and local businesses, Website design and development services and Who should own your website, domain and analytics accounts?.