Enterprise UX · B2B SaaS · Oil & Gas

Bibaswan

I design enterprise systems
that people actually use.

Senior UX Designer specialising in complex B2B SaaS — reducing friction, driving adoption, and closing the gap between what products promise and how people actually work.

View work hello@bibaswan.works
+67%
Product adoption increase
Enterprise workspace redesign for geoscience operations — 3,000+ users onboarded within 6 months of launch.
21→3
Clicks to complete core task
Workflow simplification that directly unblocked cloud migration for a mission-critical platform.
+80%
User satisfaction increase
Measured post-launch via structured usability validation with domain experts and geoscientists.
Enterprise UX· Workflow Simplification· B2B SaaS· Design Strategy· Interaction Design· Figma· Framer· User Research· Information Architecture· Design Systems· Enterprise UX· Workflow Simplification· B2B SaaS· Design Strategy· Interaction Design· Figma· Framer· User Research· Information Architecture· Design Systems·
Enterprise products fail not because of bad design — but because complexity is never confronted.
Oil & Gas / Geoscience SaaS
Mission-critical workflow design
Adoption-driven UX strategy
Cross-functional design leadership
Visiting Faculty · UX Design
Selected Work

Projects that
moved the needle

03
01 — Featured
Oil & Gas · Enterprise SaaS

Reducing Enterprise
Workspace Friction
by 67%

Redesigned a mission-critical geoscience workspace to unblock cloud migration — reducing core task completion from 21 clicks to 3.

+67%
Product Adoption · 3,000+ users onboarded
02
Healthcare · Pathology
NDA

100% Team Adoption in 2 Weeks

End-to-end redesign of a clinical reporting tool — from zero engagement to full team adoption through targeted workflow intervention.

100%
Pathology team adoption rate
03
Enterprise SaaS
NDA

Design System for Complex Domain Workflows

Scalable component library and design language for a multi-product enterprise platform serving domain experts across global teams.

4×
Design-to-dev handoff speed
How I work

Outcomes over outputs.
Always.

01
Understand the domain

Enterprise work fails when designers don't understand what users actually do. I embed in the domain before touching a screen.

02
Map the friction

I find where workflows break — not where they look broken. Click depth, cognitive load, and task failure are the real diagnostics.

03
Design the decision

Every screen is a decision point. I design for the choice users need to make — not the feature the team wanted to ship.

04
Validate and measure

Design is a hypothesis. I test it, instrument it, and hold myself to the outcome — not the deliverable.

From people I've worked with

What they say

His work is impeccable and has the rare quality of simplicity.

Rashmi Mishra
Technology Leader · Ex VP Thoughtworks, UST & PierianDx

His design solutions consistently drove stakeholder confidence and accelerated project momentum.

Dhiraj Shelke
Senior UX Designer · SLB

Bibaswan is one of the most extraordinarily talented people I have worked with.

Shishir Kanthi
Vice President · JP Morgan Chase & Co.

Have a complex workflow
that needs untangling?

Let's talk
Case Study · 01

Reducing Enterprise
Workspace Friction
by 67%

Domain
Oil & Gas · Geoscience SaaS
Timeline
24 months
My role
Lead UX Designer
Team
Product, Design, Engineering, SMEs

Redesigned a mission-critical geoscience workspace to unblock cloud migration — by confronting 21-click complexity and rebuilding around how geologists actually work.

+67%
Active product adoption
21→3
Clicks for core task
+80%
User satisfaction
3K+
New users in 6 months
The Problem

Users were losing time before work even started

Enterprise users — geologists, geophysicists, and technical operators — needed a faster and clearer way to discover applications, resume recent work, view updates, and monitor product status. But the existing workspace experience was fragmented, forcing users to rely on manual search, repeated navigation, and disconnected tools just to begin everyday tasks.

The business consequence was direct: users were hesitant to adopt the cloud workspace because the experience created friction in daily workflows — too many steps before they could start work, weak visibility of recent projects, fragmented application access, and unclear system status.

"I spend more time navigating than actually working. By the time I get to the data, I've already lost my train of thought."

Cloud infrastructure was ready. Adoption wasn't. The gap was entirely in the user experience — and it was measurable: 21 clicks to complete a core task that should have taken 3.

My Role

What I owned —
and what I fought for.

I led end-to-end UX strategy for the workspace redesign — owning research direction, design principles, prioritisation calls, and validation. I also owned the hardest conversation: convincing engineering to simplify the underlying interaction model, not just rearrange the surface UI.

The 24-month timeline reflects the reality of enterprise B2B: stakeholder alignment, legacy dependency mapping, phased rollouts, and iteration on real usage data. The design took 4 months. Getting it built and shipped correctly took the rest.

The hard part

The temptation was to rearrange the existing structure — make it look cleaner without changing the underlying model. I pushed back hard against this. The problem wasn't visual; it was architectural. We ran a cross-functional workshop with Engineering to map which interaction layers could be collapsed. That conversation was uncomfortable, and it took three rounds to reach alignment. It was also the decision that made 21→3 clicks possible. A cosmetic fix would have got us to 21→14 at best.

Sneak peak —
Before and After.

Before
After
Before: settings-heavy, fragmented navigation · After: work-first, unified workspace
User Research

Starting with listening — not assumptions

My process started with listening to users and understanding how they moved across tools, projects, and cloud workflows. To understand why users were facing friction, I studied how geologists, geophysicists, and enterprise users moved from login to actual work — analyzing the workspace not just as a dashboard, but as a daily productivity environment.

Listen and think

The research focused on four areas: how users accessed applications, how they resumed recent projects, how they understood cloud-session status, and where they lost time in the workflow.

40
User Interviews
1:1 sessions with geologists, geophysicists, and enterprise cloud users to map needs and workflow friction.
3
Workflow Walkthroughs
Mapped login, app launch, and recent work access — tracking every decision point users encountered.
5
UX Audit Areas
Identified navigation, visibility, and trust issues across the existing workspace experience.
21→3
Click Reduction Target
Usage and support ticket analysis revealed the quantifiable opportunity to simplify core workflows.

Interview Methods

I conducted feedback synthesis from 40 professional geologists and geophysicists — combining 1:1 interviews, workflow walkthroughs, support-ticket analysis, contextual inquiry, and review of product usage data. I collaborated closely with internal domain experts throughout.

Research Method Scale Purpose
User Interviews 40 users Understood user needs and workflow friction
Workflow Walkthroughs 3 core workflows Mapped login, app launch, and recent work access
UX Audit 5 friction areas Identified navigation, visibility, and trust issues
Usage & Support Analysis 21 → 3 clicks Found opportunities to reduce workflow effort
UX Audit

Five major friction areas — all measurable

I audited the existing workspace experience across navigation, app access, recent work visibility, system feedback, and user confidence. The audit surfaced five critical failure points — not aesthetic issues, but structural problems in how the workspace communicated and responded to users.

Heuristic Evaluation Finding
Visibility of System Status ✗ Fail Navigation unclear. App does not communicate well with the user — information is present but not discoverable.
User Control & Flexibility ✗ Fail User feels no sense of control. No customisations available — no ability to prioritise or personalise workflow.
Learnability ✓ Pass Terminology is fair but improvable. Basic task completion is possible for experienced users with patience.
Error Control ✗ Fail No provision for error recovery or help documentation. Edge cases produce dead ends with no guidance.
Operability ✗ Fail Inconsistent app behaviour, no rapid response feedback, no option to save defaults. Critical workflow issues.
Fragmented App Access
No centralized entry point. Users had to move between different areas to find and launch the tools they needed, making the experience feel disconnected.
Poor Task Continuity
Users lacked a quick way to resume recent projects or continue work from where they left off — forcing repeated manual search every session.
Unclear Launch Behaviour
Users needed clarity on whether an application would open in browser, desktop app, or another environment. Uncertainty interrupted the workflow at the critical moment.
Weak Discoverability
Available products were not easy to find or understand — especially for new or occasional users who hadn't memorized the workspace structure.
No System Visibility
Cloud session health was hidden or unclear. Users couldn't tell if an issue was a system problem, network issue, or application failure — eroding trust.
Click-Heavy Flows
Everyday tasks required far more clicks than necessary. The 21-step core workflow was the most extreme symptom of a systemically overengineered navigation model.
Research Synthesis

What the data actually said

Mapping user struggles to business impacts made the cost of inaction impossible to ignore. Every friction point in the user experience had a direct operational consequence for the business — stalled cloud migration, unused infrastructure, and rising support load.

Key Insight Evidence
Users frequently resume the same work multiple times a day 6 in-depth interviews with geologists and geophysicists
Finding "where I left off" was harder than performing the task itself Product usage data + workflow walkthroughs
Tool discovery was a secondary friction — the launch flow was the primary blocker Usage data + interview synthesis
Context switching between views increased errors and user hesitation Shadowing sessions + support ticket review
User Friction Business Impact
21 clicks + multiple redirects before starting work Users hesitant to migrate to cloud — expensive servers going unused
Outdated tech, inconsistent interface, high cognitive load Users reverting to legacy systems — high cost of maintaining parallel infrastructure
No visibility of system status, overwhelming technical jargon Poor app access and trust deficit — preventing business scaling and adoption targets

How Might We

How might we reduce the steps between login and starting actual work to under 3 clicks?

How might we surface recent projects so users can resume work without searching again?

How might we give users visibility into system health without overwhelming them with technical detail?

How might we make application discovery intuitive for both new and experienced users?

How might we
Design Opportunity

Translating user needs into design decisions

Each insight from research was mapped directly to a design intervention — and each intervention was evaluated against the value it would deliver to users. This kept the work anchored to outcomes, not features.

User Need
Cloud workstation ready on login — apps and projects loaded immediately
Choose desktop type for app launch (RDP, Remote, TGX)
App & product updates visible and meaningful
Tech control on demand — not always visible
Design Intervention
Combine login & session start · Main workspace covers work access
Provide choice of RDP, Remote app, or TGX at launch
Dedicate part of workspace to recent app updates
Hide unnecessary settings unless explicitly needed
Value for Users
Clicks & redirects reduced · Productivity
User control and freedom
Increases trust between user and system
Increase in productivity
Affinity Map
Design opportunity map — user need → design intervention → value for users
Design Principles

Four principles.
Every decision ran through them.

Based on research with professional geologists, I defined four principles that governed every design decision. Not aspirational guidelines — actual filters. If a proposed solution didn't hold up against all four, it didn't ship.

01
Resume over rediscover

Help users continue work instantly. The home screen is not a launchpad — it's a resumption point.

02
Task-first, not tool-first

Organise the interface around what users are doing, not what features the product has.

03
Reduce cognitive load

Minimise decisions required before meaningful action. Every extra choice is friction.

04
Respect domain complexity

Simplify the workflow — never the domain. Geologists need professional-grade tools.

Wireframes

Initial wireframes
which provided a direction

Workspace layout
Apps and Projects
App settings
Workspace settings
Design Decisions

The calls that changed adoption

Every design decision was tied to a specific friction point identified in research. The goal wasn't to redesign the interface — it was to remove the obstacles between users and their work.

Decision 01 - Recent work
SURFACE RECENT WORK AS THE PRIMARY ENTRY POINT
Users consistently expressed frustration with finding their last active datasets. I introduced a "Recent Work" section as the primary entry point — enabling users to resume tasks in a single interaction. Surfacing recent projects and key actions upfront reduced time-to-task and improved re-engagement significantly.
Decision 02
Reduce click depth from 21 to 3
Deep hierarchies increased time-to-task and cognitive load. I collaborated with engineering to remove unnecessary decision points and simplify the workflow. Every redirect, confirmation step, and loading state was examined and either eliminated or absorbed into the background.
Decision 03
GIVE USERS LAUNCH CONTROL — CONTEXTUALLY
Users were confused about how to open applications: Remote App, RDP, or TGX. Rather than hiding this complexity, I surfaced it as a contextual choice per app — a lightweight dropdown at point of launch, with ability to set a default. Clarity over simplification.
Decision 04
EMBED SYSTEM HEALTH — DON'T CREATE A NEW DESTINATION
Users lost confidence mid-session when they couldn't tell if the system was working. Rather than adding a status dashboard (a new place to navigate), I embedded health signals directly into the Cloud Workstation control surface — network health, storage, and session state visible in one panel without leaving context.
Decision 05
DESIGN THE EMPTY STATE — IT'S A FIRST-WEEK EXPERIENCE
With 3,000 new users onboarding, the empty state wasn't an edge case. I designed a clear zero-data state that communicates what recent projects are, why there are none yet, and gives a single clear action — rather than leaving new users staring at a blank screen wondering if something broke.
Trade-offs & Prioritisation
To maximise adoption impact within delivery constraints, I prioritised high-frequency daily workflows and deferred lower-frequency enhancements. Prioritised core flows over long-tail edge cases for v1 · Deferred advanced personalisation to reduce engineering complexity · Used progressive disclosure instead of adding more controls on the first view.
Friction Map

Flow Comparison — 85% step reduction from redesign

The friction map documents the exact journey users had to take before and after the redesign. It reveals where unnecessary steps, repeated navigation, and unclear states were costing users time — and shows exactly how the redesign collapsed a four-stage, 21-click process into a two-stage, ~3-click flow.

Before: Users navigated through Login → Launch Subscription → Boot Virtual Machine → Open Recent Work — accumulating 21 clicks, multiple redirects, and significant wait time before starting actual work.

After: Login & VM launch are combined into a single step. The workspace loads ready-to-use with apps and recent projects visible. One click to start working.

Flow comparison diagram showing 21-click before flow and 3-click after flow with 85% step reduction
Flow comparison — Before: 21 clicks across 4 steps · After: ~3 clicks across 2 steps · 85% step reduction
Impact

The redesign converted a flat adoption trend into measurable growth

Within six months of launch, the redesign delivered results that were measurable across every dimension — user behaviour, satisfaction, and business adoption. The data validated not just the design decisions, but the research approach that preceded them.

Impact metrics — 5.5K total user traffic, 3.5K accessed recent projects, 2K directly opened apps, 85% task efficiency, 18 clicks reduced, 95% discoverability
Usability validation data — Google Analytics confirmed the hypothesis that users prioritise recent work access

The adoption rate chart below tells the fuller story — a flat growth curve from 2020–2024 that sharply inflected upward immediately after the redesign launch, reaching +13,000 new users by December 2024.

User adoption rate chart — flat from Jan 2020 to Jan 2024, steep rise from Jan 2024 to Dec 2024 post-redesign
User adoption rate on cloud profile — before and after the redesign
+67%
Active product adoption
Measured against pre-launch baseline across the geoscience user base within six months.
+80%
User satisfaction
Measured post-launch via structured usability validation with domain experts and geoscientists.
3K+
New users onboarded
New customers onboarded within 6 months of launch — the direct result of removing the adoption barrier.
85%
Task efficiency gain
Step reduction in core workflow — from 21 clicks to approximately 3, with 95% discoverability score.
Reflection

What I'd do differently
on this specific project

Want to discuss this
or a similar challenge?

Get in touch