Product · UX & AI PM Portfolio · Ahmedabad, India

14+ Years Building
Products People Use.

Now Building Toward AI product
Work Users can Actually Trust.

UX depth, frontend fluency, and product execution experience — now being applied to AI product thinking, trust-sensitive workflows, and case-study-led learning.

IBM AI PM Certificate
CSPO · Scrum Alliance
FinTech · LMS · Enterprise SaaS
See My Work Let's Talk
Featured Work

Work That Shows the Thinking

Not design showcases. Each one walks through a real problem, the decisions that shaped the response, and what the outcome revealed. Anything conceptual is labeled upfront.

View All Work
Real Work LMS · EdTech Product & Delivery
01

Three LMS platforms. The design wasn't the common thread — the wrong starting question was.

Across three separate LMS projects at Tridhya Tech, I led end-to-end delivery — from stakeholder alignment through UX, frontend execution, and production deployment. Each platform had a different user, a different failure mode, and required a different answer to the same upstream question: what does this learner actually need to do, and what is currently stopping them?

All three delivered to production · Cross-functional teams led end-to-end · Stakeholder communication and reporting throughout
Product & Delivery Lead · UX · Frontend · Stakeholder Management Read case study
Concept · Course Work FinTech · AI Feature
02

Google Pay already works. What would it take to add AI-driven nudges without making users feel watched?

Full PRD with prototype produced as part of the IBM AI PM program. The brief wasn't "add AI." It was "define what the user should feel when AI touches their money." Framing centred on trust transparency, opt-out clarity, and context sensitivity.

Product Thinking · PRD · Prototype · AI Feature Design Read case study
Real Work Enterprise · CRM · Logistics
03

Field teams were ignoring a CRM the business had invested heavily in. The interface wasn't the problem — the mental model it assumed was.

Reframed the problem with stakeholders before a single screen was touched. The CRM had been designed around how managers expected field teams to work — not how they actually worked. Restructuring the information architecture around real field workflows changed the conversation entirely.

UX Strategy · Information Architecture · Stakeholder Reframing Read case study
How I Work

I don't lead with solutions.
I lead with the problem
worth solving.

The sequence is the same whether I join at discovery or inherit something mid-build. What changes is where I have to push hardest.

  1. Frame the right problem

    Most product conversations start too late — already deep in solution mode. I push back to the problem first. What's actually broken? For whom? At what cost to the business? The answer to that question shapes everything that follows.

    Discovery Problem Framing Stakeholder Alignment
  2. Map the human layer

    Who is this for, and what are they actually trying to do? In AI products, I add one more layer most teams skip: where does the user's trust in the system break? That's almost always where the real design problem is hiding.

    User Research Trust Mapping Mental Models
  3. Define the decision space

    Not everything worth building should be built now. I help teams make the tradeoff explicit — and write down why we made the call we made. That documentation alone prevents three future arguments.

    Prioritisation Tradeoff Analysis PRD Writing
  4. Design for usability and trust

    I write the brief, map the flow, and spec it close enough to development that the intent survives handoff. Having shipped frontend code myself — HTML, CSS, React, Angular — means I know what ambiguity costs on the other side of the process.

    UX Flows Feature Briefs Dev Handoff
  5. Ship, measure, adjust

    I stay close through delivery. The work isn't done when it ships — it's done when you understand what changed and why. The first version is usually wrong about something specific. That's what version two is for.

    Delivery Outcome Tracking Iteration
Proof of Thinking

Thinking, Made Visible

Credentials tell you where someone has been. Artifacts tell you how they think when they get there. These are working documents — the kind produced before a designer opens Figma or an engineer opens a ticket.

View All Artifacts
Google Pay — AI Feature PRD

Full product requirements document from my IBM AI PM program. Problem definition, trust framing, feature spec, edge cases, and success metrics. Includes working prototype.

Concept · IBM AI PM Program · Available Now
Read case study
Problem Framing Template

A one-page format I use to align stakeholders before any solution discussion. Forces clarity on who is affected, what they need, and why existing options fail.

Framework · Available Now
Read case study
AI Feature Brief Structure

How I structure a brief for an AI-powered feature: user need, trust considerations, edge cases, error states, and success criteria — before design begins.

Work sample · On Request
Riase a request
Uday Dave — AI Product Manager based in Ahmedabad, India
IBM AI Product Manager Certificate — Nov 2025
CSPO · Scrum Alliance
Meta Front-End Developer Certificate
Business Analysis · ECBA · IIBA
UX + HCI · Interaction Design Foundation
About

14+ years of craft.
One deliberate direction.

I started as a Jr. Web Designer in 2012. Over the next 14+ years I moved through frontend development, UX design, team leadership, business analysis, and product ownership — across FinTech platforms, SaaS products, healthcare systems, and enterprise tools. Different domains, different teams, the same underlying pull: toward the decisions upstream of design.

At Tridhya Tech that pattern became explicit. I joined as Lead UX Designer and left as Associate Project Manager — with a CSPO and an ECBA earned along the way. Three and a half years of watching product decisions get made well and badly from close range. The title changed. The underlying problem I kept trying to solve did not.

I completed the IBM AI Product Manager Professional Certificate in November 2025. The focus now is AI products — specifically the gap between what teams ship and what users can actually trust and use. That gap is not a technology problem. It is a product thinking and experience design problem. It is also the problem I have been building toward.

Ahmedabad, India  ·  Building toward AI PM roles  ·  Open to thoughtful product conversations
For hiring managers & recruiters

Building a product team that needs someone who can own the experience — not just describe it?

I’m building toward AI PM roles and documenting that transition through case studies, PRDs, and product thinking work. If my background in UX, frontend, and product execution looks relevant, I’d be glad to connect.

Connect on LinkedIn Email me directly
For founders & product teams

Working on an AI product that technically works but isn't landing with users?

I’m open to thoughtful conversations around product clarity,
AI feature framing, workflow UX, and early-stage
product thinking.

Start a conversation