Thinking
- Rachel

- May 1
- 1 min read
Something I keep thinking about after my last post about my son’s class:
From the teacher’s perspective, there probably isn’t a problem.
The rules are clear.
The intent is good.
Everyone is being treated “the same.”
But from the student’s perspective, the experience tells a different story.
That gap doesn’t usually come from bad intentions. It comes from the language we use to describe what’s happening.
At the bedside, this shows up all the time.
A policy says the process is “clear.”
A workflow is labeled “standard.”
An expectation is described as “reasonable.”
Meanwhile, staff are:
translating the policy into real steps
adapting it to the patient in front of them
and quietly filling the gaps so care doesn’t fall apart
When the policy only reflects intent — not experience — the system looks fine on paper, and frustration grows in practice.
Over time, culture follows the language we allow. People stop speaking up because it doesn’t seem to change anything.
They comply, but cautiously.
They do the right thing — and stop expecting the system to meet them halfway.
Plain language isn’t about dumbing things down.
It’s about naming what work actually looks like.
Because when we can describe reality clearly, we can improve it. And when we don’t, the system keeps teaching people to work around it instead.
This is why I care so much about plain language in compliance —
it’s how systems become visible to the people who have to live inside them.




Comments