Around year six of Encore, we had a recruiter who kept overriding the default candidate status labels. She had her own system. Color-coded sticky notes on her monitor, personal shorthand in the notes field, a whole parallel workflow running alongside the platform. The system we built had role-based views for a reason. Recruiters see pipeline. Candidates see status. Admins see everything. But her per-user behavior was drifting from the persona we’d designed, and it was dragging three other recruiters with her. Small accommodations had compounded into a shadow process.

I fixed it by adding a configurable label layer. Kept the shared architecture underneath, kept the role-based views, but gave individual recruiters room to name things in language that matched how they actually worked. Three layers: the platform everyone shares, the role-based experience, the individual adaptation.

That same week I was home standing in the kitchen trying to figure out dinner. Four people. Four different sets of restrictions. I had a batch of shredded chicken, rice in two forms, a red sauce, and roasted vegetables from Sunday. The question was assembly. Peter gets the gluten-free tortillas. One kid gets the rice bowl with no meat. The other gets the regular tortillas with everything. My wife gets her version. Same base ingredients, four plates, each one built to the person eating it.

I didn’t notice the parallel at the time. I was just tired and trying to get food on the table before 7:30.

But the structure is identical. At Encore, the group body is the platform architecture. The persona layer is role-based views. The individual accommodation is per-user configuration. In the kitchen, the group body is the batch base (protein, starch, sauce, vegetables cooked in volume). The persona layer is the cuisine framework (Italian night, Mexican night, BBQ night) that tells me how to season and combine. The individual accommodation is per-person assembly.

Both systems face the same governance problem. Drift. At Encore, drift looked like a recruiter building a shadow process because “close enough” decisions accumulated over months. In the kitchen, drift looks like me skipping the Sunday batch cook because I’m flaring and then spending the whole week improvising meals from whatever is in the fridge. Both cases follow the same pattern: the person maintaining the system makes one small concession, then another, then another, and by Thursday the structure is gone.

And both systems have to survive low-resource days. At work, that’s an understaffed sprint where the team is running at 60% capacity. At home, that’s an autoimmune flare where I’m operating at maybe 40%. The question is the same in both rooms: does the system hold when the person running it is depleted? If the answer is no, it’s not a system. It’s a performance that requires full energy every time.

I want to be careful here. I’m describing something that sounds clean. It isn’t. The kitchen still breaks down. I still have weeks where the batch cook doesn’t happen and we’re eating scrambled eggs for dinner on a Wednesday. Encore had stretches where the governance we built couldn’t keep up with how fast the user base was changing. The three-layer model gives me a way to see what’s happening, to diagnose where the drift started, to know which layer broke. It doesn’t prevent the breaking.

I used to think I was applying enterprise thinking to the household. That I’d learned something at work and brought it home. But that’s not what happened. I’ve been cooking for a family with complex restrictions for longer than I’ve been building recruiting platforms. The kitchen came first. The operation was already running before I had any vocabulary for it.

I build the shared base, differentiate by role or context, then accommodate the individual. I do it at work. I do it at home. I do it when I’m designing a system and when I’m plating four different dinners from the same batch of chicken.

It helps. It doesn’t solve. The weeks it breaks are the weeks I learn the most about where the structure needs to be stronger. That’s the practice. Ongoing, imperfect, and never finished.