Melissa Denby
Creating an action
My goal on this project was to help our users create an action to resolve a problem. As part of this flow, our team wanted the user to be able to test the action before they saved it. Context: these actions are important because they allow our users to solve problems faster that impact their customers, and business.
"I spend a lot of time answering, 'How can we do this better the next time?'"
01
Identify persona
I started by meeting with our team of designers, developers, managers, and project manager to better understand the problem, our persona, and make sure we were aligned in our common understanding.
​
Persona: Orion the Site Reliability Engineer (SRE). We identified his wants, needs, pain points, and goals.​
​
Problem: Orion, the Site Reliability Engineer (SRE), needs to resolve repeated, known incidents on his application quickly so he can spend time focusing on solving more challenging incidents and creating new features with his team.
​​​​​
02
Wireframe ideas
I created several wireframe flows that would allow Orion the SRE to create, and test an action that resolved an incident.
Then I presented these ideas to our team, and we collaborated together to revise the idea. After a few iterations, I began working with our visual and content designer to further refine the design.
I also presented these designs across teams, and to the larger design team for critique and to help maintain consistency across our product.
During this time our product was transitioning between design systems, so I worked with my team to think about how the design could work for our current system, and our future system, in addition to working with other teams on create patterns across our product.
03
Final designs
Once the final designs were complete, I and my design team handed them off to be implemented by our development team. As the designs were created in our product, I monitored, answered questions, and worked on quality assurance (QA).
04
User feedback
Since this project was a priority, and was released into Preview (or Beta) for our customers, we were able to gather feedback on customers before releasing it to the main product.
​
We met with several internal SREs, and several external customers for feedback. Customer usage was also captured in Amplitude. And this feedback informed our next iteration, and future projects.
