Step 1: Improving the performance of ‘Preview’

Before: The preview function would break and was an unreliable tool for developers and content editors trying to view and update sites.

Solution: Fix the preview through engineering, improve the user experience through transparent design by:

• Creating a widget that shares the status of the site

• Providing a way to share site with stakeholders

• Providing a link back to the CMS to make more edits

Step 2: Enabling a way for content editors to get feedback on sites

Before: Content editors have various methods for receiving feedback on sites before publishing. Whether it’s through scribbles on screenshots, email, or slack — this was an opportunity for us to close that gap in the process.

Solution: Implemented a feedback panel

• Give content editors a way to capture comments form stakeholder

• Give content editors a way to respond to feedback

Step 3: Providing a feedback experience for developers

Before: Development teams did not have a way to give feedback on code within the experience

Solution: Created an inspect view to add feedback

• Gives developers a way to view code, and add feedback

• A way to take action on feedback by providing a link directly to elements in the CMS

Challenges & Outcome

• A large amount of technical debt needed to be sorted before this project could move forward in its entirety.

• A functioning MVP was built in 2, and usability tests were conducted on the entire concept. However due to resourcing the team shifted to backend performance and the remainder of the experience was never shipped.