『Tech Fatigue: Why Ordering a Burger Shouldn't Require an Onboarding Process』のカバーアート

Tech Fatigue: Why Ordering a Burger Shouldn't Require an Onboarding Process

Tech Fatigue: Why Ordering a Burger Shouldn't Require an Onboarding Process

無料で聴く

ポッドキャストの詳細を見る

"I miss when ordering a burger didn't require an onboarding process." That's the line that kicked off this episode, and once you hear it, you can't unsee it: download the app, verify your email, allow tracking, scroll for the promo code, then order your food. Greg and Spiro dig into where all this tech actually came from, and whether it's helping restaurants or quietly wearing everyone out.

Neither of them is anti-tech. Spiro's whole business is built on the tech and service side of hospitality. But they call out something most operators feel and few say out loud: a lot of restaurant software gets sold on hype, not results, "all sales, no service," and then the operator is left training staff on a tool that solves a problem it also half creates. They get into why so much of this becomes a task instead of a tool, and the two questions worth asking before you buy anything: would a guest actually use this, and would they be excited to.

Greg shares a real example: a full-service restaurant that rolled out QR code ordering during COVID, and watched servers quietly stop serving because they figured the app was doing their job for them. The fix wasn't more tech or less tech. It was doubling down on hospitality around it, servers walking guests through the app while still bringing full service, and those same servers ended up handling more tables than the ones working without it. The problem was never the technology. It's when tech replaces the humans instead of freeing them up.

In this episode:

  • Why "it's not a tool anymore, it's a task" is the phrase restaurant owners keep repeating, and what's actually behind it
  • The real cost of stacking new software on top of software, and what happens when only one person on staff knows how to run it
  • How to spot a vendor selling "all sales, no service" before you're locked into a contract
  • The QR code story: what happens when a restaurant assumes the app is doing the server's job
  • Two questions to ask about anything in your tech stack: would a guest use it, and would they be excited to
  • Why the operators pulling ahead build their tech around their culture instead of reshaping their culture around the tech
  • The takeaway: use tech to enhance hospitality, never to replace it

Whether you think restaurants need more tech or less, this episode makes the case that the real question isn't how much technology you're running. It's whether it's helping your team connect with guests, or getting in the way of it.

Agree? Disagree? Greg and Spiro want to hear it in the comments.

🎧 Catch every episode of Ride or Die at gphospitalitypartners.com/podcast, or subscribe on Apple Podcasts, Spotify, YouTube, and Amazon Music so you never miss one.
📈 Ready to build a team that can run your tech stack without losing the hospitality that makes guests come back? Learn about Greg's Leadership Circle: gphospitalitypartners.com/leadership-circle
📖 Grab Greg's books: gphospitalitypartners.com/books

#RestaurantIndustry #RideOrDiePodcast #RestaurantTech #HospitalityIndustry #RestaurantMarketing #TechFatigue #CustomerExperience

adbl_web_anon_alc_button_suppression_t1
まだレビューはありません