A project rarely fails on the technology
When a transformation project goes off track, the tool or the supplier is readily blamed. In practice, projects are almost always lost in the same three places: scoping, decisions and adoption.
Driss Lebrun · October 2026 · 5 min read
First place: scoping that everyone reads their own way
A poorly scoped project does not have a vague objective: it has several, which everyone believes are shared. Leadership wants to cut costs, the business wants to save time, IT wants to replace an ageing system. All three are legitimate, but they do not lead to the same choices.
Good scoping fits on a few pages: why it is being done, what is in and what is out, what it costs, who decides, and how success will be recognised. It is signed. What is not in it is not in the project, and that protects everyone.
Second place: decisions that wait
A project produces decisions every week. When they have nowhere to be taken, they escalate, wait for one committee, then another. The schedule does not collapse all at once: it slips, silently, one week after another.
Governance is not bureaucracy. It is the answer to a simple question: who decides what, at what pace, on the basis of what information. A steering committee that genuinely arbitrates, a project committee that tracks risks, a short team check-in. Each decision has its forum; the rest is dealt with outside meetings.
Third place: the day after
A delivered system is not an adopted system. If the teams were not involved, they keep their habits, rebuild their spreadsheets and work around the new tool. The project is finished on paper, and nothing has changed in the work.
Adoption is prepared from the start: key users in the project team, tests run by those who will use the tool, training at the right moment, and relays in each team. It is also measured, with the same rigour as the budget.
Technology matters, but it follows
Technical difficulties exist: data migration, interfaces, performance. They are real, but they are visible and can be dealt with. What makes a project fail is what does not show up in a schedule: an objective that is poorly shared, a decision that nobody takes, a team that was not brought along.