Skip to content
Available for new opportunities

UX Designer Who Builds Trust.

5 years designing complex systems — healthcare AI, enterprise platforms, and design systems — where clarity, trust, and human judgment are non-negotiable.

5+
YRS EXP
E2E
PROCESS
92%
AI TRUST
4.2×
ROI
Shaik Shekath Ali headshot photo

Shaik Shekath Ali

I'm a UX / Product Designer with 5 years of experience working on complex, high-stakes products where design decisions carry real consequences — clinical workflows, enterprise systems, and AI interfaces.

My approach starts with understanding the system before touching the interface. I map stakeholder needs, audit existing workflows, and find the moments where friction creates the most damage — then design the minimum intervention that creates the maximum clarity.

I'm comfortable navigating ambiguity, constraints, and competing priorities. Whether working with clinicians, engineers, or executives, I translate complexity into decisions that stick.

UX Research Product Strategy Figma Design Systems Healthcare UX AI Interfaces IA (Information Architecture) Prototyping Usability Testing Stakeholder Alignment WCAG 2.1 Compliance Interaction Design
Experience 5+ years
Domains Healthcare, Enterprise, AI
Process End-to-end
Location Hyderabad, India
Remote Open to remote

Selected Work

Healthcare AI · End-to-End UX · 2025

HIP One: Designing for Trust in Healthcare AI

Transforming fragmented medical reviews into a unified, HIPAA-compliant decision workflow — where AI accelerates the work, but humans remain accountable for every outcome.

40%
FASTER REVIEW
65%
ERROR REDUCTION
92%
AI TRUST SCORE
4.2×
FIRST-YEAR ROI
Process
The Delays
Manual PDF and fax-based reviews with zero automation. Teams spent hours per case, extending turnaround times for critical clinical decisions.
System
The Errors
Disconnected tools for review, analytics, and compliance created silos and duplicate work. Manual data entry dramatically increased error rates.
Human
The Burnout
High cognitive load and overwhelming audit requirements led reviewers to distrust AI — creating resistance to adoption and costly manual overrides.
The UX challenge: Design a single system that supports high-stakes decisions, AI transparency, and enterprise scalability — without overwhelming the humans responsible for each outcome.
Hyperscience
High-accuracy OCR
Gives data, not decisions. No native clinical decision support or RBAC.
Rossum
Invoice Processing
Built for finance, not healthcare. Weak domain modeling, no audit-ready UX.
Nanonets
Custom ML Models
Developer-first, not reviewer-first. No role-based or audit-trail UX.
01 / INTERVIEWS

Stakeholder Interviews

Aligning regulatory non-negotiables and compliance requirements before any design work begins.

Limited access: clinician time is scarce
02 / INQUIRY

Contextual Inquiry

Shadowing manual PDF and EHR workflows in real clinical environments to understand true pain points.

Embedded legacy: deeply ingrained daily routines
03 / MAPPING

Artifact Mapping

Analyzing legacy spreadsheets and forms used daily to capture hidden workflow logic.

High confidentiality: strict HIPAA restrictions
04 / VALIDATION

Early Validation

Testing information architecture with real clinicians before any high-fidelity work.

AI skepticism: high distrust of automation
Medical Reviewer

Nurse / Clinician

Goal: Accurate, fast decisions — Confidence and personal accountability

"I need to quickly understand patient context and risks, so I can make a defensible decision without missing critical details."
Operations Manager

Ops Lead

Goal: Throughput and SLA compliance — Predictability and bottleneck visibility

"I need visibility into task status, so I can meet SLAs and avoid escalations before they become crises."
Quality Analyst

QA Specialist

Goal: Maintain STAR ratings — Proactive risk insight and audit readiness

"I need early signals of risk, so we can intervene before performance drops affect our compliance ratings."
Problem

Extraction is not Understanding

Users scan more than read. Large datasets overwhelm. Information without context is noise.

Design Response

Progressive Disclosure

Show summaries first. Apply Gestalt principles to guide hierarchy. Reveal complexity on demand.

Problem

Low AI Trust

Reviewers distrust "black box" decisions. In healthcare, errors carry irreversible, personal consequences.

Design Response

Explainable AI

AI suggests, humans decide. Confidence scores and source evidence always visible before any action is taken.

Problem

Compliance Anxiety

Fear of missing critical documentation during audits paralyzes reviewers mid-task.

Design Response

Invisible Compliance

Built-in confirmations and error prevention. HIPAA compliance runs silently in the background — always present, never blocking.

Above the Surface — User Experience

Frictionless task routing between roles
Clean, focused interfaces per role
One-click action confirmations
Progressive disclosure of AI confidence levels

Below the Surface — Compliance Engine

RBAC: Granular permissions restrict PHI access invisibly
Audit Trail: Every decision, timestamp, and user ID logged automatically
HIPAA: Secure data handling running constantly in background
Error Prevention: Mandatory validation before pipeline entry
Execution 01

Reviewer Dashboard

Left-aligned progressive filtering by Priority, Type, and Status. High-contrast status indicators provide immediate visual hierarchy. Clear primary actions tied directly to SLA-driven workflows. Reduces cognitive load through instant workload clarity.

Execution 02

Document Intake and Task Management

Drag-and-drop upload with real-time file validation prevents incomplete submissions. Mandatory metadata capture enforced before any task enters the pipeline. Clear inline visual feedback on upload success and format compatibility.

Execution 03

AI-Assisted Medical Review

The "Examine and Update" architecture juxtaposes the source document alongside the AI decision panel — eliminating tab-switching. AI-extracted answers are visually distinct from manual inputs. Mandatory human confirmation required for all AI outputs.

Execution 04

Explainable AI Summary View

AI accuracy metrics and field extraction confidence levels grouped upfront before review begins. Visual indicators flag low-confidence extractions. A targeted validation tab prevents blind trust in automation results.

Dashboard
Review List
Examine and Update
Document Management
Medicare Analytics
IA Principle 01

Role-Based — Users only see features relevant to their permissions level.

IA Principle 02

Task-Oriented — Navigation follows natural clinical workflow sequences.

40%
FASTER TURNAROUND for medical review completion
65%
ERROR REDUCTION in manual data entry tasks
92%
AI TRUST SCORE — reviewer confidence in AI workflows
4.2×
RETURN ON INVESTMENT in the first year
Reduced reviewer burnout through role-based, focused interfaces
Eliminated tool fragmentation — 5 legacy systems replaced by one
100% audit-ready compliance built into every workflow step
Design Systems · Product Architecture · Governance · 2024

Architecting Scale: A Playbook for Product Design and Governance

A comprehensive framework for scaling enterprise product design — covering governance, component architecture for personalization, and translating UX into measurable business outcomes.

Governance layers 3
Modernization steps 4
Duplicate patterns 0
Design language Unified
Core thesis: Great design systems are behavioral, not just visual. True scalability is achieved when systems, optimization, and alignment operate as a single continuous loop.
PILLAR 01

Craft and Governance

Solving visual and behavioral inconsistency through centralized systems, strict semantic versioning, and continuous auditing workflows that prevent future decay.

PILLAR 02

Product Optimization

Balancing cognitive load and performance through progressive disclosure, logical hierarchy, and role-based personalization at the component architecture level.

PILLAR 03

Leadership and Impact

Translating UX into business outcomes, bridging engineering constraints, and navigating feature evolution — speaking the language of stakeholders, not just designers.

Governance enables

Robust product architecture — modular systems and cross-platform tokens ensure consistency.

Architecture frees time for

Managerial leadership — solving complex, dynamic, role-based workflows at scale.

Leadership feeds back into

Governance and craft — aligning stakeholders, navigating constraints, focusing on business impact.

Figma library with version-controlled components, design tokens, interaction patterns, and accessibility guidelines. The single source of truth for all product teams across the organization.
Reduces duplicate patterns. Collaboration rituals including design reviews, component approval workflows, and weekly PM/Dev syncs. Prevents behavioral drift before it becomes technical debt.
Monitoring adoption through usage tracking. The goal: behavioral consistency so users experience the product as one unified system regardless of which team built the feature.
STEP 01

Discovery

  • Audit components
  • Identify duplicates
  • Analyze spacing
STEP 02

Prioritization

  • Usability impact
  • Accessibility depth
  • Tech debt triage
STEP 03

Restructuring

  • Consolidate elements
  • Standardize tokens
  • Write instructions
STEP 04

Governance

  • Define guidelines
  • Build approval loops
  • Track library adoption
Key insight: Success depends less on redesigning components and more on driving adoption across teams. Governance is a product problem, not a design one.

Top Layer — Contextual Overlays

Adapts to user role, data state, permissions, and preferences. Dynamic cards and context-aware notifications that flex without breaking system logic.

Middle Layer — Shared Patterns

Component behaviors and content hierarchy rules. The behavioral contract between the design system and all product teams.

Base Layer — Tokens and Layout

Structural constraints, spacing, and layout rules. Ensures visual stability across all permutations and screen sizes.

Personalization must feel intentional, not visually chaotic. Flexible architecture allows screens to adapt without breaking system logic.
Dimension Admin Manager End-User
Focus Configuration and Governance Team Oversight and Approvals Task Completion and Productivity
Flow Permission mapping, system setup Reporting tutorials, workflow routing Progressive feature discovery, avoiding Day-1 overload
Defaults Administrative dashboards Team metric views Active task queues
UX Strategy

Progressive Disclosure

Reveal information step-by-step to reduce cognitive overload. Improves comprehension, simplifies decision-making, and increases task completion rates.

Applied to: Multi-step onboarding flows, complex form inputs, dashboard drill-downs.

Step 1
Step 2 ●
Step 3
Research Method

The Friction Diagnostic Loop

Map the user flow to measure completion rates, exit points, time spent, and error frequency — finding the exact step where behavioral friction occurs.

Phase 1 — Identify (The Funnel)

  • Map completion rates at each step
  • Identify exit points and drop-off moments
  • Measure time spent on each action
  • Track error frequency and recovery paths

Phase 2 — Diagnose (The Loop)

  • Session recordings and heatmap analysis
  • User interviews and usability testing
  • Evaluate cognitive load and form complexity
  • Assess trust issues and performance delays
Key insight: In onboarding, friction spikes at permission requests or complex fields. Minor UX tweaks at these moments exponentially drive conversion.
Good UX is not about reducing steps blindly — it is about reducing cognitive effort. Leadership in design means translating craft decisions into business language that stakeholders can act on.
LESSON 01

Translating UX to Business

Avoid UX jargon. Translate "cognitive overload" into "increased drop-offs and support costs." Frame all design decisions around conversion, retention, and revenue. Speak the language of decisions, not design.

LESSON 02

Bridging Engineering and PM

Clarify constraints openly and prioritize impact vs. effort. Propose phased MVP rollouts and iterative compromises when ideal UX is not immediately feasible. The best design that ships beats the perfect design that does not.

LESSON 03

Owning Post-Launch Failures

When a simplified workflow failed because contextual guidance was removed, we did not defend the design. We analyzed behavior data and reintroduced cues. Iteration and accountability, not defensiveness.

Design System Role

Treated as a Shipped Product

Semantic versioning, backward compatibility, release notes, deprecation strategies, and migration documentation.

Adoption Strategy

Behavioral, Not Just Visual

Success is measured by team adoption rates and behavioral consistency — not by how beautiful the component library looks.

Impact Measurement

Conversion, Retention, Revenue

Every design decision traced to a business metric. No "nice to have" — only "what problem does this solve and how do we measure it."

Banking · B2B SaaS · User Agent App · Redesign · 2022

VAM: Redesigning the Legacy Bank User Agent Application

End-to-end redesign of a fragmented, outdated bank user agent management platform — transforming a tool that frustrated frontline staff into a streamlined, intuitive system for managing customer accounts, policies, and transactions.

Project type Redesign
My role Lead UX Designer
Framework used Double Diamond
Outcome Shipped
The challenge: Bank agents relied on a legacy desktop application riddled with navigation inconsistencies, redundant flows, and zero feedback mechanisms — causing delays in serving customers and frequent escalations to supervisors.
Context

What is VAM?

A B2B SaaS platform used by bank user agents to manage customer accounts, process policy updates, handle transactions, and resolve service requests — all from a single interface used daily by frontline staff.

Why Redesign?

Platform had Decayed

The existing system was built on outdated UI patterns with no design system, inconsistent interactions across modules, and no alignment between agent workflows and the software's information architecture.

My Contribution

End-to-End Ownership

Led the complete UX redesign — from discovery research and journey mapping to interaction design, prototyping, and final delivery. Collaborated with product managers and engineering leads throughout.

Goal 02

Support All Workflows in One App

Consolidate account management, policy handling, and transaction processing into a single, coherent information architecture.

Goal 03

Build a Scalable Design System

Establish reusable components and design patterns that the engineering team can extend as new features are added to the platform.

PHASE 01

Discover

Contextual interviews with bank agents, observation of daily workflows, competitive analysis of banking platforms.

PHASE 02

Define

Persona creation, journey mapping, pain point synthesis, KPI definition and project goal alignment.

PHASE 03

Develop

Information architecture, wireframing, user flows, component library creation, and iterative prototyping.

PHASE 04

Deliver

High-fidelity mockups, design system handoff, usability testing, dev collaboration, and shipped product.

🔍
Structured research process followed. Discovery began by shadowing bank agents during live sessions to understand how the legacy application was actually used — not just how it was intended to be used. The gap was significant.
Research Method 01

Contextual Interviews

Conducted structured interviews with frontline bank agents across multiple branches. Focused on task frequency, pain points with current software, workarounds they had developed, and unmet needs that caused daily friction.

Research Method 02

Workflow Observation

Observed agents in live customer service scenarios. Mapped the actual steps taken versus the system's intended flow — surfacing navigation dead-ends, redundant screens, and missing feedback states.

Analysed comparable banking agent platforms including Temenos, Salesforce Financial Services Cloud, and SAP Banking. Key insight: successful platforms prioritise task-oriented navigation over feature-grouped navigation — the opposite of what VAM currently used.
Finding 01

Navigation Overload

Agents navigated an average of 7 screens to complete tasks that should require 2–3. The menu structure was organised by system logic, not agent workflow.

Finding 02

No System Feedback

The legacy system provided no confirmation states, loading indicators, or error explanations. Agents frequently repeated actions unsure whether they had succeeded.

Finding 03

User Efficiency Blockers

Inconsistent table layouts, non-standard date pickers, and unlabelled icon buttons created a steep learning curve even for experienced agents.

Operational Pain

Slow, Fragmented Workflows

Policy updates, account lookups, and transaction processing each lived in separate modules with no cross-linking — forcing agents to memorise navigation paths and lose context when switching tasks.

Trust and Confidence

Agents Did Not Trust the System

Without success confirmations or inline validation, agents regularly escalated to supervisors to verify actions — creating bottlenecks and undermining confidence in the tool entirely.

User Persona 01

Priya S.

Senior Bank Agent · 3 years experience · High volume daily transactions

"I know what I need to do, but the system makes me take 10 steps to do what should take 2. Every delay frustrates the customer waiting in front of me."
User Persona 02

Ravi M.

New Bank Agent · 6 months experience · Still learning workflows

"I can barely navigate the system on my own. I'm always asking colleagues where to find things — it's embarrassing in front of customers."
User Persona 03

Ananya P.

Branch Manager · Oversight and approvals · Concerned with compliance

"I spend too much time verifying actions my team should be able to handle independently. The system gives them no confidence."
Stage Login Search Customer View Account Update Policy Confirm Action
Actions Enter credentials, navigate to module Use search bar across 3 possible entry points Parse dense table to locate account Navigate 5 sub-screens to locate field No confirmation shown — repeat action
Pain Level Low Medium High Critical Critical
Feeling Neutral Mildly frustrated Confused, scanning Frustrated, lost Anxious, uncertain
KPI 01

Reduce Average Task Completion

Target: Cut average steps per task from 7 to 3. Measured through usability testing session recordings and time-on-task analysis.

KPI 02

Increase Agent Confidence Score

Target: Improve self-reported confidence with the system from 2.1/5 to above 4/5. Measured through post-session SUS surveys.

KPI 03

Reduce Supervisor Escalations

Target: Reduce task-related escalations to supervisors by 60%. Measured through operational logs before and after launch.

Problem

Feature-grouped navigation

System organised by module logic, not agent workflow — forcing mental mapping at every step.

Design Decision

Task-oriented navigation

Restructured IA around the most frequent agent tasks. Primary nav reflects jobs-to-be-done, not system modules.

Problem

No system feedback or confirmation

Agents had no way to know if their actions succeeded, pending, or failed.

Design Decision

Persistent status visibility

Every action now produces an inline status response. Toast notifications, confirmation dialogs, and real-time form validation built into every flow.

Problem

Steep learning curve for new agents

Unlabelled icons, inconsistent patterns, and zero onboarding created a hostile first-use experience.

Design Decision

Progressive disclosure and labelled UI

All interactive elements labelled. Contextual help text added to complex fields. Complex tasks broken into guided, stepped flows.

Graphical Structure Workshops — War-Room Canvas Experience. Ran cross-functional whiteboard workshops with product managers, engineers, and agent representatives. Used physical card sorting and affinity mapping to validate the new information architecture before any digital wireframing began.

Primary Navigation — Task-Oriented

Dashboard, Customer Search, Account Management, Policy Updates, Transactions, Reports. Organised by agent job-to-be-done, not system modules.

Contextual Actions — Inline and Accessible

Quick actions surfaced directly on customer records. No more navigating to a separate module to update a policy or process a transaction.

Feedback Layer — Always Visible

System status always communicated. Success confirmations, error explanations, loading states, and validation messages present at every decision point.

Wireframe Phase

Low-Fidelity Iteration

Produced rapid lo-fi wireframes for all core flows: customer search and account view, policy update flow, transaction processing, and the dashboard summary. Tested with agents before investing in high-fidelity.

Prototype Testing

Usability Sessions with Agents

Ran 3 rounds of usability testing with 5 bank agents each. Used task-based scenarios reflecting real work conditions. Iterated on navigation labels, action placement, and form field ordering based on findings.

Data tables with sorting and filtering, form elements with validation states, status badges, action menus, confirmation modals, and notification toasts — all designed with consistent sizing, spacing, and behaviour rules.
Defined colour, typography, spacing, and elevation tokens that map directly to CSS variables — giving engineering a single source of truth that prevents visual drift as the platform evolves.
Documented interaction patterns for the most complex flows: multi-step policy update, bulk transaction processing, customer account drill-down, and exception handling — with annotated specs for each state.
Desktop-first final designs shipped. The redesigned VAM application introduced a clean dashboard-first experience, a global customer search bar accessible from every screen, task-grouped navigation, and inline feedback at every action point.
Screen 01

Agent Dashboard

At-a-glance overview of pending tasks, recent customer interactions, performance metrics (daily transactions processed, open cases), and quick-access shortcuts to the most frequent workflows.

Screen 02

Customer Account View

Consolidated single-page view of all customer data — account summary, policy status, transaction history, and open cases — eliminating the need to navigate between modules for a complete customer picture.

Screen 03

Policy Update Flow

Stepped guided flow reduced from 7 screens to 3. Each step shows only relevant fields, with inline validation, clear progress indication, and a review-and-confirm final step before any change is submitted.

Screen 04

Transaction Management

Redesigned transaction table with advanced filtering, sortable columns, status indicators, and bulk action support. Confirmation dialogs added for all irreversible operations.

57%
REDUCTION IN STEPS per average agent task
4.3/5
AGENT CONFIDENCE SCORE post-launch (up from 2.1)
63%
FEWER ESCALATIONS to supervisors for task help
90%
TASK SUCCESS RATE in final usability testing sessions
Shipped complete design system with 40+ documented components
New agent onboarding time reduced from 3 weeks to under 1 week
Zero critical usability issues found in final QA round before launch

How I Work

01 / 05
🔍

Discover

  • Stakeholder interviews
  • Contextual shadowing
  • Artifact analysis
  • Competitive audits
02 / 05
🗺

Define

  • Synthesis & insights
  • Persona creation
  • Journey mapping
  • KPI definition
03 / 05

Design

  • IA & wireframing
  • High-fidelity mockups
  • Design system tokens
  • Interactive prototyping
04 / 05
🧪

Validate

  • Usability testing
  • Clinical walkthroughs
  • Friction diagnostics
  • Design QA audits
05 / 05
🚀

Deliver

  • Developer handoff
  • Implementation syncs
  • Impact monitoring
  • System governance

Let's work together.

Open to full-time UX and product design roles, contract engagements, and consulting for complex design challenges. Especially interested in healthcare, enterprise, and AI products where the stakes are high and clarity matters most.

I work best with teams that value research, move with intention, and care about the humans using what they build.

in
LinkedIn
shaik-shekath-ali-b8a45352
Connect →

Open to Work

Looking for a designer who brings both craft and strategic thinking — who can navigate regulated domains, complex systems, and human-critical products without losing sight of the user.

Available now — Hyderabad, India — Open to remote
Full-time roles Contract Consulting Healthcare UX Enterprise design
Email copied to clipboard!