The Quiet Half of Culture · ISSUE NO. 02
- Lauren Wu
- May 15
- 6 min read
EDITOR’S NOTE
A quick thank you to everyone who replied to Issue No. 01. The most common pattern in your responses was the same one I keep running into in advisory work — a behavior we'd been subtly attributing to a person, when the system around them was producing the same shape across multiple people.
Issue No. 02 picks up the thread. We are moving from H to E in the HEART pillars — from Humanity, the people inside the system, to Environment, the system itself.
— Lauren
Most cultural problems are environmental problems wearing a costume.
When a team is “not collaborating,” the first instinct is a workshop. When morale dips, we suspect leadership style. When good people start quietly checking out, we worry about engagement scores. We zoom in on the people. We rarely audit the room where they are asked to do their best work.
The environment is doing more work than we admit. The shape of the calendar — back-to-back, no recovery, no thinking time — produces a particular kind of mind. The shape of the comms stack: three channels, all interruption-shaped, none of them archival, produces a particular kind of decision. The shape of the meeting defaults: same room, same agenda template, same speaker order, produces a particular kind of voice in the room and a particular kind of silence around it.
If you change the environment, you change the behavior. If you don't change the environment, no amount of feedback, framework, or coaching will durably change the behavior. The environment will keep winning.
This is the part of culture work that gets the least credit and produces the most leverage. It is also the part most leaders skip, because it does not feel like leadership in the heroic sense. Restructuring the meeting cadence does not read like a leadership move. Removing a Slack channel does not read like courage. Replacing the default agenda template does not read like a vision.
It is all three of those things. It just happens at the layer most leaders are not trained to look at.
A short Environment audit, by way of three questions I keep returning to:
What does this team's default week look like — and what kind of work could only happen in that shape?
Where in the system is recovery being assumed but not designed?
If I removed one default — one recurring meeting, one channel, one ritual — what would actually break? And what might finally breathe?
The answers tell you where the architecture is doing the work, where it is doing the damage, and where you have been mistaking environmental pressure for individual choice.
Don't redesign the team. Redesign the room.
FROM YOUR REPLIES · ISSUE NO. 01'S QUESTION
Seven replies came in to last issue's audit question — name a behavior you've been quietly attributing to a person, then ask what condition would have to be true for that behavior to make sense. Different industries. Different surface behaviors. The same move underneath.
Anonymized:
“Resistance to change” — healthcare / clinical ops. → The proposed change introduces patient-safety ambiguity, unclear protocols, or cognitive load without support.
“Overly risk-averse” — fintech / product & compliance. → Regulatory expectations are unclear or punitive, and the cost of being wrong far outweighs the reward of moving quickly.
“Not collaborative” — banking / cross-functional teams. → Incentives, KPIs, or reporting structures reward individual performance over shared outcomes.
“Disengaged” — securities / trading and ops. → Decision-making is centralized, input is routinely ignored, or outcomes feel disconnected from effort.
“Micromanaging” — healthcare leadership. → There is high perceived accountability without reliable systems, visibility, or trust in process consistency.
“Avoids speaking up” — teaching / academic institutions. → Psychological safety is low, dissent is penalized formally or informally, or past feedback led to negative consequences.
“Slow to execute” — fintech / startups / product teams. → Prior mistakes were punished, expectations are ambiguous, or rework cycles are frequent due to unclear strategy.
The conditions readers named cluster into three patterns.
Ambiguity meeting asymmetric cost. When the rules are unclear and being wrong is punished disproportionately, hesitation is the rational response. From the outside, we read it as resistance, risk aversion, slow execution, and micromanagement.
Incentives misaligned to the work. When the system rewards individual performance, but the work requires shared outcomes, the behavior we then label “not collaborative” is exactly what the incentives produced.
Voice without consequence. When input is routinely ignored or dissent is penalized, people stop offering either, and we mistake the silence for disengagement or for not speaking up.
The shape underneath all three: the system is asking the person to absorb a structural cost that someone, somewhere, designed in. Sometimes deliberately. Often through accretion. Almost never through malice. Almost always through the environment.
Which is exactly why the fix is rarely at the level of the person. Thank you to everyone who replied — and a particular thank you to the readers who took the time to write more than I could fit. A second pass will land in the coming issue.
THE PILLAR · ENVIRONMENT
Environment is the second pillar of HEART, and the one most often outsourced. We delegate office design to ops and assume culture happens elsewhere. But environment is not just the physical room. It is every default the system establishes that people then operate inside without naming.
The defaults that matter most are usually invisible:
The unspoken rule is that the first person to fall behind absorbs the rework.
The unwritten norm that calendar density signals importance.
The implicit standard is that the manager who answers fastest is the one being trusted.
None of those defaults appear in any handbook. All of them shape who can succeed inside the system, and at what cost.
The Environment question for this week: what is one default in your team's environment that no one chose, and that is shaping outcomes you don't actually want?
FIELD NOTES · WHERE I'M SHOWING UP
CLE faculty appearance · May 11. Joining TRT CLE as faculty for “California Privacy & AI: From Constitutional Right to Algorithmic Fight.” California has been shaping the future of privacy law for more than fifty years; this session walks through where constitutional privacy meets algorithmic decision-making, and what that collision is now producing for practitioners. Open to licensed attorneys for CLE credit; details and registration at trtcle.com.
Attending · May 13-14. Attending Mic Drop LIVE, a two-day immersive conference for women growing paid speaking careers with real tools, real connection, and real momentum. So excited to meet my Speaker Sisters IRL.
Keynote · May 13. Speaking at the Women in Tech 2026 Global Conference with a version of “Still Here, Still Working.” The throughline: AI is reshaping the environment in which everyone now works, and what it takes to design a workplace where people remain in it. Conference details on the WTGC site.
Adjunct teaching · Just submitted grades and sent personalized emails to each student to thank them for an amazing semester. Felt like such a gift to teach these students.
READING · WHAT GOOD SYSTEM AUDITS ACTUALLY LOOK LIKE
A short list I keep returning to. Each earns its place; none are new.
Donella Meadows, Thinking in Systems: A Primer. The canonical short text. Start with the appendix on leverage points — it pays for the rest of the book on its own.
Christina Maslach & Michael Leiter, The Truth About Burnout. From the researchers who built the field's measurement instrument. The most rigorous case that burnout is a workplace condition, not a personality one — and the closest thing we have to a structural diagnostic.
W. Edwards Deming on the Red Bead Experiment. A single demonstration that does more to dismantle individual-blame thinking than any chapter ever has. Find one of the original recordings on YouTube; ten minutes very well spent.
Edgar Schein, Organizational Culture and Leadership. The three-level model — artifacts, espoused values, underlying assumptions — is the backbone of most useful audits I've seen, mine included.
ONE QUESTION
This week, name one default in your team's environment that no one on the team actually chose. Then ask what would change if that default were redesigned. Reply with what you find — the most useful answers will show up, anonymized, in a future issue.
—
The Heartwright is written by Lauren Wu and published by Heart Led Leadership.www.heartledleadership.org
Comments