Employer:
CISCO
DevNet Docs Redesign
A BETTER WAY TO SEARCH FOR DOCS
DESIGN CHALLENGE
developer.cisco.com/docs was one of the most viewed pages on developer.cisco.com, but it only showed 80 out of the 300+ developer documents that are available on develper.cisco.com. Also, it was manually updated by one single person 🫨, which not only limited the user experience for anyone viewing the page, but created a back-end nightmare. I was tasked with looking at how we could make this page dynamic so that anytime a new document was published, a developer looking for the documentation would be able to find it on developer.cisco.com/docs. This required not only a visual refresh but also working with doc writers and engineering on the backend system to tag and update properly. Turning a static page into a dynamic and automated system. Allowing developers to find the documentation they needed
RESULTS
– User return rate went from 1.4 to 4.4 times
– 44% of users where are able to find content faster
– Automating the page going from 80 docs to showing over 310
– Working with the content team to clean up docs on the backend for better tagging and description
Taking a step back and a deeper look
When going into this project the biggest thing was to step back and look at the bigger picture. I created a Miro board to cross-collaborate to work with our content team. To look at what content is missing and what is needed as well as documenting issues from user research. This helped us get on the same page and divide up the work needed from the design and content teams.
Explore what’s new and focus on search
We broke the page into two pages the first focused on the search and most popular Documentation. The second was to create a more granular level of search giving more filters and allowing users to drill down and find the documentation they were looking for.
