Platform Product Management
Platform decisions connect the experience people see with the structures and services underneath it. My work spans content management, hotel systems and commerce. I make the moving parts understandable: which capabilities are shared, what depends on them and how a change affects the people and products around it.
01 / The practice
How I work.
Map the system around the task
I start with the user's workflow and follow the information through the services that support it. Making dependencies visible helps the team see where a local problem comes from and who needs to be involved in changing it.
Find the right shared foundation
I look for repeated needs and opportunities to make behaviour more consistent. A shared capability should reduce repeated work while still supporting the differences that matter to individual products. The boundary deserves as much attention as the capability itself.
Sequence change around its effects
Platform work rarely happens in isolation. I consider existing consumers, data and operational workflows when shaping a rollout. A technically cleaner system is most valuable when the teams and users around it can make a successful transition.
02 / Something useful
What comes out of it.
- A system and dependency map
- Shared capabilities with clear boundaries
- A sequence for adoption and change
03 / In practice
The work behind the words.
A shared CMS foundation
The CMS refactor brought siloed implementations into a reusable core, improving consistency and creating a stronger base for bringing new products onto the platform.
Managing multiple hotel properties
The central reservation system brought rates, invoices, reservations and accounting into a portfolio-level workflow.
Connected inventory in BrickStack
The inventory product connects identification, valuation and collection workflows with external catalogue and marketplace APIs.