loader image

Feedback Workflow Best Practices

2 Minute read

There are two main ways to go about revisions inside of MarkUp:

  1. Agile Feedback Loops
  2. Structured Feedback Loops

Agile Feedback Loops

With Agile Feedback Loops, teams start with Version 1 of their site inside of MarkUp and can use the MarkUp Chrome Extension to consistently capture screenshots when placing comments. No matter how many changes are taking place by the designer/developer inside the CMS, these agile teams keep this same MarkUp project as a running log of all comments and changes over time until going live.

As things are changed on the CMS side, those changes are automatically pushed through to MarkUp. When a reviewer is looking at changes made to the site, they can easily refer to the screenshot inside of each comment to see what was previously there to confirm changes before resolving each comment. They can continue to share with clients, stakeholders, and others across their organization until all comments have been resolved and stored inside the same project.

Once the project is complete, MarkUp does not have the ability to archive projects, but this is something we plan to add with our Teams plan in 2021.

Structured Feedback Loops

While MarkUp does not have dedicated version control, we know that teams like to maintain different “versions” of their content inside of MarkUp. 

The main option for Version History is quite simple: Structured Feedback Loops. With this approach, you can create different MarkUp projects for each stage of the review cycle you are on. You can upload your URL as many times as you’d like and simply create labels for each project (i.e. “Version 1”, “Version 2”) on your MarkUp Dashboard. This is a great way to split up feedback for teams that don’t want to keep all review comments in the same project over time. 

Just remember, if you are keeping the same URL every time, your Version 1 MarkUp site will look the same as your subsequent versions when you are done, because MarkUp constantly updates that same URL.

Going this route is more so about keeping the comments from each round in separate MarkUp projects. Additionally, having the MarkUp Chrome Extension is a great way to ensure more contextual comments can be seen over each Version you create. Even as the site in Version 1 looks the same as Version 5, with the extension, those comments across each project will have screenshots attached to them to show you what has changed over time. This is an excellent way to always have context in absence of true versioning inside of MarkUp.

Was this helpful?

You already voted!
12 out of 12 people found this helpful