My father was a concrete mason. One of the best I've ever seen. He could read a pour the way other people read a room, knowing exactly where the material would settle, where the finish would need attention, where the margin for error was and wasn't. Nobody on a job site questioned his craft.
But what made him exceptional wasn't just his skill with concrete. It was knowing when to step back and direct, when to let the crew work, and when to get his hands in it himself. The best tradespeople I've known understand that mastery of the craft and mastery of the work are two different things. One is about what you can do. The other is about what gets done.
A lot of technical people in corporate environments never figure that out.
The Competence Trap
Early in a technical career, being the best at the work is the whole game. You get recognized, relied on, and rewarded for being the person who can solve the hardest problems fastest. That's real and it matters. But the behaviors that earn you that reputation start working against you the moment the organization needs something different from you.
The best technical person in the room gets pulled into every hard problem. They become the answer to every question. And because they're good, they keep answering, keep solving, keep being indispensable at the execution level. Meanwhile the strategic conversations, the ones about direction and priority and what the organization should be doing next, happen without them.
Not because they're not capable of contributing. Because they're too busy being the best at what they already do.
What the Ceiling Actually Looks Like
You don't hit it all at once. It's gradual. You notice that certain meetings keep happening without you. That decisions get made and then handed to you to implement. That your opinion gets sought on technical questions but rarely on anything upstream of those questions.
You're excellent at your level and invisible above it. And the longer it goes on, the harder it is to change because the organization has you categorized. You're the person who executes brilliantly. That's valuable. It's also a box.
The Shift That Has to Happen
Getting out of that box requires doing something that feels deeply counterintuitive to people who built their identity on technical excellence. You have to start letting other people be the best at the execution, and redirect your energy toward the problems that sit above execution.
That means asking different questions in meetings. Not "how do we build this" but "should we build this, and what are we trading off if we do." It means writing up your thinking rather than just demonstrating it. It means investing time in making the people around you better rather than staying the person they all depend on.
In concrete work, the moment you become worth more as a foreman than as a finisher, you have to make that transition or you'll be finishing concrete for the rest of your career. There's nothing wrong with that if it's what you want. But if you want something more, you have to be willing to stop being the best at what you already are.
The Identity Part Is the Hard Part
The real obstacle isn't skill. Most technically strong people can develop strategic thinking relatively quickly once they decide to. The obstacle is identity. Being the best in the room at something feels good. Giving that up, even temporarily, even in service of something bigger, is uncomfortable in a way that's hard to explain to people who haven't experienced it.
But the people who make that transition successfully carry their technical credibility with them. They don't stop being experts. They become experts who can also see the bigger picture, which is a combination almost nobody has and every organization desperately needs.
The goal isn't to stop being good at what you do. It's to stop letting it be the only thing you're known for.