One example of a common problem that arises when things are out of order is this:

We have completed the design phase and moved it onto to HTML/CSS coding phase. Maybe something new was thought of, a mistake was caught, or someone’s boss decided they wanted something different. To backtrack from that change once it is in the coding phase will take two to three times the amount of effort as it would have required had the change been defined during the design revision phase. That is why it is so important to get concrete approval before moving forward. It is like trying to add a key ingredient to a recipe once it’s in the oven.

This doesn’t mean that it is impossible to make changes later. However, requesting many or significant changes can really distract from the overall cohesion of a site. Not to mention, take the project way out of scope.

This is also why having a full and expert process for assessment and planning consultation at the beginning of the project is so important. It’s actually a money and time saver to properly plan. You can rely on our years of experience knowing what works in the end and what doesn’t.