In this article
Organizational culture is visible in the rules people learn through experience: what attracts attention, how decisions really happen, which concerns can be raised, and what behavior receives recognition. Those rules may differ from the values in a handbook.
A company can announce collaboration while rewarding only individual results. A manager can invite questions while signaling impatience whenever a difficult one appears. Employees then have to decide which message to trust.
The following five “unwritten rules” are a practical way to examine those signals. They are not universal laws or a validated diagnostic scale. Use them to investigate actual experience and identify a change the organization can follow through on.
1. Attention signals what matters
Look at what leaders discuss, measure, fund, and recognize. Attention does not automatically cause improvement, but it tells people what is likely to count when priorities compete.
If every meeting focuses on urgent problems and nobody asks why the same problems recur, prevention can become invisible work. If only new sales receive recognition, the people who make existing commitments reliable may feel that their contribution matters less.
Review two weeks of meetings and decisions. How much time went to immediate output, customer experience, employee development, quality, and improvement? Compare the pattern with the organization’s stated priorities.
Choose one adjustment. For example, include a short discussion of a prevented problem or a useful process improvement alongside the usual performance figures. Keep the discussion connected to evidence; replacing one selective success story with another does not create a fuller picture.
2. Leadership behavior sets an example
People notice whether leaders apply the standards they ask of others. A manager who calls for early risk reporting but reacts with blame may teach the team to delay bad news.
Examine a recent moment of pressure. How did you respond to an error, disagreement, or missed commitment? What might someone reasonably conclude about the consequences of speaking openly?
Choose a behavior to practice rather than promising a new personality. It could be acknowledging your own contribution to a problem, asking for a contrary view before deciding, or explaining why you changed your mind.
Invite specific feedback about the effect. Leadership is influential, but it is not the only source of culture: incentives, peer expectations, resources, and the wider organization can reinforce or contradict the example. Our guide to values-based leadership examines that connection.
3. Conversation determines what becomes discussable
Notice not only what is said, but who has room to say it. Who is interrupted? Which questions are deferred repeatedly? Do important concerns appear only after the meeting has ended?
A useful meeting practice is to invite risks and unanswered questions before closing a decision. Give people time to prepare and a written route for contributing where that helps. In distributed teams, do not make one live meeting the only opportunity to influence the outcome.
Listening requires a response, not automatic agreement. Clarify the point, explain what will happen to it, and return with a decision or update. Asking for candor without responding can be as discouraging as never asking.
Sensitive individual matters may need a separate confidential route. A public team discussion is not an appropriate answer to every concern. See employee feedback approaches for choosing a suitable setting and purpose.
4. Daily decisions reveal the real standard
Broad values need interpretation in recurring situations. What does customer focus mean when a request conflicts with an existing promise? What does respect mean when one team’s urgent work repeatedly disrupts another?
Select three common decisions and agree on a usable principle for each. For an illustrative service team, a principle might be: first establish what the customer needs and what can responsibly be delivered, then explain the available options. Investigating responsibility can still matter, but it should not prevent an immediate, appropriate response.
Make authority clear. A principle that tells employees to solve a problem while withholding permission to act creates frustration. Specify the decisions they can make and where an exception goes.
Review real cases together. If the principle produces unintended effects, revise it. Values should support judgment, not become a formula used to avoid difficult trade-offs.
5. Learning needs time to become part of work
Introducing ideas faster than people can test and integrate them can create a growing backlog of unfinished change. A new initiative may look active while earlier improvements quietly disappear.
Review the changes currently affecting a team. Which need learning time, which duplicate effort, and which should pause? After a pilot, allow time to understand what happened and update the relevant process before expanding it.
This is the practical value of the organic-growth perspective: attend to the conditions and capacity for development. It does not mean avoiding urgent decisions or assuming that every organization has a predetermined natural rhythm.
Use a short, recurring review to ask what should continue, what needs adjustment, and what should stop. The five-stage change management guide connects that learning with implementation and ongoing ownership.
Listen to the language people use
Phrases such as “don’t rock the boat,” “we’re always firefighting,” or “get it approved upstairs” can point to patterns worth exploring. They are clues, not proof of a single shared belief.
Ask what an expression means in practice and request a recent example. Different teams may use the same phrase differently. A newcomer can also notice assumptions that long-serving colleagues have stopped questioning.
Changing the vocabulary alone will not change the conditions. If people describe constant firefighting, investigate interruptions, capacity, dependencies, and how priorities are set. Do not simply ban the phrase and call the culture positive.
An illustrative pattern across all five rules
Imagine a manufacturer that wants more initiative. Meetings focus on errors, supervisors approve every routine decision, concerns stay in corridor conversations, and improvement work has no allocated time.
An innovation workshop might introduce useful ideas, but the existing signals still discourage their use. A more coherent response could combine limited delegated authority, a regular discussion of practical improvements, a clear route for concerns, and time to test one change.
The team would then review both the work and the experience of contributing. This example illustrates the relationship between conditions; it is not a documented claim of a particular client outcome.
Make unwritten rules visible without manipulation
Work with employees to identify which patterns help and which create difficulty. Ask what is genuinely rewarded, what people learn not to mention, and what a new colleague needs to know to get work done.
Choose one pattern, describe the desired behavior, and agree on a change in the supporting conditions. Name an owner and a review date. Incorporate what works into meetings, onboarding, decision routines, and leadership development.
Avoid treating culture as a way to quietly engineer compliance. The point is to make expectations discussable and improve the work, including room for disagreement and legitimate differences.
OQM can add a structured employee perspective through its eight organizational factors. It does not read hidden intentions or automatically explain every cultural pattern. Combine findings with observation and dialogue. Explore organizational development beyond the org chart or contact OQM to consider your starting point.