Skip to content

Projects

Five mistakes that sink a digital project.

Digital projects rarely fail on technology. They fail on scoping, on the order of decisions, and on the absence of measurement. Five mistakes we see everywhere — and how to avoid them.

26 May 2026 · 7 min read

After enough projects — our own, and the ones we take over from others — the same causes of failure come back with striking regularity. None of them is technical. All of them are decided before the first line of code.

1. Scoping as you go

“We'll figure it out along the way” is the most expensive sentence in digital. Un-arbitrated scope is paid for in weeks of rework, never in hours. Written scoping — what's in, what's out, what settles disagreements — isn't bureaucracy: it's what protects the budget and the schedule.

2. Designing for yourself, not the user

The board approves on a large screen, on fibre, with demo data. The real user is on a mid-range phone, on 3G, with real messy data. Designing for the second — screens, connections, edge cases — is what separates an adopted tool from an abandoned one.

3. Launching without measurement

Going live without tracking is flying without instruments: you'll know something is wrong, but never what. Measurement — conversion, sources, journeys — is installed before launch, not after the first doubt. What isn't measured can't be improved; what is measured improves almost by itself.

4. Confusing delivery with the end

A digital system is an organism, not a monument. Without maintenance, backups, updates and iteration, its value erodes within months — and the company is back where it started, having paid. The projects that keep producing are the ones that enter a cycle: measure, learn, improve, every month.

5. Stacking vendors with nobody accountable for the result

The website here, the ads there, the CRM with a third party. Everyone optimizes their piece; nobody answers for the final number. When the result doesn't come, everyone is right and the company has lost. There must be one owner of the complete chain — internal or external, but one.

A digital project almost never dies of a code problem. It dies of a decision that wasn't taken at the right time.

The good news: all five mistakes are avoidable, and all in the same place — before production. That is exactly what serious scoping is for: turning expensive surprises into cheap decisions.

Does this sound familiar?

Let's talk about your situation — thirty minutes, no commitment.

Start a conversation