Applied · Clear at the BenchChapter 02 of 04
The ApproachThe signature model The Augmented FunctionAI & digital capability The WorkThe case studies The SeriesPacks & toolkits PerspectivesThe throughline The LineHow I got here The Way InHow to work together Get in TouchA 45-min chat
The WorkClear at the BenchThe Counter Lesson
Chapter 02 · The Counter Lesson

How a 19-year-old closes a restaurant that turns over $120k a week.

Quick-service restaurants solved a version of Ironbark’s problem decades ago. They run food safety law, workplace safety law, employment law, cash handling, equipment failure and customer incidents — through shift leaders who are often teenagers, alone, at 11pm on a Saturday.

They don’t do it by making the teenagers read the operations manual. They do it through five design moves worth stealing:

Move 01
Decisions live at stations, not in manuals

The rule is physically present where the decision happens — laminated at the fryer, not filed at head office. Knowledge is placed, not stored.

Move 02
Every decision sorts three ways

Do it. Check first. Call the manager. No shift leader ever weighs ten authority tiers — they sort into three outcomes, instantly.

Move 03
Escalation is a name and a number

“Call the manager” is never abstract. It’s a person, a phone number, a stated timeframe. Escalation designed as a service, not a failure.

Move 04
The record is built into the act

Temperature logged as it’s checked. Waste counted as it’s binned. Documentation isn’t a second job done later — it’s part of the decision itself.

Move 05
You rehearse the play

Shift leaders drill the rare events — the grease fire, the hold-up — before they happen. The first time they run the play isn’t the real one.

“The genius of the quick-service model isn’t simplicity of the business. It’s simplicity at the point of decision — engineered by people who did the hard thinking once, so the person on shift doesn’t have to do it every time.”

That last line is the reframe. The bench at Ironbark is orders of magnitude more complex than fried chicken — which is precisely why its decision supports should be better engineered, not left to memory and goodwill. The complexity belongs in the design work, done once, by people paid to do it. Clarity belongs at the bench.

The frame

Four lanes. Three lights. Three questions.

Everything the case had surfaced condensed into a frame simple enough to say out loud in a corridor, and robust enough to carry the full weight of the instruments behind it. Four lanes name where a decision lives: Technical, People, Research, Commercial. Three lights sort what the decision-maker does with it. Three questions are how anyone sorts a decision they’ve never seen before.

Green
Decide.

This authority is yours at your tier. Decide it, document it as you go, keep moving. No permission-seeking theatre.

The rule: decide → record → done.
Amber
Consult.

Yours to decide — after a named check-in. An HRBP endorsement, a workforce-director consult, an ethics touchpoint. The consult is a step, not a stop.

The rule: check in → decide → record.
Red
Escalate.

Not yours — and knowing that fast is a strength, not a failure. Your job is a crisp brief to a named person, then holding the technical thread while they decide.

The rule: brief → hand up → stay close.
The challenge worth naming out loud

The smartest person at the bench doesn’t like asking permission.

These leaders are selected, trained and rewarded for autonomous expertise. For many, referring a decision to someone else carries a real cost — time, momentum, and quietly, status. Any frame that reads as ask first will be politely ignored by exactly the people it’s for. This one is built the other way around:

i.

Green is autonomy, written down

Most of the map is green or amber — the frame’s first job is to prove how much is already yours, in writing. A card that says “decide and record” is a licence, not a leash.

ii.

The card replaces the asking, not the judgement

Ten seconds against a card beats twenty minutes of email — and beats deciding from memory and carrying the risk personally. The expertise stays exactly where it is. What moves is the checking.

iii.

Red is jurisdiction, not competence

A red light is not a judgement that someone isn’t capable of the call. It marks decisions that were never in the room to begin with — the conflict of interest nobody may assess for themselves. That’s design, not doubt.

Without the card — autonomy’s two bad options
  • Ask — slow, and it costs standing every time
  • Don’t ask — fast, and the risk is carried personally, invisibly, until the day it’s tested
  • Either way, the decision and its defensibility live in one person’s head
With the card — the third option
  • Check — ten seconds, private, no audience and no asking
  • Decide — alone, exactly as preferred, now inside the lines
  • Record — one line, and the defensibility travels with the decision instead of the person
Autonomy without clarity is exposure wearing confidence. The card doesn’t ask experts to be less autonomous — it makes their autonomy defensible.
Question one
Is this mine?
Which lane is it in, and does my tier hold the authority? If the answer isn’t findable in thirty seconds, that’s a design failure — not your failure.
Question two
Who must be in the room?
Name the mandatory consult or endorsement before deciding, not after. Conditions are the amber light’s whole job.
Question three
Where’s the record?
Every light ends in a written trace — a file note, a brief, an approval reference. Built into the act, never a second job for Friday afternoon.
A deliberate constraint There is no fourth light and no fifth question. The moment the frame needs a legend, it has failed the corridor test. All nuance lives one layer down — on the cards, which the next chapter builds.
This kind of work

Augmented partnering, on your organisation’s hardest governance problem. When you’re ready, it starts with a conversation.

Start the conversation →
The People Practice · Au · — Applied · Case Study 02 · Ironbark Back to the front page
Back to the top