CRASHES
Company: Cisco
Role: Lead Content Designer
In enterprise networking, the nuances of hardware and software crashes demand clear communication. Users require insights into crash triggers, system vulnerabilities, and recovery protocols for both campus (physical hardware) and cloud networks.
Upon joining the project, I focused on simplifying intricate details by employing content-design tools like user-decision trees and conversation exercises to improve the information architecture. I also rewrote tooltips and labels to optimize information delivery and simplify user experience.
CR 2
CR 3
Actions & Statuses
Tackling hundreds of actions and statuses to cover various crash-file analyses and outcomes, I spearheaded the creation of an extensive content matrix. Of the hundreds I wrote, here are just a few examples.
CR 4
CR 5
Empty States
ES 1
ES 2
Ontological Guide
Co-creating this ontological guide, I focused on incorporating product information, taxonomies, and other critical information. These guides proved indispensable for familiarizing new UX/UI designers, stakeholders, and product managers with complex products, simplifying information to ensure a smooth transition.