Stop Calling It Broken. You Were Hired to Build It.
We are living through a shift that most job descriptions have not caught up to yet.
AI and the pace of disruption are compressing the work that used to define a run job. Systems that once needed a team to keep humming now maintain themselves, or close to it. Software patches itself. Reports generate themselves. The run work is not vanishing, but the human share of it is shrinking to oversight, and whole categories of “keep it operating” work are getting absorbed by the machine every quarter.
Here is the part most people have not built inside themselves yet. Entire careers were shaped around the run. People trained for decades to inherit a system, protect it, and keep it steady. That is a real skill and it took real years to earn. But it is not the same skill as building something from nothing, and nobody handed most professionals the second skill along with the first. That muscle was never exercised because it was never required. Now it is required constantly, and the gap between the skill people spent a career sharpening and the skill the market suddenly wants is where a lot of quiet panic is coming from.
There are two kinds of jobs. One asks you to run something that already exists. The other asks you to build something that does not. They can carry the same title. They can sit in the same Unit. They are not the same job, and confusing the two is where good hires go bad, especially now, when the ratio between them is shifting fast.
A run job! It comes with infrastructure. The systems work. The playbook is written. Your value is consistency, quality, and stewardship. That is honorable work and every organization still depends on it, even as there is less of it to go around.
A build job! comes with ambiguity. The systems do not exist yet. The playbook is blank because you were hired to write it. Your value is judgment, invention, and the willingness to work without a map. That is also honorable work. It is just a different kind, and it is the kind this moment increasingly asks for.
The trouble starts the moment someone accepts one and expects the other.
The Conversation I Have Had Too Many Times
I have created positions at my institution that did not exist before the person walked through the door. In those conversations I say it plainly. This role is new. The systems are not built. I need you to help me build them. People nod. They accept the offer. They accept the salary that reflects the difficulty of a build.
Then, months in, I hear that it is too much work. That there is no infrastructure. That nothing runs smoothly. That the role requires a level of risk, build critical thinking they did not expect. None of that is a surprise. All of it was the job description.
My rule. If the role did not exist before you, nothing about it was ever going to run smoothly on day one.
The Dead Giveaways
You do not need a memo to know which job you are being offered. Two signals tell you almost everything before anyone says a word.
A title that never existed before is the first one. If the position has no history at the organization, there is no precedent for how it runs, because it has never run at all. You are not stepping into a seat. You are building the seat.
A Unit that was just created is the second one. New units do not inherit workflows, reporting habits, or institutional muscle memory. Whatever gets built inside that unit gets built by the first people standing inside it. That is you.
Neither signal is subtle once you know to look. They are not warning signs that something is wrong. They are the plainest evidence available that the role in front of you is a build, and the pathways still need to be laid before anything can run on them.
The Promotion Trap
This is not only about the job you take from the outside. It is about the job you get promoted into from the inside, and that version of the trap is harder to see because everything around you looks familiar.
A promotion feels like a reward for running well. You kept your Unit steady, you hit your numbers, you earned the next chair. So you carry the operator’s mindset up a level and expect a bigger version of the job you just left. But the next chair up is often a build wearing a promotion’s clothing. A new function the organization has never had. A restructured portfolio nobody has managed before. A mandate to create what your old role only had to maintain.
The person who gets promoted and keeps running is the most common quiet failure I see in leadership.
They were excellent at the job below and they keep doing it from the job above, polishing systems that already work while the thing they were elevated to build sits untouched. Nobody warned them the promotion changed the category of the work, not just the size of it.
So before you accept the promotion, ask the same question you would ask a stranger offering you a job. Is this a bigger run or is this a build. The title going up does not tell you. The work does.
To the Supervisor
Clarity is your responsibility, and it does not end at the offer letter.
If you are hiring for a build, say so in the posting, in the interview, and in the first week. Do not dress a build as a run to close a candidate. Do not use the language of stability to sell a role defined by construction. That is how you manufacture resentment on a delay, and it always arrives.
Then keep saying it. Ambiguity feels different at month four than it does at the interview table. When a builder hits the hard middle, remind them what they signed up for and why you chose them for it. Give them air cover, resources, and honest feedback on the thing they are inventing, not the thing you wish already existed.
Four errors I watch supervisors make, and what I do instead.
One. Selling a build as a run to close the hire. The systems get described as “still settling” instead of “not yet built.” I tell the candidate exactly what does not exist yet, in the interview, out loud, before an offer is on the table.
Two. Going quiet after the offer letter is signed. The truth gets told once and never again, and four months later the builder is drowning with nobody repeating the deal they made. I repeat it. I check in on the hard middle specifically, and I remind the person why I chose them for exactly this kind of problem.
Three. Treating every complaint as a clarity problem. Sometimes the person does not understand the role. Sometimes the role is the wrong fit for who they are. Those are different diagnoses and they need different responses. I ask which one I am looking at before I decide how to respond.
Four. Promoting the best operator into a build and calling it a reward. Running well proves someone can run. It does not prove they can build, and elevating them without naming the shift sets up a loyal performer to fail in public. When I promote someone into a build, I tell them the category of the work is changing, not just the scope, and we talk about whether they actually want the blank page before they say yes.
To the Employee
Understanding the job you accept is your responsibility, and it does not end at the signature. That applies to the promotion you accept from the inside just as much as the offer you accept from the outside.
Before you say yes, ask the question that matters. Am I being hired to run something or to build something.
If the answer is build, believe it. The missing infrastructure is not a flaw in the role. It is the role.
The compensation tells you the same thing. Organizations pay a premium for builds because they understand the time, the effort, and the judgment required. You cannot take the builder’s salary and expect the operator’s day. If what you actually want is a role where the systems hum and the path is paved, that is a legitimate want. Go pursue it openly. But name it honestly, to yourself first.
There is a whole genre of workplace content right now insisting that friction is always a management failure and difficulty is always a red flag. Some of it is useful. Much of it flattens the difference between a build and a run into one generic complaint about employers. That flattening hurts everyone. It sets employees up to feel betrayed by jobs they were told the truth about, and it teaches organizations to stop trusting the people they hire to build.
Four errors I watch employees make, and how to avoid them.
One. Accepting the offer without asking the one question that matters. Ask it directly, in the interview, and listen to the actual answer instead of the answer you want to hear.
Two. Treating a promotion as a bigger version of the old job. Many promotions change the category of the work, not just the size of it, and the person who keeps operating from a chair they were elevated to build from fails slowly and visibly. Ask the run or build question about every promotion.
Three. Mistaking ambiguity for dysfunction. A missing playbook in a build role is not evidence the organization is disorganized. It is evidence you were hired before the playbook existed. Name that difference for yourself early, so you are not diagnosing the wrong problem six months in. I will say it again! Do Not Mistake Ambiguity is Dysfunction. They both might exist, but knowing the difference is everything!
Four. Staying quiet about the mismatch instead of naming it. Silent frustration curdles into resentment, and resentment shows up as disengagement long before anyone names the actual issue. If the job feels different from what was promised, say so directly and early, while there is still time to fix it or to leave with clarity instead of bitterness.
The Needle
This is not about blame. It is about self knowledge before the handshake, whether that handshake happens at an interview table or in your own boss’s office.
And here is the part that ties it together. Every build is supposed to become a run. The builder’s real deliverable is not just the thing. It is the playbook that lets someone else run the thing. A builder who cannot make their work survivable without them has not finished building. A supervisor who cannot tell when a build has become a run will keep paying build premiums for run work.
Knowing which phase you are in is the whole discipline.
Builders are rare and I treasure them. The people who thrive in a build do not pretend it is easy. They knew it would be hard and they came anyway. They find meaning in making something exist that did not exist before. Watching them work is one of the great privileges of leadership.
Runners are essential and I cherish them. They are the reason anything scales. A build that never finds its runners stays a prototype forever, and an organization of nothing but builders is a pile of half finished systems with nobody keeping the lights on. Consistency is not the absence of ambition. It is what ambition looks like once it works.
The key is knowing who you are and which job you took. Get that match right and both kinds of people do the best work of their lives. Get it wrong and the mismatch ends careers on one side and starts organizational decline on the other.
So here is the deal, stated as plainly as I can make it.
Supervisors, tell the truth about the job. Every time. Including the promotion.
Employees, hear the truth about the job. Before you take it. Especially the promotion.
A build is not a broken run. It is a build. And in a world where the machines are taking over more of the running every year, the organizations that thrive will be the ones honest enough to name the difference, and the people who thrive will be the ones brave enough to choose it.
Take the job you actually want, then want the job you actually took.