Friction is part of the work
The project meeting is calm. The milestones are green and nobody challenges the recovery plan.
Then the project fails exactly where several people had expected it to fail.
Afterwards, the warning signs appear in every reconstruction. The engineer had doubts about the design. Procurement knew the supplier was slipping. Operations did not believe the commissioning window was realistic.
The information existed. It never became a decision.
This is why culture is not the soft side of business. Culture determines whether the knowledge already present in the organisation can affect the work before reality makes the decision for you.
A quiet room can be expensive
Many organisations separate hard subjects from soft ones. Strategy, finance and technology belong to the serious agenda. Culture is discussed afterwards, often through values, surveys and workshops.
Daily work does not respect that separation.
A technical risk has to be voiced. A plan has to survive disagreement. A manager has to hear that the preferred solution will not work. The quality of these interactions changes the quality of the operating decision.
If people cannot challenge a weak assumption, the organisation has not removed the conflict. It has postponed it.
The later version usually costs more.
What Project Aristotle actually tells us
Google’s Project Aristotle asked what made teams effective inside Google. The researchers identified five team dynamics: psychological Safety, dependability, structure and clarity, meaning, and impact.
Psychological Safety came first. Team members needed to believe that interpersonal risk would not be punished when they asked a question, admitted uncertainty or offered an idea.
That finding is useful. It is not a universal law proving that talent or team composition never matter. Google itself presents the work as a way to think about effective teams and explicitly notes that other organisations may find different patterns.
The practical lesson is narrower and stronger: expertise creates value only when the interaction around it allows the expertise to enter the work.
A brilliant engineer who withholds a doubt contributes less than the organisation has paid for. A diverse team whose members edit themselves before speaking cannot use its diversity.
Psychological Safety is not comfort
The word “safety” invites a common misunderstanding. A psychologically safe team is not a room in which everyone feels comfortable and nobody is challenged.
Often the opposite is visible.
People ask the question that slows the meeting. They admit that an estimate is weak. A technician tells a senior manager that the proposed restart crosses a boundary.
These moments create discomfort. What psychological Safety changes is the personal price attached to that discomfort.
The work can become harder in the room because it becomes less dangerous outside it.
This is also why niceness is not enough. A polite team can avoid every difficult issue. Respect matters, but respect without candour protects harmony rather than performance.
Productive conflict needs boundaries
Permission to disagree does not mean every debate should continue indefinitely.
Teams need a shared purpose and enough technical context to understand what is being protected. Decision rights must be clear. Someone remains accountable for closing the discussion and choosing a course of action.
Without those conditions, voice can become noise. People repeat preferences, defend territory or reopen decisions without new information.
Psychological Safety does not remove the need for leadership. It changes the work of leadership.
The leader has to make dissent usable. They ask for the observation behind the objection. They distinguish a violated boundary from a different preference. Then they decide or place the decision where the best information sits.
The aim is not agreement. It is a decision that has had contact with reality.
Culture becomes visible in the first response
Values do not determine whether people speak next time. Reactions do.
A manager can invite challenge and still close the market within seconds. They roll their eyes, defend the plan before asking a question or explain how much effort has already gone into the decision.
The room learns quickly.
The reverse is equally concrete. A leader can pause, ask what the person sees and check whether the new information changes a boundary or assumption. The objection may still be rejected. What matters is that it was examined rather than socially punished.
Culture is built in this sequence, not in the poster beside the meeting room.
The hard currency is earlier truth
Calling culture “hard currency” does not mean inventing a financial value for every conversation.
Its economic effect lies in timing.
An early contradiction leaves choices. The design can change before procurement. The maintenance window can move before customers are promised a date. A weak signal can be inspected before it becomes an outage.
When disagreement is socially expensive, the same information arrives later. Options disappear while the eventual correction becomes more disruptive.
This is the connection to the Capacity Tax. Silence converts an avoidable conversation into delay, rework or damage. The invoice appears in operations, although the cause began in an interaction.
Culture is therefore not separate from performance. It governs when reality is allowed into the decision.
Put one decision under pressure
Do not begin with another culture programme.
Choose one important decision that appears settled. Ask the people closest to the consequences what would make it fail.
Do not defend it while they answer.
Then examine the strongest objection. Is it new information, a misunderstood boundary or merely a different preference? Decide what changes and explain what does not.
Finally, watch what happens at the next meeting. Do people bring difficult information earlier, or did they learn that the invitation was ceremonial?
That is a harder test of culture than a value statement.
The room should not always feel easy
A capable organisation does not eliminate tension. It prevents tension from going underground.
People can disagree without turning the disagreement into a personal contest. Leaders can remain accountable without pretending to hold all relevant knowledge. Teams can close a decision without silencing the information needed to revisit it later.
This is not a cosy affair.
It is disciplined contact with reality.
Further reading
Google re:Work: Understand team effectiveness
Google’s own guide describes the five dynamics identified in Project Aristotle and presents psychological Safety as the first. It is also valuable for its restraint: the findings came from Google teams, and other organisations may discover different drivers in their own context.
“Psychological Safety and Learning Behavior in Work Teams” by Amy C. Edmondson
Edmondson’s study connects psychological Safety to learning behaviour rather than comfort. The mechanism matters: teams perform better when people can ask for help, discuss errors and test uncertainty in the work.
“Employee Voice and Silence: Taking Stock a Decade Later” by Elizabeth W. Morrison
Morrison reviews why employees speak up or withhold work-related information. The article adds an important guardrail: voice is a discretionary behaviour shaped by hierarchy, context and expected consequences, not something leaders create by issuing an invitation.
Explore more in The Shift series
The Internal Market for Truth
How leadership reactions set the social price of bad news and determine whether local information arrives in time.
The Hero Reflex
Why an answer-giving leader can dominate the room even while asking other people to contribute.
Leadership without heroes. Decisions without a central nerve.
Get the „Capacity Protocol“. 7 heuristics for leadership in complex systems. Enter your email address here, and I’ll send you my free PDF within minutes.
You’ll also receive occasional updates, news, and notifications about new offers or publications from me. You can unsubscribe at any time with a single click.