Senior Product Manager · Seattle, WA
I'm Danny — a people-first PM with 6+ years at P&G leading enterprise data products, AI-powered capabilities, and cross-functional teams across global organizations. My engineering and analytics background means I can go deep with technical teams — while staying obsessively focused on the humans who use what we build.
"The best products don't come from the smartest individual in the room — they come from teams who trust each other enough to build something none of them could alone."
How I Work
Six principles I return to regardless of what I'm building, who I'm partnering with, or how murky the roadmap looks.
I spend a disproportionate amount of time in discovery — user interviews, usage pattern analysis, support ticket trends — before a roadmap takes shape. Skipping this step is where most bad products begin. It's where I uncovered the real performance bottlenecks at P&G before anyone opened a Jira ticket.
Specs and PRDs are just tools. My real job is defining the success delta — the measurable difference in user behavior and business value — and ensuring the team has the autonomy to find the best path to get there.
Quantitative data tells me what's happening. Qualitative research tells me why. Good decisions need both — and occasionally, the courage to move when the user signal is strong but the dataset is thin.
I've built A/B testing culture at P&G — from experiment design and measurable hypothesis framing to statistical rigor and post-launch iteration loops. Teams that experiment consistently make better decisions over time, full stop.
The "Yes" must be earned; the "No" must be defended. In an era where AI has lowered the cost of building, the PM's most vital role is as a filter. I focus on protecting the product's core value by resisting feature bloat and hype-chasing — ensuring every roadmap item solves a high-stakes problem rather than just increasing the surface area of the product.
In a high-velocity environment, the spec is never the finished product. I leverage AI-assisted prototyping and iterative loops to fail safely and cheaply. This allows us to sharpen requirements through actual usage — ensuring that when we finally hit build, we are scaling a validated success.
Selected Work · Procter & Gamble
Three initiatives from my time at P&G — the problem, my process, and what we learned along the way.
Commercial teams at P&G were bottlenecked waiting weeks for data changes that should have taken hours. Through structured discovery with UX Research and Data Science, I found the real friction wasn't data access — it was the absence of guided self-serve tooling. I led the development of Data Studio, an AI-powered capability embedded in FastMart (P&G's enterprise data platform), enabling users to query and act on data without engineering dependency — while also implementing AI-driven chatbots and intelligent data pipelines that transformed operational throughput.
My Process
Outcomes
What I'd do differently: I'd invest more in internal evangelism before launch. Several teams didn't discover the capability until weeks after GA.
FastMart users were experiencing sluggish query performance that was eroding platform trust across commercial and supply chain teams. Rather than defaulting to an infrastructure fix, I led user interviews across 15 sales teams to understand where performance degradation was actually felt — and what it was costing them day-to-day. Those insights revealed a mix of behavioral patterns and architectural bottlenecks, ultimately informing a migration to Databricks Unity Catalog and a new monitoring strategy that dramatically improved reliability and adoption.
My Process
Outcomes
What I'd do differently: Pulling governance stakeholders in earlier would have shortened the compliance review by at least a sprint.
Analysts across P&G had no safe environment for exploratory data work that didn't risk production systems. There was no standard onboarding, no shared resources, and no visibility into usage or cost. I created and led Analyst Sandbox from scratch — designing the full intake-to-offboarding flow, publishing golden datasets and starter kits, building usage and cost dashboards with alerting, and automating deprovisioning to eliminate a recurring manual ops burden. Adoption was driven by the documentation and resources, not the launch announcement.
My Process
Outcomes
What I'd do differently: I'd replicate the documentation-first sequencing in every platform feature going forward — it's the highest-leverage adoption move I've made.
Toolkit
Core PM competencies shaped by enterprise data, AI, and consumer product work — paired with hands-on technical depth that lets me move faster with engineering and data science teams.
The Human Behind the PRDs
I believe who you are outside of work directly shapes how you show up in it. Here's what keeps me curious.
I came to product management through an unconventional path — industrial engineering, supply chain ops, enterprise data analytics — before landing in PM. That cross-disciplinary background is something I lean on constantly. I can sit with an engineer and talk data pipeline architecture, then walk into a leadership review and translate it into business impact without losing either audience.
I grew up bilingual — English and Telugu — which has shaped how I think about communication: clear, intentional, never assuming shared context. I bring that same instinct to PRDs, roadmaps, and stakeholder conversations. Outside of work, you'll find me at a track day, behind a camera, on a mountain, or overthinking a 4-foot putt.
Let's Talk
Whether you're a recruiter, a founder, or a fellow PM who wants to swap notes on data products and AI — I'm always up for a good conversation. I try to respond within 24 hours.