I was standing at the stove one night, adjusting the heat under a pan of onions, when it hit me. I’d done this exact thing that morning at work. Different material. Same four moves.

At work it was a migration plan for a legacy codebase. I’d spent thirty minutes reading the state of things: what the team understood, what they didn’t, where the real risk was hiding. Then I reached into what I knew about incremental rollouts and contract testing. I picked the one approach that fit this team’s capacity and this system’s constraints. And I sequenced the phases so each one reduced risk for the next.

At the stove I was reading the onions. Reaching into what I knew about heat and sugar and timing. Picking a lower temperature because the pan was thin and the pieces were uneven. Sequencing the steps so the garlic went in late enough to not burn.

Same four moves. Different room.

The Selector

I didn’t design this pattern. I found it by looking backward.

Once I started paying attention, I couldn’t stop seeing it. Every room I’d ever worked in, every material I’d ever handled, the same operation was running underneath.

Four moves. I started calling it The Selector.

Read. What does this room actually need right now? Not what it says it needs. Not what I planned to give it. What’s actually happening in front of me. The energy in the room, the state of the system, the constraints nobody mentioned yet.

Reach. Into the accumulated repertoire. Everything I’ve studied, built, broken, repaired. Design history, musical knowledge, pedagogical tools, cooking technique, architectural patterns. The crate. You spend decades filling it, and then you spend the rest of your life reaching into it.

Select. Not the best option. The right option for this room at this moment. A track that’s technically perfect but wrong for this crowd at 1 AM is the wrong track. A teaching method that works beautifully in theory but overwhelms this particular student is the wrong method. Selection is judgment, and judgment is where the years show.

Sequence. Because order matters. Pacing matters. The arc matters. You can have every right element and still lose the room if you put them in the wrong order. The first thing you play sets the expectation. The first thing you teach sets the frame. The first migration step determines whether the team trusts you for step two.

The Same Operation in Every Room

Behind a pair of turntables, this was instinct before I had words for it. Read the floor. How are people moving? What did the last track do to the energy? Reach into the crate, thousands of records organized by feel as much as genre. Select the one that answers what the room is asking for. Sequence the transition so the energy builds without breaking the thread.

In a classroom, the same operation looked completely different on the surface. Read the student. Not their test scores, their actual state. Are they shut down? Overwhelmed? Bored because the scaffolding is too low? Reach into the pedagogical toolkit. Select the accommodation that meets this kid where they are right now, not where the lesson plan assumes they should be. Sequence the supports so each one builds capacity for the next.

On Encore, it was the same thing at enterprise scale. Read the codebase and the team. Where is the drift? Where has intent separated from execution? Reach into twelve years of institutional knowledge and architectural patterns. Select the approach that this team, with these constraints, can actually execute. Sequence the work so early wins build momentum.

Even writing this post. I’m reading you, the reader, trying to gauge what you’ve absorbed from the previous twenty-two posts. Reaching into examples and framings I’ve accumulated. Selecting the ones that will land without belaboring what you already understand. Sequencing so the recognition builds.

What I Didn’t Know I Was Doing

Here’s the honest part. I was doing this for twenty years before I could name it. The Selector wasn’t a framework I developed and then applied. It was a pattern I recognized after the fact, by looking at the shape of my own decisions across wildly different contexts.

DJing taught it to me physically. The read-reach-select-sequence cycle happened in real time, hundreds of times a night, with immediate feedback. The floor tells you instantly whether you selected right. That somatic training carried into every room after. I learned to read energy before I learned to read code.

Teaching reinforced it. A classroom gives you the same real-time feedback loop, just slower. You read a face and know in three seconds whether your selection landed. You adjust. You reach again. The cycle runs continuously.

By the time I was working in enterprise software, the pattern was so deep I didn’t think about it anymore. I just did it. It took writing these posts, looking back across the rooms, to see that one operation had been running the whole time.

What Changes Now

Once you see the pattern, the question shifts. It’s no longer “what do I do in this new room?” It’s “how does each of these four moves actually work, and how do I get better at each one?”

Reading a room is its own skill. It can be sharpened. The reach depends on what you’ve put in the crate, and how you’ve organized it. Selection is the hardest move to teach because it’s where experience becomes judgment. And sequencing is where most people lose the room, because they have the right pieces in the wrong order.

That’s where this series goes next. The pattern is visible now. The next movement takes each step apart.