Case 02 / Transformation Design
From a screen network to sellable inventory
Large retail organisations have screens, players and content processes. That is not yet a product anyone can sell.
- Role
- Head of Product Retail
- Context
- Large retail organisations, retail media
- Reading time
- 4 minutes
Photo to followPhoto for this case
Executive Summary
01 / 07A readiness model that brings together technical infrastructure, inventory data, operating logic and commercialisation — and pulls the uncomfortable decisions in front of the first campaign instead of behind it.
The situation
02 / 07The screens exist. Sellable inventory does not.
Large retail organisations usually have screens, players and functioning content processes already. That regularly produces the expectation that retail media is essentially a sales task: the space exists, now someone just has to sell it.
Work on concrete initiatives showed something else. A viable start required technical foundations, location and inventory data, time and slot logic, booking models, reporting and a possible programmatic connection to be thought through together — and beforehand.
In place
- Screens
- Players
- Content processes
Needed for launch
- Location & inventory data
- Time & slot logic
- Booking models
- Reporting
- Programmatic connection
= not just a sales task
The real problem & My mandate
03 / 07The gap lies between vision and operability.
The gap was not between vision and technology but between vision and operability. Retail media was understood as a revenue opportunity. The preconditions for scalable booking, playout and proof of delivery were not.
This is where such initiatives fail without anyone noticing. Without standards, manual exceptions appear. Exceptions produce incomplete data. Incomplete data makes impact measurement contestable — and without defensible impact measurement no advertiser renews a budget.
- 01No standards
- 02Manual special cases
- 03Incomplete data
- 04Contestable measurement
- 05No renewed budget
My mandate
Translate the technical, data-related and organisational requirements into an understandable enablement model — and derive from it workshops and concrete decision questions that customer teams can actually answer.
Approach
04 / 07Four steps from device to operating product
- A
Develop a readiness pyramid
The preconditions were structured into layers that build on each other: hardware and screens, inventory and location data, time and slot logic, commercialisation model, reporting, programmatic connection. The sequence is the substance of the model: sell layer four while layer two is missing and you create commitments operations cannot keep.
- 01Hardware & screens
- 02Inventory & location data
- 03Time & slot logic
- 04Commercialisation model
- 05Reporting
- 06Programmatic connection
- B
Operationalise inventory
A screen was no longer treated as a device but as a clearly describable, filterable and bookable surface. That sounds like a data modelling question and is in fact a product decision: only this definition turns hardware into something you can put in a media plan.
- 01Device
- 02Describable
- 03Filterable
- 04Bookable
- C
Pull decisions in front of the launch
Questions about share of voice, booking groups, sellable time and failure rules were moved ahead of the first campaign. Every one of them becomes more expensive after launch — not technically, but politically, because by then expectations exist in the market.
Decided before the first campaign - Share of voice
- Booking groups
- Sellable time
- Fallback rules
- D
Treat technology, data and commercialisation as one operating model
Not as three sub-projects with interfaces, but as shared accountability. The most common cause of stalling transformations is not missing software but a missing shared role model.
One operating model
- Technology
- Data
- Commercialisation
The trade-offs
05 / 07Three tensions before the first campaign
- Fast pilotsolid foundation
An early start creates learning and momentum, but must not produce uncontrollable data and operating deficits that can only be fixed by migration later.
- Standardisationlocal reality
A shared data model has to allow local specifics without disintegrating into one-off solutions. Every exception granted is a bet that it stays the exception.
- Direct salesprogrammatic
The operating model must enable different commercialisation routes and still set clear priorities. Serving both equally consumes capacity that is not there at the start.
Outcome
06 / 07- 01
The readiness model became the shared language between technology, data, operations and commercialisation — four areas that had been discussing the same things in different vocabularies. The preconditions for piloting and scaling could be settled up front rather than mid-flight.
- 02
Out of it came a workshop approach that prepares customer teams for concrete decisions before campaigns go live. The value lies less in the model itself than in the fact that it asks the awkward questions early.
What I took from it
07 / 07In transformations, the missing shared data and role model is almost always more critical than the software.
The reflex to solve an operating problem with a tool is particularly strong in technology companies — after all, you own the tool. That is precisely why the product side has to slow things down here rather than speed them up.
Competences shown
- Transformation Design
- Operating Model
- Customer Enablement