When the executive team is expected to run a change project “on the side” – An article by Patrick Brun, Partner at FS Partners
A change project has been approved, but nothing is taken off the day-to-day agenda to make room for it. Running it on the side works as long as the project fits within existing structures. Once it starts changing those structures or turns the executive team into a bottleneck, additional leadership capacity is needed.
When responsibility grows but time doesn’t
I’ve seen this scenario many times in recent years: a change project is approved, and the budget and target date are set. Operational management takes on responsibility for it, on top of day-to-day business.
It gets difficult when nothing is taken off their plate. Customers still need answers, and personnel decisions are pending within the team. At the same time, the new project constantly demands decisions on money, resources and priorities.
Clarify who does what before the start
Before the start, the executive team should clarify which tasks can be handed off, which deadlines are fixed and who makes which decisions in the project. Only then does it become clear whether the extra responsibility can be absorbed internally. If this is only checked once deadlines are already slipping, time has been lost.
When “on the side” works
Not every change requires an additional person. Many projects can be delivered with the existing organisation. This is more likely to succeed if the initiative is clearly scoped, the intensive phase lasts only a few weeks and a deputy in the business can actually make decisions. It also helps if the team has delivered something similar before. In concrete terms, the following points speak in favour:
- The initiative is clearly defined, such as new reporting or a tool for a single department.
- The peak workload lasts weeks, not months.
- There is a deputy who is genuinely authorised to make decisions in day-to-day business.
- The team has done something similar before.
If several of these conditions are missing, I would take a closer look at whether leading the project alongside day-to-day business is realistic.
When capacity runs short
As the project progresses, clear warning signs often emerge:
- Deadlines slip by two or three weeks at a time. Each delay seems harmless, but add them up and go-live is a quarter late.
- The steering committee postpones decisions because the groundwork hasn’t been done.
- Project work happens in the evenings and at weekends.
- The same three key people sit in every workshop.
- Things that used to be routine fall by the wayside: staff appraisals, customer visits, the month-end analysis.
If two or three of these apply, the executive team should reassess whether the workload is realistically distributed. This is rarely down to a lack of commitment from those involved. Usually, nobody clarified at the outset what would be dropped from day-to-day business to make room.
Three real-world situations
I come across the following constellations, in similar forms, again and again. They show that the right solution looks different each time.
- The CFO and the new ERP
A mid-sized industrial company is introducing a new ERP system. The CFO is leading the project, and go-live is scheduled for 1 January. Autumn, of all times, is when the budgeting process, bank meetings and preparations for the annual financial statements take place.
During this phase, key users from finance may be unavailable for testing. Decisions on data migration stall, and go-live may be pushed back.
An external project manager would not automatically solve this. It may be more helpful to cover day-to-day business temporarily, for example with an interim head of accounting. The CFO can then keep leading the project, where his internal knowledge matters most.
- Integration after an acquisition
A company acquires a competitor. The COO, who is also running the company’s own plant, is to be responsible for the integration. A lot comes up in the first few months: which systems stay, who looks after which customers, which key people does the company want to keep?
If these questions remain open for too long, the risk grows that employees leave or customers start looking for alternatives.
The integration needs enough time and someone who brings both sides on board. An external person can help, provided they have experience with integrations of this kind and work independently of both organisations.
- Restructuring your own division
The executive team decides to restructure a division, including job cuts. The head of the division is to implement this. She has known many of those affected for years and will continue working with the remaining team afterwards. Here, the issue is less about available time than about her role. She has to carry out the cuts and then keep leading the same team.
A temporary external executive could take over the implementation. The division head could then contribute to the division’s new direction and to rebuilding the team.
When external support makes sense
The question is rarely “external help: yes or no?” What matters is exactly where capacity is lacking. In practice, I see four options:
| Solution | Fits if … | Typical example |
|---|---|---|
| Prioritise internally | another initiative can wait without major harm | A second digital project is postponed by a quarter |
| Free up capacity internally | a manager can take on the project if someone covers part of their ongoing duties | A deputy takes over some leadership duties during the ERP implementation |
| External line cover | the knowledge to lead the project exists internally, but the line role must remain filled | An interim head of accounting temporarily takes over day-to-day business |
| External project lead | project experience, independence or rapid availability is needed | An external person leads the integration after an acquisition |
When it comes to interim management, many people first think of an external person taking over the project. Sometimes it’s more helpful to fill the line role temporarily. The internal manager can then keep leading the project, where their knowledge matters most.
My rule of thumb: if a project requires a lot of internal knowledge and ownership of the operation afterwards, project leadership should stay in-house wherever possible. If experience with a specific situation, independence or rapid availability is needed, an external person may be the better fit.
Clarify decisions and handover early
Internal or external: before the start, it should be clear who is authorised to make which decisions.
Additional support does little good if operational decisions still rest with an overloaded executive team. Whoever leads a project needs clear room to act, for example on budget questions or personnel decisions. When goals conflict, there needs to be an accessible point of contact who makes binding decisions.
With a fixed-term mandate, it should be clarified early on who will take over the role later and what needs to be working by then. One possible signal for the handover would be the month-end close being delivered on time twice in a row.
An external executive can free up time for the change. The executive team still has to decide what priority the initiative has and which tasks it will hand over.