AI Product Manager · IBM AI PM · HelloPM Cohort 49 · Ahmedabad, India

I don't start with AI.
I start with the problem.

e.g.

14+ years across UX, frontend, and product execution. Now applying that depth to AI products — where the gap between what ships and what users actually trust is a product thinking problem, not a technology one.

Featured Work

Case studies that show product depth.

Problem framing, decision quality, and delivery outcomes across concept and production work.

View All Work
Research Snapshot
AI Fluency Gap
Where professionals stall between tool usage and true workflow-level adoption.
Group Project · In Progress AI Adoption · Enterprise

The AI Fluency Gap — 75% use AI. Almost nobody changed how they work.

Mapping the journey from AI-aware to AI-fluent: where professionals stall, what compounds the gap, and what a product built around deliberate AI practice could look like. Research in progress as part of HelloPM Cohort 49 capstone.

  • 75%Use AI tools regularly
  • 3%Reach fluency
  • 142×LinkedIn growth signal
Decision Layer
Smart Mandi
AI-guided sell timing that works with existing farmer behaviour, not against it.
Concept · Mentor Validated AgriTech · AI

Smart Mandi — farmers know their crop. They don't know the right moment to sell.

Not a data problem — a trust and timing problem. AI surfaces the exact right moment to sell without requiring farmers to learn a new interface or change existing behaviour. Mentor-validated concept from HelloPM cohort work.

  • 94%Ahmedabad SMBs adopting AI
  • ₹28Best price missed daily
  • 3 moPeak price timing window
Decision Intelligence
Financial Fluency
Making consequence visibility available at the exact moment financial choices are made.
Concept · Course Work FinTech · AI

Financial Fluency Gap — real-time consequence visibility at the moment of decision.

People know financial theory. They still make the wrong call in the moment. Budgeting apps track history. This concept helps users decide better at the fork, not after. Built on FinTech domain experience and research into real financial stress behaviour.

  • 72%Impulsive EMI decisions
  • 0Apps help in-decision today
  • ₹8,400Potential savings in 2 months
Delivery Pattern
LMS Portfolio Work
Three platforms, three failure modes, and one root cause corrected upstream.
Real Work LMS · EdTech

Three LMS platforms. Three different failures. One upstream cause.

The design wasn't the common thread — the wrong problem had been defined first. Led end-to-end across all three from stakeholder alignment through UX, frontend development, and production deployment.

  • 3Platforms delivered
  • 3Failure modes decoded
  • 1Upstream cause solved
How I Work

Five layers.
One process.

From problem space to solution space — the same process mapped into five practical cards.

Problem Space
01 Frame the right problem

Most product conversations start too late — already deep in solution mode. I push back to the problem first. What is actually broken? For whom? At what cost to the business? Without this step, every decision after is built on sand.

Problem Space — Layer 1
Stakeholders
Context
Root Cause
Problem Brief
Output: A clear, agreed problem statement
02 Get close to the user

I talk to users before forming opinions — not to validate, but to learn. The signal is usually in what people do, not what they say. For AI products I add one more layer: where does trust in the system break? That is almost always where the real design problem hides.

Problem Space — Layer 2
User Segments
JTBD
Pain Points
Trust Map
Output: Validated user insights and mental models
Solution Space
03 Define the right solution scope

Most teams build too much of the wrong thing. I define the smallest version of the right solution — what must be true for it to work and what can wait. This is where prioritisation gets made honestly, and where the PRD becomes a decision document rather than a wish list.

Solution Space — Layer 3
Ideation
Prioritise
ICE / Kano
PRD
Output: Backlog and scoped roadmap
04 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 means I know what ambiguity costs. For AI features, explicit trust and error state design goes into every brief.

Solution Space — Layer 4
UX Flows
Feature Brief
Trust Design
Dev Handoff
Output: Specs that survive handoff
05 Ship, measure, adjust

I stay close through delivery. The work is not done when it ships — it is done when you understand what changed and why. The first version is usually wrong about something specific. That is not failure, that is what version two is for.

Solution Space — Layer 5
Ship v1.0
Measure
Learnings
Ship v2.0
Output: A continuous improvement loop
Craft & Capabilities

Skills, tools, and working strengths

A cross-functional foundation across design, frontend, product, and AI-enabled workflows.

Design

Research, flows, systems thinking, and interface clarity.

  • Figma
  • UX Research
  • Design Systems
  • Interaction Design

Frontend

Implementation awareness that helps keep design intent intact.

  • HTML/CSS
  • JavaScript
  • React
  • Frontend Delivery

Product

Clarity, prioritization, alignment, and execution.

  • PRD Writing
  • Stakeholder Management
  • Roadmapping
  • Discovery Thinking

AI

Practical exploration of AI product thinking and workflow design.

  • AI Product Thinking
  • Prompting
  • LLM Workflow Design
  • AI Tooling
Proof of Thinking

Thinking, Made Visible

Credentials tell you where someone has been. Artifacts tell you how they think. Working documents — the kind produced before a designer opens Figma.

View All Artifacts
Google Pay — AI Feature PRD

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

Concept · IBM AI PM · Available on request
Problem Framing Template

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

Framework · In preparation — available on request
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 · In preparation — available on request
"I don't start with AI.
I start with the problem."
— Uday Dave
AI Product Manager
About
Uday Dave — AI Product Manager, Ahmedabad
IBM AI PM Certificate
HelloPM AI PM · Cohort 49
CSPO · Scrum Alliance
Meta Front-End Developer
UX + HCI · IxDF

14 years of craft.
One deliberate direction.

I started as a Jr. Web Designer in 2012. Over the next fourteen 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 earned along the way. Three 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 and am completing HelloPM Cohort 49 — ending April 2026. The focus: AI products where the gap between what ships and what users actually trust is still a product thinking problem. That's the problem I've been building toward.

14+
Years Experience
6
Domains
5
Certifications
1
Direction
Career journey — scroll →
2025 – Present
Sr. Manager · AI PM Transition
63 Moons Technologies · Ahmedabad
2021 – 2025
Team Lead → BA → Associate PM
Tridhya Tech · Ahmedabad
2020 – 2021
UI Designer · FinTech Products
Digi-corp · Ahmedabad
2015 – 2020
Senior UI Designer
SPEC INDIA · Ahmedabad
2012 – 2015
Jr. Web Designer → UI Designer
Early career · Ahmedabad
Ahmedabad, India  ·  Open to remote AI PM roles  ·  Available for select consulting