Work 01 · Product transformation
Rebuilding a failed product function around evidence
A startup needed more than a roadmap. I began with 164 interviews, rebuilt the product system, and helped turn learning into two commerce platforms.
The starting point
The product function had failed because the organization lacked a shared view of the customer and the work.
I entered as a consultant and interviewed 164 users, operators, and stakeholders. The evidence showed that a feature list would not solve the underlying gaps in discovery, ownership, prioritization, and commercial alignment.
I translated the findings into a product reset: clearer problems, explicit measures, connected roadmaps, and a delivery rhythm the team could maintain.
Defining the whole product
The roadmap had to connect customer behavior, operations, data, and economics.
I owned roadmaps and P&L while partnering with design, engineering, operations, and leadership. We built two commerce platforms with predictive capabilities, delivering the first within three months of my promotion and both within seven months.
The work included the operating system around delivery: backlog quality, decision rights, success measures, and cross-functional accountability.
Outcomes and continuity
The products changed behavior, and the team could continue without me at the center.
Activation increased by 37%, and first-quarter revenue increased by 40%. I led a nine-person cross-functional team and prepared a successor so the product function could keep growing after my departure.
Reflection
A roadmap is useful only when it connects evidence, decisions, delivery, and economics.
- What I would do differently
- I would instrument the discovery-to-decision trail earlier so the team could see how each priority connected to user evidence and business value.
- Framework connection
- Product Diagnosis Canvas · Evidence Ladder · Alignment Map
Results reflect the professional record in my current CV. Confidential product and company details are withheld.