Ops Term of the Month: Lean
Lean is precision.
Most people hear "lean" and think smaller. Fewer people, fewer resources, doing more with less. That's not what it means, and half a definition isn't good enough to build an Ops Term on. The term comes out of a Toyota assembly line, and the version that made it that far had almost nothing to do with cutting things thin. Lean means eliminating waste, anything that doesn't add real value, so what's left is pointed straight at what matters.
We're a Kitchen Nightmares household, and the show is basically a documentary on what happens when a kitchen loses that. Gordon Ramsay walks into a restaurant that used to be good. Now the menu is fifty pages long, the fish is frozen when fresh and local is easy to get, and the person who brought the heart to the place either left or got worn down trying to hold it together. Nothing about that restaurant got leaner. It got heavier, and it lost its way.
A kitchen that's actually lean looks different. The menu is dialed in. There’s a recipe card for every dish, so the flavor doesn't depend on who's cooking that night. Ingredients are staged before service, not scrambled mid-order. When the rush hits the grill station harder than the salad station, someone moves over and works the grill, because the goal is clean plates on time, not defending a job title. Nothing is wasted, not food, not time, not skill, and everything left is pointed straight at the plate going out the door.
Here's what that looks like at E.TBD:
Roles get sized to the actual work. People aren't locked into one fixed title regardless of what an engagement needs. Team members get assigned based on what the work calls for and what they're skilled for, so the right skill lands on the right problem instead of whoever happens to hold the title.
Shared services means nobody overhires, and nobody's stuck in a part-time patchwork. Earlier this year, one Executive Assistant worked full-time, not by serving one org, but by covering the EA needs of two or three organizations at once. None of those orgs needed a full-time EA on its own. But split the role across a few of them, and it added up to full-time, stable work for the person in it. We're bringing the model back this fall, same shape, three clients and one person covering all three. Nobody's hiring for capacity they don't need, and nobody's cobbling together three part-time gigs just to make rent.
Structure protects space instead of dictating it. Delshan has designated days for how she uses her brain: worktime for allocated tasks, focused time for the thinking a day calls for, humantime for just being a person, and unallocated time held open for whatever the week actually needs. A blocked two hours for what matters doesn't feel like an order. It feels like room made on purpose.
Summer runs on pull, not shrinkage. Fewer contractors active, focus on current straightforward engagements, Maya covering the external-facing work Delshan usually leads. That's not the team running thin. It's the team staffed for what the season is actually asking for, and no more than that.
That's not the restaurant that lost its heart. That's the opposite of it.
Lean. Not thin. Not stretched. Just precise, and pointed at what actually matters.
We shared this article in E.TBD’s newsletter. You can read the full issue here or subscribe here.
