In which organizations develop their own weather.
Reading the Air
I used to trust a green dashboard the way you trust a quiet house at night: lights on, doors locked, nothing visibly wrong. The longer I stayed close to the work, the more that wall of green felt less like safety and more like silence settling after an argument nobody wants to continue.
Silence has weight. A hush that muffles what's happening underneath. Calm becomes camouflage for problems learning to hide better. Behavior shifts first. Numbers follow later.
I learned that in meetings long before I learned it in metrics. Arguments, even heated ones, mean people still believe change is possible. What unsettles me now are the too-smooth meetings where consensus slides in without resistance, where nobody slows things down with a hard or pointed question. Frictionless agreement often masks deeper trouble.
The signals arrive through quieter cues before anything else. A familiar joke stops landing. People speak in shorter sentences. Healthy debate turns into hesitation everyone agrees to call patience. A teammate who once challenged assumptions now just nods along. A team builds workarounds in private. Problems stop getting mentioned, not because they're solved, but because people long ago stopped expecting solutions.
The Japanese have a phrase for a skill most organizations lack: kuuki wo yomu (空気を読む), reading the air. It names the ability to sense what's happening in a room before anyone says it aloud. In Japanese social and work life, failing to read the air isn't a small mistake. It means you've missed what everyone else already feels.
We all like to think we can read the air. Sometimes we can. Sometimes we convince ourselves we can. I've walked into rooms certain I understood where a decision would land and watched it break the other way. I've mistaken fatigue for dissent. I've ignored tension because the numbers still looked fine.
You can feel it before you name it. The hallway outside a difficult meeting carries a different pressure. People check their phones with unnecessary focus. A laugh surfaces half a second late and the room tilts. The coffee machine hums while everyone waits for something they won't say out loud.
Teams develop climate the way cities do. Pressure builds over weeks and settles. A reorg leaves a cold front that lingers long after the announcement. Conversations that once moved easily begin to drag. None of this appears on the dashboards leaders check each morning. You notice it in the pause after a simple question, or in the silence that enters a room once a senior manager steps out.
I have a dwarf cypress planted in a pot that does not suit it. The soil dries faster than it should. Some seasons it needs almost nothing from me. Others, a few dry weeks pull the earth away from the rim and leave brittle needles collecting at the base. The difference between health and decline turns on whether I notice conditions shifting before the damage sets in. Ignoring the signals has never once worked out.
I've witnessed quarters that looked flawless on paper while hallway conversations told another story. Informal updates contradicted reports. Anecdotes in the coffee line revealed stressors that never made it into status meetings. At first, people laugh off the mismatches. Eventually, the gaps stop being funny.
That's when trust begins to erode. Teams route around the official system, leaning on their own experience instead. Success becomes a mask for cracks widening underneath.
The most dangerous contradictions hide in plain sight: teams hitting targets while morale sinks, customer scores rising while support queues overflow, efficiency metrics improving while the work itself gets harder. When official metrics and lived experience drift apart, people stop trusting the numbers. Decisions migrate to side chats and backchannels while the dashboards keep updating as if nothing changed.
By the time dashboards flip red, the problem already has roots. Calm periods demand the most vigilance, because smooth metrics invite smooth meetings, and smooth meetings discourage hard questions.
When calm feels too clean, I tug on threads. Not from cynicism, but from curiosity about what's really holding things together.
| What I Ask | What I'm Really Looking For |
|---|---|
| What are we constantly working around? | The gap between designed process and actual practice. Broken steps everyone steps over without naming. |
| What's the thing we all pretend is fine? | Trouble we've normalized just to keep moving. The elephant that's been in the room so long it feels like furniture. |
| Where do we succeed despite our systems? | Individual heroics mistaken for process. Luck reframed as strategy. Effort stretched thin and treated as baseline. |
| What do new hires ask that we stopped questioning? | Misalignments we've trained ourselves not to notice. Fresh eyes catch what familiarity hides. |
| What breaks if two key people disappear? | Critical knowledge kept only in memory. Relationships propping up what structure never covered. |
| What gets skipped when pressure rises? | The steps that show their true value the moment they're dropped. Props in a play versus load-bearing beams. |
| Who stopped speaking up, and when? | Voices that went quiet after being ignored. Early alarms that learned not to sound. |
| What story do we tell ourselves about why this works? | The narrative gap between how we explain our success and what actually drives it. Stories polished into strategy. |
Sometimes I add a little stress, not to break things, but to see where they're already fragile. The fractures that appear under light pressure were always there. They just needed a reason to show.
Healthy systems can withstand examination.
Fragile ones deflect inquiry, change the subject, or treat curiosity as disloyalty. I've learned to watch what happens when someone asks an uncomfortable question in a meeting. Do people take it seriously, or pivot immediately to safer ground? Does curiosity get labeled as negativity? Do follow-ups get brushed off? How people respond to inquiry often tells more than the answer itself. The most brittle systems develop elaborate defenses against uncomfortable truths. They reward smooth consensus over messy accuracy. They punish skepticism instead of treating it as vigilance.
Engagement surveys arrive after decisions land. Pulse checks measure the afterglow rather than the event. The number in your inbox tells you something, though rarely the part that shapes how people show up the next morning. Reading the air works on a different frequency.
Belonging forms through repetition. People decide whether they fit through dozens of moments where effort feels recognized or ignored. Morale follows the same pattern. When that accumulation turns negative and leaders move forward as if nothing has changed, people narrow their commitments. Risk-taking contracts. Decisions stretch across days rather than hours because no one wants to stand exposed if the temperature drops again.
The moment of the shift is easy to miss. Weather does not announce itself. It settles until ordinary tasks feel heavier. Meetings drift. Projects slip an inch at a time. The day feels harder than it should, and no one can say exactly why.
A few weeks of inattention in the wrong season, and what looked like health turns out to have been momentum.
Calm is rarely resolution. It's often the interval where problems learn to survive without being seen. The air changes long before the dashboard does.
Footnotes
I've also seen leaders convince themselves that unease meant decay, only to discover the system was fine and their own anxiety was the distortion.
Numbers can lag behavior. They can also correct it. Distrusting metrics entirely is just another kind of blindness.
Reading the air can also become projection. Sometimes what feels like tension is just discomfort with change. Sometimes what feels like fragility is simply growth.
The important skill isn't sensing something unusual. It's separating signal from whatever you're carrying into the room.
Reply
I’d welcome your thoughts on this essay. Send me a note →
