Range Is The Asset

I've been thinking about a pattern I noticed years ago and never had good words for. It came into focus on my way out of Meta, when I spent some time looking back at the leads I'd worked with across a decade and trying to figure out what actually separated the ones who moved the company from the ones who didn't.

Almost everyone had a lane. Some leads lived in code reviews. Some lived in tickets. Some lived in pixels. They were all excellent at what they did, and the work they produced was the work you'd expect from a person operating at the top of their altitude. None of them, on their own, were moving the company.

The ones who were moving things were doing something different. They'd start a message about a specific bug and four sentences later be naming a structural pattern. They'd answer a tactical question with a proof-of-work example they'd shipped that morning. They'd reframe an org complaint as a product decision. One person, one message, three or four different altitudes.

That's the move. That's the thing most design leadership advice tells you not to do.

The standard advice is to pick a lane and get excellent at it. Strategy at the executive table. Craft in Figma. Coaching in 1:1s. The argument is that mastery requires focus, and focus requires constraint. Pick the altitude that fits your stage and stay there.

I don't think that's right anymore. Production time is collapsing and design teams are shrinking. When your team is three people instead of twelve, you can't afford a leader who only does strategy. You also can't afford a leader who only does pixels. The rare person is the one who does both in the same conversation.

That's what range is. Not being competent at multiple things. Being able to move across them in real time, in a single message, without losing the thread.

There are three moves I've watched range operators make that the one-altitude leads can't copy.

The first is that they stack altitudes in a single message. When someone asks about a specific bug, they answer the question, name the structural cause, and tie it back to the company's goal, all in one paragraph. Not as three separate replies. The tactical answer lives inside the strategic observation lives inside the culture frame. The reader has to move with them from layer to layer. Most people will tell you this is "not staying focused." It isn't. It's operating at the altitude the problem actually lives at. Bugs don't exist in only one layer. Strategy doesn't exist in only one layer. You have to match the shape of the thing you're working on.

The second is that they argue with something they just shipped. One-altitude leads argue with abstractions. "We should be shipping faster." "Our product isn't premium enough." "The team needs better tooling." All true, all generic, all impossible to disagree with in a way that goes anywhere. Range operators argue with a thing. "I shipped this yesterday in three hours. Here's what it proves." Now the abstraction is grounded in evidence you produced. That's a move nobody can copy without also making the thing. The rule that the prototype is the decision extends up the stack. The artifact is also the strategy. The artifact is also the culture frame. The artifact is also the hiring argument.

The third is that they frame everything in customer outcomes instead of internal process. One-altitude leads get trapped in process language. Roadmaps, priorities, headcount, tickets. That vocabulary lives entirely inside the company. It doesn't touch the customer, and it doesn't touch the bet. Range operators frame craft decisions, hiring arguments, org design, and strategy memos in terms of what the company is trying to become. Every move is tied back to the bet. This is harder than it sounds, because it requires that you always know what the bet is. Most orgs don't. That's why most messages drift into process talk. It's the lowest-risk register for someone who isn't sure what they're supposed to be optimizing for.

Range is not a personality trait. It's a practice. And it's hard.

I catch myself regressing all the time. When I'm tired, my messages shrink to one altitude. When I'm overwhelmed, I drift into process language. When I'm not sure what the bet is, I start arguing abstractions instead of shipping the thing. Every one of those is a failure mode I keep having to climb out of. The people I admire most aren't the ones who never fall into single-altitude work. They're the ones who notice it faster than I do and pull themselves back out.

The fix is not getting better at any single altitude. The fix is protecting the practice of moving between them. Ship the rough thing in the morning. Name the structural pattern in the afternoon. Write the hiring argument in the evening. All in your own voice. All grounded in work you actually did.

The industry keeps telling design leaders to pick a side. IC or manager, strategy or craft, high altitude or ground level. That binary is comfortable because it gives you permission to stop doing half the job. The operators who are actually moving companies right now don't accept the binary. They do both at once, in the same paragraph, in the same conversation. The contrast with everyone else is what makes them legible.

Range is the asset. Protect it.