VAIDAS
BOLIAKU
← All projects

Case study

SAI360

Enterprise GRC platform

A comprehensive governance, risk and compliance platform helping organizations manage risk, ensure compliance and build a stronger, more ethical culture.

Enterprise SaaSDesign SystemsComplex WorkflowsAI Features
SAI360 risk overview report with a risk matrix, treatment plan chart and detailed risk table
Risk overview
SAI360 incident management dashboard with status, impact and action charts
Incident management
2023 – 2026
Senior UX/UI Designer
Industry
GRC / Compliance
Team
Product, Engineering,
Stakeholders
—

Project overview

Four areas, one complex product ecosystem.

My work at SAI360 spanned core product flows, assessment experiences, alternative data representations and the design system behind them. Each problem was different, but the goal was the same: make a complex enterprise platform easier to understand and use.

01

Landing page design

A central hub for what matters.

Users needed one dependable starting point across a fragmented set of modules, roles and priorities.

Decision
A stable hierarchy for notifications, inbox items, recent activity and quick actions.
Outcome
A clearer entry point where priority work and next actions are easier to identify.
NEW INSIGHT

Smarter risk signals

Review patterns across your latest GRC data.

Quick actionsView risks
One overview, shared across solutions
02 · Part 01

Assessment experience

The assessment pattern needed to feel consistent with the wider platform while supporting more information and clearer progress.

Shared patternsVisible progressClear answer states
ASSESSMENT ENGINESESSION: SR-1042STATUS: ACTIVE
Supplier Risk AssessmentLast saved 14:32
ITEM: ASMT-004TYPE: SINGLE SELECT
PRIVACY / DATA PROCESSING

Does the supplier document how personal data is processed?

The same assessment task with clearer progress, context and answer states.
02 · Part 02

Configuration flow

A long setup flow had to support existing rules, optional settings and expanding data needs without breaking established workflows.

Existing rulesOptional settingsContextual guidance
Assessment configurationSettings
Same assessment rules, reorganized into a clearer configuration workflow.
03

Alternative data views

Different workflows,
the same underlying data.

Comparison-heavy tasks needed density, while status-led workflows needed faster scanning. Table, list and card views share the same filters, permissions and actions, so users can change representation without relearning the product.

NameTypeDue date
Vendor privacy reviewPrivacy
Data retention reviewPrivacyDue in 3 days
Access control auditControl
One dataset, represented for different workflow needs.
04

Design system & contextual features

Scaling patterns,
not isolated screens.

I worked with engineering to turn recurring navigation, data and guidance needs into reusable patterns that could support legacy modules, new product work and contextual AI experiences.

Reusable patternsShared statesProduct context
Supplier risk

High-risk suppliers

Attention
24Open records
Risk trendLast 6 months
3 require review this week
Shared system foundations, adapted to the information and decisions in each product context.
—

Final thoughts

“Complex tools can be simple
when the experience is designed
with people in mind.”

SAI360 reinforced that enterprise design is as much about structuring decisions as shaping screens. Working across product, engineering and stakeholder constraints helped me create patterns that are clearer for users, reusable across solutions and realistic to implement.