Australian hospitality is full of good people working hard inside systems that have quietly become more fragile. Food Game Media exists to name what changed, explain why effort alone stopped working, and help the industry redesign the game so it's actually winnable again.
Julian Blok spent sixteen years in investment banking — across Goldman Sachs, Morgan Stanley, Bankers Trust, and Citibank — doing what banking teaches you to do: find the pattern underneath the noise. Strip out the narrative. Ask what's actually driving the number.
Then in 2014, he did what any sensible person would do at the peak of a banking career: he left it all to run a hospitality supplies warehouse.
Over the next decade, he grew that business from $500K to $5M — building commercial kitchens, supplying national brands, and having a front-row seat to thousands of hospitality operations at every level. Not from the dining room. From the loading dock, the walk-in, the service call at 11pm on a Friday.
That vantage point — banker's brain, supplier's eyes — is what makes Food Game Media different. Most industry commentary comes from chefs, operators, or journalists. This comes from someone who spent a decade watching the same failure modes repeat across venues of every size, concept, and ambition — and couldn't stop asking why.
The answer, it turns out, isn't that people don't care enough. It's that hospitality asks care to compensate for systems that were never designed for the pressure they're now under. That's not a motivation problem. It's a design problem.
Calm is smooth. Smooth creates control. Control is authentic. Authentic creates experience. That is the destination. Everything below is a step toward it — at whatever depth you’re ready for.
Eight questions. Five minutes. A clear picture of where your design problems actually live.
You’ve diagnosed the problem a dozen times. Wrong roster. Wrong hire. Wrong week. That diagnosis never quite fixes it — because it’s aimed at the wrong cause. The Diagnostic Card gives you a different starting point: the six domains where design problems hide in plain sight, costing you in ways that are hard to name until you know what you’re looking for.
The pattern your answers produce tells you which part of your operation is carrying the most load — and exactly where calm is farthest away. It’s the first step in every engagement we run, and it’s free.
Download the Diagnostic Card — Free →Your audience has heard every version of “work harder, care more, add technology.” They’ve tried all three. The gap between effort and outcome hasn’t closed. This talk explains why — and names what they’ve been missing.
Julian opens by confronting the audience with something they believe that is wrong. Not provocative for the sake of it — wrong in a specific, verifiable way the next hour will demonstrate. From 20 years watching hospitality from the supply side — 16 years in investment banking across Goldman Sachs, Morgan Stanley, and Citibank, then a decade delivering to operators across Australia — he has seen what breaks first, what gets blamed, and what the problem actually turns out to be after the third emergency call.
The talk ends at calm. Not as a mood or an ambition. As a design outcome that is either built or absent — and that every person in the room can start designing toward.
Qantas, dnata, Fishbowl, PFD Food Services, Dee Why RSL, and operators across the national hospitality ecosystem.
A keynote that leaves the room with a better model for understanding their situation — not a checklist, not a motivation hit. Every attendee receives a Diagnostic Card at close, with a direct path into The Systems Conversation.
Available in 45, 60, and 75-minute formats. The 75-minute version includes a facilitated reflection where attendees apply the framework to their own operation before they leave the room.
From $3,800 — internal / CPD events
From $5,500 — conference / external events
You know something is wrong. You’re not sure if it’s the team, the layout, the roster, or something you haven’t quite named yet. The real answer is almost never what it looks like from the inside — which is why diagnosing it from inside rarely works.
Julian reads your completed Diagnostic Card before the call begins. He arrives with a hypothesis — not questions. The 60 minutes test it across the six domains applied to your specific operation. This is not a discovery call or a sales conversation. It is a diagnostic. What you’re paying for is the written output, not the session itself.
The gap between what you think is producing your problems and what the framework reveals is, consistently, the most useful thing that happens in this conversation.
Complete the Diagnostic Card before the session. It’s sent when you book. It takes five minutes and shapes everything that follows. If it isn’t completed, the session is rescheduled. That is how important it is.
A written Diagnostic Summary within 48 hours — three design problems stated concretely, what each one is costing you, and what a redesign would look like. One page. Yours to use however you want. It doesn’t obligate you to anything further.
$1,500 standalone
Complimentary following an S1 keynote engagement
Your team can see the symptoms. They can’t agree on the cause. Every post-service debrief ends the same way — we’ll fix it next week — and next week never quite sorts it, because the design that produced the problem was never changed.
A 3.5-hour facilitated session where your team applies the six-domain framework to a real operational challenge — one they bring into the room. Julian doesn’t present the answer. He holds the frame while the room does the thinking.
When an experienced team stops arguing about who’s responsible and starts looking at what the design is producing — that is the moment this workshop was built for. It happens in almost every session.
Each participant submits one sentence before the session: “The operational problem I’m bringing today is…” Julian reads every submission. One anonymised case opens the session as a worked example.
A written workshop report with three priority redesign directions per participant. Not action items — design pointers. The people in the room know how to act. They needed to be able to see it first.
From $4,500 — internal group
From $6,500 — conference / open cohort
You’ve had plenty of people tell you what they think your venue needs. None of them watched the whole service first. That single gap explains most of the advice that didn’t work.
Julian arrives before service begins and stays until it ends. He watches the flow, the timing, the staff behaviour, the decision-making, and the six domains playing out in real time. No agenda until he’s seen it. The conversation with your team comes after the observation — not before. This sequence is not flexible. It exists because what an operation actually does and what an operator thinks it does are rarely the same thing — and the gap between them is always where the design problems live.
90 days of trading data, your current floor plan, a typical week’s roster, and a 20-question intake document — all reviewed before Julian arrives. He knows the numbers before he sees the operation.
The Venue Systems Report — 10 to 15 pages. What Julian observed, a domain-by-domain diagnostic, five ranked redesign opportunities, and one clear priority: the single thing he would address first if this were his operation. Delivered within 48 hours. Yours to implement at your own pace.
$9,500 — single venue
$14,500 — two venues, comparative
$800 — optional 60-day follow-up call
The design problems you solve this quarter will be replaced by new ones. Not because something went wrong — because operational design is never finished. The question is whether you’re working through them alone, or with someone who has the framework to see them before they cascade.
A fixed monthly session — 90 minutes, same day each month — plus a written advisory note within 72 hours, and one emergency call per month if the operation needs it. The structure is deliberate. A rhythm of reflection that most operators cannot create from inside the operation. If you arrive with nothing specific, Julian reviews the previous month’s note and identifies what has and hasn’t moved. There is always something worth looking at.
By month six, you hold six written advisory notes that together tell the story of where your operation has moved — and where the remaining design problems are concentrated. That is operational memory built deliberately. It doesn’t happen by accident, and it doesn’t exist anywhere in your operation until someone builds it.
$5,500 per month — 6-month minimum
Includes monthly session, written advisory note, one emergency call, quarterly review
The fitout firm designed the space. Someone designed the operating model. Someone else designed the service flow. These three decisions were almost certainly made in sequence, by different people, without a shared frame. The conflicts between them are costing you in ways that are genuinely hard to name — because no one has ever put all three domains in the same room.
The Ecosystem Map crosses the boundaries a standard venue review cannot. Julian reads the physical design against the operating model against the service architecture — simultaneously — and maps the points where they work together and the points where they conflict. The analysis moves across the organisational lines that usually prevent this diagnosis from happening at all.
This engagement is capped at eight per year. That is not a marketing constraint. It is a quality constraint.
A visual and written map of alignment points, conflict points, and the redesign priorities that require cross-domain coordination to implement. A 90-minute group debrief with all three domain leads in the room simultaneously — often the first time they have seen the same operation from the same vantage point.
This engagement is scoped individually. It begins with a conversation — not a quote form.
Your members are having the same conversation about the same problems every year. The advice offered changes. The outcomes don’t. This is what happens when the framework doesn’t travel with the people who went through it.
A designed programme arc — opening keynote, three facilitated workshops across sub-groups, a closing cohort review — delivered over 3 to 6 months to up to 300 participants. Not a one-off event. Not a speaker series. A programme where the framework is embedded in the people who went through it, with tools they continue using after it ends.
Available with an annual licence: your organisation delivers the workshop format independently, with Julian’s facilitation guide and tools, updated every year. Designed to leave the framework inside your organisation — not dependent on external delivery.
Programme summary report and participant diagnostic outputs across the cohort. Optional ongoing licence to continue the programme without Julian’s continued presence. Tailored to your sector, event structure, and member mix.
This engagement is scoped individually. It begins with a conversation — not a quote form.
Not sure where to start? Start with the card. It takes five minutes and tells you more than most consultants find in a day.
Download the Diagnostic Card — Free →
Then COVID came along and removed the last layer of padding that was stopping everyone from feeling it properly. Before that, the industry survived on a series of unspoken buffers — softer enforcement, easier labour, forgiving customers, flexible landlords. That world doesn't exist anymore. But the industry still behaves as if it does.
The Food Game argues that the pain isn't a motivation problem. It's a design problem. The book moves from what changed, to where the pressure actually comes from, to how humans behave under it, to why "calm" is the rarest and most valuable outcome a venue can produce.
The reader experience is designed to feel like: "This is what I've been feeling, but couldn't name."
Everyone in hospitality has a story where one small thing — a sick dishwasher, a late delivery, a surprise inspection — cascaded into a week of pain. Those aren't anecdotes. They're data. And they reveal the rules of the game more honestly than any industry report.
The Food Game Podcast captures those stories from across the ecosystem: operators, executives, suppliers, chefs, landlords, lawyers, accountants — anyone who touches the machinery of a venue. It's warm, candid, and occasionally absurd. Because hospitality is all three.
Whether you're an independent operator who knows things need to change, a multi-site group looking for a different lens, or a professional in the hospitality ecosystem who's tired of the same conversations — we'd like to hear from you. No pitch decks. No funnels. Just a conversation about what's actually going on.
Edit text and links below, then click Save. Changes persist in your browser. Press Ctrl+Shift+E to show/hide the edit button.