I'm a Technical/Data Product Manager. At Side I own Sidekick, the revenue platform that is now the standard reporting tool across the company, along with the data pipelines and the AI billing workflow behind it. Before that I ran the roadmap for Dubs, a consumer app with 100k+ users.
Engineering foundation from RV College and AirAsia Tech. Data science depth from a Master's at the University of Colorado Boulder. Product work on both sides: enterprise (B2B) data products for Finance and Ops teams, and a consumer social app.
I've written the code, built the data models and sat in the user interviews myself, so my calls rest on what's actually true. I run discovery before I write specs, and I read the data before I make the call. Most of the hard problems I've worked on came down to finding the real problem before building the wrong solution well.
I recently completed an Executive MBA at IIM Visakhapatnam, graduating Rank 1, and I hold ISB's Professional Certificate in Product Management, CSPO and a Lean Six Sigma Black Belt.
Dec 2025 - Present · 1 yr
Jan 2024 - Dec 2025 · 2 yrs
Jan 2023 - Jan 2024 · 1 yr 1 mo
Jan 2021 - Jan 2023 · 2 yrs 1 mo
One set of revenue numbers the whole company agrees on.
Finance, Ops and leadership each had their own version of the revenue numbers, and month-end reconciliation took days.
I sat down with each team. The reports weren't the issue. Every office entered project data differently, so the numbers couldn't agree however the dashboards were built.
Phase 1 - Foundation (shipped)
Phase 2 - AI-integrated insight generation (shipped)
Phase 3 - Seamless end-to-end integration (vision)
AI reads the billing documents. Rules decide what gets posted.
Finance built the monthly billing journals for the ERP by hand. I mapped both billing routes with Finance, step by step, and asked for each raw export alongside the hand-corrected copy. The difference between the two showed exactly where the manual work was.
Prepare
Source data lands in Fabric, gets checked, and is frozen for the month.
Read
AI pulls the billable lines from the approved quote and PDF.
Build
Mapping rules create the journal. Validation flags errors.
Review
Finance approves, edits or rejects. Nothing posts without this.
Post
Upload file first, ERP API later.
Reconcile
Source, journal and invoice must match, or it raises an exception.
A safer social platform for gamers to find teammates and build communities around the games they play.
Gamers, many of them teens, had nowhere safe to find teammates. Existing apps handled chat once you'd found your people; Dubs set out to help them find those people in the first place.
What this area was: How users found live lobbies and the right people to play with.
Key decisions I made
Dig into the detail
What this area was: AI-powered identity and interaction inside a social gaming product.
Key decisions I made
Dig into the detail
Key decisions I made
Why this design
Guardrails - Kyle was limited to game-related topics and designed to deflect unsafe or off-topic prompts.
Disambiguation - AI iconography made it clear when users were interacting with Kyle rather than another person.
What this area was: Chat, voice and communities: where users spent their time once they'd found each other.
What I owned
What this area was: How a new user became a Dubs user, from age-gated signup and identity setup to building their first social connections.
Dig into the detail
Why this design
Permission timing - Used a soft prompt before the OS-level notification request because iOS limits the chance to ask again after a decline.
Safety by design - Added guidance during username setup to reduce risky identity choices early.
Why this design
Everywhere - friend requests can be sent from search, Team Up, lobbies and chat, because friending was the output metric for Team Up.
High-intent actions first - Prioritized Accept Request in search results to reduce friction on the most valuable social action.
What this area was: The in-app economy and store.
What I owned
Key decisions I made
What this area was: The systems that made DUBS safer to join, trust, and participate in.
What I owned
Contributing analyst on the XDS 2026 Insights Report.
A survey of 250+ studios, publishers and service providers on external development and AI governance. I set up the analysis structure, kept questions comparable year over year, and added new measures on AI permissions, disclosure and data-training limits.
Product strategy · Roadmap ownership · PRD writing · User stories and acceptance criteria · User research · Funnel analysis · Retention strategy · RICE prioritization · A/B testing · Sprint planning · Stakeholder management
Technical discovery · Data-flow mapping · Data quality · Semantic modelling · Pipeline design · SQL · Microsoft Fabric · REST APIs · Jira · Git
AI product design · LLM concepts · AI workflow design · AI safety and governance · Human-in-the-loop systems
B2B enterprise data products · Consumer social · Finance and Operations · ERP · Trust and Safety
Indian Institute of Management Visakhapatnam · 2024–26
University of Colorado Boulder · 2022–24
R.V. College of Engineering, Bangalore · 2017–21
Indian School of Business (ISB) · 2024
Scrum Alliance
The Council for Six Sigma Certification (CSSC) · 2024
Local event hosted by SRM Institute (AARUUSH'20) · October 2020
R.V. College of Engineering · 2020–21
Open to Technical PM, Data PM, and B2C or B2B PM conversations.
niveditamadhava1@gmail.com · +91 9482127568
Bangalore, India