Leadership & Operations frameworks

Marketplace operations produce a constant stream of urgent signals: driver disputes, SLA breaches, cancellation spikes at peak hours, a compliance deadline that moves. Most of it is noise around a much smaller number of real patterns. Emotional regulation is the discipline of telling the two apart before acting — and of not passing the volume of my inbox on to the team.

In practice

• Separate the decision from the reaction, especially on escalations that arrive angry
• Read the pattern across a week of tickets before redesigning a process on the strength of one
• Hold a neutral tone with fleet partners and drivers when the conversation is already hot
• Absorb pressure coming from above instead of passing it down unfiltered
• Be the stable point during an incident, when everyone else is improvising

Marketplace operations run on feedback travelling between people who have no authority over each other: Ops and Product, Support and Engineering, and fleet partners who are commercial counterparts rather than employees. Sincere candor means saying the thing that needs saying — to a partner whose performance is sliding, to a product lead whose feature is creating operational friction, to a team member whose quality has dropped — with the evidence attached, and without diluting it into politeness.

In practice

• Lead with the observation and the number, not with the interpretation
• Give feedback while it is still one incident, not once it is a pattern and a grievance
• Tell a fleet partner their numbers are slipping before it becomes a contract conversation
• Separate a hard message from a harsh one — directness is not a licence
• Ask the uncomfortable question in the meeting, not in the corridor afterwards

Regulated fleet work puts you in front of drivers, fleet operators, corporate clients and authorities at the same time — and each of them can verify what you told the others. Unimpeachable character means commitments hold once they turn out to be expensive, and decisions look the same whether or not anyone is checking. In a compliance-first context that is not a values statement; it is the operating requirement.

In practice

• Keep private conduct matching the public version of it
• Honour a commitment once it has become inconvenient, or renegotiate it openly and early
• Own mistakes where they were made, and give credit in the same room
• Never trade a short-term optic against long-term trust with a partner or a regulator
• Give every audience the same account of the same situation

Supply strategy, regulatory requirements and cross-functional dependencies each arrive in their own vocabulary, and the ambiguity between them is where operational time disappears. Clarity means compressing that until someone can act without re-deriving the context every time: define the outcome before the method, and write the decision down instead of only saying it in a meeting.

In practice

• Define the outcome and how it will be measured before agreeing the method
• Write the decision down — with the owner and the reasoning, not just the task
• Use language that survives the trip from Ops to Product to a fleet partner
• Turn a regulatory requirement into a concrete operational rule somebody can follow
• Cut meeting time by circulating the context in advance

In marketplace operations the failures that cost most are the ones that fall between functions: an order that fails, a driver who never activates, a regulatory requirement that changed and nobody mapped. Ownership means the useful question is not whose scope this sits in but what has to happen now — and that a handover only counts once the other side has confirmed they have it.

In practice

• Escalate with a proposed decision, not with an open question
• Close the loop on problems outside my scope instead of routing them onward
• Turn “not my job” into “here is who owns it, and I have confirmed they do”
• Take the blame in public and hand the credit over in public
• Treat a recurring gap between two teams as something to design away, not to chase weekly

Define expectations, priorities, ownership, and how success will be measured — before the work starts, not after it goes wrong.

In practice

• Set clear goals and expected outcomes
• Define KPIs or observable success criteria
• Clarify decision rights and responsibilities
• Connect individual work to team objectives

Understand what the person needs to succeed and remove the barriers that are not theirs to solve.

In practice

• Regular 1:1s
• Understand motivation and individual goals
• Remove blockers
• Create psychological safety to surface problems
• Give autonomy over how outcomes are achieved

Cross-reference: Coaching is the key mechanism of Support — it is how support becomes capability instead of rescue.

Performance requires follow-through, not only clarity and support. Accountability is what makes the first two mean something.

In practice

• Review commitments consistently
• Recognize when commitments are met
• Address gaps early
• Use evidence rather than assumptions
• Agree corrective actions and follow up

Cross-reference: Corrective Feedback structures the follow-up conversation so the gap turns into an agreed next step.

Development is not simply “sending people to training.” The goal is progressively increasing the person’s ability to solve problems and make decisions independently.

In practice

• Identify capability gaps
• Coach through real problems
• Give progressively larger ownership
• Delegate decisions, not only tasks
• Review decisions and reasoning
• Create opportunities to practice new capabilities

• 01UnderstandUnderstand the person’s perspective, context, and reasoning before giving advice.
• 02QuestionUse questions to help them examine the problem, assumptions, options, and consequences. What do you think is causing this? What options do you see? What would you do if I weren’t available?
• 03ChallengeTest their reasoning. Surface blind spots and challenge assumptions without taking ownership of the problem away from them.
• 04CommitConvert the conversation into a decision or a concrete next action that the person owns.
• 05ReviewReturn to the decision. Evaluate both the outcome and the reasoning: what happened, what did you learn, what would you do differently?

• 01ObserveState the factual behavior or performance gap without assigning motive.
• 02ExplainDescribe the impact and why the issue matters.
• 03ListenHear the employee’s perspective and diagnose the cause — the natural point to apply Skill / Will / System.
• 04AgreeDefine the corrective action, the expectation, the support required, the owner, and the timeline.
• 05Follow upReturn to the commitment. Without this step the conversation was information, not management.

The same symptom — missed deadlines, quality gaps, escalations — has three very different causes, and each one calls for a different response. Applying the wrong one damages the person and leaves the problem in place.

Break strategic objectives into measurable operational outcomes.

In practice

• Convert broad objectives into outcomes the operation can actually understand
• Define a measurable direction — “reduce onboarding time while maintaining activation quality” rather than “improve Service Delivery”

Turn outcomes into explicit commitments.

In practice

• Every meaningful commitment needs an owner
• Clarify what they control and what they depend on
• Shared responsibility without a primary owner becomes no responsibility

Create visibility through milestones, KPIs, dashboards, or operating reviews.

In practice

• Dashboards, KPIs, milestones, weekly reviews
• The purpose is early detection and informed intervention
• Not micromanagement — tracking exists to enable action, not to report status

Do not simply report the deviation. Intervene.

In practice

• Remove blockers, change priorities, reallocate resources
• Coach, escalate, adjust timelines, or redesign the mechanism

Map the process, listen to the people inside it, collect evidence, establish a baseline, and separate symptoms from root causes before proposing anything.

In practice

• Listen to customers and frontline employees
• Map the process or funnel end to end
• Collect facts and operational data
• Locate bottlenecks, failure points, and handoff problems
• Separate symptoms from root causes
• Establish a measurable baseline before changing the system

A diagnosis usually produces more problems than capacity. The decision lens is Impact × Frequency × Urgency — how much the outcome moves, how often the problem occurs, and how fast it has to be addressed.

Operational KPI buckets

Business lens

Operational movement only matters if it reaches the business. These are the outcomes the four buckets above are supposed to serve.

In operations it is easy to assume that an operational fix will produce better retention or better economics. In reality that connection has to be evidenced, not assumed. We prioritise knowing we are moving an operational indicator that could affect a business outcome — and we say it that way until the data says otherwise.

Design the mechanism that changes the outcome. A mechanism is rarely just software.

The mechanisms available

• Processes and SOPs
• Playbooks and decision rules
• Ownership and escalation rules
• Dashboards and operational tooling
• Automation
• Meeting and review rhythms
• SLAs and service standards
• Training and enablement
• Customer communication protocols

Implementation is not completion. A process is not successfully implemented until it is monitored, adopted, and owned.

In practice

• Monitor KPIs and exceptions
• Review performance at a defined cadence
• Enforce agreed standards
• Follow up on commitments
• Coach where execution is weak
• Adjust when assumptions prove wrong

Service Delivery is the operational discipline of moving a customer from commercial commitment to successfully delivered service. It is considerably broader than ticket handling.

Typical lifecycle

Contract signed, onboarding, order management, logistics, technical setup, activation, go-live, clean handover.

Ownership means ensuring the system keeps moving and that nothing important becomes ownerless between two of those stages.

• 01PromiseEstablish a clear baseline: scope, timeline, SLA, responsibilities.
• 02MeasureCompare actual delivery with the promise — not with a general impression of how it went.
• 03CommunicateOperational transparency. Customers should not have to chase anyone for status.
• 04ImprovePerformance data feeds process improvement — this is the handoff back into Operational Improvement.

Service Delivery depends on Engineering, Product, Customer Success, Support, Logistics, and external partners. The leader is accountable for the outcome without hierarchical authority over most of the contributors.

In practice

• Establish a shared outcome
• Map dependencies and decision points
• Clarify ownership across functions
• Align priorities and deadlines
• Surface and remove blockers
• Escalate when local coordination is insufficient
• Drive decisions and closure

• 01UnderstandKnow the system functionally: what it does, its components, its dependencies, and how it behaves when it fails.
• 02DiscussHold substantive conversations with engineers about APIs, integrations, authentication, and dependencies.
• 03TranslateConvert technical constraints into operational decisions the business can act on.

This is not about writing code. It is about understanding the system well enough that technical reality and operational decisions stay connected.

Mature Service Delivery reduces dependence on customers as the monitoring system. Every incident a customer reports first is a gap in detection, not only a gap in the product.

Receive, update, verify.

Technical services depend on external operators and APIs. When an external party changes a parameter, internal systems must reflect the change — and somebody has to confirm that they did. Skipping the verification step is how silent, delayed failures are created.