TL;DR

• The 5 Ws of customer feedback are why, who, what, when, and where you collect it, plus one H for how. Together they're a checklist for scoping a feedback effort before you send anything.
• Answer all six before you write a single question. Skip them and you collect data with no decision waiting on it.
• Match the metric to the moment: NPS for the relationship, CSAT for a single interaction, CES for how hard something was.
• Timing is a trigger decision, not a calendar one. Relationship surveys run on a schedule. Transactional ones fire after an event.
• The whole pass takes about 30 minutes and turns "we should get some feedback" into a plan someone can actually run.

Most teams think their feedback problem is a collection problem. Not enough responses. Not enough channels. Not the right tool.

It's rarely that.

The real problem shows up later. The responses arrive, land in a dashboard, and sit there. Nobody decided what they were for before the survey went out, so the data has no owner and no decision waiting on it. You end up with a number and a shrug.

The 5 Ws fix that at the start, not the end. Why, who, what, when, where, and how. Six questions that turn "we should collect some feedback" into a plan your team can run, and a customer experience you can actually move.

What Are the 5 Ws of Customer Feedback?

The 5 Ws of customer feedback are the six questions you answer to plan any feedback effort: why you're collecting it, who you're asking, what you're measuring, when you'll ask, where you'll reach people, and how you'll collect and act on it. Strictly, that's five Ws and one H. The "how" earns its spot, so most people fold it in and keep the name.

Here's the shift that makes the framework useful. Don't treat each W as a topic to read about. Treat it as a decision with an output. You're not learning why feedback matters. You're deciding what a specific round of feedback is for, then letting that decision settle the other five. Work through all six and you've scoped the whole effort before a single question exists.

The checklist sits one level below a full voice of customer framework. Think of it as the pre-launch pass you run for one survey, one campaign, one moment. For the wider view of how feedback fits your overall customer feedback program, start with the pillar and come back here when you're ready to scope something specific.

Why: Decide What the Feedback Is For

Naming why you're collecting feedback is the first step. It's also the decision that governs the other five. Get it wrong and everything downstream drifts. Get it right and the rest almost answers itself.

The rule is blunt. If you can't name the action a result would trigger, you're not ready to send. "We want a better understanding of our customers" isn't a reason. "We want to know whether the new onboarding flow met customer expectations and cut early churn" is. One tells you nothing about who to ask or what to measure. The other tells your customer success team both.

The payoff lives here too. Bain & Company's research on loyalty found that companies that build a system around customer feedback, rather than just gathering it, consistently outperform their peers. The gathering was never the hard part. Acting on it is. And you can't act on feedback you collected without a reason.

Who: Decide Whose Voice You Need

Once you know the decision, who to ask gets sharper. The instinct is to survey everyone. Resist it. Weight your audience by decision value, not by how many responses you'll get.

Your happy customers and your unhappy ones answer different questions for you. Ask promoters and long-tenured accounts what's working, so you know what to protect and scale. Mine the negative feedback and customer complaints from detractors, churned customers, and anyone who hit a wall, so you know what to fix. A pile of positive feedback feels good and teaches you little. The difficult answers are where the customer experience actually improves.

Segment before you send. Potential customers mid-evaluation, new versus established accounts, high-value versus long-tail. A detractor on a renewal-sized account and a detractor on a free trial are not the same signal, and treating them the same buries the one your sales and service teams most need to see.

What: Decide the Metric and the Data Type

What you measure follows from the question you're asking. Three metrics do most of the work, and each answers something different.

Pick the metric that matches the moment. NPS reads the relationship, so save it for relationship moments. CSAT, or customer satisfaction, reads a single interaction. CES reads effort, and it's the one most teams underuse. Research from CEB, published in the Harvard Business Review, found that reducing customer effort predicts loyalty better than trying to delight people. If your decision is about friction, CES is your metric.

Then decide the data type. A rating gives you a number you can track. An open-ended follow-up gives you the reason behind it. You want both. The score tells you something moved, and the text tells you why. For the full breakdown, see the three core metrics to measure customer feedback.

When: Decide the Trigger, Not the Calendar

When to ask isn't a date on a calendar. It's a trigger tied to the customer journey, and it depends on whether you're measuring the whole relationship or one moment against a customer's expectations.

Relationship feedback runs on a schedule. Quarterly NPS, an annual health check, a post-onboarding pulse at day 30. Transactional feedback fires on an event: a support case closes, an order ships, a demo wraps. Match the survey type to what you're measuring and the timing takes care of itself. Send relationship NPS after one support ticket and you're asking someone to rate a marriage after one conversation.

One more rule. Memory fades fast. A CSAT sent two hours after a resolved ticket gets a real answer. The same survey three days later gets a guess. Ask while the moment is still fresh.

Where: Decide the Channel by Where the Customer Already Is

Where you ask should follow the customer, not your team's convenience. Email, SMS, in-app, website, kiosk. Each reaches a different person in a different context, and the right one is wherever your customer already spends attention.

A mobile-first user won't open an email survey but will tap an SMS. A SaaS user mid-session will answer an in-app prompt and ignore a message that pulls them out of the product. A walk-in customer responds to a kiosk before they've left the building. Pick the channel that meets people where they are, and response rates climb without you touching the questions. When you're weighing options, this rundown of ways to collect customer feedback covers each channel and what it's good for.

How: Decide the Method, Then What Happens Next

How isn't just the survey format. It's the loop. Collection is step one of four: collect, analyze, route, recover. Most teams plan the first and forget the other three, which is exactly why so much feedback dies in a dashboard.

• Collect with the method that fits the channel and the moment.
• Analyze to find the pattern and the root cause, not just the average.
• Route the recurring customer issue to the person who can act on it.
• Recover by following up, so the customer knows they were heard.

At low volume you can read every response and route by hand. At scale you can't. When a few hundred open-ended answers come in a month, you need something to cluster them into themes and flag the ones moving your score, so you can dig deeper on what actually matters. That's where a feedback platform like Zonka Feedback earns its place. It groups responses into themes and surfaces the signals worth acting on, so a wall of text becomes a short list of things to fix. The last step, closing the loop, is the one that separates a program from a survey habit. Here's how to close the feedback loop once the responses are in.

How to Run the 5 Ws Checklist in 30 Minutes

You don't need a workshop for this. You need about half an hour and a decision worth making. Say your onboarding team suspects new SaaS customers are struggling in week one. Walk the six, evaluating each in a couple of minutes.

Why. To learn whether the revised onboarding flow reduced early drop-off. That's the decision. Everything else serves it.

Who. Customers who finished onboarding in the last 30 days. Not the whole base. The people who just lived through the thing you changed.

What. CES on the setup itself, plus one open-ended question asking what got in the way. A number you can track and a reason you can act on.

When. Triggered the day a customer completes onboarding, while it's fresh.

Where. In-app, since that's where they already are.

How. Auto-triggered survey, responses routed to the onboarding lead, detractors followed up within 48 hours. Six answers, one plan, no meeting required. Keep a reusable customer feedback survey template on hand and the setup drops to minutes. And once you know what you're running, this guide to customer feedback tools covers the options for actually running it.

Put the Six Questions to Work

The 5 Ws don't make your feedback smarter. They make sure someone's ready to act on it before it arrives. Every survey should have a decision waiting on the other end. If it doesn't, the answer is to plan, not to send.

That scopes one effort well. Do it enough times, with owners and workflows behind each one, and you've got something bigger. A repeatable feedback strategy. When you're ready to build that, a full voice of customer framework turns these six questions into an always-on program.