About

Prashanth Samudrala

Enterprise Product Design Leader · 17 years · Hyderabad, India

I came to UX through sociology — which means I was trained to ask why people behave the way they do before I ever thought about designing for them. That's still how I work. Every design decision I make starts with a question about human behaviour, not a Figma artboard.

Over 17 years, I've worked across enterprise SaaS, developer tools, healthcare, finance, mobility, and HR platforms — at the intersection of what users need and what the business is building toward. The work has ranged from turning a low-performing conversion funnel into a company's #1 priority, to rebuilding a design practice from -8% performance to positive growth within a year.

Photo
(replace in /images)
Origin story

From sociology to UX — the long way around

Sociology taught me to observe social structures, understand what drives human behaviour, and notice what people don't say as much as what they do. That training turned out to be an unusual and useful foundation for UX work.

Where most designers learned to empathise with users through design thinking frameworks, I learned it through qualitative research methodology. That shift — from empathy as a technique to empathy as a lens — is what I bring to every engagement. It's why I run usability sessions the way I do, why I ask different questions in stakeholder interviews, and why I care as much about the sociology of an organisation as I do about the usability of its product.


Where I came from

From Web Designer to Design Architect.

  1. 2025 — Present
    Persistent Systems
    Design Architect
  2. 2022 — 2023
    Darwinbox
    Sr. Manager
  3. 2021 — 2022
    Neudesic
    Sr. Manager, UX
  4. 2019 — 2021
    Innominds
    Manager, UX
  5. 2016 — 2019
    Pramati
    Lead Interaction Designer
  6. 2014 — 2016
    Cognizant
    Sr. Associate
  7. 2011 — 2014
    Kony
    Project Lead
  8. 2006 — 2011
    VoiceGate
    Creative Lead
  9. 2005 — 2006
    IMImobile
    Web Designer

What I believe

Three principles I come back to

01
Complexity is the material, not the obstacle
Enterprise environments are inherently complex — multi-stakeholder, politically charged, technically constrained. The job isn't to simplify away from that reality. It's to design systems that work within it, while making that complexity invisible to the people using the product.
02
Alignment before artefacts
The most expensive design mistake in enterprise is building the right thing for the wrong room. I spend more time than most designers ensuring the people who will approve, build, and live with a design are aligned on the problem — before a single screen is presented.
03
Adoption is the real success metric
A product that people avoid using has failed, regardless of how well it performed in testing. I measure design success at the point of real-world use — where habit forms, where the workaround emerges, where the training falls apart.

How I work

The four competencies, in practice.

Leading the work
Shaping direction without a mandate
Most of my career has been in environments where design doesn't have formal authority over product decisions. I've learned to build alignment through clarity: making the tradeoffs visible, the user impact concrete, and the path forward obvious enough that the right decision becomes the easiest one.
Stakeholder alignment before screens
I run structured sessions early — not to present work, but to surface what each stakeholder actually needs the product to do. The goal is to find the constraint before it becomes a blocker.
Bridging research and engineering
I translate between what users say in sessions and what engineering can realistically build in the next sprint. That connective role — being fluent in both directions — is where I've had the most impact on product outcomes.
Doing the work
Systems-level interaction design
Enterprise workflows have second and third-order effects. I design for the role who uses the system at 6am with no training time, not just the primary persona in the research brief.
Moderated usability research
I run sessions myself, not just define them. The pattern that matters is rarely in the first observation — it's in what five different users do at the same moment for different reasons.
Information architecture for complexity
Healthcare scheduling, IoT fleet management, HRMS platforms — environments where the data model and the mental model rarely match. Finding the structure that serves both is the core of the work.
Design systems with governance
Components are the easy part. The hard part is the conversation that keeps them coherent when four product teams are pulling in different directions simultaneously.