AI Fluency Gap
75% use AI — almost nobody changed how they work. Mapping where professionals stall between using AI and true fluency.
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.
Problem framing, decision quality, and delivery outcomes across concept and production work.
75% use AI — almost nobody changed how they work. Mapping where professionals stall between using AI and true fluency.
Farmers know their crop — not the right moment to sell. AI surfaces the exact sell window without changing how they already work.
People know financial theory but still make the wrong call in the moment. Real-time consequence visibility at the decision fork — not after.
Three platforms, three different failures, one upstream cause. Led end-to-end from stakeholder alignment through UX, frontend and deployment.
From problem space to solution space — the same process mapped into five practical cards.
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.
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.
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.
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.
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.
A cross-functional foundation across design, frontend, product, and AI-enabled workflows.
Research, flows, systems thinking, and interface clarity.
Implementation awareness that helps keep design intent intact.
Clarity, prioritization, alignment, and execution.
Practical exploration of AI product thinking and workflow design.
Credentials tell you where someone has been. Artifacts tell you how they think. Working documents — the kind produced before a designer opens Figma.
Full PRD from IBM AI PM program. Problem definition, trust framing, feature spec, edge cases, and success metrics. Includes working prototype.
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.
How I structure a brief for an AI-powered feature: user need, trust considerations, edge cases, error states, and success criteria — before design begins.
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.
I'm looking for an AI PM role where the problem is real and the work goes deeper than ticket management. 14+ years of execution, IBM AI PM, HelloPM Cohort 49, and a CSPO. I know what I'm bringing and what I'm still building.
That's a specific problem. I work with founders and small product teams on the thinking that happens before design begins — user framing, feature definition, trust decisions. A focused conversation that moves something forward.