CASE 01 / VISION PORTAL / DASHBOARDS
Making cybersecurity data easier to understand and act on.
Vision already contained valuable security data, but clients struggled to understand what it meant, what required attention first, and how ISH was improving their environment.
I designed a dashboard foundation that translated technical signals into clearer views of risk, priority and progress for clients and internal teams.
+32%
Monthly active users
Within three months of release
+60%
Views per client account
More frequent access to security information
6+ dashboards
Priority views delivered
Across the first dashboard suite
COMPANY / ISH TECH
PRODUCT / VISION PORTAL
ROLE / UX/UI DESIGNER
PRODUCT VIEW / VISION DASHBOARDS
FROM SECURITY SIGNALS TO ACTIONABLE PRIORITIES

RAW TECHNICAL OUTPUTS
Product-specific metrics
Security jargon
Inconsistent visual hierarchy
USER QUESTION
What is happening, and what needs attention first?
PRIORITIZED INFORMATION
Severity, exposure, trends and service status
SHARED CONTEXT
The same operational picture for clients, Sales and security teams
ACTIONABLE DASHBOARDS
Clear priorities without relying on support to interpret the data
FROM TECHNICAL OUTPUTS TO DECISION SUPPORT
STRATEGIC DECISION / START WITH THE QUESTIONS
Build the dashboard around decisions, not around every available metric.
TRADE-OFF / A shorter two-stage discovery process prioritized delivery speed while still validating the problem directly with clients.
Conversations with Customer Service, Sales and clients showed that the main gap was not missing data.
It was missing interpretation.
I organized the first dashboards around three recurring questions: What is happening? What needs attention first? What is ISH doing about it?
This gave design, data and engineering a shared information hierarchy while keeping the first release focused and technically feasible.
SERVICE COMPLAINTS → CLIENT INTERVIEWS → DATA FEASIBILITY → BASE DASHBOARDS FIRST
SOLUTION / FOUR DECISION VIEWS
One dashboard language across different security contexts.
The first releases established a repeatable information structure: current state, priority, change over time and next action. That logic could then scale across Vision without forcing users to relearn the dashboard for every security service.
IMPACT / FOUR PRODUCT SHIFTS
The operation became repeatable, not just faster.
DESIGN PRINCIPLE
SHOW THE DECISION, NOT JUST THE DATA.
The dashboards became useful when technical metrics were organized around context, urgency and next action, not around everything the systems could expose.
01
SCATTERED SECURITY METRICS
→ SHARED SECURITY OVERVIEW
Clients and internal teams gained a common view of exposure, priorities and progress.
02
DATA WITHOUT PRIORITY
→ RISK ORDERED FOR ACTION
Severity, exploitability and trends made it clearer what required attention first.
03
REACTIVE SUPPORT EXPLANATIONS
→ CONTEXT INSIDE THE PRODUCT
Clients could understand the service without starting from a separate support explanation.
04
LOW PORTAL ADOPTION
→ A PRODUCT CLIENTS RETURNED TO
Clearer information made Vision more useful as an ongoing monitoring experience.
+32% MONTHLY ACTIVE USERS
Growth measured during the first three months after the initial dashboard releases.
+60% VIEWS PER CLIENT ACCOUNT
More frequent access to security information and monitoring inside Vision.



