1. Why Pub Operators Must Adopt the Toyota Production System (TPS)
After World War II, Toyota faced conditions far harsher than American giants like Ford or GM. They lacked capital. They lacked technology. They lacked scale. Toyota had only one option: minimize capital investment and maximize human productivity.
On top of that, Japan’s postwar policy pushed for mass passenger-car adoption.
Copying American-style mass production—small variety, large batches—was impossible. Toyota had to survive through high-mix, low-volume production. That necessity gave birth to TPS. Today’s small pub operators are in the same position.
- Limited capital
- No budget for massive marketing
- No room for heavy automation
- Small teams
- Wide menus
By nature, pubs are high-mix, low-volume businesses. Trying to apply Ford-style mass production to a pub leads to collapse—as we saw earlier.
👉 [See:Why Burger King Thrives, but Pasta Pubs Struggle — The Assembly-Line Hell Created by Fordism]
2. Why “Just In Time” Is Non-Negotiable for Pubs
(1) Concept Comparison
So how do you survive with low capital and high complexity?
Toyota’s answer was simple: Eliminate waste.
Hidden waste exists everywhere in production:
- Inventory waste
- Motion waste
- Waiting-time waste
All waste equals money that stops flowing. Think about three kilograms of pre-fried potatoes sitting in a warmer. That’s not food. That’s frozen cash. To remove waste, Toyota abandoned batch production and moved to flow production:
Demand occurs → Assembly is triggered → Component production is triggered
Post-processing happens only at the exact moment it’s needed. No excess inventory. No idle stock.
The key point is this: only the parts needed by the assembly line are prepared—just in time.
The downstream process pulls from the upstream process, instead of upstream pushing work forward. Production flow moves like water—without wasting time, materials, or labor. Flow production required real-time information sharing—which led to Kanban, the backbone of Just In Time (JIT).
Pubs must operate the same way. This is the fundamental difference from batch systems, where upstream processes hold excessive work-in-process inventory and choke the entire flow. Compare this with traditional Fordism production:
Parts delivered → Machining → Assembly → Painting → Delivery
Each stage piles up inventory. Each pile equals waste. To optimize the entire production flow, there is a point where division of labor must stop. And that directly contradicts what we’ve been taught—that specialization is always a virtue.
In a typical system, each station tries to maximize its own utilization and specialization. But the result is predictable:
- Work-in-process piles up.
- Extra roles appear just to coordinate work.
- More layers of management are added.
- The organization swells—without producing more value.
Isn’t this eerily similar to the brigade system? “I just do my job at my station.” That mindset isn’t professionalism. It’s irresponsibility disguised as efficiency.
Just-In-Time means the assembly line doesn’t prepare parts in advance. The next process physically comes to pick them up.
(2) Summary Table
| Feature | Traditional Batch Kitchen (Push System) | Toyota JIT / Pull Kitchen (Flow System) |
| Workflow | Prep huge batches → Wait for orders | Order received → Cook & Prep simultaneously |
| Inventory | High “Work-In-Progress” (WIP) sitting around | Zero WIP. Ingredients stay raw until needed. |
| Mindset | “I prepped my station, I’m done.” | “I produce only what the next station needs now.” |
Traditional Batch Kitchen (Push System)
Prep → Push → Wait → Cook → Push → Wait → Serve
[ INGREDIENT TABLE ] → [ BULK PREP AREA ] → [ WAITING TRAY ] : food sitting, no customer yet
[ COOKING STATION ] → [ WAITING TRAY ] → [ SERVING ]
Toyota JIT / Pull Kitchen (Flow System)
Order → Cook → Prep → Ingredients
CUSTOMER ORDER → [ FINAL COOK ] : Cook pulls exactly what is needed from [PREP AREA]
[ PREP AREA ] → [ RAW INGREDIENTS ] : Prep pulls exactly what is needed from [RAW INGREDIENTS ]
Example: The Ramen Shop Flow
A ramen order comes in. The head chef starts boiling the noodles and shakes off the water. At the same time, the assistant chef grills only the exact amount of meat needed and prepares the toppings—nothing more. Just as the head chef pours the broth, the toppings are ready. They go on. The bowl goes out immediately.
A Fordist ramen shop would do it like this. Meat is pre-grilled in batches, broth is prepared in advance, and noodles are pre-boiled. When an order comes in, the line cook grabs the ingredients and assembles the dish. This approach works well for single-item menus with high table turnover. But as I just mentioned, most pubs have diverse menus. You cannot stockpile inventory like that. So in the Toyota method, when an order comes in, the noodles and meat are cooked in parallel and delivered just in time — exactly as I described.
Note that multi-skilled workers are operating in parallel in order to minimize inventory and keep production flexible.
3. Just In Time Applied to Pub Operations
In a pub:
- Order comes in
- FOH prepares for pickup
- Kitchen starts cooking from zero stock (Ideally)
There is no pre-assembled inventory waiting around. One chef handles the dish from start to finish. No segmentation. No assembly-line roles. No Work-in-progress. This is the opposite of Fordism—where one person grills, another assembles, another wraps.
Why? Because labor cost control is central to TPS.
4. Lead Time Is Everything in a Pub
If your restaurant has: Very few menu items, Extremely high turnover. Then batch production can work. But pubs are different.
- Many menu items
- Higher quality expectations
- Irregular order patterns
That means lead time management becomes critical.
Key TPS adaptations for pubs:
- Multiple dishes cooked in parallel
- Minimal setup time between dishes
- Work standardization
- One tool = one function
- Multi-skilled, single-chef operation
- Synchronized cooking times
Because there’s no buffer inventory, the kitchen must multitask in real time. In a pub, everything must stay synchronized: Order received → Cooking starts → Food served. Always live. Always flowing. To achieve this, you need to create a system that cooks 4 to 5 menu items simultaneously. Here, I have introduced my actual case. 👉 See: How I Make 5 Dishes in 15 Minutes — A Real-World Example
4. The Key Difference Between Toyota Cars and the Toyota Pub
Demand Forecasting Changes Everything
The biggest operational difference is simple: Toyota Motors can forecast demand. Pubs cannot. At Toyota Motor Corporation, demand forecasting is everything.
- Production planning depends on stable demand forecasts
- Kanban signals are calibrated to expected volume
- If demand swings too wildly, flow production collapses
In short, flow only works when demand is predictable.
How Pubs Actually Work
Pubs live in chaos.
- Weather changes
- Political or social issues
- Last-minute reservation cancellations
- Random group visits
There is no reliable monthly cycle like a gym or barber shop. Demand is volatile by default. So pubs must follow different rules.
(1) Stock Raw Materials, Not Finished Goods
In restaurants, it’s tempting to pre-make everything. But if you prep: three types of pasta, multiple sauces, finished portions, Your fridge fills fast—and spoilage risk skyrockets.
Instead:
- Minimize finished-product inventory
- Stock raw, flexible ingredients:
- onions
- potatoes
- carrots
- celery
- Frozen-food is useful (Figure out which items taste good when thawed and cooked. Using frozen food effectively helps with running a pub.)
Raw ingredients last longer and adapt to demand changes far better than cooked food.
(2) Selling Out Is Better Than Overstocking
Keep prep quantities conservative. If you sell out during a rush, that’s okay. “We’re out of that today, but I can recommend something similar.” Most customers understand—especially when guided calmly. Overstock Everything is worse. Waste doesn’t scream. It kills you quietly.
(3) Move Away from Live Pan Cooking
Live-fire pan cooking (pasta, stir-fry, Spain dishes) locks the chef to one station. That structure naturally pushes kitchens toward Fordism. Instead, shift toward:
- Reheat-based systems (soups, stews) like German dishes
- Oven roasting
- Frying modules
Machines handle heat. Chefs handle timing. That’s what enables flow production.
[See: “Why Hot Dogs Beat Burgers in Pub Operations” ]
(4) Maximize Ingredient Cross-Utilization
Design menus around shared base ingredients.
Examples:
- One stock → pasta and stew
- One ragù → chili dogs and nachos
Fewer ingredients = fewer SKUs = less waste.
(5) Use Frozen Ingredients—But in Smart way
Frozen pork or chicken is perfectly fine if:
- Defrosted properly
- Used in stews, roasts, or fried dishes
Modern blast freezing and vacuum packing preserve quality extremely well. For items like french fries, frozen OEM products have a much higher ROI and are scientifically tastier. Occasionally, I see places claiming to serve ‘homemade fries’ by slicing and frying potatoes stored at room temperature, but they are not crispy and tasteless.
(6) Order Every 1–3 Days, Not Weekly
Weekly ordering assumes stable demand. Pubs don’t have that luxury. Smaller, more frequent orders:
- reduce risk
- track real demand
- keep cash flowing
5. Summary
In this section, we covered:
- Why pubs cannot rely on demand forecasting
- How Just-In-Time must be adapted for volatility
- Why raw materials beat finished goods
- How flow production survives chaos
Toyota builds cars in a predictable world. Pubs survive in an unpredictable one. That’s why TPS matters even more in hospitality.
6. Next Step
In the next article, we’ll dive deeper into:
- Bottleneck Management
- Production Leveling (Heijunka)
- Kanban Systems
- Andon Alerts
- Poka-Yoke (Mistake-Proofing)
- Standardized Work
- 5S Principles
We’ll see how each TPS principle is adapted for real-world pub operations. Stay tuned!
If you enjoyed this article, you can support the project – thank you!