What happens when a website project has no real brief

Spoiler: the site launches, everyone is tired, and six months later nobody remembers what it was supposed to achieve. A project without a brief is not doomed — it is just quietly expensive, and the bill arrives in a currency the project plan never had a line for: rework, drift, and decisions relitigated by whoever speaks loudest in the room that week.

Anatomy of the drift

It follows a pattern we have seen enough times to predict:

• Week 1–2 — agreement by ambiguity. Everyone nods at "modern, clean, professional". No page list, no audience, no number that defines success. Ambiguity feels like harmony; it is actually unallocated decision-making.
• Week 3–6 — the design reveals the arguments. The first homepage draft forces ten decisions nobody made (what is the primary action? who is this for? what do we de-emphasize?). The arguments happen anyway — now with pixels attached, so they cost more.
• Week 7–10 — scope accretes sideways. Each new request is reasonable in isolation; no one owns a list that says no. The build absorbs all of them, late, because saying yes is faster than explaining a change order nobody planned for.
• Launch — success with no definition. The site goes live. Nobody can point at what improved, because nothing was measured before, so nothing can be measured after either.

The hidden costs, named

Rework is the obvious one. The larger ones are subtler: decision fatigue tax (the same argument recurring with new props), stakeholder arbitrage (late-stage veto power because early authority was never assigned), and measurement blindness (no baseline = no proof of value = next project starts with zero credibility). Brief-less projects do not fail loudly; they fail as diminished returns.

The rescue brief

If you are mid-project without a brief, stop adding features for one week and write one page — the same seven facts from our discovery checklist: outcome, decision maker, audience per language, references, existing assets, budget band, deadline with a reason. One page, signed by the decision maker. In our experience this single page resets more projects than any redesign does, because it converts taste debates into criteria comparisons.

If you are starting fresh

Start with the brief, not the vendor. Thirty minutes of structured discovery (ours is public: bring the seven facts) yields a written, fixed quote in about two working days — with a page list, exclusions and revision rounds that function as the project's immune system. A website without a brief is not a design problem. It is a decision problem wearing a design problem's clothes, and decisions are cheaper before the pixels.