Insights
You can't fix a people problem that's actually a system problem.
April 27, 2026
Something goes wrong on the floor.
A guest gets the wrong information. A procedure isn't followed. The same mistake happens again.
And the first instinct is always the same.
"We need to talk to that staff member."
It looks like a people problem.
Someone didn't follow the procedure.
Someone forgot to pass on the update.
Someone trained the new hire the wrong way.
So you address it. You have the conversation. You remind the team.
And for a while, it gets better.
Then it happens again.
When the same problem keeps coming back
If a mistake happens once, it might be a people problem.
If it keeps happening — with different staff, across different shifts — it's a system problem wearing a people problem's face.
The system allowed it.
The system didn't make the right information visible.
The system relied on memory, timing, and whoever happened to be in the room.
Fixing the person doesn't fix the system.
What a system problem actually looks like
It looks like this:
A procedure changes. The manager tells whoever is on shift that day. Everyone else finds out eventually — or they don't.
A veteran staff member keeps doing things the old way. Not because they're careless. Because no one knew they hadn't seen the update.
A new hire gets trained by someone working from outdated information. The mistake gets passed down like a tradition.
Nobody is trying to cause problems.
The system just has no way to close the loop.
The difference between addressing and solving
Addressing a people problem feels productive.
It's a conversation. An action. Something visible.
Solving a system problem is quieter.
It means changing the structure so the same mistake becomes less likely — regardless of who's on shift, how experienced they are, or whether they happened to be in the room when the update was announced.
One approach depends on the right person doing the right thing at the right time.
The other doesn't.
This is what I'm building toward
Growpath is built on a simple idea: the right information should reach the right people — automatically, regardless of shift, tenure, or who remembers to mention it.
When a procedure changes, read status resets for everyone.
No one gets to stay on an outdated version just because they weren't in the room.
Not because we don't trust the team.
Because we don't make the team carry what the system should be carrying.
If you keep having the same conversations about the same mistakes — it might be time to look at the system, not the people.
Growpath makes "what changed" and "who has seen the latest version" visible across your whole team.
If your team relies on whoever's on shift to keep everyone else informed — it's probably already costing you more than you think.
Growpath makes "what changed" and "what was missed" visible across shifts.