All articles

Digital transformation

Leading a transformation without breaking your teams

Agile UP, 1 min read

Transformation projects rarely fail on the technology. They fail when teams drop off along the way. Here’s what keeps them on board.

Agile UP, 2 min read

Change fatigue

A new tool, a new organisation, new indicators, sometimes all at once. Teams absorb it, then grow tired. You hear less from them in meetings, old habits creep back in, and the project moves forward on paper while it slips back on the ground.

Say why before saying what

A team accepts a lot of effort when it understands what we’re trying to solve and what it will change for them. Explaining the problem before the solution takes time at the start. That time is more than recovered later.

Involve the people who do the work

The people who handle the files every day know where the blockages are. Involving them from the assessment gives the project its best source of information, and the best chance that the solution holds once the consultants have left.

Move in small waves

Three successful changes, one after the other, are worth more than a full switchover that exhausts everyone. Each wave brings visible proof that the effort was worth it, and that proof feeds the next one.

Protect the day-to-day

During a transformation, the business carries on. Clients are waiting, invoices have to go out. A good project plans what teams can let go of while they learn something else. Otherwise you’re asking them to do two jobs at once, and that’s where you break them.

What we take from it

Moving faster without breaking your teams is our promise, and it comes down to a few things: explain, involve, move step by step, protect the day-to-day. Nothing spectacular. Yet it’s what separates a project that lands from one that runs out of steam.

Next article The hidden cost of the spreadsheets that run the business