Web Design Proposal - Managing Scope Creep

In making a web design proposal, there are bound to be things that will be (but not deliberately) overlooked. When these things eventually surface and cause minor to major changes in the development of the design that were not agreed upon directly in the web design proposal, then these are collectively called scope creep.

Scope creep technically refers to the additional requirements outside of the accepted proposal that come up after web development has started. They are potentially dangerous because they usually have significant negative effects on the process due to the following results:

1. Extension of the project duration

2. Missed deadlines

3. Additional costs

4. Possible collapse of client–developer relationship

5. Customer dissatisfaction

6. Loss of developer credibility due to late delivery


Scope creep can be avoided and dealt with using the following methods:

Start with a design that is well researched.

This gives the developer a lot of insight on the possible angles where additional requirements might spring from. If the developer has a lot of experience and research on the agreed template or design, then there is little chance for things to be overlooked. Even if the client forgets or is not able to foresee certain changes, the developer would be able to plan things ahead or at least communicate to the client what possible considerations to make for future changes.

Set milestones

It is important to set measurable milestones. This sets out your timetable and stresses to the client how important time constraint is to each of the steps in the development. This not only keeps the client updated with the progress of the design but also prevents him/her from messing with the time table by suggesting additional features which were not included in the web design proposal.

Clarify all the expectations of all parties involved

Before starting on the development, make sure that everyone involved in the project – the client, the developer and the CEO, understands what each and every party expects to be done. It is vital that everyone has the same understanding in order for the development to proceed without surprises.

Refuse last-minute features or changes

No matter how simple the requests are, they entail the risk of affecting the whole process. Even if these additional features seemingly cause little changes, they might compromise the integrity of the whole design in the end. By the time the developer goes back them, they would have had caused significant delay in the process already. This is not usually the primary cause of scope creep but it does promote delays.

Make a prototype product for early feedback

This allows you to test certain features before investing time in incorporating them in the design. If the end-customer does not like these features, then you don’t have to invest time to developing them.

Recommend changes for future development

If changes and additional features do come up, it would be better to put them in a recommendation to prevent scope creep. Forcing to incorporate them will only jeopardize the integrity of the design as well as the deadlines agreed upon in the web design proposal, not to mention the costs involved. Put the features and functionality into future releases. It is inevitable that better ideas would come up after you have already started development.

Kelly Wilson
Web Design Proposal
Website Proposal Template
Web Design Contract