What does the newcomer learn?
A team is about to ship. Someone spots a defect and asks for a delay. The manager says, "We care about quality," then blames that person for missing the deadline. A newcomer watches. Next time, will they raise the problem or keep quiet?
Culture includes the shared meanings and repeated behaviour people learn together. Praise, punishment and what passes without comment can teach a different lesson from the welcome speech. The same tension appears when a team praises learning through play but ridicules an unsuccessful experiment.
To change culture, change what happens when people act on the values you claim.
This is our operational synthesis, not a universal proven law. It directs attention to a response you might change, rather than promising that one response will fix a whole culture. The scene above is illustrative, not a diagnosis of a real team.
Separate what was said, what happened and what you suspect.
- Declared values
- "Quality comes first." This is what the team says matters.
- Enacted patterns
- Shipping on time earns praise. Raising a defect brings blame. Look for what gets rewarded, tolerated or punished across repeated choices.
- Possible deep assumptions
- "Bad news threatens my standing, so I should hide it." That is a hypothesis to investigate with people, not something you can read from one incident.
Workload, missing skills or unclear authority may also explain a failure. Different groups can learn different lessons in the same organisation. Ask what people learned; do not assume culture explains everything or that belonging requires agreement.
Follow the consequences into everyday work.
Values become visible in trade-offs. In the quality example, which mattered more when time ran short? Beliefs shape what deserves attention. If the team assumes a delay is always worse than a defect, what evidence would change that belief?
Incentives and tools affect which choices are easy, costly or even possible. A defect form is little help if nobody has the right to pause delivery. Compare who earns praise with who can decide, question or stop the work.
Onboarding teaches enacted patterns as well as written instructions. A newcomer needs to see how decisions and feedback connect, including who can stop or correct a choice. Asking them to recite the values does not show what they have learned from watching the team.
Play gives people room to try. Reflection matters when it changes the next decision. If a failed experiment earns ridicule, start by changing that response, not by demanding more enthusiasm for experimentation.
Try one consequence change, with willing people.
Choose one recurring mismatch between a claimed value and what happens when someone acts on it. Keep the practice small and voluntary. Declining or disagreeing must carry no penalty. Nobody owes the group personal disclosure or agreement.
- Agree who can safely pause work when a defect appears, who will support the person raising it, and how the team will handle the delay without blame. If you cannot agree a safe pause and support, do not start.
- At the next comparable decision, notice whether bad news surfaces and what happens to the person who raises it. Was the defect addressed? Ask willing participants whether speaking up felt safer; do not infer their answer from silence.
- Keep a minimal note of the choice, response and result. Protect privacy: leave out names and personal disclosures, and agree who may see the note. Review what the response taught people and revise it before the next comparable choice.
If retaliation appears, stop the experiment and seek a safer way to hear people. Preserve dissent and the right to leave. A team learning together does not need everyone to tell the same story.
Read the result without flattering yourself.
More defect reports may mean better visibility, not worse quality. Silence does not prove safety. One better interaction is a useful signal, not proof that the whole culture changed.
The practice we propose is to make useful small moves, surface mistakes early, keep enough evidence to learn and correct course. Documentation alone is not proof that we live it. We have no recorded outcome from this proposed practice to offer here.
Edgar Schein's 1983 paper, The Role of the Founder in the Creation of Organizational Culture, distinguishes underlying assumptions from stated values and visible behaviour. Its conceptual account and cases help frame the distinction; they do not prove this practice works in every team. The consequence-change practice here is our application, not a result from that paper.
What would happen in your team if someone acted on the value you say matters most?