This is the twelfth article in a series about the Design Process.
This is the twelfth article in a series about the Design Process.
Many times, the design of the site needs to be altered once you get the final content or others have a chance to test the prototypes.
Nobody is perfect, an no amount of preparation can prepare you for the business stakeholders changing their minds.
One of the most important things you should do is to communicate to both the person requesting the change and the leadership of the project what has occurred and what the implication is. Sometimes, this affects your deadlines and can put your project in jeopardy.
Sometimes, it’s merely adjusting the height of width of something to accommodate a sentence or word, or lack of content that you’d planned on having, but you never get for whatever reason.
This should be viewed as your final touches as a designer, for the web or for print projects. This is the final step before you send it to the development team or the printer.
In many cases it is not, and that is where the project gets much more expensive (in both wasting of time, money and other resources).
Potential Pitfalls
This step in particular is opposite of the rest of them. You can NOT constantly change the look and feel of the project. Typically, aesthetic things can be changed before development starts, depending on what it is, but it must be limited and planned for. If you don’t have a planned interval to review the design, then it’s natural for people to feel that they can make changes whenever they want to.
This is step 12 of 17 from the Design Process Playbook
Next: No More Features! How Late Scope Changes Waste Time and Money
Comments ()