There is a version of professional growth that is easy to accommodate. You get better at the job. You get faster. You build expertise. You take on harder assignments. Maybe eventually the title changes. That's growth we understand.
But sometimes something else happens. The person doesn't just get better at doing the work.
The recruiter starts noticing patterns across searches. The operator starts questioning the operation. The person executing the process starts seeing where the process itself is creating the problem. They build something. They connect things that weren't previously connected. Their questions change. Their contribution starts stretching beyond the boundaries of the role they were originally hired to perform. And now we have a different question.
Growth changes the work.
I think we sometimes talk about development as though the person changes while the job stays perfectly still. Learn this competency. Take on this assignment. Develop this skill. Demonstrate this behavior. Progress. But real growth isn't always that tidy.
Sometimes learning one thing changes how you understand everything around it. You learn to use data, and suddenly you're not just looking at whether a search is moving. You're asking why it's moving the way it is. You develop deeper domain knowledge, and now you can challenge an assumption you previously would have accepted. You understand the process well enough to recognize that the problem isn't actually the process. You solve enough individual problems that eventually you notice you're solving versions of the same problem over and over again.
And then you stop asking: How do I solve this one? You start asking:
That's a different altitude of work. The original responsibilities haven't necessarily disappeared. You've just developed the ability to see beyond them.
I don't think expertise means already knowing.
This is something I've had to reconsider over the course of my career. There was a time when I thought being a strong recruiter meant I should be able to recruit anything. Give me the role. I'll figure it out. And yes, there are recruiters who are extraordinarily adaptable. Learning quickly is part of the craft.
But I've developed a much deeper respect for domain expertise. Knowing enough to recognize nuance. Knowing how the people you're recruiting think and talk. Understanding the work well enough to know when an answer makes sense in context. Knowing the market. Knowing the history. Knowing enough to ask a better question. And also knowing enough to know what you don't know yet.
That last part matters. Because I don't think capability comes from reaching some magical point where you finally possess all the answers. I'm not sure that point exists. I think it comes from developing the ability to enter increasingly complicated problems and figure out what you need to learn next. Ask questions. Find the information. Seek expertise. Experiment. Come back. Try again. Eventually, you're not just accumulating knowledge.
And that can take someone's work in directions nobody predicted when the job description was written.
Pressure can reveal capability.
I don't think all constraints are bad. Actually, some of the most meaningful growth can happen because the work gets harder. A complicated problem asks more of you. You stretch. The next one asks for something else. You stretch again. Eventually, you're doing work you wouldn't have known to ask for because you didn't know you were capable of doing it yet.
There is something powerful about being in an environment that gives you enough challenge to discover your own range. That kind of pressure can sharpen you. It can reveal strengths. It can force you to develop muscles that easier work never would have required.
Sometimes you find out you're a builder because somebody gave you something that needed building. Sometimes you discover you're good at strategy because execution alone stopped solving the problem. Sometimes you realize you've been thinking in systems because you finally have enough complexity in front of you to see the system. That kind of stretch can transform a career.
But there is another kind of pressure.
Stretching someone is different from containing them.
One asks:
The other says:
Those are not the same environment. You can challenge someone enormously and still give them room. Room to question. Room to experiment. Room to build. Room to bring back something different from what you originally asked for. Room to say, I think the problem is somewhere else. Room to develop a perspective. Room to be wrong and learn something. Room to become more capable than the original role required.
Without that room, something happens to the work. It gets smaller. Not necessarily because the person becomes less capable. Because eventually people learn where their capability is welcome. If every attempt to improve something gets redirected back toward execution, you execute. If every question is treated as resistance, you stop asking. If every idea outside the immediate assignment is considered outside your lane, eventually you learn the dimensions of the lane. The organization may still have a high performer. But it may never discover what else that person could have built.
Organizations love builders. In theory.
Builder is one of those words that sounds great. We want builders. Innovators. Strategic thinkers. People who take initiative. People who challenge assumptions. People who see around corners. People who don't wait to be told exactly what to do. I understand the appeal. Those people can create enormous value.
They can also be inconvenient. Because a builder eventually notices something that could be built better. A strategic thinker eventually develops a strategy. Someone who challenges assumptions will, at some point, challenge your assumption. Someone with initiative may create something that wasn't on the roadmap. Someone who sees around corners may tell you there's something around the corner you would rather not deal with yet.
That's the bargain. You don't get the upside of expansive thinking while requiring the person doing it to remain perfectly contained. If you want people who think beyond the task, you have to create some room for what they see.
Not every expansion needs a promotion.
I want to be careful here. This isn't an argument that every new capability deserves a new title. Or that every idea deserves adoption. Or that ambitious people should be allowed to roam around organizations doing whatever they want because they have declared themselves strategic. Absolutely not.
Ideas still need evidence. Work still needs to create value. People still need feedback. Priorities are real. Businesses have constraints. And sometimes the answer to a good idea is still no.
But I think there's a difference between evaluating someone's expanding contribution and simply trying to fit it back into the shape you're accustomed to. Maybe the role grows. Maybe the person eventually moves into another one. Maybe a project becomes part of their scope. Maybe their work influences something outside their immediate team. Maybe the organization discovers a capability it didn't know it needed. The answer doesn't have to be predetermined. That's the point. Growth should be allowed to produce possibilities we didn't already plan for.
The role is a container. It shouldn't become a ceiling.
Job descriptions are useful. Levels are useful. Responsibilities matter. Organizations need structure. But those things describe work at a moment in time.
People keep moving. They learn. They encounter harder problems. They develop new interests. They become better at things nobody hired them to do. They connect dots that weren't connected when their role was created. And sometimes, if they're given enough room, the work starts becoming something bigger.
I think organizations should pay attention when that happens. Not because every person needs unlimited space. Because capability is an investment you've already been making. You gave someone the problems. The context. The repetition. The pressure. The opportunities to learn. And somewhere inside all of that, they became capable of something new.
It would be strange to cultivate that growth and then become uncomfortable when it no longer fits neatly inside the original box.
Maybe the better question isn't:
Maybe it's: