Running a digital transformation

The problem it solves

The decision to transform is almost always announced in a management meeting and almost never turned into an assignment of authority. An intention is approved, a technical lead is named, and everyone assumes the leadership team will keep running the company while somebody else, in parallel and with the same people, changes it.

The symptoms show up early and they all look alike. Initiatives move forward until they reach a decision the technical area has no standing to make: who approves this now, what stops being done, which exception disappears, which department gives up a task it considers its own. There they stop and wait. The people assigned to the change are the people holding up daily operations, and when operations press, the change gives way. Nothing is formally cancelled. It is simply postponed until it stops coming up in meetings.

What remains is a company with many initiatives open and none closed, a budget spent on half-finished work, and a team that has drawn a reasonable conclusion about how these announcements end. The next time leadership proposes a change, the organisation will listen calmly and wait to see whether this one is different.

What it covers

The programme treats transformation as the work of directing a company, not as a systems project. It runs across successive sessions with the team that actually decides, and it opens with an uncomfortable inventory: every initiative currently open, what it has already consumed, what it still needs, and the name of the person answerable for it. With that list on the table, the group separates what carries the direction of the business from what merely occupies capacity.

The second part works on absorption capacity, the limit almost no plan acknowledges. Through scenario analysis, participants estimate how many operating people each possible sequence would tie up at once, what would go unattended while that happens, and which part of the year is a bad time to touch anything. Out of that comes a defensible order, with dependencies made explicit: what has to exist before the next initiative can begin at all.

The third part installs the decision structure. The group works through who approves a change of scope, who settles a disagreement between two departments, what an initiative owner may decide alone and what must come back up. A management simulation puts participants in front of the ordinary conflicts of a transformation year: two departments claiming the same person, an initiative slipping with no visible culprit, and an internal cost nobody budgeted. The group decides in the room, then examines which rule it had been applying without ever writing it down.

The closing session takes up what is almost never agreed until it is needed: the rule for stopping. Participants draft the criterion that allows an initiative to be closed, redirected or paused, along with the signals that trigger it and the person who applies it, and they test it against their own live initiatives in an action-planning exercise. They leave with an ordered portfolio, a one-page decision structure and a review calendar with its own agenda.

What participants learn

• Evaluate the initiatives currently open and determine which ones carry the direction of the business and which only occupy capacity.
• Prioritise initiatives against the operation's capacity to absorb change rather than against the enthusiasm with which they were presented.
• Design the decision structure for the transformation: who approves, who executes, who settles a disagreement and within what time.
• Develop the written rule that allows an initiative to be stopped, redirected or closed without it reading as a personal failure.
• Apply a review rhythm with fixed dates and an agenda that forces decisions instead of reports.

Agenda

1. 01What separates a transformation from a large project
2. 02The portfolio: what enters, what leaves and what does not start yet
3. 03Absorption capacity: how much change the operation can carry at once
4. 04Authority and decision structure while the change is running
5. 05Internal cost: the operating hours that never reach the budget
6. 06Review rhythm: what gets looked at, who attends and what gets decided
7. 07Stopping, redirecting or closing an initiative without penalty
8. 08What the organisation is told, and when

What the organisation leaves with

• A written transformation portfolio with an owner, a sequence and a next review date for each initiative.
• A one-page decision structure stating who approves what and who settles disagreements.
• A written criterion for stopping, redirecting or closing an initiative, agreed before it is needed.
• A portfolio review calendar with the agenda each session will follow.