Run a small reader task session before requesting a new feature

A reader can sincerely say that a website is easy to use and still struggle to find yesterday's edition. General opinions and observed tasks answer different questions. Before requesting a substantial new feature, a small publication can watch a few willing readers attempt an ordinary task. The exercise does not need to become a formal research programme. It needs a clear question, respectful participation and honest notes about what happened. This guide describes a practical session that a small newsroom can organise without treating a handful of participants as a representative survey.

Choose one decision the session should inform

Start with a decision that is still open. Perhaps the team is considering a new archive menu because readers ask for previous editions. The session should investigate how people currently look for an edition and where the process becomes unclear. It should not begin with a mission to prove that the proposed menu is necessary. A missing date label may explain the difficulty just as well.

Write the decision and the uncertainty separately. The decision might concern whether to change archive navigation. The uncertainty is whether readers can distinguish edition dates using the current page. Keeping these separate prevents a preference for a particular design from determining the result. If the team already knows that a link is broken, repair and verify that defect before asking readers to spend time demonstrating it.

Invite participation without creating pressure

Explain the purpose in ordinary language: the publication wants to understand whether a particular task is clear. Participation should be voluntary, and the reader should be free to stop. Make clear that the website is being examined, not the person's intelligence or technical skill. Avoid recruiting only colleagues who already know where everything is. Their familiarity can hide difficulties encountered by occasional visitors.

Agree how notes will be taken. Written observations may be sufficient; recording a person's screen or voice is not automatically necessary. Do not ask participants to disclose passwords, private messages or unrelated browsing history. If the task reaches an account or payment step, use an appropriate prepared demonstration arrangement rather than improvising with someone's sensitive information. Keep the exercise proportionate to the question being investigated.

Describe the task without revealing its route

A useful task presents a goal and enough context to recognise completion. For example: find the district edition published on a specified recent date. Avoid instructions that name the exact menu and button to press. Those instructions test whether someone can follow directions, not whether the route makes sense. Use an edition that actually exists so that the task has a fair endpoint.

Check the task yourself beforehand to identify broken links or ambiguous wording. If multiple editions share a date, specify which one the reader needs. The purpose is not to create a puzzle. It is to observe a realistic action that matters to the publication. Prepare a second task only if it helps answer the same decision, such as returning from the opened edition to the archive list.

Observe actions before offering explanations

Ask the participant to proceed as they normally would. Notice the labels they examine, the links they choose and the points where they hesitate or change direction. A brief question about what they expected can clarify an action. Avoid explaining the layout every time they pause. Immediate coaching may make the session feel smoother while concealing the very uncertainty the team needs to understand.

If someone becomes stuck, offer help respectfully and record when it was given. Assisted completion is still useful evidence, but it should not be counted as independent success. Note the difference between a wrong destination and a correct destination that the person did not recognise. Those outcomes suggest different problems. One may require clearer navigation; the other may require a more informative page heading or edition label.

Keep observation separate from interpretation

An observation might read: the participant opened two links with identical labels before finding the requested district. An interpretation might be: the labels did not provide enough distinguishing information. Keep both, but do not merge them into a claim that all readers are confused. The notes should allow another team member to understand what actually happened without relying entirely on the observer's conclusion.

Avoid collecting more detail than the decision requires. A short sequence of actions, the result and any assistance given can be sufficient. Do not convert a small informal session into impressive-looking percentages that suggest population-level certainty. If three participants encountered the same label problem, say exactly that. The repeated observation is worth investigating even though the sample cannot establish how common the problem is across the readership.

Turn the finding into a limited change

Discuss the smallest change that addresses the observed difficulty. If the issue is indistinguishable edition links, descriptive date and district labels may be an appropriate first proposal. If participants repeatedly leave the archive because the route back is unclear, examine that route. Do not expand every finding into a request for a completely new publishing system. A specific observation deserves a specific response.

Confirm what can actually be changed in the publication's account. The Press Nexa plan page and contact route can support a concrete availability question. This process does not imply that custom research dashboards, arbitrary interface changes or a particular archive control are included in a subscription. Present the reader task and the observed obstacle so that the provider can discuss an appropriate supported option.

Repeat the task and report the limits

After an agreed change, check the same underlying task again with willing participants. Preserve the goal while avoiding a rehearsed walkthrough. Record whether the original obstacle remains and whether the change introduced a different difficulty. A reader who memorised the route from the first session may complete it easily for that reason, so acknowledge previous exposure when interpreting the result.

Finish with a short decision note: the task, participants involved, observations, change made and remaining uncertainty. That note is more useful than a broad declaration that the website is now user friendly. Small sessions can guide careful improvements when their limits stay visible. Their value comes from seeing a real reader's work clearly and responding to it, rather than collecting approval for a feature the team had already decided to build.