top of page

Groups

View groups and posts below.

  • Facebook
  • Twitter
  • LinkedIn

©2021 by Navin's Portfolio. Proudly created with Wix.com

bottom of page

Designing clarity
into complex systems.

That's the work.

Enterprise products get messy. Fast. Too many workflows. Too many edge cases. Too many decisions made in silos.

That's where I come in. I work with Product and Engineering teams to simplify how things actually work, not just how they look.

Less confusion. More adoption. Better outcomes.

I build systems that scale across products where complexity is the default.

UX Writing Leader · Content Systems · Enterprise UX
Navin Mathew portrait
Navin Mathew
18+ years · Enterprise SaaS · Systems over screens
Hire me →
40+
Products supported
Across enterprise SaaS modules, startups, and multinationals.
57%
Reduction in support calls
By fixing flows, not just screens. Less confusion. More adoption.
AI-assisted
Workflows
15–24% productivity lift through AI-driven onboarding and task optimization.
Leadership impact

Leadership impact.

Not just what I shipped. What changed because of it.

18
Years experience
Across enterprise UX, content systems, and design leadership. Across SaaS, EdTech, FinTech, Healthcare, and Enterprise Software.
40+
Enterprise products
Multiple enterprise SaaS modules within startups and large multinationals. Workflows tied to onboarding, documentation, and learning systems.
70+
Product org collaborators
Cross-functional partners across Product, Engineering, Support, Compliance, and Research. Alignment isn't a deck. It's the work.
4
Direct reports
Restructured roles. Introduced review systems. Built a leadership bench, not just a team.
How I think

How I think.

No big frameworks. Just a few principles that have held up in messy, real-world systems.

Clarity beats completeness.

Trade-off

Trying to cover every edge case usually makes things worse.

In practice

Instead, I prioritize:

  • Clear primary paths
  • Predictable behavior
  • Fewer decisions for the user

Systems over screens.

Trade-off

Fixing the screen without fixing the system? Temporary at best.

In practice

I don't start with UI. I start with flow. Using tools like:

  • FigJam (mapping workflows)
  • Miro (stakeholder alignment)
  • Figma (once the thinking is clear)

Solve for the next team, not just the next release.

Trade-off

Every solution should scale. So the next team doesn't start from scratch.

In practice

That's why I focus on:

  • Reusable patterns
  • Design systems
  • Documentation standards

Great UX doesn't come from better screens. It comes from better decisions.

I work best with teams building complex products, where workflows are messy, stakeholders are many, and clarity is hard to find.

The kind of environment where Product wants speed, Engineering wants feasibility, Users just want things to work.

That tension? That's the work. And that's where I do my best thinking.

Navin · Bangalore · 2026
Strategic influence

Strategic influence beyond projects.

Strategy doesn't live in decks. It shows up in decisions. Over the last few years, my role has been less about screens, and more about direction. What gets built. What doesn't. And why.

i

Roadmap influence.

Partnered with Product leads to shape prioritization using:

  • Support ticket trends
  • Usage analytics
  • Workflow friction data
Result? Fewer "nice-to-have" features. More meaningful releases.
ii

Cross-org alignment.

Worked across Product, Engineering, and Customer Success to align on:

  • Design standards
  • UX review cycles
  • Release readiness
Less back-and-forth. More forward movement.
iii

Team scaling.

Restructured a team of UX writers into a more structured system:

  • Defined roles
  • Introduced review frameworks
  • Built repeatable processes
Output improved. So did confidence.
What I'm looking for

Roles where UX shapes real outcomes.

I want to work on complex products. Where UX shapes real outcomes. I do my best work in environments where UX is expected to do more than execution.

  • Lead UX across products
    Lead UX across multiple product areas. Set direction, not just deliverables.
  • Work closely with Product and Engineering
    Partner closely with Product and Engineering on roadmap decisions, before they're roadmap decisions.
  • Improve real business results
    Improve adoption, efficiency, and support outcomes. Tie UX to metrics the org actually cares about.
  • Build and grow strong teams
    Build and grow teams that deliver consistently at scale.

At this level, UX isn't just about usability. It's about clarity.

And clarity changes everything.

What people say

Words from collaborators.

"Navin took over the technical writing on my product midstream. He was happy to continue with the layout and process we already had, but also brought a new perspective and several ideas that made our documentation much clearer. He did this all without adding much time to delivery. He went out of his way to work around our changing timelines. His flexibility was a real asset."

Cassandra Welden
Director of Analytic Product Management · Information Resources, Inc.
Senior to Navin · April 2015

"Navin was hired as a documentation specialist during the Symphony Teleca tenure for the IRI products. He quickly picked up the pretty complex predictive analytics products in short time and delivered very effectively on time. He directly interacted with customer and created his credibility in the IRI. He is always a valuable asset for any organization."

Soujanya Aluri
Chief Digital and Technology Officer
Managed Navin directly · April 2017

"I have known Navin for a little over 3 years now. Not a single day has passed that he hasn't surprised with his innovative thinking. He is a great listener and even better speaker. He is dependable and works mostly without much supervision. I would like and prefer to count on him for anything that we would work together on."

Varunish Garg
Product & UX Content Strategist · Turning Complex Workflows into Clear Docs
Worked with Navin on different teams · October 2014

"I had the honor of working with Navin on a wide range of Citrix technical documentation. Navin is a quick learner that rapidly acquainted himself with both the product knowledge and the technical platform. Navin always had great questions, a positive attitude, and a willingness to learn and contribute. An invaluable asset to any team in need of a professional, driven, and team-oriented contributor."

Jerred Metts
Technical Writer at Apple
Worked with Navin on the same team · October 2017

"I had the opportunity to work with Navin on my analytic solutions at IRI. Navin is an excellent and well-organized documentation lead. He can handle multiple priorities and always responds in a timely manner. He did an excellent job integrating my feedback to bring the right message to our users."

Jonathan Dizney
Mix Director
Worked with Navin on the same team · June 2016

"I am extremely impressed with the technical acumen with which Navin produces his deliverables. Blessed with a calm and composed mind, he shows no signs of arrogance. I would recommend him for a managerial role that involves working with a team of diverse portfolio."

Rajdeep Gupta
Technical Writing · Trainer · AI-enabled Technical Documentation
Worked with Navin · October 2014

"Navin, as part of the core operations team at RAC-F, helped plan the communication and content strategy for the annual Tour Of Nilgiris cycling tour. He helped manage participant data online and worked with the PR and Marketing teams both on and off the tour, and helped build a cycling community by working in the background."

Sridhar Pabbisetty
Enabling Inclusive Governance and Regenerative Economy
Navin's client · March 2018
, About

I didn't start as a designer.
I started by fixing clarity problems.

I saw users struggle. Not because of design. But because things were hard to follow. Workflows were broken. Instructions were unclear. Decisions didn't match user needs.

And honestly, that turned out to be the real job.

In enterprise systems, users don't struggle because of bad visuals. They struggle because nothing connects. Workflows break. Instructions don't help. Decisions made upstream create confusion downstream.

I saw this early, working across complex SaaS products where a single workflow could touch Product, Engineering, Support, and Compliance.

That's where I started asking better questions. Not "How do we design this?" But, "Why does this feel hard in the first place?"

How I think about UX

That shaped how I work today.

I don't look at screens first. I look at systems. How users move through workflows. Where friction builds. What slows them down, and why it exists in the first place.

Using tools like:

FigJam to map end-to-end workflows
Dovetail to synthesize support data and user feedback
Figma to translate decisions into usable patterns
Confluence to create documentation that actually answers tough questions

Because fixing the interface without fixing the system? Is temporary, at best.

Over time, I've grown into a UX leader who connects dots others miss. Between user behavior and product decisions. Between design execution and business outcomes. Between teams that need alignment but rarely have it.

That shift changed the kind of work I do. Less about deliverables. More about direction.

I care about doing work that actually moves something.

How I work

My approach in four moves.

No big frameworks. Just what has worked, repeatedly, in messy, real-world systems.

Move one

Start with problems, not features.

I look for where users struggle. I use support data and usage data. I talk to teams and stakeholders. This helps us solve the right problem.

I start with friction: support tickets, drop-off points in workflows, repeated user confusion.

At PowerSchool, this meant analyzing support trends across modules and identifying patterns in where users consistently got stuck. That's what led to: 57% reduction in support calls. Not because we redesigned screens. Because we fixed the flow.
Move two

Tie UX to business value.

If UX doesn't move metrics, it won't survive prioritization. So I connect design decisions to outcomes like adoption rates, workflow completion time, and support dependency.

I connect UX work to real outcomes: better product use, faster workflows, fewer support issues.

Example: Simplifying onboarding and task flows led to ~20% improvement in delivery efficiency and 15–24% increase in productivity. UX isn't decoration. It's leverage.
Move three

Bring structure.

Most UX problems are actually process problems. So I build systems: UX governance frameworks, design review cycles, reusable content and interaction patterns.

I help teams work better. I set up clear processes, shared patterns, better collaboration.

At PowerSchool, this reduced design iteration cycles by 30%. Less rework. More consistency. Better outcomes.
Move four

Stay close to the work.

I don't disappear into strategy. I stay involved in workflow decisions, design reviews, and key product tradeoffs.

I stay involved in workflows, key decisions, and design reviews. This keeps things practical and useful.

Because strategy only matters if it shows up in the product. And most of the time, that's where it breaks.
Trusted by

Built for teams where UX shapes outcomes.

Across industries where complexity is the default, not the exception.

Industry
SaaS
Enterprise platforms, multi-tenant workflows, complex permissions.
Industry
EdTech
K–12 + higher-ed platforms. Onboarding, instruction, assessment.
Industry
FinTech
Regulated flows. Compliance UX. Decisions under risk.
Industry
Healthcare
Staffing marketplaces, clinical workflows, structured matching.
Industry
Enterprise Software
Multi-product orgs. Governance. Internal tools that scale.
Core competencies

Where I do the work.

The capabilities I bring, and the ones I build in others.

01
Strategy
Connecting UX work to business outcomes. Roadmap influence. Decision frameworks.
02
Research
Synthesizing support data, usage patterns, and qualitative feedback into direction.
03
Team leadership
Structuring roles. Coaching ICs into leaders. Building review systems that scale.
04
AI UX
Designing AI-assisted workflows. Productivity gains of 15–24% from intelligent task flows.
05
Governance
Intake models, design review cycles, content standards. The unglamorous work that compounds.
Who I work with

Built for teams where UX shapes outcomes.

I do my best work in environments where UX is expected to do more than execution. Where clarity matters as much as craft.

Heads of Product

Who need UX to shape direction, not just deliver screens. You want roadmap influence backed by user data, not opinion.

VPs of Engineering

Who want fewer rework cycles and clearer specs. You want UX that respects feasibility and reduces back-and-forth.

Founders building complex SaaS

Whose product touches Product, Engineering, Support, and Compliance. You need someone who can see the system, not just the screen.

Design leaders scaling teams

Who want help building governance, review frameworks, and reusable patterns. You want a UX leader who thinks in systems.

, Coaching

Three programs.
One conversation that changes how your leaders think.

Most teams don't have a design problem. They have a decision problem.

Managers stuck in execution. Leads unsure how to influence. Senior ICs not ready for leadership, but promoted anyway.

That gap? It shows up as: slow decisions, rework across teams, misaligned roadmaps.

I help close that gap. Not with advice. With structured coaching that builds better decision-makers inside your org.

Who this is for

Not everyone needs this.

But if you see these patterns in your team, you probably do.

  • 1.
    The "strong executor" manager. Delivers consistently. Struggles to influence. Good at solving problems. Not yet shaping them.
  • 2.
    The "almost-there" design lead. Trusted by their team. Still dependent on direction from Product or leadership. Ready for more. Not yet operating at that level.
  • 3.
    The "overloaded" senior manager. Managing people. Managing delivery. Managing expectations. No time to think. No space to grow.
  • 4.
    The "future leader" you can't afford to lose. High potential. Low clarity on next steps. These are the people who either grow into leaders, or leave to find that growth elsewhere.
What actually changes

Not confidence. Not motivation. Capability.

Real shifts in how your leaders think, decide, and influence.

In your leaders
  • They start influencing roadmap decisions, not just reacting to them.
  • They push back with clarity, not hesitation.
  • They connect UX work to metrics like adoption, efficiency, and support cost.
  • They handle ambiguity without escalation.
In your outcomes
  • Faster decision cycles.
  • Fewer design rework loops.
  • Better cross-team alignment.
  • Stronger leadership bench.
This is the difference between "we need better designers" and "we have leaders who can run this."
Programs

Three ways to build better leaders.

Each program is structured. Clear scope. Clear outcomes. No fluff.

Clarity Sprint

4 weeks

Short. Focused. High-impact.

Best for: specific leadership challenges, decision-making gaps, stakeholder friction.

We work on framing problems clearly, identifying root causes (not symptoms), and building sharper decision narratives.

Fixing one high-impact leadership bottleneck.

Start a conversation →
Recommended

Growth Partnership

3 months

This is where real change happens.

Not surface-level improvement. Behavioral shift.

We work across influence without authority, roadmap conversations, stakeholder alignment, and decision-making under ambiguity, using real work, real situations, real pressure.

From "reliable manager" to "trusted leader."

Start a conversation →

Leadership Transformation

6 months

Long-term investment.

For orgs that want: stronger succession pipelines, future-ready leaders, consistent leadership behavior across teams.

We focus on leadership identity, strategic thinking, scaling influence, mentoring other leaders.

This isn't training. Capability building at scale.

Start a conversation →
Not sure where to start? Good.

That's usually a signal something needs attention. Let's talk.

Book a 30-min conversation →

No pitch. Just clarity.

Navin Mathew signature
Navin · Bangalore
, Get in touch

Let's talk.

Whether it's a role, a coaching enquiry, or just a question about how I work, drop me a line. I read everything, and reply within a few days.

navin.matthew@gmail.com LinkedIn →
Selected work

Cases that moved something.

Each project below shows the problem, the decisions, the trade-offs, and what actually changed. Long-form on purpose. Click to read.

Confidentiality

Some project details in this portfolio have been generalized to respect company confidentiality and NDAs.

Product names, metrics, and architecture details may be modified where necessary.

01
2024
Acropolis, Sweden healthcare staffing marketplace
Designed a two-sided marketplace replacing manual healthcare staffing with structured, algorithm-driven matching.
SEK 5.4B market
02
2024
Bell the Bull, AI safety intelligence for K–12
Built a detection-first system for earlier, smarter student safety intervention. Not faster reporting. Better detection.
$18M ARR potential
03
2023
Acme Analytics, AI-driven cybersecurity platform
Turning security noise into decision-ready intelligence. From monitoring system to decision intelligence system.
90% faster MTTR
04
TBD
Case Study 04, coming soon
Navin sending content within a few days. Slot reserved.
In progress
← Back to all work
01 · Smart Recruit · Sweden Healthcare Staffing Marketplace

Designing a marketplace for faster, more reliable healthcare staffing.

A digital staffing platform connecting healthcare organizations with qualified consultants (doctors, nurses, specialists) across Sweden. Replaces a manual, fragmented process with a streamlined, data-driven marketplace.

Role
UX Lead
Team
11 people
Phases
3
Sector
Healthcare
Region
Sweden
i. The problem

Staffing was manual slow and imprecise.

Healthcare staffing was highly manual and time-consuming. Dependent on intermediaries and fragmented communication. Prone to mismatches between roles and consultants. Slow to respond to urgent staffing needs.

This resulted in delayed placements, increased operational cost, and poor matching quality.

ii. Why this matters

A SEK 5.4 billion staffing market with no operating system.

SEK 5.4B
Annual healthcare staffing market in Sweden. Growing steadily. Highly competitive.

Improving speed and accuracy of staffing directly impacts revenue growth, customer retention, and platform scalability. The opportunity wasn't to digitize the existing process. It was to redesign it.

iii. My role

Led UX thinking and product structuring for the platform experience.

Focused on marketplace workflow design, matching logic and experience, user journeys for both customers and consultants, and simplifying complex staffing processes.

Worked closely with stakeholders to align business model, pricing logic, and user experience.

2
Designers
1
UX Writer
1
Researcher
2
PMs
5
Engineers
11
Total
What I led

End-to-end UX direction.

  • Marketplace workflow design across all four lifecycle stages
  • Matching logic and experience architecture
  • Two-sided journey design (customer + consultant)
  • Stakeholder alignment on business model and pricing
  • Simplification of complex staffing processes
What I executed

Hands-on, where it mattered.

  • Critical flow design alongside the 2 designers
  • Design reviews and quality gating
  • Content direction with the UX writer
  • Research synthesis with the researcher
  • Spec hand-offs to engineering
Key decisions I drove

Four early decisions shaped the whole platform.

Marketplace, not directory
Build a true two-sided platform with structured matching, not a job board with profiles.
Lifecycle over feature list
Reframe the process into four stages: Seeking → Matching → Staffing → Follow-up.
Algorithmic matching as the differentiator
Match on salary, skills, availability, not just keyword search.
Pricing transparency built in
Hourly wage, surcharge, VAT, visible upfront, not negotiated after.
iv. Approach

Three moves that shaped the design.

1. Understanding dual-sided marketplace needs. Mapped two key user journeys, Customers (healthcare organizations) and Consultants (job seekers). Identified friction in job posting, matching, communication, and follow-up.

2. Simplifying the staffing lifecycle. Reframed the process into four core stages: Seeking, Matching, Staffing, Follow-up. Each stage owns specific decisions and hand-offs.

3. Designing for speed + accuracy. Focused on reducing manual steps, improving match quality, and automating updates and communication.

v. Solution

A platform built around structured matching.

Marketplace platform

Two-sided platform enabling direct matching between consultants and organizations.

Matching engine

Algorithm-driven matching considering:

  • Salary expectations
  • Skills
  • Availability

Automated communication

Notifications for:

  • Job matches
  • Updates
  • Opportunities

Pricing transparency

Clear pricing structure:

  • Hourly wage
  • Surcharge
  • VAT

Reduced ambiguity in decision-making.

vi. Impact

What changed in how staffing happens.

Faster
Staffing cycles
Reduced manual coordination across the lifecycle.
Higher
Match accuracy
Through structured data and algorithmic matching.
Scalable
Platform throughput
Automation absorbs volume without adding ops headcount.
Less
Intermediary dependency
Direct routing between hospitals and consultants.

Estimated outcomes based on system design and comparable benchmarks.

vii. What changed

Before → After.

Before

  • Manual staffing
  • Slow communication
  • Poor match quality
  • Fragmented process

After

  • Centralized marketplace
  • Automated matching
  • Faster placements
  • Transparent pricing
viii. Iterations

Three phases.

i
Phase one

Designing for end-users, doctors, nurses, and other healthcare professionals. Marketplace design thinking. AI integration.

ii
Phase two

Designing mobile interface for hospitals and consultants.

iii
Phase three

Designing web interface for hospitals.

x. Reflection

Marketplaces are trust systems not just interfaces.

  1. Both sides must be optimized.
    Platforms succeed when both consultants and customers see value. One-sided optimization breaks the ecosystem.
  2. UX is trust, clarity, and efficiency.
    In marketplaces, UX isn't just interface design. It's how trust gets built between strangers transacting at speed.
  3. Business model = UX outcome.
    Pricing and matching logic decisions are UX decisions. The structure of value capture shapes how people behave on the platform.
← Back to all work
02 · Bell the Bull · AI Safety Intelligence for K–12 Schools

Designing a system for earlier, smarter student safety intervention.

Not faster reporting. Better detection. Bell the Bull is an AI-powered safety intelligence concept built for K–12 schools, designed to identify risk earlier and guide structured intervention before situations escalate.

Role
UX Lead · End-to-end
Team
7 people
ARR potential
~$18M
NPV projected
~$24M
Sector
K–12 EdTech
i. The problem

Schools don't lack reporting. They lack early detection.

Most incidents, bullying, abuse, emotional distress, are caught late. Sometimes too late.

Because current systems depend on:

  • Students speaking up
  • Teachers noticing patterns
  • Fragmented signals across platforms

That rarely works.

ii. Why this matters

This isn't a UX problem. It's a governance problem.

Delayed detection leads to:

  • Escalation before intervention
  • Inconsistent response across staff
  • Increased administrative burden

And for schools:

  • Regulatory risk
  • Reputational damage
  • Breakdown of trust
Safety systems shouldn't react.
They should anticipate.
iii. My role

Led the initiative end-to-end.

  • Defined UX strategy and system architecture
  • Aligned Product, Engineering, and Legal
  • Built the business case and presented to leadership
  • Drove governance and escalation design
3
UX Designers
2
UX Writers
1
Researcher
1
PM
What I led

The whole concept, end-to-end.

  • UX strategy and system architecture
  • Alignment across Product, Engineering, and Legal
  • Business case + leadership presentation
  • Governance and escalation design
  • Detection-first reframing of the problem
What I executed

Hands-on through the critical paths.

  • Severity model and classification logic
  • Escalation flow wireframes
  • AI explainability spec with engineering
  • Microcopy direction with writers (alerts → actions)
  • Hackathon demo design and pitch deck
Key decisions I drove

Four early decisions shaped everything.

Not a reporting tool
A detection and governance system. The framing change ruled out half the obvious feature set.
AI supports decisions. It doesn't replace them.
Human validation is always part of the flow. No auto-escalation without a person in the loop.
Severity must be structured
Not all incidents are equal. → Mild / Moderate / Chronic. Classification drives routing.
Escalation must be system-led
Not dependent on individual judgment. Consistency across schools, staff, and shifts.
iv. Approach

Start with friction. Not features.

I studied:

  • Incident reporting workflows
  • Delay points in intervention
  • Behavioral signal patterns

Then reframed the problem:

From "incident reporting"
To "early detection + guided intervention"

I worked across teams to align on one core tension:

Detection sensitivity vs false positives. Too sensitive → noise. Too strict → missed signals.

We defined thresholds. And built human override into the system.

v. Solution

An AI-assisted safety intelligence layer embedded into the SIS.

The system flow

Standby → Detection → Classification → Validation → Escalation

Simple on paper. Complex in execution.

What powers it

  • AI voice pattern analysis
  • NLP-based cyberbullying detection
  • Behavioral signal aggregation
  • Severity-based classification

What enables action

  • Role-based escalation (teacher, counselor, admin)
  • Geofenced routing logic
  • Audit trails for compliance
  • Structured intervention workflows

What users see

  • Risk detection dashboard
  • Prioritized alerts
  • Incident timelines
  • Recommended actions

The point

This wasn't about adding features. It was about building a system schools could trust.

vi. Impact

Modeled against Bark and GoGuardian benchmarks.

30–50%
Earlier detection
Reduces time-to-signal for emerging incidents.
40–60%
Faster escalation
System-routed paths cut hand-off delay between staff.
20–35%
More reporting consistency
Structured classification reduces under- and over-reporting variance.
30–45%
Reduced response time
From first signal to first action across the workflow.
~$18M
ARR potential
Across the K–12 SIS market envelope at modeled penetration.
~$24M
Projected NPV
Including platform synergies and retention lift across the install base.

But the real impact?

→ Schools act earlier.

→ Staff respond consistently.

→ Students fall through fewer gaps.

vii. What changed

Before → After.

Before

  • Manual observation
  • Delayed reporting
  • Inconsistent escalation
  • Fragmented communication

After

  • AI-assisted detection
  • Structured classification
  • Guided escalation
  • Unified visibility across stakeholders
viii. Iterations

We didn't get it right in one pass.

i
Alert sensitivity

Reduced noise without missing signals. Threshold tuning across cohorts.

ii
Severity model

Refined classification to match real-world scenarios. Mild / Moderate / Chronic.

iii
Escalation logic

Balanced automation with human control. Override always one click away.

iv
Messaging clarity

From vague alerts → actionable prompts.

x. Reflection

Designing for safety is different.

You're not optimizing convenience. You're managing risk.

  1. Trust is everything.
    If users don't trust the system, they won't act on it. Detection without trust is just noise.
  2. AI needs boundaries.
    Detection is powerful, but must remain accountable. Explainability isn't optional in safety contexts.

This project shifted how I think about UX. From designing interfaces → to designing systems that shape decisions.

xi. Outcome

Three signals the work landed.

SLT-approved
Innovation concept
Greenlit by senior leadership as a strategic platform direction.
Engineering-validated
Technical feasibility
Engineering confirmed the system architecture and AI thresholds are buildable.
1st place
Hackathon + People's Choice
Won both the jury vote and the room.
← Back to all work
03 · Acme Analytics · AI-Driven Cybersecurity Platform

Turning security noise into decision-ready intelligence.

An AI-driven enterprise security and performance intelligence platform that helps organizations detect risks, monitor user behavior, and optimize system performance at scale. From monitoring system → to decision intelligence system.

Role
UX Strategy Lead
Team
10 people
MTTR impact
90% faster
Alert noise
35–50% ↓
Sector
Enterprise Security
i. The problem

Security teams don't lack data. They're drowning in it.

Thousands of alerts. Every day. Most of them irrelevant.

Analysts were stuck:

  • Chasing false positives
  • Switching between fragmented views
  • Missing real threats buried in noise

Clarity wasn't the issue. Signal was.

ii. Why this matters

When signal is weak, response is slow.

And in cybersecurity, slow is expensive. This created real business risk:

  • Delayed threat response (high MTTR)
  • Missed anomalies across systems
  • Analyst burnout and attrition
  • Growing SLA pressure from enterprise clients
The platform wasn't failing.
It just wasn't helping decisions.
iii. My role

Led UX strategy for the platform.

This wasn't just a redesign. It was a reframing of how security decisions happen.

2
UX Designers
1
UX Writer
1
UX Researcher
1
PM
5
Engineers
Me
Project Lead
What I led

Direction and decisions.

  • Managed a multidisciplinary team across design, writing, research
  • Partnered with Product and Engineering on roadmap direction
  • Defined experience architecture and AI explainability models
  • Reframing of monitoring → decision intelligence
  • AI governance: explainability + confidence thresholds
What I executed

Hands-on in Figma where it mattered.

  • Critical workflow design (threat dashboard, alert grouping)
  • Severity model wireframes and prototypes
  • Design reviews and quality gating
  • Microcopy direction with the writer
  • Spec hand-offs with engineering
Key decisions I drove

Four hard calls, early.

Prioritize signal over completeness
Not all data deserves equal visibility. Ranking is the product.
Design for decision speed, not exploration
Analysts don't browse. They act. The UI should respect that.
Make AI explainable by default
Every alert shows confidence level, reason for flagging, severity context.
Group before you show
Raw logs → clustered incidents → actionable alerts. Aggregation is the workflow.
iv. Approach

Start with the analyst's mental model. Not the system's data model.

Through research, we identified how analysts actually think:

  • Risk score, How bad is this?
  • Threat alerts, What needs attention now?
  • Behavioral trends, Is this pattern new or recurring?
  • Predictive risk, What's likely to happen next?

This became the foundation of the experience.

We also studied:

  • Alert fatigue patterns
  • Triage workflows
  • Breakdowns in escalation

Then simplified the system around one goal: Faster, more confident decisions.

v. Solution

An AI-driven analytics layer that transforms raw logs into prioritized intelligence.

What the system does

  • Aggregates data across users, devices, apps, networks
  • Builds behavioral profiles using machine learning
  • Detects anomalies and assigns risk scores
  • Suppresses redundant alerts
  • Groups related events into single incidents

What users see

  • Unified threat dashboard
  • Severity-based alert grouping
  • Risk score indicators with confidence levels
  • Drill-down views for investigation
  • Clear, action-oriented labels

No more scanning logs.

Just decisions.

vi. Impact

Measured against MTTD and MTTR benchmarks.

90%
Faster threat response time
Reduced MTTR through ML-grouped incidents and prioritized routing.
35–50%
Reduction in alert noise
Suppression rules and clustering removed redundant signals.
25–40%
Increase in analyst productivity
Less context-switching. More incidents handled per analyst.
20–30%
Reduction in false positives
Explainability + confidence thresholds tuned classifier outputs.

Operationally:

→ Analysts handled more incidents with less effort.

→ Critical threats surfaced earlier.

→ Decision time dropped significantly.

vii. What changed

From noise → signal.

Before

  • Raw logs across multiple systems
  • High alert duplication
  • No clear prioritization
  • Slow, manual triage

After

  • AI-grouped incidents
  • Risk-based prioritization
  • Clear severity indicators
  • Faster, structured response

From monitoring → action.

viii. Iterations

We refined aggressively.

i
Alert grouping logic

Early versions over-clustered → reduced visibility. Tuned ML thresholds.

ii
Risk scoring clarity

Users didn't trust scores initially. Added explainability + contributing factors.

iii
Dashboard density

Too much data upfront. Moved to progressive disclosure.

iv
Language and labeling

Reduced technical jargon. Clear, action-driven microcopy.

x. Reflection

In complex systems, more data doesn't help.

Better decisions do.

Career timeline

Eighteen years. One throughline.

Fixing clarity in enterprise systems. The role keeps changing. The work doesn't.

2007, 2010 · Foundation
Technical writing, enterprise documentation
Early years writing enterprise documentation. Learned that most user struggles aren't design problems, they're clarity problems.
2010, 2015 · Expansion
Senior IC across SaaS, FinTech, Healthcare
Worked across regulated industries. Learned how systems break at scale. Started moving from writing about products to shaping how they work.
2015, 2020 · Leadership
First UX/Content leadership roles
Stepped into team leadership. Built review systems, design intake models, content standards. First time the unglamorous infrastructure work compounded.
2020, 2023 · Strategy
PowerSchool · EdTech at scale
UX governance across 40+ products. Restructured roles, introduced review cycles, tied UX to outcomes. Delivered the 57% support call reduction and 30% rework cut.
2024, PRESENT · Direction
UX Leadership · AI-assisted workflows
Designing AI-assisted enterprise workflows. 15–24% productivity gains through intelligent task flows. Coaching the next layer of leaders.
How I work

The stack behind the work.

Tools, certifications, and contexts, the working surface.

Tools
Figma FigJam Dovetail Confluence Miro Notion Jira Linear
Workflow-first. Tools serve the system, not the other way around.
Certifications
  • UX Strategy · Nielsen Norman Group
  • Information Architecture · NNg
  • Content Design · UX Writing Hub
  • Leadership · Reforge / cohort-based
Updating with detailed list, placeholder for now.
Domain footprint
SaaS
15+ products
EdTech
PowerSchool, K–12
FinTech
Regulated flows
Healthcare
Staffing, clinical UX
Enterprise Software
Multi-product orgs, governance, internal platforms
Geographies
Bangalore, India
Home base · IST
United States
PST/EST distributed teams
Europe
CET partners and clients
Asia-Pacific
SG, AU stakeholder networks