Every experienced digital leader has one: the website project that was approved with confidence, started with energy, and is now eighteen months old, half-built and quietly avoided in meetings. Stalled enterprise website projects are common enough that they deserve a diagnosis rather than a shrug — because the causes are consistent, and so is the way out.
The idea
Projects rarely stall because of design or code. They stall in the gaps between decisions that were never made.
No agreed objective. Marketing wanted leads, IT wanted a platform, the board wanted “modern”. Each team optimized for its own version, and the project became a negotiation instead of a build.
Content arrived last. The design was approved with placeholder text. Real content — products, markets, legal, investor — turned out to be larger, messier and more political than anyone budgeted for. The site was ready; the organization was not.
Too many hands. A strategy consultancy, a design agency, a development vendor and an internal IT team, each responsible for a slice, none responsible for the whole. Every hand-off lost information and added weeks.
Scope without architecture. Features were listed; the content model, integrations and multilingual structure were not designed. Each new requirement became an exception, and exceptions compound.
The wrong platform for the team. A CMS chosen from a comparison table rather than from how the organization publishes and maintains. Every change needed the vendor; the vendor was busy.
Why it matters
A stalled project is expensive in ways that do not appear in its budget. The current website keeps aging, and with it the organization’s credibility with customers, investors and candidates. Internal appetite for digital work drains away — the next proposal is met with “remember last time”. And the eventual restart usually throws away good work because nobody trusts what exists.
The organizations that recover fastest are the ones that treat the stall as information. Something in the original plan was untrue; find it, correct it, and keep what was sound.
In practice
A manufacturing group arrived with a project two years in: a signed-off design, a half-configured CMS, three vendors and no launch date. The instinct was to start again. We began instead with an audit — of the design, the content, the platform configuration and the decisions that had never been made.
The design was good and was kept. The content model did not exist; it was designed in three weeks and it explained most of the stalling. The platform was appropriate but configured for a different site than the one being designed; it was rebuilt to the new model. One senior team took responsibility for strategy, design and engineering together, with the client’s own people embedded in it. The site launched four months later, in five languages, and the group’s editorial team has run it since.
What to do
If your project has stalled, resist the two reflexes: pushing harder, and starting over. Instead, ask five questions and write down the answers. What is the website for, in one sentence everyone accepts? Does the content exist, and who owns it? Who is responsible for the whole, not a slice? Is there a content model and an integration design, or a feature list? Can our team run this platform without the vendor? The unanswered questions are the diagnosis. Then keep everything that survives the answers, and re-plan the rest with one accountable team.
This is the work our Website Redesign and Website Audit services exist for. A way forward after a stalled project is usually shorter than the project has already been.
FAQ
Should we keep the original agency?
Keep whoever can take responsibility for the whole. The most common structural fix is reducing the number of parties, not changing them all. If the current partner can hold strategy, design and engineering together, keep them; if the stall is caused by hand-offs between partners, consolidate.
Can the completed design be reused?
Often, yes. Good visual design is rarely the reason a project stalled. It may need adjusting to a proper content model and design system, but throwing it away is usually a loss of value rather than a clean slate.
How long does a restart take?
Typically three to six months, depending on how much of the content and platform work survives the audit. The audit itself takes two to four weeks and gives you a real plan and a real date.
A project that has lost its way? Tell us where it stands — we will tell you what we would keep.