Your Privacy

This site uses cookies to enhance your browsing experience and deliver personalized content. By continuing to use this site, you consent to our use of cookies.
COOKIE POLICY

Skip to main content

Fast Casual: Digital Disrupting Traditional Service

Fast Casual: Digital Disrupting Traditional Service
Back to insights

Our team visits Starbucks, Panera, and Chipotle on a regular basis. We are constantly ordering coffee and lunch during the week. All three companies have mobile applications that help you find the most convenient location, make customizing an order easy and set expectations on when your order will be ready. However, I feel like I am cheating when I mobile order. I feel sorry for all the people standing in line or sitting in the drive-thru waiting. I constantly feel this look of disgust from the traditional, non-tech savvy customer when I walk in, grab my order and walk out. If given a chance, I will mobile order before using the walk up line. The transaction is easier to accomplish and my order is never wrong.

I have made it a point to talk to employees at each place that are directly involved in handling mobile food and drink orders. The story is fairly consistent. There are a few peak times at which the customer experience will degrade until the peak is over. This service issue is a queuing problem that is part staffing and part capacity. The employees mention that their managers can’t over staff because the sales data doesn’t support it or the peak isn’t long enough to justify it. At peak times adding more people to the problem wouldn’t matter because they don’t have the equipment or space to deliver more product.  The Starbucks and Panera appear to suffer from it more than Chipotle, as Chipotle has more traditional customers that stand in line to order.

The traditional walk-in customer feels the pain more than mobile customers. Part of this is because mobile ordering sets expectations around delivery and the traditional model doesn’t. As a regular customer you feel the wait time because it wasn’t what you expected and you can’t see orders queuing because a physical customer doesn’t exist until they show up. I am not sure how you can rectify this issue until everyone adopts mobile ordering and the traditional ordering method goes completely away. I suspect that will happen over the next 5 years for fast food and fast casual. The staff will completely focus on fulfillment and customer service.

As the digital movement continues and companies spend more time and money in their digital offerings like chat bots, SMS bots, mobile applications and voice automation, they can’t overlook the impact to traditional customers. In fact, that personalized experience if focused on, could become a competitive asset that other digital only channels miss. The risk is if your digital channels aren’t strong, you will miss out on an entire customer segment that expects exceptional digital service.

If you are considering the impact of your digital solutions on your traditional offering ask yourself the following 3 questions:

  1. If your digital offering is a success, what are the potential impacts to your traditional users?
  2. Through automation, what personal touches are lost with the customer that are value add? How do you recapture them or make sure the digital channel replicates or reinforces your brand experience?
  3. How will you motivate traditional customers to embrace digital channels or not feel alienated by the digital experience?

Ultimately, whether your customers choose to interact with your brand in person, on-line or through a mobile ordering application, you want them to have a great experience, that aligns with your brand, every time.  The companies that win my business get that, and continue to improve my experience at every touch point.Andy Frank

About Andy Frank

Andy Frank is our Founder and CEO. Since founding UDig, he has had the opportunity to build a business fueled by finding clients the right technology solutions to solve their business challenges.

Digging In

  • Software Engineering

    When There’s Too Much to Fix: How Smart Prioritization Unlocks Revenue at Scale

    Every operations team has a backlog. The question isn’t whether you can clear it — it’s whether you’re clearing it in the right order. For most teams, the honest answer is no. And that gap between the order work gets done, and the order it should get done is quietly costing organizations millions. The Volume Problem High-volume exception processing shows up across […]

  • Software Engineering

    Creating Reusable Code Templates to Reduce Client Project Startup Time

    In consulting, one of the least visible but most expensive phases of a project is the beginning. Teams can spend days or weeks setting up repositories, agreeing on structure, wiring basic infrastructure, and solving problems that have already been solved many times before. Code templates are a practical way to reduce overhead while improving consistency. […]

  • Software Engineering

    Player Three Has Entered the Game: How AI Is Finally Bridging the Divide Between Design and Engineering

    As AI begins to become more prominent in our day-to-day lives, I find myself in a unique position. As a practicing software engineer and UI/UX designer, I am genuinely happy to see the introduction of AI tools begin to take shape in our industry. But more importantly, I am happy to start seeing the effects it is having on what has historically been a pretty challenging relationship: the […]

  • Software Engineering

    The Disappearing Middle of Software Work: Why the Bookends – Strategy & Impact – Matter Most Now

    Here’s a question nobody in enterprise software wants to sit with: what happens to the middle? Not the middle of the org chart. The middle of the work. The vast, expensive layer of effort that has defined enterprise software delivery for thirty years—translating what the business wants into working code. The requirements-to-implementation pipeline. The “build phase.” […]

  • Software Engineering

    Zero-Code Telemetry with OpenTelemetry’s OBI

    Full distributed tracing and exception capture for any application — without writing a single line of instrumentation code. View the source code on GitHub → The Premise Observability is essential for understanding what’s happening inside your services, but instrumenting an application by hand — adding trace spans, logging calls, and metric counters throughout your codebase […]

  • Software Engineering

    Building a Consultant in the Trenches: How Playing Offensive Line Shaped My Consulting Career

    People often ask me the same question when they find out that I played college football: “Do you miss it?” On the surface, it’s a bad question with an obvious answer. Yes. However, if I give myself a minute to sit with that question, the answer is more nuanced. Yes, I miss playing football, but […]