Attacks vs. Feedback

1. Filter out the tone.

Most of us wouldn't scream at a salesperson face to face, but it happens in writing, whether through clumsiness or the safety of anonymity. Just because someone is shouting at you about how YOUR SHODDY PRODUCT RUINED TIMMY'S CHRISTMAS MORNING! doesn't mean the complaint isn't valid.

2. Can you verify the underlying facts?

The customer isn't always right, but even when they're wrong there may still be a kernel of truth—so dig before dismissing. If nothing else, you may discover a place where you could more clearly set expectations.

3. Is there consensus or contradiction?

I received chapter markups from one reader who wanted more detail, while another felt I was too wordy. Contradiction doesn't make the opinions invalid—both may be fair depending on usage, department, or some other circumstance.

4. Do they suggest fixes?

If a customer or employee writes a paragraph about what's wrong, they're more likely to be a disappointed fan than a fussbudget. Even impractical suggestions may still be great brainstorming fodder.

5. Are there related themes?

Before you dismiss a comment, look for similar issues—that outlier may just be a different expression of a more common issue.

6. Quantify it!

Whether through coding verbatims or adding a rating question to the next edition, try to get a tally on your issues.