How to manage a successful website revision process
We’re in the final stages of your new website and are super excited to hand it over to you now for your feedback! We know this can be a fun but challenging part, especially now that we’re getting so close to the end. To help make this as successful and easeful as possible, we’ve put together this revisions document to guide you through making the most of this part of the process.
Here’s what a typical round of revisions looks like
Step 1
Review the site and share it with any staff, board members, and other stakeholders whose input is needed.
Step 2
Everyone submits comments and requests using Feedbucket.
Step 3
The point-person—or core project team—reviews all comments in Feedbucket to ensure alignment and accuracy. (see checklist below)
Step 4
Email us and let us know you finished compiling your Round 1 of revision requests.
Step 5
We’ll review and begin making updates. If anything is unclear or requires discussion, we’ll schedule a meeting.
Repeat
Repeat steps 1-5 for Round 2. This round is typically a shorter round where you confirm changes from Round 1 and add anything else we missed the first time through.
What to include in your revision requests
Revisions Checklist
Make all requests that are passed on to us actionable:
Actionable request: “Remove this image and replace it with this…”
Non-actionable request: “I’m not sure about this image.”
Image requests: include the new image as an attachment.
Text changes: specify what text should be added, what should be removed, and where. Feel free to copy entire sections, edit the text, and paste it in Feedbucket rather than leaving a bunch of comments if that’s easier!
Mobile review: Check the site on multiple mobile phones and tablets.
Test everything: Test all functionality including links, galleries, forms, etc.
Clean up requests: Look over all revisions submitted by staff and other stakeholders, and remove any you don’t want to proceed with.
Tips for managing stakeholders
- Share the site broadly with stakeholders and others who can offer valuable feedback. You can share it with as many or as few people as you’d like.
- Designate a person to collect and compile the revisions. Their job is to decide what feedback to pass on and what to ignore.
- Don’t just blindly pass over all of the feedback you get from your stakeholders. If you get feedback from lots of different people, chances are you won’t agree with all of it, and some requests might contradict others.
- Remind stakeholders where we are in the process and what sort of feedback we’re looking for.
- Solicit specific feedback (rather than open-ended). Rather than having all staff members give opinions on the whole site, you might want to ask specific people to focus on the parts of the site most relevant to them. Dave from Development should be invited to give extensive feedback on the Support Us page, but his opinions on the blog layout may not be as helpful.
What's next
Once we finish both rounds of revisions, we’ll get your go-ahead to prepare for launch and set a date. We’ll run the site through our pre-launch checklist, including SEO optimization, accessibility, and final testing. Then we’ll launch on the agreed upon date, usually before or after working hours, and send you a launch congratulations email once the site is live. We usually recommend waiting at least 24 hours before promoting the new website to ensure it’s had time to fully propagate across the internet.
We continue to provide full support for the site for 30 days after launch. During this time, we’ll schedule a Zoom training to show you how to edit and add content to your website using the WordPress dashboard.
After 30 days is complete, we’ll invite you to sign up for a website care plan so we can continue to monitor, support, and improve your website into the future. Or if you decide to manage it yourself, we’ll ensure you have the access you need.