Episode #22: Balancing Marketplace Demand and Rider Experience with Papatya Sutcliffe

Food delivery looks simple at the door, but the product decisions behind it involve shifting demand, independent riders, cost, timing, and food quality. In Episode 22, Papatya Sutcliffe shares how she approaches that system at Deliveroo and what her path across aerospace, energy, and delivery taught her about product management.

What you'll learn

• Why core product skills transfer across very different industries

• How a delivery marketplace balances customer, rider, and network outcomes

• When financial and non-financial experiments answer different questions

• How to guide stakeholder disagreement without rushing to a false consensus

Product judgment travels across industries

Papatya began her career in a commercial graduate role before becoming chief of staff to the head of a data science and technology division at Rolls-Royce. That position placed her close to both business concerns and technical work. She discovered product management as a discipline operating at that intersection, then moved into work with startups and scale-ups building software propositions around company data. At BP, she later led the roadmap and delivery of a virtual payment product for smaller fleets in Central Europe.

Moving from large industrial companies to Deliveroo changed the organizational setting, but not the foundations of the job. In each environment, the product manager still has to identify value, prioritize opportunities, and determine the smallest useful release. The major difference is the culture in which those decisions happen. Working inside established companies also gave Papatya practice with stakeholders who held firm views or were reluctant to change. That experience helped her build patience and resilience for later product discussions.

For product teams, the lesson is practical: domain knowledge matters, but product judgment is portable. A new industry still rewards clear outcomes, careful prioritization, and the ability to connect commercial goals with technical possibilities.

Balance the whole marketplace, not one metric

Papatya works on matching Deliveroo's logistics capacity with a highly variable order profile. The problem becomes especially visible during peaks such as a rainy Friday night in London. Orders may surge, while riders remain self-employed and choose when and where they work. The team cannot treat supply as a fixed resource. It has to understand demand, forecast pressure, and align incentives while preserving rider flexibility.

That creates several outcomes to balance. Customers want affordable orders delivered quickly and in good condition. Riders want fair pay, useful information, and control over their work. The network needs to operate efficiently. Improving one dimension without watching the others can produce a poor overall result.

This is why product roadmaps in a marketplace should describe the system being improved, not just a sequence of features. A local change to pricing, guidance, or allocation can influence rider behavior, order coverage, cost, and customer experience at the same time. Teams need shared metrics that reveal those trade-offs rather than hiding them.

Match the experiment to the behavior

Papatya describes both financial and non-financial ways to improve supply and demand matching. On the non-financial side, the team can help riders understand the best places and times to work. A clearer interface and better educational guidance can make existing information more useful. She mentions an algorithm called Sherlock that shows busy times and locations, creating opportunities to test how effectively that information is communicated.

Financial experiments ask a different question. A team might move budget from one period to another, offer more at a peak time, and compare the incremental order volume with the added cost. The goal is not simply to increase activity. It is to learn which lever aligns rider choice with customer demand most efficiently while maintaining a fair rider experience.

The broader takeaway is to avoid treating every behavior problem as a pricing problem. Sometimes people need a stronger incentive. Sometimes they need clearer, more timely information. Product teams should test each mechanism against the outcome they actually want.

Let disagreement reveal the real decision

Stakeholder alignment is one of Papatya's harder responsibilities. Earlier in her career, strong and conflicting opinions could pull her from one position to another. She came to see that developing an informed view takes time. Listening before judging, examining the data, and observing how initial features perform are part of building that view.

Her approach is not to end disagreement immediately. A product manager can let different perspectives surface, ask neutral questions, and listen for the true points of contention. The next step is to return the group to agreed outcomes and metrics. Some disagreements affect those outcomes directly; others can be set aside. The skill lies in knowing when the debate is still producing useful information and when it is time to draw it to a conclusion.

Episode 22 offers a grounded look at product work inside a complex marketplace. Listen to the full conversation for Papatya's perspective on transferable product skills, experimentation, and making balanced decisions with a cross-functional team.