Most teams don't notice a communication problem until someone walks in and makes the absence visible. Ours was no different.
We had dashboards. We had a weekly standup. We had a shared channel where people posted updates — when they remembered. By every surface measure, our ops team was functional. Incidents got handled. Deploys went out. Nothing was on fire.
But nothing was getting better, either.
Not a VP. Not a staff engineer. An ops coordinator — someone whose entire job was to track what was happening across the team and make sure the right people knew the right things at the right time.
We'd never had this role before. The honest reason we created it was that our founder was tired of asking three people the same question and getting three different answers.
Her name isn't the point. What she did in her first two weeks is.
Her onboarding wasn't passive. Instead of quietly reading docs and nodding along, she started asking questions that exposed how thin our shared understanding was.
"Where is the decision recorded?"
"Who owns this after the handoff?"
"If you were out sick tomorrow, how would someone pick this up?"
These weren't gotcha questions. They were the kind a newcomer asks when they genuinely need to do their job and the answers don't exist yet. The discomfort wasn't coming from her tone. It was coming from the gaps.
Within five days, she'd surfaced a pattern none of us had named: decisions were made in private messages and never written down. Status lived in people's heads. Escalation paths depended on who happened to be online.
We'd been running on tribal knowledge and calling it process.
She didn't ask permission to change the culture. She just started doing her job in a way that made the old habits feel obviously wrong.
Every meeting she attended got a short summary posted to the shared channel within ten minutes: what was discussed, what was decided, who was responsible for what. Every escalation she was involved in got a timeline — not a postmortem, just a plain-language sequence of events.
The format was nothing special. Bullet points. Timestamps. Names next to action items. But it was consistent, and it was visible.
Within a week, other people started doing the same thing. Not because she told them to. Because once someone models the behavior, the absence of it starts to look like negligence.
Here's what changed in the month after she joined:
Escalations got faster. When people could see a written timeline of what had already been tried, they stopped asking "did you check X?" and started contributing at the right altitude. Less repetition meant shorter resolution times.
Ownership got clearer. Writing down "Maria owns the next step" in a public channel is a small act with a large forcing function. It removes ambiguity without adding bureaucracy. People stopped assuming someone else was handling things.
Meetings got shorter. When the previous meeting's outcomes were already documented, the next meeting didn't need its first fifteen minutes reconstructing what happened last time. We got that time back.
Disagreements got healthier. When a decision and its reasoning are written down, you can revisit them without relitigating them. "We chose this because of Y constraint" beats "I think we decided something about this a while ago."
None of these outcomes required a new tool, a new framework, or an all-hands announcement. They required one person doing visible work that made invisible work harder to ignore.
It would be easy to frame this as "we hired a superstar." That misses the lesson.
What actually happened: we hired someone whose job description forced a discipline we'd been avoiding. She wasn't unusually talented at documentation. She was the first person whose role made documentation non-optional.
The culture didn't change because she was exceptional. It changed because her working style collided with our defaults — and her defaults were better.
Any team can have this collision, if they're willing to let a new perspective actually land instead of smoothing it into the existing shape.
Culture shifts rarely come from memos or offsites. They come from moments: a question nobody had asked, a habit someone models, a visible gap someone refuses to walk past.
If you're waiting for the right time to rewrite your team norms, you may be looking in the wrong direction. The catalyst might be a single hire whose daily work makes the old way untenable.
You don't need a manifesto. You need one person doing the work visibly, consistently, and without apology. The rest follows — not because people are told to change, but because they can finally see what good looks like.
Be the first to comment.
0 comments
Loading comments...