Product Design
Your product does a lot. Let’s make it easier to use.
I work with founders and teams on AI, deep-tech, and enterprise products. I get into how your users and industry work, then design the flows, screens, and details that help people get things done.
Speak with Disha
Flighty
Complaints Intelligence Platform: Faster investigations, with human judgment still in charge
This complaints management platform for a life sciences company gives investigators a structured workflow for every stage, with AI assistance alongside built-in evidence and traceability. Investigators can move faster while keeping the reasoning behind every decision visible.
Investigators at a life sciences company were piecing together cases across disconnected systems under strict regulatory rules. The challenge was preserving context: what they found, how it connected, and why decisions were made.
I designed around how they work, with structured flows and AI alongside the evidence to support—not make—decisions. Traceability kept the reasoning behind each step visible and reviewable, helping stakeholders move forward faster.
In high-stakes products, people trust AI when they can still see their own judgment in the work.
Where I come in
Sometimes the pieces are there. They just don’t quite fit.
People sign up, but don’t know where to start. A simple task takes too many steps. New features keep getting added, and the product starts feeling harder to navigate.
What I look for
Where products usually lose people.
Onboarding
People sign up curious and leave before the product ever makes sense to them.
Activation
The first real win takes too long, or nobody shows people what to do after it.
Different roles, one flow
Admins, operators and reviewers end up squeezed into a flow built for just one of them.
Generic workflows
The product works in theory, but it doesn’t fit how your industry actually operates, budgets or decides.
Errors, drop-offs and branches
The empty states, failed states and exceptions. Your users hit these every day, and they’re usually designed last.
Teams out of sync
Design, engineering and business pull in different directions, and the experience shows the gaps as you grow.
My process
How I work through a product.
01 / Product audit
First, understand what’s there.
I look at your product, who uses it, and the work they’re trying to get done. Together, we find where things get difficult and what’s worth addressing first.
Typical outputs:
- 01Product and UX review
- 02Review of relevant competitors
- 03Friction points across key journeys
- 04Priorities and a plan for the design work
02 / User flows + IA
Make the structure make sense.
I map how people move through the product—what they need to find, decide, and do. This includes the different roles, permissions, and handoffs along the way.
Typical outputs:
- 01Key user flows
- 02Navigation and information structure
- 03Roles and permissions mapping
- 04Alternate paths and edge cases
03 / Wireframes + UX
Work out how it should behave.
I use wireframes and prototypes to work through the important screens and interactions. We review the flow, question assumptions, and refine the details before moving into visual design.
Typical outputs:
- 01Wireframes for key screens
- 02Interaction patterns
- 03Clickable prototypes
- 04Empty, loading, and error states
04 / Product UI
Bring the experience into focus.
I shape the visual details so people can tell what matters and what to do next. Layout, type, colour, and components come together across the product.
Typical outputs:
- 01High-fidelity screens
- 02Reusable UI components
- 03Responsive layouts
- 04Component and interaction states
05 / Handoff + QA
Carry the thinking into the build.
I work with your developers on behaviour, states, and the details that can get missed between design and implementation. As things take shape, I review the build and help resolve gaps.
Typical outputs:
- 01Organised design files and annotations
- 02Interaction and behaviour notes
- 03Design reviews of the build
- 04Follow-up fixes and refinements
How I think about the work
I design products with business and users in mind.
Your users have a job to do. Your team has goals to meet and constraints to work within. I keep both in view as I work through the product.
- 01
Get into the complexity
I take time to understand your industry and domain—how people work, the decisions they make, and the constraints they work within. Those details shape how an AI-native tool, mobile app, or SaaS product should work.
- 02
Think through the build
I consider edge cases, components, user permissions, accessibility and responsive behaviour as I design. And I work through technical constraints with your engineers along the way.
- 03
Work closely with your team
I work directly with founders, product managers, and engineers. We talk through decisions as they come up, so the reasoning stays clear as the product takes shape.
Ways to work together
A fresh look, a focused project, or someone to keep building with.
We can start with an audit, design a proof of concept or MVP, or work together as your product evolves.
3-5 days
Product Clarity Audit
For teams with a live product that feels harder to use than it should. I help you understand where people get stuck and what needs attention first.
What is included:
- 01Review of key user journeys & friction points
- 02User Interface consistency, visual design and accessibility review
- 03Findings prioritised by impact and effort
- 04Clear recommendations that your team can act upon
2-8 weeks
One-time Design Project
For founders and teams with something specific to build or rethink—a PoC, an MVP, a new feature, or an existing product. We agree on the scope and work through it together.
What is included:
- 01Agreed goals, scope, deliverables, and timeline
- 02User flows, wireframes, and key edge cases
- 03Detailed UI, reusable components, and prototypes
- 04Design context and documentation for AI-assisted builds
- 05Developer handoff and design reviews during the build
Monthly retainer
Design Retainers
For teams that need design support as their product evolves. I stay close to the product and the people building it, with time set aside each month.
What is included:
- 01Dedicated design time around monthly priorities
- 02Design for new features and existing product improvements
- 03Components and patterns that evolve with your product
- 04Regular team reviews and ongoing developer support
Testimonials
From people I’ve built things with.
She distills complex ideas into structured, coherent narratives that strengthen both product positioning and brand perception.
Clarity is the most underrated design skill — and one that truly defines impactful work. Disha consistently brings this clarity to every engagement.
She distills complex ideas into structured, coherent narratives that strengthen both product positioning and brand perception. She is a strong asset to any team — thoughtful, capable, and full of long‑term potential.
N.A., Founder & CEO, Shweta Labs (IIT Bombay)
Daniel G Bright, Founder, Bright Studios
Shubh Agrawal, Head of Growth, Valley
Adriano Reis, Founder, Ancorpoint Studio
Dan Pugsley, Co-founder & CTO, Stealth Ed-tech startupFrequently asked questions
A few things you might want to know before we work together.
I mostly work on AI, deep-tech, and enterprise products, often in industries where there’s a lot to understand before you can design anything useful. That could be a new idea you’re testing, an MVP, or an existing product that needs rethinking.
Yes. We can look at where people are getting stuck, what’s become harder to use, or where the product no longer fits how they work. Sometimes that leads to a focused improvement; sometimes it means rethinking the structure or a larger part of the experience.
Yes. I work directly with founders, product managers, designers, and engineers. I take time to understand the decisions already made and the constraints your team is working within. We agree on what I’ll own and stay in touch as the work takes shape.
Yes. I work through the flows, component behaviour, permissions, and edge cases so your engineers have the context they need to build. That includes documentation for AI-assisted development and reviewing the implementation as it takes shape. I can also develop frontends myself, with that work scoped separately.
Both. We can work on something specific, like an MVP, a new feature, or a redesign. If you need someone to stay close to the product as it evolves, I also offer ongoing support. We agree on the scope or monthly capacity around what your team needs.
You can book a call or drop me an email with a little about your product and where you need help.
You might be figuring out a new idea, working through a difficult workflow, or noticing that people aren’t using the product the way you expected. We can talk through it, bounce around ideas, and see what might make sense. You don’t need to have the solution figured out before we speak.