How can culture change work in everyday practice?

A new organisational chart, different software or a shared workshop can mark the completion of a project. Whether people work together differently afterwards is another question. Culture change concerns the repeated practice that develops or remains after a formal introduction.

A fictional company introduces cross-departmental project teams, for example. If decisions continue to be made exclusively along old hierarchies, the structure has changed, but an important behavioural pattern has not. The next step would then be to clarify decision rights and escalation routes.

Not every change therefore needs a large culture programme. Sometimes improving a specific process is enough. Talking about culture change is helpful when several connected habits and expectations are affected. The article on company culture explains the underlying concept.

A useful starting point is an observed tension between working practices and requirements. Perhaps teams are growing while decisions still converge on a single person. Perhaps greater personal responsibility is the goal, but mistakes are publicly penalised. Or departments are expected to work more closely together even though their goals work against one another.

First describe the problem and its business consequence. “We need to become more modern” leaves room for many interpretations. “Customer projects repeatedly wait for unclear approvals”, by contrast, describes a situation you can work on. Established habits also belong in this assessment: what should explicitly be retained?

Check the scale in your own organisation. Where does rework, delay or avoidable coordination arise? What evidence do you have? A culture initiative does not become financially worthwhile by assigning large blanket savings to it. A small, concrete change can be easier to review than an extensive programme.

Translate abstract values into behaviour and conditions. “More trust” might mean, for example, that a team makes decisions independently within an agreed budget. This requires clear boundaries, accessible information and a manager who actually respects that scope.

On small screens, you can swipe the table sideways if needed to see all columns.

The table contains our own working examples, not guarantees of success. For each initiative, define who is affected, who can make a decision and when you will review it together. A goal does not have to cover every aspect of culture to be useful.

A well-known guide is Kotter’s steps for change. Among other things, it connects a shared direction, removing obstacles and embedding new habits. A model structures the work; it does not replace examining your specific situation.

For a manageable start, we recommend clarifying the reason, describing the desired behaviour, choosing a suitable area of work and changing a relevant process there. Gather experience before rolling out the same solution everywhere. A local success will not necessarily work in the same way under different conditions.

Plan the review from the outset. If you only set an introduction date, you may discover late that the new working practice is not being used. Brief regular feedback can make implementation problems visible. Supplement it with observation of the process and a named person who can address obstacles.

A communication action mainly helps when information is missing or understood differently. Training can make sense when people are not yet confident in performing a task. An exchange format can make knowledge available. None of these actions automatically resolves unclear authority or a lasting lack of time.

Before each action, therefore ask: what is currently preventing the desired behaviour? If everyone knows the handover rule but cannot apply it under deadline pressure, you may need different planning. Another presentation on collaboration would then do little to address the obstacle.

Record the action and its assumed mechanism separately. For example: “We are introducing shared prioritisation so that conflicting assignments are clarified earlier.” You can then check whether prioritisation takes place and whether it provides direction. This turns an action into an assumption you can review, rather than just another programme item.

Do not immediately label every critical comment as resistance. Objections can point to real conflicts between goals, poor timing or experiences with previous initiatives. First clarify exactly what is being rejected: the goal, the approach, the additional work or an unclear personal consequence.

A fictional team criticises new coordination meetings. A lack of understanding could be the cause. But there may already be too many meetings. Instead of calling for more openness, you could review existing appointments and replace a new round with a shorter format.

Not every conflict can be resolved. In that case, state openly which decision is fixed and where there is room to shape it. Participation without real scope disappoints expectations. Also give people a way to raise a concern outside the group. Criticism must not become an individual assessment or disadvantage the person.

Distinguish three questions: was the action implemented? Is the changed way of working experienced in everyday practice? Has the relevant business problem improved? A well-attended workshop only answers a small part of the first question.

Define suitable observations and your own questions before starting. If the aim is to clarify decision-making scope, a statement might be: “I know which decisions I can make independently in my role.” Use the same wording again so that a trend remains interpretable. A changed question starts a new comparison.

A better rating after an action is an indication, not proof of causation on its own. Other changes, new team members or different participation can also play a role. Document these events and consider several observations. Measuring company culture explains the detailed approach.

Senior management or the responsible department head owns the goals, resources and decisions about obstacles. HR and organisational development can structure the process and bring perspectives together. Managers translate it into everyday work; employees contribute experience and specific ideas for improvement.

With several teams, you need a shared framework, but not necessarily the same action everywhere. One interface may work well while another needs support. An overall score must not hide these differences. Nor should feedback become a ranking that pressures teams to produce the best possible numbers.

Agree on a brief management review with clear questions: what has been implemented, what is unclear and which decision is pending? Discuss only data intended and accessible for this purpose. A management role alone does not automatically justify access to all feedback. The page for senior management describes how to get started across several teams.

There is no reliable blanket timeframe for this. A specific handover rule can be observed sooner than a changed approach to mistakes. What matters is whether enough relevant everyday situations have occurred to assess an experience.

Adjust if the action is not implemented, the assumed obstacle remains or new problems arise. This does not have to mean failure. Perhaps the explanation of the problem was too broad or a prerequisite was missing. Record what you change so that later feedback can be put in context.

If an approach helps, translate it into normal processes: responsibilities, onboarding, meetings or decision rules. Otherwise, it remains dependent on the commitment of individuals. A culture programme does not meaningfully end with a closing event, but with a way of working that is sustained afterwards.

EngageBeat Team makes mood and motivation visible regularly. EngageBeat Fokus adds custom questions about specific changes. This allows you to identify implementation problems earlier and check whether actions are experienced differently by the team. The actions themselves and their implementation in the business remain your responsibility.

The analysis provides recurring guidance, not a comprehensive culture index. In the demo, you can view a question trend with fictional data. How EngageBeat works explains the weekly process. If this fits your initiative, “Set up for free” takes you into the trial process.

The guide to the change process shows how to prepare an individual transition. Putting transformation into everyday practice addresses several connected initiatives.