When strict rules support or constrain a team

The same change, two different responses

A new employee changes the order of sections in a report so the most important risk appears first. In one department, she is thanked for taking initiative. In another, she is reminded that everyone has used the established template for years. The difference need not reflect the report's quality or personal dislike. It may reveal different expectations about how much freedom people have in relation to shared rules. While those expectations remain unspoken, each side can easily see the other as unreasonable. The concepts of tight and loose cultures concern the strength of norms and tolerance of deviation. They are not a simple division into good and bad, modern and outdated organisations. A strong norm may concern reporting errors, mutual respect or the order in which documents are approved. We must therefore ask separately both how strongly conformity is expected and what people are expected to conform to. Strict enforcement of a useful rule is not the same as defending an empty ritual. A norm need not be written to exert a strong influence. Employees may know that formally they may challenge decisions while observing a cold response to anyone who does. Elsewhere, regulations may look rigid but everyday practice allows many agreed exceptions. A description of culture should therefore consider both official rules and the actual consequences of deviation. Check whether a rule applies equally to everyone. If high-status people may freely bypass it, others learn a hierarchy of privilege rather than a common standard. This is distinct from the strength of norms itself and calls for a discussion of consistency and justification.

What research allows us to say

Gelfand and colleagues compared the strength of norms in 33 countries. Their study does not justify assigning traits to individual employees on the basis of nationality. Di Santo and colleagues focus instead on organizational units and links between their culture and workplace attitudes and behavior. This distinction between levels matters: the norms of a particular team may differ from an image of its country or company as a whole. Gelfand et al., 2011; Di Santo et al., 2021. For everyday cooperation, investigate local situations. What happens when someone questions a manager's idea? Does an unusual way of completing a task require permission? How does the team respond to a minor deviation that did not worsen the result? The answers show norms in action. “We value initiative” explains little if every independent decision brings a public reprimand. Likewise, a slogan about flexibility does not remove genuine safety requirements.

When predictability helps and when it begins to constrain

Consider a team responsible for a shift handover in a manufacturing plant. A common sequence for sharing information may prevent a hazard from being overlooked. Someone who simplifies the procedure unilaterally changes other people's working conditions. Here, the agreed standard has a concrete function that should be explained to newcomers instead of saying only, “That's how we do things.” Understanding a rule also makes it possible to notice when it no longer serves its purpose and needs improvement. Early-stage product ideation may require something different. If every sketch must immediately fit an existing template, the group narrows the scope for experimentation. Creative work does not require an absence of rules: ideas can remain open while budget, deadline and testing methods are clear. The practical goal is to match the strength of rules to the type of risk. Some rules should be fixed, while other areas should deliberately remain open to experimentation. Ask what exactly a rule protects. Does it prevent error, support coordination, meet an external requirement or merely repeat an old custom? The answer need not abolish the rule; it may reveal a less burdensome way to achieve the same purpose. Different areas of the same team's work can also differ. A team may need a strict standard for transferring responsibility and wide freedom when generating ideas. There is no need to choose one label for the entire organization. The practical conversation is about where deviation creates real risk, who may assess it and how others will be informed. Freedom then need not mean unpredictability, while consistency need not mean unquestioning obedience.

Friction does not always mean a lack of professionalism

Someone accustomed to strict rules may experience a looser team as unpredictable. Someone used to broad autonomy may experience ordinary oversight as mistrust. Before attributing these reactions to laziness or a desire to dominate, clarify expectations: “Which matters can I decide independently, and which should I consult?” The answer should include examples. A general assurance that employees are responsible leaves too much room for different interpretations. A leader can distinguish three situations: a rule that always applies, a rule with agreed exceptions, and an area of free choice. This is a way to structure the conversation, not the finding of a single experiment. Its purpose is to reduce guesswork. If deviations are allowed, people need to know who agrees them and how others are informed. If they are not, explain why. Exceptions available only to high-status people quickly undermine the credibility of a shared standard.

Examine the rule before trying to change people

In the report example, the manager can explain that the fixed layout allows results to be compared across departments. The employee can show that the risk disappears at the end of the document. A short summary added to the common template may solve both problems. The conversation need not decide whether the team is “too rigid” or the employee “too independent.” It can connect the rule's function with information about its cost, turning the deviation into an opportunity to agree the method consciously. Explain rule changes to those who previously bore the cost of compliance. If a format was enforced for years and bypassing it is suddenly rewarded, some employees may feel unfairly treated. State the reason for the change and recognize past contributions: the old standard served a function, but present conditions require something different. People attached to it need not be portrayed as enemies of progress. Likewise, when strengthening a rule, identify the specific risk rather than citing a general lack of trust. Change is easier to understand when people see the connection between the rule, the purpose of the work and their responsibility for the shared outcome.

The strength of norms shapes how a team receives initiative and responds to deviations. Good cooperation requires recognizing where predictability protects a shared outcome and where it restricts necessary freedom. The most useful rule is one whose purpose and boundaries are understood.

Using Empatyzer to agree on rules for collaboration

Empatyzer can help prepare a conversation about how much predictability and autonomy the people involved need. Organizational culture offers a starting point for examining available information about workplace preferences, but it is not an automatic measure of tightness or looseness as defined in research. In Talk to Em about your team, you can prepare an explanation of a specific rule, its purpose and permissible exceptions. You can also formulate questions that reveal the rule's cost for different people. Em adapts language using the available group profile, but it does not assess a procedure's compliance with technical or legal requirements; those issues must be checked separately. The tool can support a conversation without labelling people rigid or irresponsible. The final agreement should clearly state what applies, why it applies and how a need for change can be raised.