In mid-January 2026, Blinkit dropped "10-minute delivery" from its branding after Labour Minister Mansukh Mandaviya raised delivery workers' safety with quick commerce companies (ThePrint, Jan 2026). Its parent company Eternal said its business model was unchanged. Within a day, reports said Zepto, Swiggy and Flipkart were changing their messaging as well (The Week, Jan 2026), and Zepto CEO Aadit Palicha called the ministry's suggestion a fair one (YourStory, Jan 2026).
The label went away. The work behind it did not. Dark stores still have to pick, pack and dispatch fast, and customers still expect their order quickly. For anyone interested in operations, this episode is a clean case study in the difference between a promise made to customers and the process built to keep it.
Promise, service level and process
Operations people separate three things that marketing often blends:
- The promise is what the customer is told: "10 minutes", "delivered tomorrow", "callback within an hour".
- The service level is what the operation commits to internally and measures: for example, a target share of orders dispatched within a set time, with a stated buffer.
- The process is how the work actually happens: how orders reach the picker, how the store is laid out, how many people are on shift, what happens when it rains.
When the promise is fixed, the process has to absorb all the variation. Weather, traffic, a sudden spike on a cricket final evening, a picker calling in sick: every one of those lands on the people doing the work. When the promise has room in it, the service level can be set honestly and the process can be designed to meet it most of the time without pushing anyone to cut corners.
The ministry's intervention was about worker safety. But the operational lesson applies to any business: a customer promise should come out of what the process can reliably do, not the other way round.
What operations work looks like day to day
An operations associate or analyst at a quick commerce company, a food delivery firm, an e-commerce warehouse or a hospital chain spends their time on questions like these:
- How long does each step take, and where do orders wait? (Process mapping, timestamps.)
- How many people and slots do we need per hour to hit the service level, given expected demand? (Capacity planning.)
- Where are we wasting time or effort? (Walking distance in the store, double handling, rework.)
- When something goes wrong repeatedly, what is the root cause? (5 Whys, a basic DMAIC cycle.)
- What does one order cost us, all in? (Unit economics: picking labour, packaging, delivery cost, discounts.)
- Is the process written down so a new hire on the night shift does it the same way? (SOPs.)
A realistic example
Imagine you join the operations team of a grocery delivery business in Hyderabad with 12 dark stores. One store keeps missing its dispatch target between 7 and 9 pm.
You start by pulling a week of order timestamps: order placed, pick started, pick done, packed, handed to rider. Pick start is fine. The gap is between "pick done" and "packed". You go to the store and watch. Two packers share one bag station, and cold items are stored at the far end, so pickers bring frozen goods last and orders queue at packing. You propose moving cold storage closer to packing and adding a second station during the evening peak. You write the new layout into the store SOP, then track the same timestamps for the next two weeks to see if the gap closes.
That is operations: data, observation, a specific fix, and measurement afterwards.
Skills that are rising
- Process mapping from real timestamps, not assumptions.
- Capacity and service-level math. Demand per hour, time per task, people needed, buffer.
- Root cause analysis with discipline.
- Unit economics. Knowing what one order earns or loses, and which lever moves it.
- SOP writing that a new team member can follow on day one.
- Metric design. Choosing measures that reward the right behaviour.
How to start
- Pick a service you use often: a canteen, a pharmacy, a courier counter. Time each step for ten customers and draw the process on paper. Mark where people wait.
- Estimate how many staff the counter needs at its busiest hour to keep waits under a target you choose. Write down your assumptions.
- Use the 5 Whys on the longest wait you saw.
- Write a one-page SOP for one step and give it to a friend to follow. Fix whatever they get wrong.
Our operations courses cover this work.
Business Operations Master covers inputs, process and output, operating models and OKRs, and cross-functional handoffs in week 1. Week 2 is process improvement: mapping a process, the seven wastes of Lean, and root causes with 5 Whys and DMAIC. Week 3 covers reading a P&L and a lesson titled "Unit Economics: How Much Do We Make on One Order?". Week 4 is scaling: signs of strain, writing SOPs, and capacity, service levels and a dashboard for scale. The assignments include mapping a process, finding waste and fixing a root cause, and a scale-up plan.
Product Management Essentials is the companion if you lean toward product and growth. Its last week covers choosing a North Star and input metrics, funnels and retention, and running experiments. That is useful for anyone who has to decide what a promise to customers should be and how to test it.
Who this is for: BBA, MBA and engineering students interested in operations, and early-career people in e-commerce, quick commerce, logistics, healthcare or service businesses who want to run processes, not just follow them.
Who this is not for: anyone looking for a deep dive on gig worker law or platform policy. These courses are about designing and running operations well.
The honest takeaway
Dropping the "10-minute" tagline did not change what customers want or what dark stores have to do. It highlighted that the promise and the process need to match, and that matching them is operations work.
Start with Business Operations Master for process, capacity and unit economics, and add Product Management Essentials if you want the metrics and experiment side. Getskilled membership (₹99 for 90 days) includes live webinars, recordings and the members' WhatsApp community.
