The Sous Chef Who Barely Moved

I was standing in the walk-in cooler when the chef started yelling. Really yelling, the kind that isn't kind. I couldn't find two ingredients. They were stacked in there somewhere, some up front, some buried behind, and I was expected to find them fast. I couldn't. She told me, not gently, that I couldn't see what was right in front of my face.

I blinked hard and refused to cry. I was a good Boston girl who'd built a career in male-dominated tech, and the rule in both worlds was the same: you do not cry. So I swallowed it and kept moving.

Here's what I only understood years later: she was wrong. It wasn't that I couldn't see. It was that the whole system of that kitchen lived inside her head and had never been mapped for anyone else. She was a brilliant, fiery chef who ran the place on instinct and adrenaline, which meant a new, exhausted intern had no way to find her footing.

And I was exhausted. This was a serious Chicago kitchen with a menu that changed nightly, open past midnight, and I was only there as an unpaid stage, moonlighting after my full-time tech job. So I ran. Prepping here, hunting there, forgetting a step and doubling back, in constant motion and never quite sure where anything was. From the outside it looked busy. From the inside it was quiet chaos. My running wasn't the problem. It was the symptom of a kitchen no one had ever mapped.

Near the end of my stage, the chef hired her permanent sous chef. And he barely moved.

That was the first thing I noticed. He was calm in a room that had no calm in it. He asked pointed questions, showed us the ropes, anticipated what each of us would need before we needed it. He'd stand at his station, ask a question here, say a quiet word there, and somehow the work was just... done. It looked like magic. I caught myself a little in awe of him.

It took me a long time to understand what I'd seen. He wasn't doing less. He was holding the whole kitchen in his head, and then setting the room up with what he knew, so no one had to run. The chef knew her kitchen too, but her knowing stayed locked inside her. His mastery was that he made the kitchen knowable for everyone in it.

That's a kind of efficiency I'd never seen in tech, where efficiency meant doing more things faster. This was efficiency of movement. He didn't cook less food. He cooked more, with less wasted movement than anyone on the line. The doing was never the problem. The motion around the doing was.

I think about that kitchen often now, because most of us are running it without realizing. The work is real and the pace is real, and none of that is what wears us down. What wears us down is the motion between the work. Running to one tool to find a client's intake, another to see if they messaged, a third for the note we wrote last week. Retyping the same thing in four places. Standing in our own walk-in, exhausted, unable to find what we know is right there.

And here's the trap, because I've fallen into it on both sides of that door. For years I was the exhausted intern, running. Later, building my own businesses, I became the chef, with the whole operation in my head, running on memory and reaction, sure I could hold it all because I always had. Both are exhausted. Both are working inside a kitchen no one ever mapped.

The fix isn't to do less. The sous chef didn't have a shorter menu. He had a system, so the long menu didn't cost him extra steps. For the rest of us, that system can't all live in our heads, and it shouldn't have to. It looks like one place a client's information lives, instead of six. A booking that updates your notes on its own. An intake someone poured themselves into that actually follows them through, instead of a form you glance at once and forget.

So much of the running is just trying to remember who a client really is... what they said, what they're actually struggling with underneath the thing they booked. That knowledge is the heart of the work, and it usually sits scattered across notes and tired memory.

That scattered knowledge is exactly what we're building Sidkik to hold. The whole point is to bring the pieces of your practice into one place, so your operations finally feel easy and the person in front of you is right there when you need them, not buried six tabs deep. Less motion, more of you available for the work that matters.

And while we build it, we made a free tool to help in the meantime: Know Your Client, a faster way to get to a real understanding of the person you're working with today. Less hunting, more knowing.

I still think about that night in the walk-in. The cold, the full hands, the tears I refused to let fall. She told me I couldn't see, and she was wrong. I could see fine. I just couldn't see inside her head, which was the only place the kitchen existed. A few weeks later I watched someone who didn't keep it there, who stood almost still and got more done than any of us, because he'd done the quiet work of knowing his world and making it knowable.

That's the whole promise. Not a smaller practice. Not less care. Just less motion between you and the work you came here to do.

Less motion, not less doing.

Find out even more about your client → Know Your Client (free)