When Waiting Turns Observational

This post presents a first-hand account of a delayed food delivery experience, using order tracking observations to explore potential gaps in dispatch visibility and coordination. It highlights the mismatch between customer-facing updates, shop readiness and perceived backend assignment flow, while also noting the often-overlooked position of delivery riders within the system. The narrative is reflective rather than accusatory, focusing on user experience and system transparency.

Disclaimer    This account is based solely on the author’s personal experience and publicly visible order status updates. It does not assert knowledge of internal systems, operational decisions or platform policies. Any interpretations of system behaviour are observational and may not reflect actual backend processes or decision-making logic.

☕️ The Curious Case of the Missing Dispatcher

A delivery story that turned into a small investigation 🔍

We’ve all been there - staring at the app like it’s going to move faster if we will it hard enough, while the ETA quietly loses credibility in real time.

What started as a simple drink order turned into one of those moments where you stop asking “Where’s my order?”

…and start asking:

“What exactly is happening behind the screen?” 🤨

So instead of just waiting - I paid attention.

🧭 The Situation (5W1H)

• What: A simple drink order that turned into a longer-than-expected waiting game
• Where: Ochado
• When: 4 May 2026 🗓️
• Who: A patient-turned-hangry customer (me), a proactive Ochado team and the delivery platform in between
• Why: A delay in driver assignment that wasn’t visible from the customer side
• How: That’s where things got… interesting

🔍 The “How”: When the logs don’t quite add up

Looking at the order updates, the flow didn’t feel like a smooth, automated process.

• A driver appeared to be assigned… and then disappeared almost instantly
• The order then sat unassigned for a noticeable stretch
• Meanwhile, the shop had already prepared the drink and was actively following up

From the outside, it didn’t look like a straightforward “nearest available driver gets the job” scenario. It felt more like the order was being reassigned or reprocessed internally before settling on a final match.

Of course, there may be factors behind the scenes I’m not privy to - but from the outside, this was how it unfolded.

🧊 The real-time reality: The pearls were watching too

While the system was figuring itself out:

• The drink was ready
• The shop was waiting
• And I was negotiating with melting ice and declining optimism 

At some point, you stop tracking minutes… and start tracking texture degradation.

At one point, I wasn’t sure if I was waiting for a driver or watching a limited series unfold episode by episode.

Credit where it’s due - the Ochado team were the real MVPs here. They were actively trying to get things moving, even following up from their side. You could tell this wasn’t on them.

🧠 The quiet disconnect

What stood out wasn’t just the delay - it was the disconnect:

• The customer sees a static screen
• The shop sees a ready order going nowhere
• The process in between… isn’t fully visible

And that invisible gap?

That’s where frustration quietly builds.

🚴‍♂️ The human layer (often overlooked)

One thing that stood out most wasn’t just the delay - it was the human layer in the middle of it all.

Drivers often end up apologising for situations they didn’t create. In reality, they’re the most visible part of a system they don’t fully control. By the time they’re assigned, the delay may have already happened - yet they’re the ones facing customers directly.

It’s an odd dynamic:

visibility ≠ control, but accountability often lands there anyway.

🏁 The Bottom Line

No system is perfect. Delays happen.

But when a ready order doesn’t move - and no one on the outside can see why - it affects everyone:

• Customers wait longer than expected
• Shops step in to follow up manually
• Drivers inherit frustration that started upstream

At its core, it’s simple:

once something is ready, it should move.

If there’s room to improve visibility in the assignment process, even small tweaks could make a meaningful difference for everyone in the chain.

Because at the end of the day, nobody orders a drink expecting a side of suspense… or melted ice as a feature. 🤷‍♂️

Some days you order tea. Some days you end up studying systems.