How do you shape a change process that works in everyday practice?

Change management supports the implementation of a change among the people who will work with it. This includes direction, preparation, support and a review of whether the new practice holds up. Project management, alongside this, organises dates, deliverables and budget, for example. The two functions need to coordinate; a completed system does not yet answer whether a handover works reliably with it.

As a working distinction: a change initiative has an identifiable subject. A transformation connects several changes into a more extensive restructuring. Companies use these terms differently. What matters is therefore clarifying the actual scope instead of spending energy on the correct label.

Culture may also be affected. If a team is expected to make its own decisions in future but existing approval rules remain unchanged, a process description is not enough. A separate article on culture change in everyday work addresses lasting shared expectations and behavioural patterns. Here, the focus is on implementing a specific initiative.

Start with an observable difficulty. “We need to become more agile” offers little help with the next work decision. “Customer enquiries are left pending because responsibility between sales and service is unclear” identifies a starting point. Add what should work differently in future and how you can recognise it.

In a fictional company, the goal is: an incoming complaint has a responsible department and a clear handover route. The team needs to know which information is required, which cases it can handle itself and when escalation makes sense. The company also checks its existing process data to see whether handling time decreases.

Also record what remains unchanged. If responsibility changes but the right to make subject-matter decisions does not, that needs to be clear. Otherwise, expectations arise that the new process cannot fulfil. A brief goal statement with a clear boundary is often more useful for a trial than an extensive presentation without a decision.

Name a person who can make decisions about the initiative and someone who coordinates practical implementation. You also need the perspective of the affected work steps. Someone receiving a handover spots different gaps from the person preparing it. Both belong in the preparation.

Do not only ask for agreement. Ask to see a current case: where is information missing? Which follow-up question arises? Which exception does not fit the proposed rule? This reveals which parts of your draft already work and which need correction. An objection can thereby become a specific design task.

Participation needs an honest framework. Say what has been decided, what can be tried and who decides in a conflict. A survey does not replace participation required by law; the guidance on employee co-determination helps with preparation. Operational collaboration with the team is an additional task.

Choose a manageable use case. Describe the trigger, the next work step, the responsible role and how to handle an exception. You can then check the new process using actual cases. A launch date alone, without these rules, shifts the design work into already demanding day-to-day operations.

For a complaint handover, a shared intake point, one fixed mandatory field and a named contact for questions might be enough. The team tries this rule using suitable cases. If particularly complex complaints need another route, define it explicitly. This means nobody has to choose between an unsuitable rule and covertly bypassing it.

Agree on which support will be available during the trial. Who answers questions? Where is a rule updated? Who can decide on an exception? Document the answers in one reliable place. Otherwise, several versions quickly emerge while everyone involved believes they are working with the latest one.

Ask about the experience of the specific work step. “I know whom to pass an incomplete complaint to” is more helpful than “I like the change”. A low value may indicate a lack of direction. Clarify exactly which information is missing using a case or an appropriate discussion.

Keep feedback and judgement separate. Someone reporting difficulties should not automatically be considered unwilling. Also ask which parts work and should be retained. For confidential feedback, it must be clear beforehand who sees the results and which inferences remain possible despite the absence of names. The confidentiality page explains the limits.

The feedback needs a recipient with scope to act. A topic nobody is allowed to decide on remains unresolved even with a good questionnaire. Therefore, communicate the next step: clarified responsibility, a decision still open or a reasoned decision not to make the proposed change, for example.

Set a decision date before the trial. Then review whether the agreed process could be applied, which obstacles remain and which business consequences are becoming visible. These questions belong together. More favourable feedback is welcome, but does not by itself prove shorter handling times.

Decide as concretely as possible: retain the rule, add support, limit the scope or reverse part of it. Record the reason. If you change everything at once, it becomes difficult to understand which adjustment helped. The article on measuring change management covers the detailed selection of metrics and repeated questions.

After a useful trial, the work of establishing the process begins. Update the relevant documentation, remove conflicting old rules and clarify who will decide on later changes. New employees must also be able to find the process. In practical terms, an initiative is only handed over once support no longer depends on individual members of the project team.

Kotter’s approach includes a shared direction, removing obstacles and embedding new ways of working. This is a useful perspective for reviewing your draft; it does not replace a decision about the specific situation. You can find the original presentation at Kotter: The 8 Steps for Leading Change.

You do not need to recreate an entire large model for a single handover. Use a framework to find gaps: is the goal clear? Is it clear who is allowed to decide on it? Can the new way of working be carried out? Is what results from it reviewed? These questions also make the process manageable in small companies.

For communication, a distribution plan alone is not enough. What matters is whether the people affected know their next step. The article on change communication shows how to check this and adapt a message to specific work situations.

EngageBeat Fokus complements implementation with brief weekly surveys. Choose prepared questions about changes or ask custom questions to understand where direction or support is missing. The questions rotate: a selected question therefore does not automatically appear the following week.

The page on supporting change management with EngageBeat shows how it is used. The software replaces neither project management nor responsible decisions about actions.