The Mr. Rogers Test: Audit Every Customer Touchpoint for Empathy

vintage tv

There is a line of dialogue that almost made it onto Mister Rogers’ Neighborhood, and it was simple, practical, and from an adult standpoint completely reasonable. The line was “don’t play in the road,” and before it could air, the head writer killed it.

That single edit contains a decision tree every founder-led business should steal. This post explains the Mr. Rogers test, why the sentence you wrote is rarely the sentence your client received, and how to run three common pieces of business copy through the test to close the gaps quietly costing you referrals.

What is the Mr. Rogers test?

The Mr. Rogers test is an empathy stress test applied to every customer-facing sentence, asking not “is this correct?” but “is this true and kind for every person who might receive it?” It was the standard behind Mister Rogers’ Neighborhood, where head writer Barry Head vetted every line to make sure it worked for every child, not most children.

Before anything aired, it went through what the team called the Neighborhood Writing Guidelines. Whatever you call it, it was a philosophy and a standard, and it changed everything about how they wrote the show, because the bar was not accuracy or clarity. The bar was empathy.

The line that never aired

Take “don’t play in the road.” Barry’s team sat with it and started asking the questions most writers skip:

  • Does every child who hears this even have a road near them?
  • Does every child have somewhere safe to play?
  • Does every child have the executive function to process a negative command and redirect themselves toward something safer?
  • And the one any parent will recognize: does telling a child not to do something actually stop them, or does it plant the idea and send them toward it?

Our brains do not handle negatives the way we assume they do, and if I tell you right now not to think about a pink elephant, you know exactly what is standing in your head. So “don’t play in the road” does not protect the kid; it puts the road in the kid’s mind and points them at the door.

The rewrite was not a softer version of the same instruction. It became “ask someone who loves you where it is safe to play,” which carries the identical concern and travels in a completely different direction: one version manufactures anxiety and fixates on the danger, while the other creates agency and points toward safety.

And they did not stop at the road. Every sentence went through the same process:

  • “Tell your mom” became “tell a grownup you trust,” because not every child has a mom or the assumed shape of a family.
  • “Go home if you’re scared” became “find a safe place,” because that line assumes home is safe, and for some children home is the scary place.

Every single time, an assumption about how a kid would process information got replaced with a principle written to travel with the child, whatever their family looked like, whatever their home felt like, whatever was happening on the day they heard it.

Why the sentence you wrote isn't the sentence your client received

The sentence you wrote and the sentence your client received are two different objects, because you wrote yours from the inside with full context and your client reads theirs from the outside with none. What feels fair to the person who built the policy is not the same as what is experienced as fair by the person on the receiving end, and that gap is where quiet damage lives.

For Fred Rogers, that gap was a moral problem, and he treated it with the gravitas it deserved. For you, the same gap is a revenue problem. Most founder-led businesses design their client experience from the inside out, which is not a criticism, it is structural, because you built the thing. You know the process, the flow, the refund policy, the automated emails that fire on day one and three and five. It all makes sense to you because you have the context.

Be honest, because I certainly have been: how many of us have had a client stumble over something and thought, I wish they would just read their emails, it was all in the email. I have said it, I still say it, and the thing to notice underneath it is that you are standing on the inside of the sentence while your client is standing on the outside.

That is the gap Barry Head spent his career closing, and it is the same gap sitting in your business right now doing damage you cannot see, because you have never experienced your own touch points the way a stranger would.

How to run the Mr. Rogers test on your business copy

To run the test, take a real piece of customer-facing copy and ask Barry’s questions: does this assume something, does it exclude anyone, does it tell someone what not to do instead of where to go, and is it kind from the outside or only from where you are standing? Then rewrite it toward the person on the other end, not the process that produced it.

Here are three common examples that do not survive.

Support tickets

“Submit a ticket and allow three to five business days” is clear and technically correct, but the person reading it is almost certainly contacting support because something went wrong, which means they are already frustrated, already doing the mental math on whether they made the right decision choosing you. The sentence also tells them what not to do (don’t expect immediate help, don’t call, don’t escalate) rather than where to go.

  • Before: Submit a ticket and allow three to five business days.
  • After: You’ll hear from a real person before the week is out.

Same timeline, except one sounds like a human wrote it for another human and the other sounds like legal reviewed it and shrugged.

FAQ deflection

“Please read our FAQ before contacting support,” read cold from the outside, is a mild accusation dressed up as a resource. It assumes you have the time, that you know where the FAQ lives, and that the answer is actually in there, and it tells you to do your homework before you are allowed to ask for help. I have lived this, mid-problem, after already Googling and reading every help article, being met by a bot insisting I read the very articles I had just read.

  • Before: Please read our FAQ before contacting support.
  • After: The fastest answers live here.

Same intent, except one trusts that the customer already tried and the other makes them prove themselves first.

Out-of-office replies

Even the humble auto-reply falls to the test. “I’ll respond when I return” leaves the reader wondering which Monday you mean and quietly tells them not to expect anything.

  • Before: I’ll be out of the office until Monday. I’ll respond when I return.
  • After: I’m back Monday the 12th, and if something urgent comes up before then, [name] can help at [email].

One clears the ambiguity and hands them a next step. The other leaves them guessing.

The one question that changes everything

Stop asking “does this make sense?” and start asking “what does this feel like to receive?”

The first question is about accuracy, and you can answer it from your desk with all of your context. The second forces you to step outside everything you know about your own business and read the thing cold, which is the only way to catch what a stranger feels.

The first question produces policies that are technically correct. The second produces experiences people actually remember, and for a founder-led business specifically, your reputation is not built on whether your policies are correct. It is built on whether clients can feel that you thought about them when you built the thing.

Satisfied clients renew and remarkable ones refer, and the gap between those two outcomes almost always lives in the sentences nobody thought to stress test.

Key Takeaways

  • The Mr. Rogers test swaps “is this correct?” for “is this true and kind for every person who receives it?”
  • You write customer copy from the inside with full context; your client reads it from the outside with none, and the gap between the two is where quiet damage happens.
  • Rewrite toward the person on the other end, not the process that produced the copy: tell people where to go rather than what not to do.
  • Support messages, FAQ deflection, and auto-replies are common places the gap hides, and each can be fixed without changing the underlying policy.
  • Change the question you ask from “does this make sense?” to “what does this feel like to receive?”

CATEGORIES

More Posts

Scroll to Top