Episode Details

Matt Feczko is director of product operations at Ocado, the UK grocery technology company whose warehouse robots and delivery automation now run for retailers including Kroger in the US and Coles in Australia. He spent the first half of his career as a customer-facing product manager, starting on SharePoint and Office at Microsoft before moving to the UK to join Skype and then four different startups over six years. A LinkedIn recruiter's typo — dropping a comma from his job title — led him to Ocado three and a half years ago, where his remit has since expanded to cover both product and engineering operations. Talking to host Randy Silver backstage at MTPcon London, he explains how he replaced Ocado's roadmap planning process, rebuilt its Jira taxonomy from scratch, and built a product management skills framework that other functions have since copied without being asked.

Key takeaways

1. Ocado's roadmap problem wasn't a lack of roadmaps, it was too many of them, rebuilt by hand every quarter. Before Feczko joined, product teams spent two months of every three-month cycle remaking roadmap slides in Google Slides, with no shared document explaining what the company was building or why, and no way for anyone outside the planning meetings to weigh in.
2. He traced that chaos to a single root cause: an inconsistent Jira taxonomy. Different teams used "epics" to mean different things, some nesting parent epics inside parent epics, so there was no agreed definition of what a feature or an initiative actually was. Feczko fixed the hierarchy first, using Denise Tilles and Melissa Perri's book Product Operations as his reference, before touching the roadmap process at all — his team nicknamed the project the "Jira Revolution".
3. The hard part wasn't designing the new structure, it was getting roughly 3,000 developers to adopt it. Feczko frames that adoption problem as the actual job of product operations: not producing an artefact, but changing how a large organisation works, thinks and describes its own output.
4. Two years on, Ocado has replaced its quarterly roadmap slide decks with an internal app, built on top of Jira data, and Feczko is aiming to run the next planning cycle with zero slides. His team also worked with finance to translate operational metrics — such as items added per basket, or driver deliveries per shift — into the financial value each initiative is expected to produce, so planning conversations use the same language as the business case.
5. To answer a question Ocado's product managers couldn't answer for themselves — what "good" looks like in the role — Feczko built a 12-skill framework across four themes, including execution, influence and strategy. He combined an existing Reforge framework with his CPO's own view of the job and his own 15 years of experience, then spent six months negotiating the exact wording with the wider team before any of it shipped.
6. The skill Feczko insisted on calling "storytelling and evangelising", over his CPO's preferred "effective communication", has become the framework's anchor. His argument: the ability to tell a clear story about a product is itself evidence of every other skill, because it requires command of the data, a defined strategy and the ability to prioritise.
7. The framework's real test came when other functions adopted it unprompted. Engineering, roughly 2,000 people, built its own version, as did design and data — keeping Feczko's four themes but writing skill definitions specific to each craft. That took total usage from around 150 product people to roughly 3,000 across the wider organisation.
8. One skill, product adoption, was added specifically because Ocado's product managers didn't see driving adoption as part of their job — they considered their job done once a feature shipped, and expected the business to work out how to use it. Feczko flags this as a gap worth checking for in any company's own