The redesign was supposed to take eight weeks. It took five months.
The budget was $35,000. The final invoice was closer to $60,000. Nobody was happy with the result, even though the site technically worked and looked better than the old one.
This story is not unusual. It happens to businesses of every size, with agencies of every quality level. The pattern is the same almost every time.
The project did not fail because the developers were slow. It did not fail because the client kept changing their mind. It failed because nobody wrote down what "done" meant before the first wireframe was drawn.
The Problem With "You Will Know It When You See It"
Most redesign projects start with a conversation. The client describes what they want. A new look. Better mobile experience. Faster load times. Something that feels more modern.
These are fine goals. They are also meaningless as project requirements.
"Modern" means something different to every person in the room. The CEO pictures clean whitespace and bold typography. The marketing director wants interactive animations and video backgrounds. The sales team just wants the contact form above the fold.
Without a written definition of done, every stakeholder fills in the blanks with their own version. Nobody realizes the versions conflict until the first round of design reviews, when the CEO says "this is too busy" and the marketing director says "this is too plain" about the same mockup.
The agency is stuck. They are being asked to build something that satisfies conflicting definitions that were never written down and never reconciled.
What a Definition of Done Actually Looks Like
A useful definition of done is a list of specific, verifiable outcomes. Not feelings. Not adjectives. Measurable things.
Here is an example for a service business redesign:
Homepage: Loads in under 2.5 seconds on mobile. Displays the company name, a one-sentence value proposition, and a contact CTA above the fold on a standard phone screen. Navigation includes links to Services, About, Portfolio, and Contact.
Services page: Lists all six service offerings with a 2-3 sentence description each. Each service links to a dedicated landing page. Each landing page includes at least one client testimonial.
Contact page: Form includes name, email, phone, and a message field. Form submissions send an email notification to three addresses and create a record in the CRM. A confirmation message appears after submission.
Performance: All pages score 80+ on Google PageSpeed Insights for mobile. No mixed content warnings. SSL configured.
Launch criteria: Client signs off on all pages. Analytics tracking confirmed working. Old URL redirects mapped and tested. DNS cutover scheduled with 24-hour notice.
This is not exciting to write. It is the most important document in the project.
Why Teams Skip This Step
Writing a definition of done requires making decisions before the fun part starts. It means the CEO and marketing director have to sit in a room and agree on what "modern" means before any designer opens Figma.
That conversation is uncomfortable. People avoid it. They assume alignment where none exists. They say things like "we trust you" and "just make it look good" because those phrases feel collaborative and positive.
But those phrases are actually a transfer of decision-making authority from the client to the agency. The agency now has to guess. And when they guess wrong, the revision cycle begins.
Every revision that could have been prevented by a clear definition of done costs money. Not just the agency's time to redo the work. The client's time to review, give feedback, schedule another meeting, review again. The project manager's time to mediate between conflicting opinions.
A $2,000 definition-of-done document at the start of a project routinely saves $15,000 or more in revision costs.
The Scope Creep Connection
Scope creep gets blamed for most redesign failures. But scope creep is a symptom. The underlying cause is an incomplete or missing definition of done.
When "done" is clearly defined, scope creep becomes easy to identify and manage. A client says "can we also add a blog?" You check the definition of done. Blog is not listed. That is a scope change. You quote the addition separately.
When "done" is vague, that same request feels like a clarification rather than an addition. The client thinks the blog was always implied. The agency is not sure. Neither party has a document to reference.
The project absorbs the blog. Then it absorbs a newsletter signup. Then an FAQ section. Then a team page with bios that nobody has written yet. Each addition feels small. Together, they are the reason the project is 60% over budget.
How to Fix This for Your Next Project
Whether you are hiring an agency or running one, the fix is the same.
Before design starts, write a document that lists every page, every feature, every integration, and every performance target. Include what is explicitly not included. "Phase 1 does not include a blog, e-commerce functionality, or multilingual support."
Get every stakeholder to sign it. Not metaphorically. Actually sign it or reply to an email confirming agreement.
When someone asks for something that is not in the document, you have a simple, non-confrontational response: "That was not in the agreed scope. We can add it to Phase 2 or re-scope Phase 1 with updated timeline and budget."
This is not rigid or adversarial. It is clear. Clarity is the thing that redesign projects lack most. Not talent. Not budget. Not technology. Clarity about what done means.
The Real Cost of Skipping It
The $35,000 redesign that became $60,000 is a real project. The extra $25,000 did not buy $25,000 worth of additional value. Most of it went to revisions that addressed conflicting expectations that existed from day one.
Five months instead of eight weeks means five months of the old site running. Five months of mobile visitors bouncing. Five months of missed SEO improvements. Five months of the team talking about the redesign instead of doing other work.
The definition of done takes a day to write. The cost of not writing it is measured in months and tens of thousands of dollars.
Start there. Everything else in the project gets easier once "done" has a definition everyone agreed to.