The Red Pen Doesn't Have to Sting: What Forty Quiz Sheets Taught Me About Feedback

The quizmaster handed me a pint and a red pen. That was the transaction. The favour was implied, the gratitude was lukewarm, and the stack of answer sheets was thicker than I'd expected. Forty sheets, eight rounds, one increasingly smudged red pen. I'd agreed to help mark a local pub quiz on a Tuesday in October, mostly because I like the pub and partly because I thought it would be a laugh. It was a laugh. It was also a masterclass in how people behave when someone tells them they're wrong.

The favour that kept giving

Marking a quiz is not complicated. You have an answer sheet, a correct answer, and a pen. The complication arrives when the teams crowd around the marking table to watch you do it. Suddenly it isn't admin. It's a public performance. Every tick is a small victory, every cross a tiny insult, and every half-mark a negotiation.

The first sheet was easy. The second was fine. By the fifth, I'd learned to keep my face neutral. By the fifteenth, I'd learned to say "I'll come back to that one" rather than argue. By the thirtieth, I'd started to notice something: the teams that took bad news well weren't the ones with the highest scores. They were the ones who understood what the mark meant.

What people do when they're marked wrong

There are broadly three reactions to being marked wrong in a pub quiz. The first is disbelief: "We definitely said that." The second is deflection: "That's not how you spell it." The third is the quiet nod, followed by a genuine question: "What was the answer, then?"

Only the third reaction is useful. The first two are about protecting face. The third is about closing the gap. And the difference between them usually isn't the person's temperament. It's how the feedback is delivered. If I slid the sheet across the table with a cross and no explanation, I got disbelief. If I said, "You put Cairo; we needed Alexandria — easy mix-up," I got a shrug and a laugh. Same mark. Different feeling.

That's not a soft point. It's a practical one. Feedback that makes people defensive is feedback they stop listening to. Feedback that makes sense is feedback they can act on.

Specific beats savage

I learned this the hard way in my own work. Client comments like "this doesn't work" used to send me into a spiral of guessing. What doesn't work? The layout? The tone? The fact that I used a semicolon in a button label? A vague criticism is not a clear instruction. It's a mood.

At the quiz table, the useful marks were the specific ones. "You wrote 'Churchill'; we needed 'Attlee'" is a fact. "Wrong" is a verdict. The fact helps. The verdict just stings.

The same applies to website reviews and client feedback. "I don't like the blue" is not a note. "The blue on the booking button fails contrast against the photo behind it — can we darken it?" is a note. One is an opinion. The other is a change request. If you want someone to do something differently, tell them what you saw, what you expected, and what would fix it. Keep it short. Keep it concrete. Don't dress it up as a personality flaw.

Say what's right, then what's next

Here's the thing about marking forty sheets: you start to notice the near misses. The team that got the year right but the wrong monarch. The team that had the right idea but the wrong spelling. A red cross alone erases that nuance. A tick with a note — "close, but we needed the full name" — keeps it.

In client work, the same principle holds. If a draft is mostly there but one section is doing the wrong job, say so. "The first three paragraphs are exactly the tone we want. The fourth repeats the intro — can we swap it for the pricing detail?" That's not flattery. It's navigation. People need to know what to keep as much as what to change.

And always end with the next step. At the quiz, the next step was simply the correct answer. In a project, it's the revised version, the phone call, the updated brief. Feedback without a next step is just a red pen with nowhere to go.

Timing is half the message

I marked most of the sheets while the teams were still eating. That was deliberate. If I'd waited until the end of the night, when everyone had had three pints and the room had gone loud, the feedback would have landed differently. Not because the answers changed, but because the audience had.

Timing matters in work, too. A comment left on a Friday afternoon with no context feels like a threat. The same comment sent on a Tuesday morning with a short note — "here's what I spotted, here's what I'd suggest" — feels like help. You can't always control when feedback arrives, but you can control whether it arrives with a frame around it.

The score isn't the story

The quiz ended, as these things do, with a tie-break and a mild argument about whether "a type of cheese" was an acceptable answer for "Stilton." It was not. The winning team bought a round. The losing team bought crisps. Nobody stormed out. The red pen went back in the drawer.

What stayed with me was how little the marking had to do with the marks. The teams that enjoyed the night weren't the ones that won. They were the ones that felt the marking was fair, clear and not personal. That's a low bar, but it's surprising how often it gets missed.

So here's my rule, borrowed from a pub table and now stuck to my monitor: mark the answer, not the person. Be specific. Say what's right. Offer the next step. And keep the red pen for the sheet, not the soul.