What was our approach?
We were influenced by a book read in our UX book club, Sprint. We really wanted to try an iterative design approach and worked on iterating a new design each week. By the end of the process we had done three iterations of the design and talked with 22 customers, user-testing the prototypes each round.
Prototype
What were the lessons learned?
The fact that we were able to iterate on our design really allowed us to transform the design from our initial thoughts. After the first round we learned that we weren't showing an new or unique data they couldn't get somewhere else, it wasn't configurable enough, and agency customers were not doing weekly crawls. So we pivoted the design to address these new concerns.
What was our process?
Typically we work in a pretty Agile Sprint process at Moz, this project was approached as more of a Waterfall, because of the sheer amount of research and the complete overhaul of the backend architecture. Once the architecture was agreed upon development worked in sprints with the first milestone being a beta to roll out to a small user base.
Final Prototype
How did we measure success?
Once the beta launches the plan is to measure both qualitative and quantitative feedback on the new Site Crawl. They will be gathering qualitative feedback from a sampling of the beta users (regular weekly interviews) along with asking for feedback through Intercom (in-app communication tool.) Quantitative feedback will consist of crawl speed and capacity metrics in relation to the old crawl.
