Sunday dinner. Four people at the table, three of them with incompatible diets. One batch of braised short ribs. One pot of polenta. One roasted vegetable sheet pan. That is the group body: the shared base that feeds everybody.

From there, the meals diverge. The Italian build gets the ribs over polenta with gremolata. The Mexican build gets the same braised meat shredded into tacos with pickled onion and cotija. The clean build skips the polenta entirely, doubles the roasted vegetables, adds the meat plain over greens. Three different plates. Same foundational batch.

That middle layer, the cuisine framework, is what I call the persona. Italian, Mexican, BBQ, French. Each one is a set of conventions: flavor profiles, techniques, plating logic. The persona gives you a grammar to work inside. It’s not the meal. It’s the set of decisions that make the meal cohere.

The third layer is individual accommodation. One person needs no dairy. Another wants heat. A third eats almost nothing green. Per-person assembly happens at the end, after the group body is built and the persona is chosen. It is the last mile. And it is where most systems break down, because most systems stop at the persona layer and call it done.

I didn’t discover this structure. I named it.

The same three layers show up everywhere I work. In a DJ set, the group body is the room’s baseline energy: tempo range, volume floor, the collective mood when you step behind the decks. The persona is the genre framework you are working inside, the specific grammar of house or breaks or ambient that gives the set its logic. The individual layer is the specific track selected for this specific moment, this transition, this particular shift in the room’s attention. You read one person leaning in or one group pulling back, and the next track is your accommodation.

In a classroom, the group body is the curriculum. Everybody gets the same content standards, the same learning objectives. The persona layer is differentiated instruction: the reading group, the math group, the cluster of kids who need visual scaffolding versus the ones who need verbal processing time. The individual layer is the IEP. One student’s specific accommodation plan. The thing that says: this person needs this particular adjustment to access the same material everyone else is accessing.

In a product, the group body is the platform architecture. The shared infrastructure that every user touches. The persona layer is the role framework: admin, contributor, viewer, each with its own set of capabilities and constraints. The individual layer is per-user accommodation. The settings, the accessibility preferences, the specific configuration that makes the platform work for this person in this context.

The pattern was always there. I didn’t learn it from a book or a workshop. I’ve always operated this way. I put ASCII art in code comments because I experience the code visually and I need the file to accommodate that. I built branded kitchen systems (mise en place stations, labeled containers, a whole batch-and-assembly workflow) because I experience the kitchen as a designed environment and four people with different needs eat there every night. The layers weren’t a model I adopted. They were a pattern I was already living in every room I worked in.

What changed was the naming. Once the pattern had a name, I could point at it. I could say to a client: your product has a strong group body and decent persona logic, but the individual accommodation layer is missing entirely. I could say to myself: this DJ set has great individual reads but the persona is incoherent, I am jumping between grammars. The naming made the pattern communicable. It turned something I did by instinct into something I could teach, diagnose, and design with.

That is the thing about frameworks that actually work. They don’t come from theory. They come from noticing what you’re already doing, then giving it enough structure that you can talk about it with someone else.