The architecture was the problem

It didn’t arrive as a single moment. There was no crisis, no dramatic shift, no morning I woke up and saw it clearly. It came in layers. The slow accumulation of friction that eventually gets heavy enough that you can't ignore it anymore.

I was venue manager. On paper, the role was split: some shifts on the floor as duty manager, the rest in the office working on the bigger picture. Revenue, COGS, labour costs, marketing, the numbers that tell you whether a venue is actually healthy or just busy. Two jobs, two registers, two sets of expectations. One person trying to hold both at once.

The problem wasn’t the workload. I’ve never minded hard work. The problem was that the information you needed to do the bigger-picture job well wasn’t flowing down. The context, the history, the full view of what was actually happening. It wasn’t anyone’s fault, not exactly. There was a renovation happening. Other venues to manage. A GM who carried most of the picture in his head because that’s how he’d always operated, and he was good at it, and it had worked until it didn’t.

But I was being asked to perform at a level the structure wasn’t built to support.

The information problem was the first thing I noticed. Not malicious. More architectural. Decisions that needed context I didn’t have. Sign-offs that sat in a queue because the person who needed to make them was already across three other things. Culture issues that everyone could see and nobody had the authority to move on. A training program that existed in theory and stalled in practice, because the GM was the system. When he was occupied elsewhere, the system paused.

I had decision-making responsibility without decision-making power. That’s a particular kind of frustration, because it looks like authority from the outside and feels like none from the inside.

The reporting was old-school. Pulled by hand, formatted by hand, the same Excel files we’d always used because they were the files we had. Weekly trade reports that took hours. COGS breakdowns that should have taken twenty minutes taking most of a morning. Data that lived in spreadsheets that lived in email chains that lived in someone’s inbox.

And underneath all of it, a skills gap I kept tripping over. The duty managers were doing their best. But there was no training pathway for them. No structured transition from senior staff to supervisor, from supervisor to someone who could actually lead a team through a difficult shift and make the right call without me. They’d been thrown in the deep end the way most hospitality people are, because that’s how it’s always been done.

I’d been through that myself. I knew what it cost.

The realisation, when it came, wasn’t about the GM or the hierarchy or the information that wasn’t flowing. It was about me.

I was trying to do everything. Running shifts. Carrying the office work. Mentoring people in the gaps between. Jumping into problems because I was the one who knew how to fix them. Which meant nobody else was learning how to fix them. Which meant they kept coming back to me. Which meant I'd stay the person who fixed them indefinitely.

I had become the bottleneck.

Not because I was indispensable. Because I hadn’t built anyone else who could take the weight. The busier I was, the less time I had to develop the people around me. The less developed the people around me, the more the work came back to me. A loop I’d helped build without realising it.

Shifts are smoother when you invest the time in your labour force. That sounds obvious. It took me longer than it should have to understand it properly. Not as a management principle. As something I was responsible for doing, right now, with the team I had.

I built two things in response.

The first was the bento box. A suite of models: Sushi for the data and reporting, Nigiri for leadership and people questions, Sashimi for my own planning. I trained all three on the context of my work and used them to cope with the information gap above me. If the full picture wasn’t coming down the chain, I’d build a system to help me work with what I had. The reporting that used to eat mornings was handled. The analytical work that needed a clear head got done while I was on the floor.

The second was the SID program. Supervisor in Development.

It came from watching duty managers struggle with a transition nobody had prepared them for. The gap between being a good senior staff member and being someone who could lead a team, hold a standard, make a call under pressure, and bring other people up with them. There was no pathway for that internally. So I built one.

A structured framework. Measurable KPIs. A way to assess progress quickly so we weren’t guessing. Leadership training that covered the things the deep end doesn’t teach you: how to shift from colleague to supervisor without losing the team, how to translate expectations into language the people around you can actually act on, how to read a situation and respond instead of react.

I couldn’t fix the ceiling above me. So I focused on building the floor beneath me.

The goal wasn’t to produce managers who needed me less.

Find the friction. Build the fix. Make yourself less necessary. That instinct is the same one that became OTW Studios.

The operators I work with now are carrying the same weight I was. They’re the ones who know how everything works, which means everything runs through them, which means they can’t step back without it slowing down. Not because they’re indispensable. Because the system was built around them rather than independent of them.

The bento box gave me hours back. The SID program gave me a team I could trust. OTW Studios is an attempt to give other operators the same thing. Not a platform, not a dashboard. A system that handles the parts of the work that were never supposed to be theirs in the first place.

The bottleneck is always fixable. It just requires being honest enough to see it.