Skip to content
3 min read

Bar Operational Intelligence: A Definition and a Playbook

Four clauses. Each one rules something out.

Matty HerreraBy Matty Herrera, Founder & CEO, Delta Kinetics

Published Updated

Delta Kinetics title card for the article Bar Operational Intelligence: A Definition and a Playbook
On this page
  1. Key takeaways
  2. What is bar operational intelligence?
  3. How does it differ from reporting and business intelligence?
  4. The playbook, without software
  5. Where the honest limit is
  6. Frequently asked questions
  7. Sources

Key takeaways

  • Bar operational intelligence is turning an operational data stream into a specific action, for a specific role, in time to change the outcome, and recording what happened.
  • Each clause excludes something: reporting, dashboards, month end analysis and alerting products without an outcome record.
  • Reporting describes, business intelligence answers questions you asked, analytics finds patterns, and operational intelligence continues to action, owner and outcome.
  • The playbook needs no software: one stream, like with like, the largest explicable gap, ask the people there within two days, one action, then check it next week.
  • The honest case for tooling is removing the weekly assembly step that kills the habit, not noticing what a competent operator would miss.

Frequently asked questions

What is bar operational intelligence?

It is the practice of turning an operational data stream into a specific action, assigned to a specific role, inside the window where the action can still change the outcome, and recording what happened next. Each of the four clauses excludes something, including things this company sells.

How is operational intelligence different from business intelligence or analytics?

Reporting describes what happened after the fact. Business intelligence lets you interrogate it but only answers questions you thought to ask, and analytics stops at the pattern. Operational intelligence continues to the action, the owner and the outcome.

Can I run operational intelligence at my bar without software?

Yes. Take point of sale transactions, compare this Friday against the last four Fridays by product, hour, section and comp, and find the largest gap with a plausible internal cause. Ask the people who were there within two days, set one action for one role for one week, and check it first next week before looking at anything new.

How much time does the manual playbook take?

About thirty minutes a week plus the assembly. The assembly, getting seven days of transactions into a shape where shifts are comparable, is most of the work and has to be redone every week. It is the reason the routine tends to die around week four.

Do I need a tool like CoreTAP to do this?

Not necessarily. An operator with the discipline and the hours does not need it, and should be told so. The case for tooling is that it removes the assembly step that kills the habit, not that software notices what a competent operator would miss.

Sources

  1. Murre and Dros (2015), Replication and Analysis of Ebbinghaus' Forgetting Curve, PLOS ONE
  2. Bar Society: Bar Analytics (research page)
  3. Toast Support: Product Mix (PMIX) Report Overview