Skip to content
Kaarne Superstore⌕
AI & Digital Tools

What Should Stay in the Website Backlog?

An old suggestion can contain a current need, an obsolete solution or a problem already addressed. Triage the relationship before assigning more work.

Coordinator sorts old feedback toward current work, reframed work and an archive envelope.

The website backlog contains a request for a larger banner, a report about an old form and a suggestion to add a service the business stopped offering. Their age does not tell you which ones still deserve work. Their relationship to the current page and need does.

Review the need before the proposed solution

Imagine a fictional community arts organisation reviewing its website backlog after changing its programmes. A comment from last spring asks for a prominent evening-class banner. The banner may be obsolete, but the underlying need could remain: prospective learners must find suitable session times.

For each item, locate the original observation, affected page and intended reader need. If the record contains only “make banner bigger,” ask what problem prompted it. Do not invent a convincing rationale simply to keep an old item alive. Mark the missing context and identify who could establish it.

Use four questions to choose a disposition

Work through a small selection with the relevant owner:

  • Does the page or journey still exist in a comparable form?
  • Does the underlying reader or business need remain relevant?
  • Is the reported issue still observable, or has another change addressed it?
  • What decision or evidence would justify further work now?

Keep the disposition separate from implementation priority. An item can describe a real problem and still wait behind a more consequential one. “Still relevant” means it deserves a deliberate place in the work; it does not promise immediate delivery.

Case one: the need remains and the issue is current

The old form report says applicants cannot tell which programme their enquiry concerns. The current form still presents the same ambiguity. Record the present route and observation, link the earlier report and define the next check. Retain the useful context without pretending the original screenshot is evidence of today’s exact interface.

The next action might be confirming the information the receiving team needs before revising the form. Avoid jumping directly from a retained item to its original proposed fix. The current page and service may support a better solution.

Case two: the page changed but the need survived

The evening-class banner no longer belongs on the redesigned programme page. Visitors still need to distinguish daytime and evening options. Reframe the backlog item around that current decision: can someone find sessions that fit their available time?

Link the old suggestion as history, then describe the present question and an owner. This preserves the reason without carrying forward obsolete implementation instructions. A refreshed title alone is insufficient if the body still directs someone to edit a component that no longer exists.

Case three: another change addressed the issue

A comment asks for the location beside every class. The current design already shows it clearly in the agreed places. Record what was inspected and how it relates to the earlier concern. If the team agrees no further work is needed, close or archive the item through the normal process with that reason.

Do not imply that a closed item can never return. A future observation may describe a different location or a later regression. Keeping the basis for the decision makes that distinction easier to establish without reopening every old discussion from memory.

Case four: context is missing or the need ended

For an unexplained screenshot, set a bounded clarification action with the person who can help. If they cannot recover enough context, record that limitation and let the backlog owner decide its disposition. Indefinite “investigate someday” items conceal an unresolved ownership choice.

If the discontinued service removes the need entirely, note the business change. Follow the organisation’s record-handling process rather than treating triage as permission to erase every historical discussion. The useful result is a smaller set of intelligible current choices, with reasons for what left active work.

Check whether an old comment still describes the current page and need. A feedback system should help you keep that context visible while you decide what deserves further work.

For an old issue reported again, compare the request, completion record and new observation. If ownership is changing, retain the important unanswered questions in an open-decision handover map.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.