The first three months of a change programme set its course. In that period people decide whether the change is serious, whether leaders mean what they say and whether it is worth their effort. Those early judgements are hard to reverse.
Ninety days is also long enough to waste. Many programmes spend the first quarter on planning documents, steering group meetings and communication material, while the people expected to change their daily work hear very little. A better use of the time is to build understanding, show early progress and set up the habits that will carry the work forward.
The outline below divides the period into three parts. The boundaries are approximate. What matters is the order.
Days 1 to 30: understand and agree
The first month is about making sure the change is understood in the same way by the people leading it and the people living with it.
- Write down the reason for the change in plain language. One short paragraph that a new employee could follow. If the leadership team cannot agree on that paragraph, the programme is not ready to start.
- Describe what will be different. Be specific about behaviour, processes and decisions. "Better collaboration" means little. "Sales and production will agree delivery dates together each Monday" can be observed.
- Talk to the people affected. Hold small conversations with the teams who will feel the change most. Ask what worries them, what they think will get in the way and what they would do first. Listen more than you explain.
- Clarify who decides what. Name the sponsor, the person running the work day to day and the people whose agreement is needed for key decisions. Unclear decision rights slow programmes down more reliably than almost anything else.
In Nordic organisations, people usually expect to be involved early on. People tend to support what they have helped to shape. Time spent here is rarely wasted, as long as it leads to decisions.
Days 31 to 60: start doing
The second month is where the change becomes visible.
Pick two or three early actions that are small enough to complete within a few weeks and meaningful enough that people notice. Good candidates remove an irritation that staff already complain about, or let a team try the new way of working on a limited scale.
Imagine a logistics company introducing a new planning process. In month two it might run the process with a single warehouse team, with the managers present at each weekly planning meeting. The team gives honest feedback, the process is adjusted, and the rest of the organisation hears from colleagues that it works.
During this period:
- Keep the early actions visible. Share what was tried, what happened and what was changed as a result.
- Make sure leaders model the change themselves. If the new process requires a weekly meeting, senior people attend it.
- Collect problems openly. A shared list of obstacles, reviewed every week, shows people that their input leads somewhere.
Days 61 to 90: build the rhythm
By the third month the programme should move from a set of activities to a routine.
- Establish a regular review. A short meeting every two weeks where the core group looks at progress, problems and next steps. Keep it brief and focused on decisions.
- Agree a few simple measures. Choose indicators that tell you whether behaviour is changing, alongside the results you ultimately want. Two or three are enough at this stage.
- Plan the next stage of rollout. Use what you learned from the early actions to decide where to go next and at what pace.
- Look after capacity. Change is extra work layered on top of normal work. Check whether key people are overloaded and adjust plans before they burn out or quietly disengage.
What to avoid
A few patterns show up again and again in programmes that lose momentum early.
- Announcing too much, too soon. A large launch event before anything has changed raises expectations that the programme cannot yet meet.
- Leaving middle managers out. Team leaders translate change into daily work. If they hear about it at the same time as everyone else, they cannot help their teams.
- Treating resistance as a problem to overcome. Objections often contain useful information about practical obstacles. Take them seriously and respond in substance.
- Measuring only activity. The number of workshops held says little about whether anything is different.
A sober pace
There is a temptation to fill the first 90 days with energy and visible activity. A steadier approach usually works better. Understand the situation properly, start small, learn quickly and build habits that will last beyond the initial attention. This reflects the Nordic idea of nøkternhet, which means sober, practical judgement about what is realistic and a preference for steady progress.
By day 90, a programme in good shape has a shared understanding of why it exists, a few real changes in place, a working rhythm and an honest view of what is hard. That is a solid base for the longer work ahead, and it is the kind of foundation Linje helps organisations put in place when they want support.