Two goals, one bet: the map that cut tickets and opened a media channel
Role
Group Product Manager for the Customer context — end-to-end direction, no execution
Team
a PM reporting to me + a design team
Timeline
~6 months, from discovery to delivery
Result
contact rate for the target reason −30% · a new recurring media revenue line
01 — My scope
As Group Product Manager for the Customer context, I carried two scopes that didn’t talk to each other: improve the post-order experience, the biggest source of contact with support, and contribute to the group’s agenda of opening new revenue fronts.
This is the case where my role was pure direction: I led the initiative end to end without designing a screen or writing a requirement.
The PM who reports to me and the design team ran all of discovery and delivery, with me directing.
02 — What was at stake
1/10
of post-purchase tickets were “I can’t find the courier” among the five largest contact categories
Each contact was operating cost and friction in the journey.
On the other side, the retail media team needed new inventory to negotiate with the industry, with less dependence on external processes.
In standard roadmap logic, they’d be two projects fighting over the same quarter.
What this diagram proves: the convergence was a deliberate decision: two agendas that would fight over the same roadmap, resolved in a single bet, with results on both sides.
Product03 — Product decision
I decided it would be a single bet.
The choice was the courier map, a feature with nothing innovative about it, and that’s exactly the point: the decision wasn’t in inventing, it was in the design and the prioritization, with the feature born customizable for the industry.
The map attacked the cause of the tickets; the user’s attention on that surface became a negotiable media space.
Direction04 — Leadership and craft decision
My rule was to direct through the questions, not the answers.
how does the process between the industry and our operation work?
what changes between a player with its own agency and one without?
I framed what discovery needed to answer and let the PM and the design team reach the answers. I tracked through critique and review rituals on a fixed cadence and stepped in only at the decision checkpoints: prioritization, trade-offs, stakeholders.
Product
By the time the proposal reached the table, it already had owners.
Buy-in came in 1:1s with the marketing, retail media, and my own leadership, before any forum.
And templatization came in as a business-model decision, not a UI one: the templates were born as the package retail media would use to negotiate with the industry, with customization levels that become price tiers.
Direction
One example of what was mine at those checkpoints: I ruled that customization would start with just two options, to learn from the real operation before releasing variations, instead of launching with the full range the commercial front wanted to sell.
The craft decision that held up the model was the templatized vision: a template that protects the technical requirements of customization, no matter who produces the asset, and that lets new variations come in through design and branding, without triggering engineering.
Customization stopped being a quality risk and became an operable system.
What this diagram proves: the craft decision is a business model: the template protects the technical requirements and the customization levels become price tiers, operated by three teams.
05 — Relative result
What this diagram proves: the result is relative and has method: an index with base 100, no absolute volumes.
The same delivery opened a new line of recurring media revenue, sold today to the industry in price tiers by customization level, negotiated by retail media.
One launch, two business goals, and a team that made the execution decisions without me.
06 — What I’d do differently
Respecting technical complexity I’d already learned in the cycle where I built the area’s governance. The map taught me a new category of it: the complexity that comes from third-party requirements. Guaranteeing the template’s structure for any asset producer took more engineering than the plan assumed. Today I’d put the template’s technical sizing inside discovery, before making commitments with the commercial stakeholders.