OneTrust offerings are targeted for the small to medium sized businesses. OneTrust wants to take their existing offerings and target enterprise businesses. This new offering is called Enterprise Risk Management (ERM). I am the lead UX designer responsible for this offering. This entails understanding the users and creating the designs for an ERM tool.
The product owners and myself had a bunch of assumptions starting the project. This was a perfect opportunity to test our assumptions with the users and learn more about their use cases.
I collaborated with the sales team to identify existing customers who might benefit from an ERM tool. I compiled a list of questions, then collaborated with the UX research team to refine the questions further. I scheduled informational sessions with the customers to learn more about how they would utilize an ERM tool.
After the user sessions, I was able to identify three key end-users: C-level, Risk Managers, and Risk Owners. This was helpful to frame the conversation, problems, and potential solutions around the users needs and goals.
_ERM%20Use%20Case.png)
I used an affinity map to help consolidate my research. This helped my team and I have one source of truth that we could always reference.
Once I had a solid foundation of the users needs, I utilized our design system to create different wires. At first, I explored a tabular design because it was easy to implement. However, I found the tabular design was a bit difficult to view a hierarchy because the users view enterprise risk with a top-down lens. That said, the wires was great to get quick feedback from the team and users.
Since the tabular view didn't meet the users need, I had to improve on the visualization. This led me to explore a card layout. However, this was outside of our design system and it would require more effort to implement.
As a result, I searched our design application to find components that were more visual. I was able to find a visual component in our organization chart that I could leverage. Using the organization chart for our MVP would buy the developers time to implement the card layout.
OneTrust offerings are targeted for the small to medium sized businesses. OneTrust wants to take their existing offerings and target enterprise businesses. This new offering is called Enterprise Risk Management (ERM). I am the lead UX designer responsible for this offering. This entails understanding the users and creating the designs for an ERM tool.
The product owners and myself had a bunch of assumptions starting the project. This was a perfect opportunity to test our assumptions with the users and learn more about their use cases.
I collaborated with the sales team to identify existing customers who might benefit from an ERM tool. I compiled a list of questions, then collaborated with the UX research team to refine the questions further. I scheduled informational sessions with the customers to learn more about how they would utilize an ERM tool.
After the user sessions, I was able to identify three key end-users: C-level, Risk Managers, and Risk Owners. This was helpful to frame the conversation, problems, and potential solutions around the users needs and goals.
I used an affinity map to help consolidate my research. This helped my team and I have one source of truth that we could always reference.
Once I had a solid foundation of the users needs, I utilized our design system to create different wires. At first, I explored a tabular design because it was easy to implement. However, I found the tabular design was a bit difficult to view a hierarchy because the users view enterprise risk with a top-down lens. That said, the wires was great to get quick feedback from the team and users.
Since the tabular view didn't meet the users need, I had to improve on the visualization. This led me to explore a card layout. However, this was outside of our design system and it would require more effort to implement.
As a result, I searched our design application to find components that were more visual. I was able to find a visual component in our organization chart that I could leverage. Using the organization chart for our MVP would buy the developers time to implement the card layout.
OneTrust offerings are targeted for the small to medium sized businesses. OneTrust wants to take their existing offerings and target enterprise businesses. This new offering is called Enterprise Risk Management (ERM). I am the lead UX designer responsible for this offering. This entails understanding the users and creating the designs for an ERM tool.
The product owners and myself had a bunch of assumptions starting the project. This was a perfect opportunity to test our assumptions with the users and learn more about their use cases.
I collaborated with the sales team to identify existing customers who might benefit from an ERM tool. I compiled a list of questions, then collaborated with the UX research team to refine the questions further. I scheduled informational sessions with the customers to learn more about how they would utilize an ERM tool.
After the user sessions, I was able to identify three key end-users: C-level, Risk Managers, and Risk Owners. This was helpful to frame the conversation, problems, and potential solutions around the users needs and goals.
I used an affinity map to help consolidate my research. This helped my team and I have one source of truth that we could always reference.
Once I had a solid foundation of the users needs, I utilized our design system to create different wires. At first, I explored a tabular design because it was easy to implement. However, I found the tabular design was a bit difficult to view a hierarchy because the users view enterprise risk with a top-down lens. That said, the wires was great to get quick feedback from the team and users.
Since the tabular view didn't meet the users need, I had to improve on the visualization. This led me to explore a card layout. However, this was outside of our design system and it would require more effort to implement.
As a result, I searched our design application to find components that were more visual. I was able to find a visual component in our organization chart that I could leverage. Using the organization chart for our MVP would buy the developers time to implement the card layout.
OneTrust offerings are targeted for the small to medium sized businesses. OneTrust wants to take their existing offerings and target enterprise businesses. This new offering is called Enterprise Risk Management (ERM). I am the lead UX designer responsible for this offering. This entails understanding the users and creating the designs for an ERM tool.
The product owners and myself had a bunch of assumptions starting the project. This was a perfect opportunity to test our assumptions with the users and learn more about their use cases.
I collaborated with the sales team to identify existing customers who might benefit from an ERM tool. I compiled a list of questions, then collaborated with the UX research team to refine the questions further. I scheduled informational sessions with the customers to learn more about how they would utilize an ERM tool.
After the user sessions, I was able to identify three key end-users: C-level, Risk Managers, and Risk Owners. This was helpful to frame the conversation, problems, and potential solutions around the users needs and goals.
I used an affinity map to help consolidate my research. This helped my team and I have one source of truth that we could always reference.
Once I had a solid foundation of the users needs, I utilized our design system to create different wires. At first, I explored a tabular design because it was easy to implement. However, I found the tabular design was a bit difficult to view a hierarchy because the users view enterprise risk with a top-down lens. That said, the wires was great to get quick feedback from the team and users.
Since the tabular view didn't meet the users need, I had to improve on the visualization. This led me to explore a card layout. However, this was outside of our design system and it would require more effort to implement.
As a result, I searched our design application to find components that were more visual. I was able to find a visual component in our organization chart that I could leverage. Using the organization chart for our MVP would buy the developers time to implement the card layout.
.png)
