My Managers Kept Missing Deadlines. Turns Out The System Was Built For The Wrong Person.

It was a menu rollout. I had my two managers prepped six weeks out. Full timeline, printed and laminated, taped inside the manager’s binder, every task assigned by name and every deadline in writing. We reached week five, and almost nothing had changed. Vendor confirmations hadn’t gone out. The staff tasting hadn’t been scheduled. The new menus hadn’t even been set up in Canva for printing.

I walked into the manager meeting that Tuesday, ready to be frustrated. Then I noticed something. Both of them looked more frustrated than I was. That’s the moment I started paying attention to the wrong thing I’d been doing.

Six Weeks Felt Like Plenty Of Time

I’d built what felt like a thorough plan. Six weeks. Eight major milestones. Ownership of every task. My managers looked at it and saw a wall.

A deadline six weeks out doesn’t feel real when you’re managing a short-staffed Thursday dinner. It sits on a list that gets checked once and then filed away until the panic sets in. By the time the panic arrives, you’re trying to finish six weeks of work in five days, and the scramble looks like failure even when the original plan was the actual problem.

I’d also handed them everything at once. The full scope, every phase laid out from week one to opening night. That’s what thoroughness looks like from a GM’s desk. From the manager’s side, a full-scope plan with no clear starting point is a different kind of overwhelm.

One-Week Windows

I rebuilt the whole thing. Collapsed the six-week plan into weekly targets. One question drove everything, “What are the three things that need to be finished by Friday?” The end of the rollout didn’t matter yet. Next month didn’t matter. Friday did.

That list went on the whiteboard in the manager’s office. Three items. Names next to each one. No project phases, no long descriptions. The task, the person, and the day it was due. Visible every time someone walked through the door.

By the following Friday, two of the three were done. The third was halfway there. More progress in one week than we’d made in the previous four combined. Short windows work because Friday is coming no matter what. Six weeks doesn’t feel that way until it’s suddenly six days.

The Meetings Weren’t Working Either

We had a manager meeting every Wednesday. An hour and a half. We’d go through financials, staff concerns, scheduling problems, floor issues, reviews, and by the time we got to ongoing projects, there were maybe fifteen minutes left, and nobody had the capacity to think through anything complicated. Projects got three sentences and a vague ‘let’s reconnect on that.’ Nothing moved.

I cut Wednesday’s meeting down to forty-five minutes, operations only. Added a ten-minute standup every morning before the AM shift. Standing in the kitchen, not sitting in the office. Each person named one thing they were going to finish before they left that day. One thing. Everyone in the room heard it.

The accountability that was created was different from anything I’d ever put in a binder. You said it out loud in front of your colleagues. You either came back the next morning having done it, or you didn’t. Most mornings, they had done it. The public commitment did something the weekly agenda never managed to do.

The Tasks Were Too Vague To Start

The original rollout plan had line items like ‘coordinate with vendors’ and ‘develop staff communication plan.’ I wrote those thinking I’d been clear. My managers read them and didn’t know where to begin.

When a task has no obvious starting point, it doesn’t get started. Doesn’t matter how experienced the person is or how much they care about the outcome. A large, shapeless task sitting alongside twelve other large, shapeless tasks in the same document. The brain scans it, finds no entry point, and moves on to something that has one.

I rewrote every project task as a single concrete action. ‘Call the Sysco rep by Wednesday and confirm the delivery date for the new proteins.’ ‘Write one paragraph explaining the menu changes for Thursday pre-shift.’ Small enough to start. Specific enough to know when it’s done. The tasks started getting done.

Working Alone Wasn’t Working For Everyone

One of my managers was one of the sharpest people I’d ever put on a floor. Great instincts with staff, fast read on service problems, could spot a table going sideways before the server knew it. She also couldn’t push through an administrative task alone without losing it somewhere in the middle.

She’d start something, get pulled away by a vendor call or a line cook question, come back twenty minutes later, lose her thread, and shelve it until the deadline had passed. She worked harder than most managers I’ve hired. Each interruption was manageable on its own. Coming back cold to a half-finished task, alone, with no momentum, is where the work died.

What worked was almost embarrassingly simple. I blocked ninety minutes every Monday afternoon, where both managers and I were in the same room working on our own separate projects. No agenda, no collaboration, no check-ins. Three people in the same space doing their own work in silence.

She finished more administrative work in those ninety minutes than she’d get done the rest of the week combined. I watched it happen enough times to stop trying to explain it and kept scheduling it.

Other people started asking to be included. A Sous Chef who’d been missing his ordering deadlines on and off for months. The other Sous Chef, who’d never once turned in a training report on time. Same room, same silence, same result. I don’t fully understand the mechanism. I know what happened when I removed the conditions that made solo work so hard.

What I Actually Figured Out

The menu rollout finished on time. Last week was still kind of messy. Restaurants are like that. The work got done, the staff was ready, and the new menu launch ran smoothly.

I spent a long time thinking I had a people problem. Two managers who were genuinely good at their jobs and couldn’t seem to finish a project on schedule. I came close to deciding the answer was different people.

What I’d actually built was a system that worked for me. I’m the kind of person who can hold a six-week timeline in my head, feel the weight of a deadline three weeks out, and break a vague task into steps without being told to. I designed for that person without thinking twice about it. My managers processed time and tasks differently, and I handed them a system that gave them no way to show it.

That’s the thing about systems. The person who builds them almost always builds them to match how they think. It feels like rigor. It feels like thoroughness. It’s mostly just a self-portrait disguised as infrastructure.

The same thing plays out everywhere. Managers watch capable people fall behind on long-horizon work. Teachers are watching strong students crumble on semester-long assignments. Coaches whose best-prepared athletes come apart when the game plan stops working. The person who built the system and the people using it are seldom the same.

If your projects keep stalling, ask one question before you look at your team, “What would it actually take for someone to use what you built?”

I write about what actually happens in restaurants and what you can do to make it better. Follow along for free.

#RestaurantManagement #FoodServiceLeadership #HospitalityIndustry #RestaurantOperations #KitchenCulture