A look at real engagements from thirteen years across shipping, logistics and media: the problem, the approach, and what it added up to. Every case here is anonymised. Client names stay out of it, the work speaks for itself, and if it sounds close to what you're dealing with, that's what the conversation is for.
A global container carrier's Customer Service and Niche Business teams needed a single owner for two demanding backlogs at the same time: Special Cargo and Reefer. Rather than split the mandate between two internal product owners, the client handed both to one external consultant. The work meant translating complex operational requirements into user stories for cross-functional SAFe and Scrum teams, keeping priorities aligned across both backlogs, and running end-user training and live demos that landed well with global business units.
Result: both product streams run in parallel, with strong adoption after each launch.When the Reefer stream's project manager left unexpectedly, the client needed someone to take over planning, execution, stakeholder communication and risk management, fast, without losing momentum on the Product Owner side. Both roles ran side by side for six months. When it was time to step back, the Reefer stream was handed to a colleague moving into her first PM role, coached through the transition and backed by full documentation so the team felt no disruption from day one.
Result: interim PM mandate covered for six months, with a documented, zero-disruption handover.A media and advertising group operating in more than 100 countries needed to move a data pipeline off a traditional data warehouse and onto a modern cloud lakehouse architecture, without disrupting the teams who relied on it every day. Leading Product Ownership for Data Services meant owning the backlog, briefing data engineers, running sprint coordination in Jira, and working through detailed API analysis across major ad platforms to keep the migration grounded in how the data was actually used.
Result: delivered within 12 months, on time and within the £360,000 budget, with a cross-functional team of five to ten people.A new carrier operating platform touched nearly every part of how the business ran its global operations, which meant the people using it day to day needed more than a manual. Designing and running the change management and training programme meant building materials, running sessions, and working region by region so the rollout felt like a normal part of the job rather than a disruption to it.
Result: 500+ key users trained across multiple regions, with minimal support needed after go-live.After the business was acquired by a larger shipping group, its core operating platform had to be integrated with the acquiring company's own systems without breaking the operations that depended on it daily. That meant managing senior stakeholder relationships on both sides of the acquisition and keeping the technical integration grounded in how the business actually worked.
Result: integration delivered 15% ahead of schedule.Rolling a new carrier operating platform out across Oceania, North and South America and Europe meant adapting to very different regional operations while keeping the implementation consistent enough that every office ended up genuinely ready to use it, not just technically live.
Result: five global rollouts coordinated end to end, each with local readiness built in.Complex, often contradictory logistics processes across regions were a common source of rework once requirements reached the development team. Structuring the analysis more rigorously before handoff, and translating it into clearer, more precise user stories, meant fewer surprises once development started.
Result: requirements rework reduced by 25% across the programme.An intermodal logistics operation needed its ERP capabilities checked against how the business actually worked, not just against the vendor's feature list. That meant analysing gaps, flagging process inefficiencies, managing change requests, and acting as the day-to-day bridge between internal stakeholders and the third-party ERP provider, backed by documentation and QA testing so changes landed cleanly.
Result: clear process documentation delivered alongside QA-tested change requests.Reefer containers fitted with smart devices streamed temperature data through an IoT platform into a customer-facing portal and API, including while containers were still at sea. The Product Owner side of that meant writing requirements around accurate live data, testing it through development, monitoring it in production, and chasing down the cases where a customer's own reports did not match what the platform showed, often working directly with the external IoT provider to resolve it.
Result: a live, API-accessible cold chain data product used by global freight forwarders.Looking for something closer to your own project? Get in touch and I'll walk you through the parts most relevant to what you're trying to do.