Monitoring DevOps
Visualize financial system integration status for testers and executives in order to increase process transparency and cross-team accountability.
Project type
Zero to one
Platform
Responsive web application
My role
Sr. UX architect
Timeline
2015
Constraints
On-site client collaboration
Legacy file system limitations
Team
1 product manager
3 engineers
1 UX architect
Experience definition
The diagrams below are the fruit of many conversations with engineering teams, QA testers, and end-users. They helped me understand the flow of their manual DevOps process—what worked, and what didn’t.
They also clarified which actions were important to them each step of the way. These artifacts translated their needs into development requirements for product managers and engineers building the monitoring experience.
Responsive design
I worked with stakeholders to envision a multi-purpose system. It functioned for testers as they looked to resolve system issues on a desktop.
It also worked as a passive TV display in the engineering war room and on the IT director’s iPad. Dark mode is available for late night deployments.
Responsibilities
Meet with executive sponsors, system integration testers, product owners, and engineers to understand needs; architect the user experience, and provide design direction for the application interface.
Deliverables
User stories and experience guidelines consisting of personas, journey maps, system taxonomy, information architecture, workflow diagrams, wireframes, and UI mockups with style specifications.