One Swiggy Order, Two Product Lessons

Disclaimer: This article is based on a personal experience and observations as a Product Designer. I don’t have visibility into Swiggy Instamart’s internal data, operational constraints, or product decisions. My intention isn’t to criticize the team behind the product, but to discuss how seemingly small product decisions can shape customer perception and business outcomes.

Most days, I place an order on Swiggy Instamart and completely forget about it until the doorbell rings.

I rarely open the order tracking page. I don’t obsess over where the delivery partner is. I don’t calculate how many minutes are left.

Because most of the time, I don’t need to. Yesterday was different.

I urgently needed the items I had ordered, so I found myself constantly tracking my delivery. And that’s when I noticed two product decisions that completely changed my experience — one operational and one within the product itself.

Route Optimization: Great Strategy… But Is It Always Great UX?

While tracking my order, I noticed something unexpected.

The delivery partner had almost reached my home. Just a few seconds away (hardly a minute away)

And then… He turned around.

I watched his location move farther away from my address while my delivery time kept increasing.

Naturally, I called him.

He explained that there was heavy traffic near my location. Instead of waiting there, he chose to complete a few nearby deliveries (within roughly a 3 km radius) before returning to mine.

At first, I actually thought this was smart.

Optimizing routes, reducing idle time, batching deliveries, and maximizing fleet efficiency are exactly the kinds of operational problems quick-commerce platforms should solve.

From a business perspective, it makes complete sense.

But from a customer’s perspective? Watching your delivery partner reach your street and then drive away feels incredibly frustrating.

Not because the strategy is wrong. But because your expectations have already been set.

The Product Question That Stayed With Me

Once the frustration settled, the Product Designer in me started asking different questions.

Was route optimization the problem? Probably not.

The real question is something much bigger.

How are these optimization decisions being executed?

1. Was the rider making that decision independently?
2. Was the system recommending it?
3. Was it incentivized?

Or was it exactly how Swiggy intended the feature to work?

I genuinely don’t know. But whichever is true, one thing becomes clear:

A strategy is only as good as its execution.

If delivery partners interpret route optimization differently, customers experience inconsistency.

If the system itself chooses to delay deliveries, then customer expectations need to be managed much better.

Either way, the customer only sees one thing:

“My order was almost here… and then it wasn’t.”

As product teams, we spend months designing systems and optimizing metrics.

But one aspect often gets overlooked:

Execution shapes perception.

Even the smartest operational strategy can feel broken if customers don’t understand why it’s happening.

Which raises an interesting question:

Can a company truly benefit from an optimization strategy if customers perceive it as a worse experience?

The second observation came from the Order Details page itself.

The Order Tracking Experience

The second observation came from the Order Track page itself.

I wasn’t there to browse Ads/Offers. I wasn’t there to discover new products. I was there for one reason — To track my delivery partner.

The map appeared for about seconds (5 seconds to be precise).

Then it disappeared and The screen swapped. Advertisements replaced the tracking view.

Every single time I navigated back to check my rider’s location, the same thing happened.

As someone waiting for an urgent order, those ads felt less like promotions and more like interruptions.

The job-to-be-done of that screen is simple:

Reduce uncertainty. Answer one question — “Where is my order?”

Instead, the product momentarily shifted my attention toward sponsored content. Will those ads generate impressions?

Probably.

Will advertisers be happy?

Most likely.

But should monetization compete with the user’s primary goal at that particular moment?

That’s where I think the conversation becomes interesting.

Because users who repeatedly open the tracking page aren’t browsing.

They’re anxious. They’re seeking reassurance.

And every unnecessary interruption increases that anxiety.

Sometimes, optimizing one business metric quietly hurts another.

My Biggest Takeaway

This experience reminded me that product design isn’t only about interfaces. It’s about orchestrating an entire experience.

Route optimization.

Customer expectations.

Delivery operations.

Communication.

Tracking.

Monetization.

Every one of these decisions influences how users perceive the product.

As Product Designers, we often talk about balancing business goals and user needs.

But I think there’s a third pillar that deserves equal attention.

Execution.

Because even a brilliant strategy can feel like a bad experience if it isn’t communicated or executed in a way users understand. And that’s often where great products separate themselves from good ones.

What Do You Think?

I’d genuinely love to hear perspectives from people who’ve worked in logistics, quick commerce, or delivery products.

• If a rider is only a few seconds away, should the system allow them to move to another delivery first?
• Should the tracking page prioritize ads while a customer is actively tracking an order?
• And where do you think the responsibility lies — product design, operations, incentives, or communication?

Curious to hear different viewpoints.