Team and User Management
Introduction
This project involved the use of Hypothesis-Driven Design methodologues to enhance the products quality and functionality.
“We believe that streamlining and simplifying user management navigation for runbook for runbook users will result in more effective planning, thereby leading to Cutover’s improved support across all use cases.”
Research
I conducted interviews with the users to assess the current process and collect feedback regarding any existing pain points.
8 Participants • Remote • Average time 12 minutes
The data gathered was summarised using affinity maps to identify common patterns.
From this I was able to summarise insights which made up the needs of the users.
Persona identification ensured alignment regarding who this was being built for.
This helped me empathise with individual users rather than groups.
Considering multiple personas enabled me to cater for different people, their needs and expectations.
I was able to make better, user centred design decisions that brought the most value.
Competitive analysis enabled me to assess the features, functions and flows of the design solutions of competitors.
Conducting Workflow Analysis provided me with insight into the complexities of the existing people management feature.
This research led me to devise a design brief outling the problems to be solved.
Design
Low fidelity wireframes enabled me to iterate fast.
This helped me organise the high level information and communicate the big ideas to stakeholders with little effort.
Usability testing was undertaken to uncover feedback early.
7 Participants • Remote • Average time 14 minutes
The permission structure was complex, so I had to ensure the design covered all permitted routes.
Workflow analysis helped me conduct a thorough breakdown.
I further refined the low fidelity designs to address permission concerns and conducted additional user testing until I was satisfied with the overall flow.
When satisfied, I moved into high fidelity mockups, bringing the ideas to life.
Prototype
Reflection
Work With Copywriters Early and Often
It was beneficial to have the resources and receive feedback on my copy from someone that had a strong grasp of writing, understood the messaging, and could provide messaging consistent with that used throughout all of the company communications.
Leading By Example
A significant aspect of the project was establishing reserach practives for my team that could be utilised in future projects. While I could have following the product teams feature requests which were based on assumption, as a designer its my responsibility to conduct thorough groundwork and reserach, regardless of predefined requirements. This ensures we deliver a solution that ads value and addresses the users’ needs rather than relying solely on assumption.