Templates & team workflows

Prioritise customer feedback without losing context

Compare feedback using impact, frequency, effort and evidence. Preserve the original problem before choosing a change.

template.fyi9 October 20264 minute read
Read the guide
Workspace with a laptop and documents
Stock photo: Mikhail Nilov / Pexels
Your starting pointCustomer feedback often arrives as a proposed feature: add a dashboard, create a new button or send more notifications. The suggested solution may be useful, but it does not fully explain the underlying problem. A prioritisation worksheet becomes more helpful when it preserves that context. Start by understanding what the customer was trying to do and where the existing process failed them.
The approachKeep a short description of the task, the difficulty and its effect. An illustrative entry might say that a project owner cannot quickly find which approvals are still missing. That tells you more than dashboard requested. Ask for clarification when the meaning is uncertain.
Your next stepRevisit the evidence and ask whether the task became easier. Where appropriate, tell the contributor what happened to their feedback. template.fyi lists a Customer Feedback Prioritizer for organising this work. Inspect the fields and adjust the definitions to your service. The value is a transparent decision process, not a score that pretends every choice can be automated.

Customer feedback often arrives as a proposed feature: add a dashboard, create a new button or send more notifications. The suggested solution may be useful, but it does not fully explain the underlying problem. A prioritisation worksheet becomes more helpful when it preserves that context. Start by understanding what the customer was trying to do and where the existing process failed them.

Record the situation behind the request

Keep a short description of the task, the difficulty and its effect. An illustrative entry might say that a project owner cannot quickly find which approvals are still missing. That tells you more than dashboard requested. Ask for clarification when the meaning is uncertain.

Separate the customer's words from your interpretation. Store personal information only when it is necessary for follow-up, and restrict access appropriately. A planning sheet does not need every detail from a support conversation.

Compare evidence consistently

Choose a small set of dimensions, such as impact, frequency and effort. Explain what each score means. A high frequency score could require several independently observed cases rather than a strong opinion in one meeting. Use a note alongside the score to show the evidence.

Mark unknowns explicitly. Missing effort information should lead to investigation, not an invented number that makes an item look ready for delivery.

Discuss the tradeoff with the team

Review items in the context of your current goal and capacity. A frequent annoyance may matter, while a rare security concern can require immediate attention for a different reason. A numerical total should not erase those distinctions. Keep a route for necessary specialist review.

When choosing an item, record why it was selected and what you expect the change to help. Define a small way to check whether the original problem has improved.

Close the loop after the change

Revisit the evidence and ask whether the task became easier. Where appropriate, tell the contributor what happened to their feedback. template.fyi lists a Customer Feedback Prioritizer for organising this work. Inspect the fields and adjust the definitions to your service. The value is a transparent decision process, not a score that pretends every choice can be automated.

Give your team a useful starting point.

Explore templates around a real task, then test the structure with one piece of work.

Explore the catalogue

Useful links and sources