What the template is and when to use it
The feedback theme template is one spreadsheet with one row per theme. Each row carries a customer problem from the first mention to the message that tells customers what changed: where it shows up, what it is, how much it matters, who owns it, what was decided, and who has been told.
It is the template promised at the end of the fifth lesson of the Voice of the Customer 101 video course, and its columns follow the course in order. Channels come from lesson 2, themes and sub-themes from lesson 3, the four-lens score from lesson 4, and owner, decision and both loops from lesson 5.
Fifteen columns, one illustrative example row and empty rows to fill. It opens in Excel and Numbers directly; in Google Sheets use File › Import › Upload.
Download the template (CSV)| Column | Lesson | What goes in it |
|---|---|---|
| Theme | 3 | The customer problem, in plain words, named as a problem rather than a solution: “Getting data out”, not “Add bulk export”. |
| Sub-themes | 3 | Two or three specific versions of the problem that a team can fix. |
| Type | 3 | Complaint, request, praise or question. Kept apart from the theme, so praise and problems never share a row. |
| Channels | 2 | Where the theme shows up: tickets, calls, reviews, community, surveys, usage, cancellations. |
| Customer quote | 3 | One verbatim line, in the customer’s words. |
| Customers affected | 4 | Volume lens. A count of customers, not mentions: one customer saying it ten times is still one customer. |
| Accounts and revenue at stake | 4 | Revenue lens. The accounts behind the theme, with renewals and open deals. |
| Trend | 4 | Growing, flat or fading since last month. |
| Severity | 4 | Annoyance, workaround or blocker that stops work. |
| Score (out of 12) | 4 | The four lenses, each scored 1 to 3, added up. Start each lens cell with its score and one line of reasoning. |
| Owner | 5 | One named person. Not a team, not a committee. |
| Decision | 5 | Fix, build, or explain why not, with the reason. |
| Due date | 5 | When the decision lands. A decision with no date is a wish. |
| Internal loop | 5 | The teams who carried the feedback in, told: yes or no, and the date. |
| External loop | 5 | The customers who raised it, told: yes or no, the date and the channel. |
- Use it when you group feedback by hand for the first time, when you prepare a planning meeting, and once a month to rescore and chase decisions.
- Do not use it for triaging single tickets or tracking bugs. A row is a problem many customers share, not one customer’s request.
- Keep it short. The theme list should fit on one screen. If it does not, merge before you add.
Channels: where the theme shows up
Lesson 2 sorts feedback into three kinds: asked (surveys and interviews), told (tickets, calls, reviews and communities) and shown (usage, renewals and cancellations). The channels column records which of these a theme appears in.
| Column | What goes in it |
|---|---|
| Channels | Where the theme shows up: tickets, calls, reviews, community, surveys, usage, cancellations. |
- Why it matters. A theme that shows up in tickets, calls and cancellations is sturdier than one that appears in a single survey. Support skews negative and surveys skew towards people who like surveys; several channels correct for both.
- Pair behaviour with words. If the theme shows up in usage or cancellations, list a channel with words next to it, so the row explains why as well as what.
- Include internal channels. The notes your sales and success teams write are customer feedback too.
Theme, sub-themes, type and quote: grouped by meaning
Lesson 3 builds themes in four steps: tag, group, name, nest. The step most teams get wrong is grouping. “I can’t find where to download my report”, “the spreadsheet export keeps timing out” and “why does the file lose my filters?” use different words for one problem. “Your reporting is fantastic” shares a word with them and is praise. Group by meaning, not keywords.
| Column | What goes in it |
|---|---|
| Theme | The customer problem, in plain words, named as a problem rather than a solution: “Getting data out”, not “Add bulk export”. |
| Sub-themes | Two or three specific versions of the problem that a team can fix. |
| Type | Complaint, request, praise or question. Kept apart from the theme, so praise and problems never share a row. |
| Customer quote | One verbatim line, in the customer’s words. |
- Two levels, no more. A leader decides with the theme; the team doing the work needs the sub-theme. Every sub-theme belongs to exactly one theme.
- Name the problem, not the fix. “Getting data out” lets the team find the best fix. “Add bulk export” locks you into one.
- Write a one-line definition per theme in a second tab, so two people tagging the same comment land on the same row.
- Keep an “other” row. When it grows, a new theme is knocking.
The four-lens score
Lesson 4 ranks themes through four lenses and scores each one 1, 2 or 3: low, medium, high. The four scores add up to a total out of 12. It is not precise, and it does not need to be; it makes the argument visible.
| Column | What goes in it |
|---|---|
| Customers affected | Volume lens. A count of customers, not mentions: one customer saying it ten times is still one customer. |
| Accounts and revenue at stake | Revenue lens. The accounts behind the theme, with renewals and open deals. |
| Trend | Growing, flat or fading since last month. |
| Severity | Annoyance, workaround or blocker that stops work. |
| Score (out of 12) | The four lenses, each scored 1 to 3, added up. Start each lens cell with its score and one line of reasoning. |
- Start each lens cell with its score. Then one line of reasoning, for example “3: rising fast”. Anyone can challenge the input instead of the answer.
- Break ties with revenue, then severity. When two themes share a total, the one with more revenue at stake goes first; if that ties too, the more severe one.
- Score the loudest customer like any other. One executive emailing every week is one customer. Their revenue counts once, in the revenue lens.
- Count the quiet ones. Customers who never complain and simply leave belong in the volume count too, which is why usage and cancellations are channels.
Owner, decision and due date
Lesson 5 closes the loop in three parts: owner, decision, tell. These three columns are the first two.
| Column | What goes in it |
|---|---|
| Owner | One named person. Not a team, not a committee. |
| Decision | Fix, build, or explain why not, with the reason. |
| Due date | When the decision lands. A decision with no date is a wish. |
- One person. A theme owned by a team or a committee is owned by nobody.
- Explain why not is a decision. A clear no, with a reason, is better than a maybe that lasts a year. Customers can plan around a no.
- Every decision gets a date. An owner without a date is the most common way a theme stalls.
Internal and external loop
The last part of lesson 5 is telling people, on two loops. The internal loop reaches the people who carried the feedback in: support agents, account managers and sales reps, who will talk to the customer next. The external loop reaches the customers who raised it, in the channel they used.
| Column | What goes in it |
|---|---|
| Internal loop | The teams who carried the feedback in, told: yes or no, and the date. |
| External loop | The customers who raised it, told: yes or no, the date and the channel. |
- A changelog is not a loop. A public release note is good, but the people who asked rarely see it. Tell them directly.
- Close the loop on a no as well. Say what you decided and why, or customers assume nobody listened.
- A row is done when both loops say yes. Move it to a closed tab with the dates, so next month’s sheet holds only open themes.
A worked example row
The course follows one invented theme through every lesson: a product whose exports fail. Here is that theme as a row in the template. It is an illustrative example: the lens scores are the judgements made in lesson 4, not measurements, and there are no real counts or account values behind them.
| Column | Illustrative entry |
|---|---|
| Theme | Example: Getting data out |
| Sub-themes | Can’t find export; export times out; export loses filters and settings |
| Type | Complaint |
| Channels | Support tickets; call recordings; community forum; review sites; cancellation reasons; founders’ shared inbox. Not in the survey. |
| Customer quote | The spreadsheet export keeps timing out. |
| Customers affected | 2: a moderate number of customers |
| Accounts and revenue at stake | 3: large accounts, several with renewals coming up |
| Trend | 3: rising fast |
| Severity | 3: blocker; it stops their work |
| Score (out of 12) | 11 |
| Owner | Product lead for data features |
| Decision | Fix the timeouts. Build scheduled exports. Explain why not for one older file format, with the reason. |
| Due date | Fix: this month. Build: next quarter. |
| Internal loop | Yes: support has an updated reply; account managers briefed before those renewals |
| External loop | Yes: a short message to every customer who reported it, in the channel they used |
Lesson 4 scores it next to two other invented themes, and the order is the point:
| Theme (illustrative) | Volume | Revenue | Trend | Severity | Total |
|---|---|---|---|---|---|
| Exports failing | 2 | 3 | 3 | 3 | 11 |
| Invoice confusion | 1 | 2 | 3 | 2 | 8 |
| Dark mode | 3 | 1 | 1 | 1 | 6 |
Dark mode is the most requested and comes last: many voices, mostly on free plans, flat, and an annoyance. Exports failing reaches fewer customers, but big accounts with renewals coming, rising fast, and it blocks their work. The course calls the theme “exports failing” for short; in the sheet it is named as the customer problem, “Getting data out”, with export failures as a sub-theme.
How to run it monthly
The template earns its keep as a monthly habit rather than a one-off exercise. Copy last month’s tab, then work through six steps.
- 01Collect. Pull the month’s feedback from every channel on your list, including the ones nobody reads today.
- 02Group. Add each piece to an existing theme or sub-theme. Add a new row only when the “other” row shows a pattern; merge before you add.
- 03Rescore every row. Not only the new ones. Renewals, deals and your product move, and a small theme that is doubling can matter more than a big one standing still.
- 04Sort by total. Take the top three to planning with one quote and the accounts behind each, and leave the scores on screen.
- 05Confirm owners, decisions and dates. Every top theme leaves the meeting with one person, one decision and one date. Flag last month’s dates that slipped.
- 06Close the loops. Tick the internal and external loop for every decision that landed, with the date and the channel, and move finished rows to the closed tab.
Where HyperOrbit fits
Everything above works in a spreadsheet, and it is worth doing by hand first so the team agrees on what a theme is. It gets hard when the feedback arrives from many channels every day and the sheet is only rebuilt once a month.
In HyperOrbit, Chorus, the voice-of-customer agent, does the collecting, grouping and scoring as feedback lands: it clusters reviews, calls, tickets and surveys into ranked themes, each with the quotes behind it and the ARR of the accounts that raised it. In the worked example on this site it groups 100 pieces of feedback into 8 themes and 35 sub-themes; the methodology page says what that example shows. The owner, the decision and the message to customers stay with your team.
The Starter plan is free: Chorus on one feedback source, 50 signals and 10 insights a month, with standard sentiment and themes. Run it on one channel and compare its read with your own sheet.