Testing, Revisions, and Acceptance

“Quality is not an act, it is a habit.” — Aristotle

Internal Review

With every project we take on, we follow established processes for reviewing our work before it is sent for external review. Our goal is to deliver work that we are proud of and to help our clients get the best results possible. Review processes take different forms for different types of projects:

  • Strategic recommendations are presented internally to leadership for feedback and revisions

  • Design projects receive feedback and internal revisions from other designers to audit creative integrity and account strategists to ensure that the clients goals are met

  • Development projects are tested on all modern browsers and responsive screen sizes

Revision Cycles

When our team prepares a project timeline, we are intentional to include revision time to allow our clients to review internally and deliver feedback and for our team to revise our work. This process typically takes a few days on the client end and an additional couple of days for our production teams to update assets. While there are large portions of our projects timelines where there is minimal client involvement, revision dates require significant attention from project stakeholders. You'll want to ensure that all appropriate stakeholders are available to review during the review period. Revision cycles are one of the greatest threats to project timelines, because they require the most coordination between project stakeholders.

Feedback Collection

Capturing and organizing client feedback and revisions is made simple with a few tools we use:

  • Content: For content collection and iteration, we typically use ContentSnare. ContentSnare gives us the ability to define content needs and requirements that can be assigned to our clients for their team to write.

  • Design: For design projects, we typically provide designs through InVision. InVision allows us to comment on specific areas and collaborate with each other through the design process.

  • Development: For development projects, we typically use BugHerd. BugHerd allows anyone who is logged in to leave feedback on a website with their intuitive reporting tools.

Revisions vs. Change Requests

Typically revisions are handled within the scope of a project and do not require additional charges. At the start of a project, we determine how many days will be included for revisions and those days are included in our initial bid. At a high level, there are typically three ways that a project may incur additional charges:

  1. At some point in the project, additional needs are discovered either by us or by the client that were not included in the scope of the project.

  2. Revision cycles require additional time beyond the allocated revision days in the original timeline.

  3. Revisions are requested to a project phase that has already been accepted. For example, we are developing a website and re-designs are requested, requiring additional design time for multiple production team members.

Acceptance

After every major phase of a project, clients are given the opportunity to review and provide feedback before we conclude the phase. After revisions are serviced, we provide a finalized asset for that phase and request acceptance to move on to the next phase of the project. We don't proceed to the next phase of a project until the previous phase has been accepted, and any additional changes to the previous phase may incur additional charges.