The 5th Element Chef

Diary Entries

Read the Stories in Order

Welcome to The Chef’s Diary — The Unfiltered Life of a Chef.

These are the free entries. Read them one by one.

When you finish the fourth entry, you can unlock the rest.

Entry 1

4 Hours 25 Minutes From Home — And I Remembered Who the Fuck I Was

At 06:00, I got in the car. Destination: South Wales. 4 hours 25 minutes away.

Normally, a long drive to an event doesn’t bother me. I’ve travelled all over the country to cook for people.

But this drive was different.

Because while I was driving to somebody else’s celebration, I was quietly questioning what the fuck I was doing with my own life.

I didn’t have a permanent job. Money was on my mind. I had another interview coming up for a position paying around £55,000 a year.

A few years ago, I probably would have looked at that salary, looked at the title and thought: take it. Security. Regular money. Executive position. Get back into a kitchen and get on with it.

But after more than 20 years in this industry, I found myself asking a completely different question: is that actually what I’m worth?

Not because £55,000 isn’t good money. But because eventually you have to stop measuring yourself purely by the salary somebody else decides to put next to your name.

Anyway. I had a dinner to cook.

It was a 40th birthday with a murder-mystery evening and a 5-course menu.

I’d driven nearly 4½ hours… and then discovered the location I’d been given wasn’t actually the location.

The real house was another 5 minutes away.

Normally, no problem. Except there was no fucking signal.

So there I was, somewhere in South Wales, driving around with a car full of food trying to find a house that apparently didn’t exist.

Eventually, I found it.

I walked through the door. And let’s just say the party had already started.

They weren’t exactly waiting for me to open the first bottle. They were already having a very good evening.

Now it was my turn.

Beef carpaccio. Saffron risotto with jumbo prawns. Chicken cacciatore. Lemon granita. Apple tarte tatin.

Five courses. One unfamiliar kitchen. A room full of people enjoying themselves. And suddenly something happened.

All the shit I’d been thinking about during that drive disappeared.

The job. The money. The interview. The setbacks. The question of what happens next. Gone.

Because I was cooking.

And when I’m cooking, I know exactly who I am.

Course after course went out. The guests talked to me. They laughed. They enjoyed the food. They treated me with respect.

Then the final course went out. And something happened that probably meant far more to me than any of them realised.

They applauded.

To them, it was probably just: ‘Thank you, Chef. Great dinner.’

To me? It hit differently.

Because there have been moments in my career where I’ve questioned everything.

I’ve questioned whether I was good enough. Whether I’d made the right decisions. Whether the setbacks had taken something away from me. Whether after everything this industry had thrown at me, I still had the same fire.

That room answered the question.

I can still fucking cook.

More importantly: I still love doing it.

When I finally got back into the car, I wasn’t the same person who had driven there that morning.

The road hadn’t changed. My situation hadn’t magically changed. There wasn’t suddenly £1 million sitting in my bank account.

I still had decisions to make. I still had an interview coming. I still didn’t know exactly what the next chapter looked like.

But something had changed.

Me.

For years, I walked into interviews hoping the company would choose me.

Now I look at them differently.

You want my experience? My standards? My leadership? My creativity? My loyalty? My ability to walk into chaos and somehow still put dinner on the table? Fine.

But I’m asking questions too.

Because the next kitchen doesn’t just need to decide whether I’m good enough for them.

After more than 20 years behind the pass… I’m finally deciding whether they’re good enough for me.

Jonathan Bradley

Entry 2

4 Events. 3 Days. 1 Chef. And Absolutely No Room for Anything to Go Wrong.

People see the finished plate. They see the Instagram picture. They see the beautiful house, the BBQ, the guests drinking champagne and the chef standing there looking like everything is under control.

What they don’t see is what happened before that picture was taken.

This particular weekend? 4 events. 3 days.

By the end of it, I was reminded why private cheffing is a completely different animal from working in a professional kitchen.

Thursday. First job. A work-group BBQ at a massive private house.

I’d only picked the booking up 2 days before because the previous chef had cancelled. No problem. That’s what I do. Turn up. Work with what I’ve got. Deliver.

Then I saw the BBQ.

Fuck me.

Old food. Old debris. Dirty.

Before I could even think about cooking someone’s dinner, I had to start cleaning their equipment.

That’s something nobody puts in the glamorous private-chef videos. ‘Come and experience the luxury life of a private chef.’ Yeah. Sometimes that luxury involves scraping somebody else’s old food off a BBQ.

Eventually, I got it clean enough to work safely. Then came problem number 2. It wouldn’t hold its heat properly.

At this point you have 2 choices. Stand there complaining about the equipment. Or find another way.

I used parchment where appropriate, grilled what I could and finished what needed finishing in the oven. Dinner went out. Guests were happy. Job done.

But Thursday had already reminded me of one of the biggest lessons in private dining: you can be the most organised chef in the world and walk into someone else’s kitchen and become disorganised within 5 minutes.

Because you’re entering their world. Their equipment. Their fridge. Their oven. Their utensils. Their idea of what constitutes a ‘fully equipped kitchen.’ And believe me… that definition varies considerably.

Friday — Cambridge. This time I had my sous chef with me. And we needed him.

20 children. 30 adults. 50 guests. Beautiful property. Massive kitchen. State-of-the-art BBQ. Pizza oven. Now we’re talking.

After Thursday’s BBQ, this looked like heaven.

Until we tried using the pizza oven. Didn’t fucking work.

Fine. We’ll adapt. Let’s see what equipment we’ve got inside this enormous kitchen. Surely a property like this has everything.

We started opening cupboards. 1 wok. 1 sieve. 1 frying pan. That was basically our professional kitchen. You couldn’t make it up.

People sometimes think the difficult part of private cheffing is the cooking. It isn’t. I know how to cook.

The difficult part is figuring out how the fuck you’re going to cook what you’ve promised with whatever happens to be inside somebody’s house.

So we figured it out. We adapted. We cooked. We served 50 people. And once again… we delivered.

That’s become a big part of what I want my business to represent. We take on things that look impossible. Then we find a way to deliver them.

Then Saturday happened.

This was supposed to be straightforward. My sous chef had an event for 23 ladies. I had another event for 16 ladies. Two chefs. Two events. Everything covered.

Until my phone went.

My sous chef had been involved in an emergency and couldn’t attend. Now I had a problem. 2 events. 39 guests. 1 chef. At basically the same time.

This is the moment where running your own business becomes very different from being employed. There’s nobody upstairs to pass the problem to. There’s no operations manager coming to save you. It’s your name on the booking.

I tried contacting the first client to see whether moving the event to Sunday was possible. No answer.

I could have cancelled. And nobody could really have blamed me. There had been an emergency.

But I fucking hate cancelling. Because behind every booking there’s already been work. Ingredients purchased. Menus written. Sauces prepared. Food prepped. Hours spent organising.

And on the other side of it, there’s a customer who’s planned an entire evening around you turning up.

So I came up with another solution. And looking back… it was slightly fucking ridiculous.

I’d arrive at the first event 2 hours before service. Get inside. Prepare everything. Cook everything as close to service as possible. Set it into the hot box ready for the guests. Then leave. Drive to my second event. And cook another dinner.

I contacted my second client and asked whether we could push their service back by 1 hour. Thankfully, they agreed.

The first client gave me the key-box code. I arrived at the property. Let myself in. And started cooking. No brigade. No sous chef. No backup. Just me in somebody else’s kitchen watching the clock.

By around 17:00, everything was cooked fresh. Into the hot box. Ready for their 18:00 service.

The client arrived back around 17:30. She looked at everything I’d managed to get done and seemed genuinely surprised. Everything looked good. Everything was ready.

I explained what needed doing. Then I got back in the car. Because my day wasn’t finished. I still had another event to cook.

The second group were brilliant. They were patient. They understood the situation. Everything was being cooked from scratch, so there were around 25 minutes between courses. Nobody made it difficult. Nobody made me feel like I’d ruined their evening.

They enjoyed themselves. When I left, they gave me a warm goodbye. I was exhausted. But we’d done it. Both events had happened. Nobody had been cancelled.

Then, around 21:30, my phone went. It was a message from the first event. The food was amazing. Everyone loved it.

That’s the message you want. After the chaos. After the stress. After trying to be in 2 places at once. We’d pulled it off.

I went home thinking I’d somehow rescued what could have been a complete disaster.

Then Sunday came. The second event paid in full. 5-star review. Brilliant.

Then I heard from the first event. They wanted compensation. Because the situation had inconvenienced them.

And that one got to me. Not because of the money. It wasn’t about the fucking money.

It was about the fact that sometimes people don’t see what happened behind their dinner.

I could have cancelled. Instead, I found a way. I could have said: ‘Sorry, there’s been an emergency. You’re on your own.’ Instead, I got into that property early, cooked their food, made sure everything was ready, then raced across to another event and did it all again.

And they’d already messaged me saying the food was amazing. But somehow the conversation still ended up being about compensation.

That’s hospitality. You can solve 10 problems nobody knows existed… and occasionally the only thing someone remembers is number 11.

I’m not writing this because I think customers should accept bad service. They shouldn’t. If you pay for something, you deserve what you’ve paid for.

But I do think sometimes we forget something very basic. The people serving you are human beings.

Chefs have emergencies. Waiters have families. Bartenders have bad days. Someone cooking your anniversary dinner might have something happening in their own life that you know absolutely nothing about.

And they’re still standing there trying to make your night special.

That weekend I was awake from around 06:00 until I finally got home at approximately 01:00.

And I’d do it again.

Because that’s what this industry has drilled into me. Find a solution. Get the food out. Don’t let the customer see the chaos. Keep moving.

I’ve spent more than 20 years doing that. The industry has battered me. Burned me. Bruised me. Tested me. And somehow I’m still standing.

Maybe that’s the part of being a chef people don’t see. We don’t develop thick skin. After long enough in this industry… you develop fucking titanium.

Jonathan Bradley

Entry 3

The Best BBQ I Ever Cooked Had Nothing to Do With the Food

I turned up to cook a private BBQ expecting what I normally expect. Unload. Find the kitchen. Work out where everything is. Get organised. Prep. Cook. Serve. Clean. Go home.

But almost immediately, this one felt different.

The hosts were welcoming. Polite. Respectful. They let me get on with my job. No unnecessary pressure. No standing over me. No treating me like I’d suddenly become part of the furniture because they’d hired me for the evening.

I felt relaxed. And when a chef feels relaxed? We cook better.

But while I was relaxed, I noticed the hosts weren’t.

They’d put effort into this event. You could tell they wanted everything perfect. The house. The food. The atmosphere. They were trying to create a brilliant evening for their friends.

There was just one problem. Their friends weren’t fucking there.

The arrival time came. Nothing. 10 minutes. 20 minutes. 30 minutes. Still waiting.

Eventually, some of the guests were around 1 hour 15 minutes late.

Now, as the chef, that’s not really my problem. Except it is. Because when you’re cooking in someone’s home, you see everything.

I could see the hosts checking their phones. Looking towards the door. Trying not to show that they were annoyed. Trying to keep smiling.

So I did what I could do. I kept everything under control. Adjust the timings. Protect the food. Keep working. Keep the atmosphere calm. Make sure that when everyone finally arrived, the hosts looked like the evening had always been planned that way.

Because that’s something I’ve learned about private cheffing. Sometimes you’re not just cooking dinner. You’re protecting someone’s evening.

Eventually, the guests started arriving. One by one.

And this is where private dining gets interesting. Because when you cook in people’s homes, you get a front-row seat to human behaviour.

Some guests walk in and immediately say hello. They ask what you’re cooking. They thank you. They have a laugh with you.

Some barely acknowledge you’re there. That’s fine too. I’m there to work.

But then occasionally you meet another type. The person who seems to think that because there’s a chef in the house, they’ve suddenly become royalty.

There’s a difference between receiving a service… and treating the person providing it like a servant. And that difference matters to me.

I’ve spent more than 20 years learning my craft. I’ve worked ridiculous hours. I’ve missed weekends. I’ve missed celebrations. I’ve been burned, cut, shouted at, pressured and pushed to limits that most people outside hospitality will never see.

So when I walk into your house wearing my chef jacket, I’ll treat you with respect. I’ll treat your family with respect. I’ll treat your guests with respect. I’ll do everything I can to make your event brilliant.

But there’s one thing that isn’t included in the price. My dignity. You don’t get to buy that.

I don’t care if you earn £30,000 a year, £100,000 a year, or you’re running a Fortune 500 company. When we’re standing in the same room, we’re 2 human beings.

Your bank balance doesn’t make you more important than the person cooking your dinner. And mine doesn’t make me more important than you.

Respect works both ways.

Despite the late arrivals and the different personalities walking through that door… I loved that event.

The hosts were good people. The atmosphere eventually came together. The food went out. Everyone enjoyed themselves.

And I drove home thinking: that might have been one of the best BBQs I’ve ever cooked.

Not because I suddenly discovered some magical new way of cooking a steak. Not because the ingredients were the most expensive I’d ever used. Not because it was the biggest event.

Because I felt respected.

And when you spend your career in hospitality, you realise how valuable that actually is.

So here’s something I’d say to anyone hiring a private chef: of course, think about the menu. Think about the wine. Think about the table. Think about the music.

But also think about who you’re inviting into the room.

Because you can hire a chef to remove the pressure of cooking. We can control the food. We can control the presentation. We can adjust the timing. We can solve problems you probably never even knew happened.

But there’s one thing we can’t control. Your guests.

And sometimes… they’re the most interesting ingredient of the entire fucking evening.

Jonathan Bradley

Entry 4

The Day I Stopped Chasing Job Titles

For years, I wanted the title. Head Chef. Then Executive Head Chef. Bigger operation. Bigger brigade. Bigger salary.

You spend years climbing the ladder believing the next title means you’ve finally made it.

Then one day I realised something. A title means fuck all if you hate the place you’re walking into every morning.

I’ve spent more than 20 years in professional kitchens. I’ve worked with chefs who became more than colleagues. When you’re getting absolutely destroyed during service, there’s a strange bond that develops.

Tickets won’t stop printing. Everyone’s sweating. Someone’s been burned. Someone else hasn’t eaten for 8 hours. The waiter is asking where table 24 is. You’re already thinking about tables 25, 26 and 27.

And the chef standing next to you doesn’t even need to ask what you need. They already know. That’s a brigade.

That’s why I’ve always struggled when people describe kitchen teams like ordinary office departments. They’re not.

You spend more time with these people than you do with some members of your own family. You argue. You laugh. You swear at each other. You fall out. Then 30 seconds later you’re plating the same table together because service doesn’t give a shit about your feelings.

I’ve lost friends through this industry. I’ve also met people I once called brothers. Some stayed. Some didn’t. That’s life.

But the chefs I respected most taught me something I’ve carried through my entire career: you bleed and burn with me, I’ll bleed and burn with you. That’s loyalty.

I’ve also watched the industry change. Some changes have been brilliant. Kitchens needed to change. The screaming, bullying and ridiculous behaviour that used to be accepted as ‘that’s just how kitchens are’ didn’t make anyone a better chef.

But we’ve lost something along the way too. Craft.

I remember kitchens where chefs made things properly. Stocks bubbling away. Sauces being reduced. Fish being broken down. Meat being butchered. Pastry being made. Vegetables arriving looking like they’d actually come out of the fucking ground.

You learned. You fucked things up. Someone showed you why. Then you did it again. And again. Until eventually your hands knew what to do before your brain had even caught up.

Now? I’ve walked into kitchens where the supplier has done half the cooking. Open packet. Heat. Plate. Serve. Then someone puts a micro herb on top and calls it homemade.

Maybe that’s efficient. Maybe it makes the spreadsheet look fantastic. But that’s not why I became a chef. I became a chef because I wanted to cook.

As I climbed higher, something else changed. The further you move from the stove, the more meetings appear. Food cost. Labour. Forecasts. Budgets. Targets. Reviews. Reports. Emails. More emails.

Then another meeting about the email nobody answered.

Of course those things matter. I’ve run big kitchens. I understand that a restaurant isn’t a charity. If you don’t make money, eventually there isn’t a restaurant.

But somewhere amongst all those spreadsheets, it’s very easy to forget the reason the customer walked through the door. The food.

And it’s very easy to forget the people producing it.

There was a time when I’d see an Executive Head Chef vacancy and immediately look at the salary. How big is the hotel? How many outlets? How many chefs? What’s the title? What’s the next step?

I don’t think like that anymore.

Now I want to know: who am I working for? How do they treat people? Do they actually care about food? Will I have the freedom to create? Can I build a brigade? Can I develop young chefs? If something goes wrong, do management look for a solution… or somebody to blame?

Because I’ve reached a point in my career where another impressive line on my CV isn’t enough.

I’ve already proved I can run kitchens. I’ve already proved I can handle pressure. I’ve already proved I can walk into chaos and find a way through it.

What I haven’t got anymore is the desire to sacrifice myself just to protect somebody else’s job title.

And that’s probably why private cheffing has changed me.

When I’m standing in somebody’s kitchen cooking a 5-course dinner, there’s nowhere to hide. No massive brigade. No corporate brand above the door. No marketing department. No General Manager. No reputation of a hotel carrying you.

It’s just me, my food, my standards, my personality, my name.

If it’s brilliant, that’s on me. If it’s shit? That’s on me too. And strangely, I love that.

It’s reminded me why I started cooking in the first place.

I’m still ambitious. I’m still interested in leading a serious kitchen. I’m still interested in the right Executive Head Chef position.

But there’s a massive difference now. I’m not desperate for the title.

If I walk into an interview, they’re interviewing me. But I’m interviewing them too.

Because the next chapter of my career isn’t about proving I can become an Executive Head Chef. I’ve already been one.

It’s about finding somewhere worthy of the years I still have left to give.

Somewhere I can cook. Lead. Teach. Build. And actually give a shit again.

And if I don’t find it? I’ll keep building something of my own.

Because after more than 20 years chasing the next rung of the ladder, I’ve finally realised: success isn’t having the biggest title in the kitchen. It’s being able to look at the person wearing the jacket and still recognise yourself.

Jonathan Bradley

Continue the Diary

The next stories are for subscribers.

You’ve read the first four entries. If you want the rest — the deeper stories, the difficult moments, the private chef chaos and the honest industry truth — that’s where the subscription begins.

Unlock the Full Diary

Subscriber Preview

Subscriber Story 01The Day I Stopped Chasing Job Titles