< Show all Articles

How Limiting Revisions Keeps a Project on Track

Revisions are a part of every project. Designers and developers do their best to bring the client’s vision to life, but sometimes, additional updates are needed to ensure the client’s vision becomes a reality.

Here at (spark), our process for handing off work allows for clients to have an input at multiple stages of work, prior to completion. This is to ensure the end result is on target with the client’s expectations. We would never want to deliver work that doesn’t exceed what the client had in mind.

For instance, during a website redesign project, the client would receive wireframes to review first. Then, the client would be able to provide feedback, which would be implemented by the designer. 

The next step is the comp phase where we mock up exactly what the website would look like. We present these designs to the client and allow for feedback and revisions here as well. Those changes get implemented and we move on to development.

Revisions and any feedback during the development phase do not occur until the end of the project. We first complete alpha testing, which is where (spark) internally tests and provides revisions to the developer before we pass the website off to the client for review.

Beta testing is the next phase. This is where we have evaluated the project to be completed. We then turn the website over to the client to review and provide any final revisions before we deploy the website.

Here’s the catcher: though our process allows for the client to always provide feedback, we do limit the amount of revisions we permit.

Providing limitations on the rounds of revisions keeps both the internal team and the client on the same page. It also helps move the project along, instead of keeping up with new ideas.

We encourage clients to dedicate time to reviewing and providing consolidated feedback to us. This provides designers or developers comprehensive notes and actionable direction in order to update the work.

We believe in limiting revisions because it makes it necessary for the client to fully develop their thoughts and feedback, rather than being able to come back with multiple changes that may take the project off course.

This also helps when working with a group of decision-makers on the client side. It encourages the key stakeholders to form one vision for the project, instead of everyone come to the table with different objectives.

(spark) dedicates ourselves to making all of our client’s visions become reality, whether that be in the initial design of a project or when we step back to implement revisions.