I've started around twenty companies. I know what delegation looks like. I know how to build a team, how to hand off responsibility, how to step back and let people run things. I've done it enough times that it no longer feels uncomfortable.
And yet right now, I write most of the content for this blog myself. I respond personally to Google reviews, Yelp reviews, TripAdvisor reviews. I study every item on the menu — what's in it, how it's made, which ingredients we use and why. I've spent time on the floor plan of each location, on the interior decisions, on every channel of marketing we're exploring. I am, by any reasonable measure, spending significant founder time on things that could be delegated.
People who know my background sometimes find this surprising. I want to explain why it isn't.
The difference between experience and understanding
Having built twenty companies does not mean I understand the café business. It means I understand how to build companies — how to structure teams, manage capital, navigate growth, handle the things that go wrong. That experience is genuinely valuable and I use it every day.
But understanding how to build a company is not the same as understanding the specific business you're building. Those are different things, and conflating them is one of the most dangerous traps an experienced entrepreneur can fall into.
The experienced founder who says "I've done this before, I know how it works, I'll hire people to handle the details" is often the same founder who discovers two years in that the foundation was never quite right — that decisions were made by people who didn't fully understand what they were deciding, that the brand accumulated in a direction nobody consciously chose, that the operation has gaps nobody noticed because nobody was looking with the right eyes.
Starting a new business — even your twentieth — requires starting from understanding, not from assumption. The details of this specific business, in this specific market, with this specific product, are not transferable from the last one. They have to be learned fresh every time.
Experience tells you how to build. It doesn't tell you what to build. That part you have to figure out for yourself, every time, from the beginning.
Why I write the content myself
Someone else could write blog posts for Three Sixteen. I could hire a content agency, a marketing manager, a ghostwriter. The posts would be grammatically correct, SEO-optimised, and published on schedule.
They would also be wrong in ways that nobody would be able to identify precisely — but that guests would feel. The voice would be slightly off. The specific details that make the brand real — the real cost of opening, the real struggle with consistency, the real reason we made a particular decision — would be absent or softened because whoever was writing wouldn't know them. Or wouldn't know which ones mattered.
When I write, I learn what I think. Writing forces precision in a way that thinking doesn't. I have sat down to write posts for this blog and discovered halfway through that I hadn't fully worked out what I actually believed about the topic. The process of writing it made me figure it out. That clarity is now in the brand — in the way we talk about what we do and why. Nobody I hired before I had that clarity could have put it there.
There's also something more practical. To brief a writer well, I have to know the material well enough to explain exactly what I want. To evaluate whether they've done it correctly, I have to know what correct looks like. If I delegate before I have that knowledge, I'm not delegating — I'm abdicating. The difference is that delegation produces the outcome you intended, and abdication produces whatever the other person thought you meant.
Why I respond to every review personally
Reviews are not a PR function. They're information.
When a guest leaves a review — positive or negative — they're telling me something about the experience they had. If I delegate the response entirely to someone else, I'm also delegating the listening. I lose direct access to what's actually happening in the room, at the bar, in the interaction between our team and the people we're serving.
I can read a report about review sentiment. I can see a summary of themes. But reading the actual words a guest chose to use — the specific thing they praised, the specific moment they describe that went wrong — gives me information that no report captures. It keeps me connected to the ground level of the business in a way that operating purely from summaries never does.
Responding also signals something to the guest and to everyone who reads the review after them. It signals that there's a person here who is paying attention. That the business is not a machine. That if you have an experience worth telling someone about, the person who built this place is listening.
That signal is part of the brand. It cannot be outsourced without changing what it communicates.
Why I study the menu in detail
Every item on Three Sixteen Cafe menu is the result of a decision. The ingredients, the preparation method, the way it's described, what it pairs with, what it signals about who we are and what we care about — all of it was chosen. Or should have been.
If I don't understand those decisions in detail, I can't evaluate whether they're right. I can't tell whether a new item belongs on the menu or doesn't. I can't brief a pastry chef properly on what we're trying to achieve. I can't explain to a guest why we make the almond croissant the way we do rather than the faster way. I can't identify when something has drifted from what it should be because I don't have a clear enough picture of what it should be.
Menu knowledge is also team knowledge. When I understand exactly what goes into every item — every ingredient, every step of preparation — I can have real conversations with the kitchen team. I can tell the difference between a process problem and an ingredient problem. I can recognise when a shortcut has been taken that shouldn't have been. I can't do any of that from a distance.
Why I'm involved in interiors and floor plans
The physical space is not decoration. It is the experience.
The decision about where a table sits affects whether two people sitting there can have a conversation without raising their voices. The decision about where natural light falls affects what the room feels like at 8am versus noon. The decision about how far the bar is from the door affects whether someone who walks in feels welcomed into the space or processed through it.
These decisions compound. Get enough of them slightly wrong and the room never quite feels right — and guests can't tell you why, but they feel it. Get them right and the space does work that no amount of marketing can do: it makes people want to stay, to come back, to bring someone else.
I can't evaluate these decisions without understanding them. And I can't understand them without being involved before they're made, not after.
The foundation principle
The reason I'm in the details at this stage of Three Sixteen's development is not because I don't trust the people around me. It's because the foundation of a business is set early, and once it's set, it's very hard to reset.
The standard we hold ourselves to — in the coffee, in the pastry, in the way we treat guests, in the way we communicate — was established in the first months of operation. The culture of the team was shaped by the expectations that were present from the beginning. The brand identity emerged from the actual decisions made in the actual moments that mattered, not from a strategy document.
If I hadn't been in those decisions — if I had handed them off before I had the knowledge to make them well — the foundation would have been set by people who cared, but who didn't carry the full picture of what we were trying to build. They couldn't have. I hadn't communicated it clearly enough yet, because I hadn't worked it out clearly enough yet.
You work it out by doing the work. By writing the posts, reading the reviews, studying the menu, walking the floor plan, sitting in the room at different times of day and feeling what it feels like. The understanding that comes from that process is what makes delegation possible — real delegation, where you hand something off to someone and trust that they know what right looks like because you've shown them.
When I will delegate — and what that actually means
This is not a permanent state. The goal is to build deep enough understanding of every area of the business that I can hire specifically for it, brief that person precisely, and evaluate their work against a standard I can articulate.
That moment is different for different functions. Some things I will delegate sooner because the right person can build on the foundation faster than I can alone. Some things I will stay closer to for longer because they're too central to the brand's identity to hand off before the identity is fully established.
But the principle is constant: I don't delegate what I don't understand. Not because I don't trust people — because delegation without understanding isn't delegation. It's hope. And hope is not a management strategy.
Twenty companies taught me that. Three Sixteen is where I'm applying it.
