Nov 2022, apr 2024 | new feature, information diagram
Risk Assessment for Data Security Product
How I defined the scope, content and place for a new feature in Netwrix 1Secure
I led the project from the initial strategy and alignment with user needs to the detailed visual design and prototyping.

What It's About

Imagine onboarding a new client and immediately highlighting their security vulnerabilities. This was the goal behind designing a Risk Assessment feature for Netwrix 1Secure. This feature allows Managed Service Providers (MSPs) to diagnose the security posture of an organization’s infrastructure, underline problematic areas, and validate the effectiveness of their services by showing a reduction in risks over time.
Netwrix 1Secure is a SaaS solution designed for MSP companies, streamlining IT audits with precision.

How I did it

I recommend you to read the full case by following this Figma link:
Risk Assessment Case Study

Feature Integration Blueprint I Used in Design Process

Wireframes blueprint, laying out where each part of risk data would live within the app screens and architecture

Overall Approach I Followed

  • User-centric design: I defined job stories and key questions to ensure the feature aligned with real user needs. Based on the existing user feedback, I simplified risk scores into straightforward severity levels and trend analyses, making complex data accessible and actionable.
  • Competitive analysis: I studied other solutions to identify best practices and differentiate our approach.
  • Strategic integration: I created detailed information diagrams for seamless integration of the new feature into the existing app.
  • Iterative design: I developed wireframes, interactive prototypes, and incorporated iterative feedback to refine the design – to improve widgets, refine the risk list, and add a new view for efficient risk search.
I still think it's better to read the full case in Figma:
Risk Assessment Case Study
More case studies
How I transformed Verifika from desktop to web and enhanced user experience by tackling 10+ issues
How my team won first place at the Netwrix AI-hackathon with the Idea of smart reports
Ready to take UX to the next level?
Contact me

Iteration 2

  1. Wave goodbye to risk scores! That's right, we trashed the original concept. We recognized that MSPs don't need a labyrinthine score to know which organizations are high-risk—they just need to understand if the risks are high, medium, or low. Simple, but incredibly powerful.
  2. But what about tracking progress, the bread and butter of any MSP's pitch? Plain-text risk trends. The real hero metric was the risk's downtrend over time, a tangible testament to an MSP's skill.
  3. When it comes to defining severity, we turned to plain-old thresholds. More than 'N' items flagged? That's a high risk, no PhD in rocket science needed. And trends? They're just the good ol' "before and after" snapshots, comparing metrics from two different time periods.