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.

1. 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.

2. 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.

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.

1. 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.

2. 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.

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.

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.

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.

So here is the deal, stated as plainly as I can make it.

1. Supervisors, tell the truth about the job. Every time. Including the promotion.

2. 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.

Running Unity for the better part of a decade, I have hired people into roles where the predecessor was beloved, resented, or quietly forgotten. I have also been the person who stepped into a chair others used to sit in. The pattern that follows is almost always the same, and it has almost nothing to do with which of those three the previous person actually was.

A newer supervisor once spent twenty minutes in my office, walking me through what their predecessor had gotten wrong. Staffing decisions. Budget choices. Tone with the team. The kind of detail that takes weeks to assemble. When they finished, I asked one question. What is your plan for the next ninety days? They did not have one. They had a dossier on somebody else. They thought that was the same thing. It is not.

And if you are a supervisor and your first instinct when something gets hard is to invoke what the last person did or did not do, you are telling everyone watching that you are not yet leading from your own authority. You are leading from theirs, and that is a borrowed posture. It has a short shelf life and a loud expiration date.

I have a list of five lines people will use to bait you into this trap, and the answers I have learned to give. We will get there. First, the bigger picture, because the answers only work if you understand why the trap is set in the first place.

Praising Them and Burying Them Are the Same Move

Both keep the previous person in the chair you are supposed to be sitting in

The team that misses the previous supervisor is doing it for a reason. Sometimes the previous person was actually great. Sometimes the team is anxious about change, and the past feels safer. Sometimes, a few people built their identity around being close to the old leader, and they are protecting that proximity. None of that is your problem to solve by trying to compete with the memory. Memory does not have bad days. You will. You will lose that fight every time.

The supervisor who blames the predecessor is making the mirror version of the same error. Every problem becomes inherited. Every weakness in the team is a leftover. Every uncomfortable decision is framed as a cleanup. It feels like accountability for the situation. It is the opposite. It is a way to stay outside the situation while pretending to lead inside it.

Whether you are praising them or burying them, you are still ceding the room to them.

The Baseline Is Not Yours Either

It is the floor you are standing on, not the explanation of who you are

Most people, when they finally stop talking about their predecessor, pivot to the baseline they inherited and start treating it as their starting point in the same way somebody else’s reputation used to be. That is also a trap, just a quieter one.

The baseline is what the unit was producing the day you walked in. Output, cost, quality, morale, turnover, customer experience, whatever the relevant numbers are for your function. That baseline is real, it is useful, and it is not yours. It belongs to the conditions, the people, and the decisions that produced it before you were in the chair. Use it the way a pilot uses a runway. Push off from it or pivot away from it. Do not dwell on it. Do not build a year of meetings around explaining it.

The baseline tells you where you started. It does not tell anyone what you are going to do. That is the only question your team actually wants answered.

Top 7 Lines People Will Use to Bait You, and My Approach

Save these. You will need them sooner than you think. Then say them in your own words, because canned lines from someone else’s playbook sound exactly like canned lines from someone else’s playbook.

1. “The last person never would have done it that way.” The opener. Usually delivered with a small smile, the way people deliver lines they have been holding for a while.

   Probably true. I am not the last person. I wasn’t in their shoes, I don’t know what they were weighing, and I can't grade calls I didn’t have to make. Here is how I am doing it. Here is why. If you want to push back on the why, I am listening.

2. “We tried that under the old boss, and it did not work.” This one sounds like data. It is not. It is a veto dressed up as history.

   Walk me through what specifically did not work. If there is a real lesson in there, I want it. If you are telling me not to try because someone else tried, that is not the same thing, and we are not going to run the unit that way.

3. “The previous person really understood us.” Almost always said with affection, which makes it harder to push back on, which is exactly why people use it.

   I have no doubt they did. I am not them. I am asking for the same window they got to learn the team on my own terms. I will earn the same standing, or I will not, but the comparison is not the work, and you knowing that I know that should tell you something.

4. My favorite. “Are you saying the previous person was wrong?” This is the trap dressed as a question. The person asking already has the headline written either way you answer.

   No. I am saying I am the one in the chair now, this is the call I am making with what I know, and if it turns out to be wrong, I will own that too. You are welcome to hold me to that. What I am not going to do is render a verdict on somebody else’s decisions to make myself feel better about mine.

5. The compliment that is actually a comparison. “You are so much more approachable than the last person.” The smile is real. The bait is real too. Nod once, and you have just co-signed a critique of someone you never worked with, delivered by someone who will say the same thing about you to whoever sits here next.

   I appreciate that, but I am going to leave the comparison alone. I do not know what your experience with them was, and I am not going to weigh in on it. What I want is for you to feel like you can bring me real things, not just the easy ones. If approachable means that, good. If it just means I smile more in meetings, that is not actually worth much.

One More Question, Because It Is Coming

“What happens to all this if you leave?”

Months in, somebody on your team will ask it. Sometimes nervously. Sometimes as a real question about whether to invest. The two easy answers are both wrong. Reassuring them that nothing will change is a lie. Acknowledging that the cycle will repeat sounds like surrender.

Some of it will outlast me and some of it will not, and which is which depends on whether we built it into the work or built it around me. That is on us, not on the next person. The job right now is to make the parts that matter strong enough that they do not need me to defend them. If I do that well, the next person inherits something real. If I do not, they inherit a story about me, which is exactly what I am trying not to do to the person who was here before.

How You Talk to Your Own Boss About What You Inherited

“They left me a mess” is not a status report. It is a flare you are firing at your own credibility.

The temptation runs in both directions. You will be tempted to drag the predecessor in front of your team, and you will be tempted to drag them in front of the person you report to.

The second temptation is more dangerous because it feels safer. Your boss is the one with the authority to grade you, so explaining your situation by explaining what you walked into feels like context. It is not. It is an excuse with better packaging.

Here is what your boss actually hears when you keep telling them what a mess you inherited.

1. They hear that you do not yet have a plan of your own.

2. They hear that you are setting up the runway to blame the predecessor for anything that does not go well in your first year.

3. They hear that you might do the same to whoever takes the job after you, which means they are now wondering whether they made the right call hiring you in the first place.

The fix is not to pretend everything is fine. Your boss already knows the unit had problems. That is part of why you got the job. Bring the baseline, bring your read of why it sits where it sits, bring your plan, and bring the timeline. If the situation is genuinely worse than what was advertised when you took the role, say that once, clearly, with specifics, and then move to what you are doing about it. Once. Not every meeting.

Why You Keep Reaching for the Comparison

Insecurity, inexperience, or the gap between the job you thought you were taking and the one that was actually waiting

Most supervisors who lean on predecessor talk are doing it because they have not yet found their own footing. The comparison is a crutch. If the predecessor was bad, you look better by contrast without having to produce anything yet. If the predecessor was good, you look humble and reverent without having to risk a real opinion yet. Both buy you the time you needed to spend building a track record.

This is not a character flaw. It is an early career pattern, and even seasoned supervisors fall into it when they take a job one rung harder than the last one they held. The fix is not pretending the predecessor never existed. The fix is refusing to use them as a reference point in your own story. Have a point of view about the work. State it. Defend it. Adjust it when you are wrong. That is the job.

The Loop You Are Trying to Break

If you do not stop it, the next person inherits it from you

Organizations that allow predecessor commentary to become a habit are organizations that train every incoming supervisor to do the same thing. It becomes the cultural script for transition. The new person spends six months explaining what was wrong, the team spends six months agreeing or resisting, and by the time anyone is ready to actually move forward, the new person is already being measured by their own successor.

You break that loop by refusing to feed it. You break it by being the supervisor who will not grade the past and insists on being graded on what comes next. That posture is unusual enough that people will notice. It is also the posture that builds the kind of trust that survives the next transition, including the one that eventually replaces you.

The Bottom Line

Tell the team how you want to do the work. Tell them why. Tell them what you expect. Then do it.

If you find yourself reaching for the predecessor or hiding behind the baseline, ask yourself what you are actually avoiding saying about your own plan. That is usually where the real work is.

The chair is yours. The ghost is not. Take the room.

I am sympathetic to that pressure. I feel it myself. This piece is not an indictment of anyone trying to find their footing in public, and it is not a lecture from someone who has it all figured out. It is a field note from someone who has made a few of these errors, watched talented people make them at scale, and concluded that the sooner we name them, the sooner we can stop mistaking them for strategy. Read it in that spirit. The goal is not to shame the impulse. The goal is to protect the work.

With that framing in mind, here are the five errors worth watching for. What I want to name specifically is a pattern I keep running into, one that shows up in different costumes but always does the same work. It signals effort without requiring it. It performs authority without earning it. It is, in every case, a flex that is not a flex.

The Tell. The Flex That Is Not a Flex

There is a particular kind of professional who has learned to perform competence without ever demonstrating it. You know the type. So do I. In the age of social media saturation and generative AI, the performance has gotten cheaper, faster, and more convincing at a glance. That is the problem. A glance is all most people give it.

What follows are five errors I watch otherwise capable supervisors make, each of which feels like a flex in the moment and reads like a tell to anyone paying attention. I am writing this as a supervisor’s guide because supervisors are the ones who set the standard for what gets rewarded on a team. If you tolerate these behaviors in yourself, you will tolerate them in the people you lead, and the people you lead will calibrate accordingly.

Faux Flex One.

Posting pablum instead of substance to manufacture credibility. The inspirational quote over a stock photo. The five bullet points about resilience. The carousel explaining that leadership is about people. None of it is wrong. None of it is yours. You did not earn it, you did not test it, and if pressed, you could not defend it beyond the caption. What you are building is not a reputation for insight. You are building a reputation for being fluent in the language of insight, which is a different thing entirely, and the people whose respect actually matters can tell the difference in about eleven seconds.

My advice. Before you post, ask whether you would say it out loud to people who know the topic better than you do. If the answer is no, the post is not ready, and neither are you.

Faux Flex Two.

The preponderance of your conversations, posts, and visibility has nothing to do with what you do for a living. If a stranger reviewed your last ninety days of output and could not reliably identify your actual job, that is information. It may mean you are bored. It may mean you are auditioning for a role you have not been offered. It may mean the work itself has stopped being interesting enough to talk about. Whatever the cause, the effect is the same. You are spending your visibility on everything except the thing you were hired to be excellent at, and the people who hired you are noticing. Quietly. They always do.

My advice. Audit your last ninety days. If a stranger could not identify your job from your output, either change the output or admit you are auditioning for a different job and be honest with yourself about which one.

Faux Flex Three.

Outsourcing your voice to AI and calling the output thought leadership.

I have written about AI slop elsewhere and will not repeat myself here. I will say this. The tool is not the problem. The laziness is. When you prompt a model to generate a post, paste it without revision, and attach your name to reasoning you did not do, you have not scaled your thinking. You have replaced it. And the replacement is visible. The cadence is wrong. The examples are generic. The conviction is missing because conviction cannot be generated, only held. Your reader may not be able to articulate what is off, but they register it, and they trust you less the next time.

My advice. Use the tool to sharpen your thinking, not to replace it. If you would be embarrassed to defend the post line by line in a meeting, do not publish it under your name.

Faux Flex Four.

Performing expertise you have not earned by borrowing the vocabulary of people who have.

There is a specific flavor of post that uses the grammar of expertise without any of the substance. Terms of art deployed as ornament. Frameworks name-checked without application. The author sounds credible if you do not know the field and absurd if you do. Supervisors fall into this when they are promoted past their domain and have not yet done the work to grow into the new one. The honest move is to say so. The dishonest move is to adopt the lexicon and hope nobody tests it. People test it.

My advice. Say what you actually know in words you actually own. If you need a term of art to sound credible, you are not yet credible on the topic, and the fastest path forward is to say so and go learn it.

Faux Flex Five.

Confusing being in the room with having done the work, and name-dropping the room as if attendance were achievement.

The conference you spoke at. The executive you had coffee with. The table you were invited to. These are not accomplishments. They are proximity. Proximity is useful and sometimes hard-won, but it is not a substitute for a track record, and treating it like one is one of the most transparent moves in professional life. The people actually doing the work rarely talk about the rooms. They talk about what they built, what failed, what they learned, and what they are trying next. If your feed is a travelogue of prestigious locations and your output is thin, you have told on yourself.

My advice. For every post about where you were, publish three about what you built, what you decided, or what you learned. If you cannot, the ratio is telling you something you already know.

A Closing Note For Supervisors.

The thread connecting all five of these is the same. Each one is an attempt to be perceived as having done something without the inconvenience of actually doing it. In a media environment that rewards volume and surface over depth and substance, the temptation is real, and it will only get stronger as the tools get better at imitation.

Your job, as a supervisor, is to be the person on your team who is not fooled. Not by your direct reports. Not by your peers. Not, and this is the hard part, by yourself.

The problem isn’t that supervisors lack skills. The problem is we’re equipping them for the wrong fight.

Most supervisory training still operates on industrial-era assumptions about hierarchy, command structures, and transactional management. Meanwhile, the people they’re supposed to lead are navigating hybrid work, AI disruption, multiple generations with vastly different expectations, and organizational structures that are being reinvented in real-time.

Here’s what nobody wants to admit about supervision in 2026.

The Structures Are Fighting The People

We built supervisory frameworks around consistency, standardization, and control. But today’s workforce demands flexibility, autonomy, and customization. Supervisors are caught in the middle, expected to enforce outdated policies while somehow also being “innovative leaders” who “empower their teams.”

That’s not a job description. That’s a contradiction.

When I watch supervisors struggle, I rarely see incompetence. What I see is people trying to reconcile two fundamentally opposing operating systems. They’re running 21st-century leadership software on 20th-century organizational hardware. The system crashes aren’t their fault.

We’re Measuring The Wrong Outcomes

Ask most organizations how they evaluate supervisory effectiveness and you’ll hear about retention rates, productivity metrics, and employee satisfaction scores. All inputs. All backward-looking. All focused on maintaining what exists rather than building what’s needed. The better question is this:

Because here’s the reality. The average career now spans 50+ years across industries that don’t exist today. Your supervisors aren’t managing a workforce. They’re stewarding human capacity through multiple waves of disruption. If they’re only good at maintaining the status quo, they’re already obsolete.

Stop Asking Supervisors To Be Psychologists

We’ve dumped every societal problem onto supervisors that governments, families, and institutions used to handle. Mental health. Financial wellness. Career development. Conflict resolution. Cultural competency. Work-life integration. The list grows every quarter.

Supervisors aren’t trained therapists. They’re not financial advisors. They’re not equipped to solve the structural failures of our society, yet we keep expecting them to patch over systemic problems with individual interventions and “having better one-on-ones.”

This isn’t sustainable. And blaming supervisors for struggling under this weight is both cruel and counterproductive.

If we want supervisors to succeed, we need to stop pretending personal development workshops and communication training will solve structural problems. We need to either redesign the role or stop pretending it’s possible for one person to fill seventeen different functions.

The Real Work Supervisors Should Be Doing

Strip away the bureaucratic bloat and the impossible expectations, and what remains? Three things.

First, supervisors should be pattern recognizers. They need to spot emerging challenges and opportunities before they become crises or missed chances. Not manage spreadsheets. Not police time clocks. But see what’s coming and help their teams prepare.

Second, supervisors should be capacity builders. Their primary job is making the people they lead more capable, more adaptable, and more resilient. Not maintaining compliance. Not protecting territory. But genuinely expanding what their people can do.

Third, supervisors should be connectors. They sit at the intersection of organizational strategy and individual execution. Their value is translating between those two worlds, not controlling one or serving the other.

Everything else is either administrative work that could be automated or systemic problems that require organizational solutions, not supervisory heroics.

What Would Change If We Got This Right

Imagine supervisors who spend their time identifying the skills their teams will need in 18 months and building pathways to develop them. Imagine supervisors who can say “that’s a structural problem requiring institutional change, not something I can fix with better communication” without being labeled as difficult.

Imagine organizations that actually supported supervisors instead of just demanding more from them.

The cost of getting this wrong isn’t just burned-out supervisors. It’s entire organizations that can’t adapt because the people responsible for developing talent are drowning in tasks that have nothing to do with actual leadership.

We know how to fix this. We’ve known for years. The frameworks exist. The research is clear. What’s missing isn’t knowledge. It’s courage.

The courage to admit that our supervisory models are broken. The courage to strip away expectations that were never realistic. The courage to rebuild roles around what actually matters rather than what we’ve always done.

My Takeaway: The supervisor’s role isn’t broken because individuals are failing. It’s broken because we’ve designed it to fail. Organizations that recognize this and redesign supervisory roles around capacity building, pattern recognition, and strategic connection will have an enormous competitive advantage. Everyone else will keep wondering why their leadership pipeline never produces the leaders they actually need.

The question isn’t whether your supervisors are good enough. The question is whether your organizational design allows good supervision to exist at all.

As a supervisor, you have the authority to assign tasks, distribute responsibilities, and empower your team to act independently. But there’s one thing that never leaves your desk: accountability for the results.

When work you’ve delegated doesn’t get done or gets done poorly, “I told them to do it” isn’t leadership. It’s abdication.

Your Three Options When Someone Isn’t Performing

1. Train them. Give them the skills, knowledge, and support they need to succeed.

2. Support them. Remove obstacles. Provide resources. Create conditions where they can deliver.

3. Replace them. If training and support haven’t worked after genuine effort, make the personnel decision.

What you cannot do is blame them and move on. That’s not management. That’s evasion.

The Hard Truth About Accountability

You will never control everything. Not every department, not every variable, not every external force. If you need complete control before you’ll accept accountability, you shouldn’t be in leadership.

The job is delivering results in an imperfect world with imperfect information and imperfect people. If that makes you uncomfortable, this isn’t your role.

And here’s what I’ve learned the hard way: taking accountability doesn’t mean keeping underperformers indefinitely while you try to fix them. When you tolerate mediocrity, high performers leave. Liabilities compound. The accountable thing is often making the change you’ve been avoiding.

The Buck Stops With You

Your team’s performance is your responsibility. Not your excuse. If they fail, you failed them first by not preparing them, supporting them, or making the necessary personnel decision.

That’s not a burden. That’s the job. Read the full deep dive on leadership accountability and the phrases managers use to avoid it here.

There are moments when the system does not just strain but snaps. A cyber breach wipes out access to every tool you rely on. Half your team resigns in the same week. A violent threat suddenly makes safety the only priority. A major source of funding disappears overnight, and with it the foundation of your work. These are not the everyday fires that seasoned managers can expect. These are once-in-a-career events that show how fragile most systems really are.

The moment the playbook fails

The first reaction is disbelief. Leaders often spend valuable time trying to force the event into familiar categories. The truth is that the usual procedures and instincts feel irrelevant. It is like holding a set of instructions for sailing when the boat has already sunk.

What matters most in a collapse

In these moments, your task is not to repair the system immediately. Your task is to steady people long enough to create clarity. That requires honesty about what you know and what you do not. It requires speaking quickly and openly, even if your words are imperfect. It means setting the horizon as the next hour or the next day instead of a grand strategy. And it means paying attention to the emotional temperature of your team because fear travels faster than any technical failure.

The long shadow of crisis

The event itself may pass quickly, but the recovery is drawn out. People leave. Confidence erodes. Trust in leadership weakens. Supervisors who believe the job ends when the emergency calms down miss the real work. The true test comes in the weeks and months that follow, when adrenaline is gone but the damage remains.

Why this matters today

The unthinkable is not as rare as leaders would like to believe. Dependence on fragile digital systems, volatile labor markets, and unstable political environments all increase the chance of events that can break a system overnight. Leaders who imagine these moments as black swans will be caught unprepared. Those who accept fragility and prepare themselves to lead in uncertainty will be the ones their teams remember.

Five steps to take when the system breaks

When the system breaks, the role of the supervisor is stripped down to its core. Presence matters more than expertise. Humility matters more than bravado. What people remember is not a flawless plan but the steady hand that gave them enough confidence to make it through.

1. Name reality fast: Do not waste time pretending it is a normal disruption. Call it what it is. People take their cues from you.

2. Speak before you are ready: Perfection kills trust. Give short, steady updates with what you know and what you do not. Silence breeds panic.

3. Narrow the horizon: Shift from long-term strategy to short-term footholds. Define the next hour, the next shift, the next day. Momentum is a form of safety.

4. Protect the human core: Systems can be rebuilt. People cannot. Watch morale, fear, and exhaustion as closely as you track technical fixes.

5. Own the aftermath: Do not vanish once the emergency subsides. The recovery period will test confidence more than the crisis itself. Stay visible, stay accountable, and guide the team through the slow rebuild.

Memes feed outrage and pity in equal measure, but they rarely point anyone toward accountability or solutions. They are noise dressed up as wisdom, and supervisors who mistake them for insight risk leading with clichés instead of clarity.

As a supervisor, your role is to keep expectations grounded. Work is not family, and it is not a substitute for life beyond the office. A job has purpose and weight, but it cannot carry every human need. The basics matter. An organization that grows at the expense of its people will fail, and employees who exploit the organization will not thrive either. Lasting success only comes when both sides commit to a shared future, so focus your energy on fostering that alignment rather than chasing perfection.

It's essential to stick to the basics for mutual success:

1. A corporation cannot flourish in the long run if it prioritizes growth over its people.

2. Individuals pursuing solely self-interest will not achieve long-term success within the corporation they are exploiting.

3. Sustainable success is achieved when both parties align their visions for the future.

This balance is hard to strike, but it is where real sustainability lives. At Unity, I have seen how deliberate choices point in that direction. Locking tuition until 2030 ties institutional growth to affordability. Setting a $100,000 base pay goal for employees makes shared prosperity tangible, even if the road is difficult.

The bigger lesson is restraint. Do not sell work as more than it is, and do not allow employees to expect it to be more than it can be. Shortcuts and manipulation, whether by leadership or staff, might win a moment but never build lasting success.

Perfect supervisors and perfect hires do not exist. Before taking or offering a role, do the homework. Learn the strengths. Accept the imperfections. Decide if the trade-offs are worth it.

Supervisors rarely wreck trust with one epic mistake. It’s usually death by a thousand paper cuts; the small, telling moves that make people quietly stop trusting you.

1. Paper Tiger Questions

Asking a question and then telling people they don’t have to answer is not dialogue. It’s theater. Skip the scene if you don’t want the script.

2. The Blame-Thrower

Blaming “the higher-ups” for a decision you’re delivering is a master class in erasing your own authority. Even if true, you’ve just announced you’re not driving the bus.

3. The U-Turn Panic

Treating a course correction as a broken promise tells your team that truth is dangerous and change is weakness. That’s how you end up steering with last month’s map.

4. The Ghost Boss

You disappear when it is time to explain the why. Decisions land without context, and you are nowhere to be found when people try to connect the dots. Silence might feel safe, but it comes across as either clueless or careless, and both erode trust.

You’ve heard it. You’ve maybe said it.
“I can’t report to someone who doesn’t know what I do.”

It sounds rational. Sensible even.
But it’s a trap.

I call it the Competency Hierarchy Fallacy; the belief that a manager must have done your job to lead you well. It’s not an official theory. You won’t find it in textbooks. But you’ll find it everywhere in the workplace.

It’s rooted in confusion between expertise and capacity, between knowing the task and knowing how to lead the people doing it.

What it gets wrong:

1. Supervision is a separate discipline.
The skills that make someone a great coder, designer, or technician don’t always translate into great supervision. And they’re not supposed to. Supervisors succeed by aligning resources, setting priorities, and driving accountability. Not by being a better version of their direct reports.

2. “They don’t get what I do” usually means “I don’t trust their judgment.”
That’s a valid concern. But it’s a breakdown in communication, context, or credibility. Not a structural flaw in the reporting line.

3. This mindset kills scalability.
As organizations grow, expecting every supervisor to be a subject matter expert becomes impossible. What you need is someone who can synthesize, coordinate, and lead across domains.

Supervision isn’t about doing your team’s job. It’s about making sure they can.

The question isn’t “Have they done my job?”
It’s “Can they make mine better?”

Where this shows up clearly:

Software Engineers Reporting to Product Managers
Some engineers grumble, “How can they lead if they can’t code?” But the role of a product manager is to prioritize work, manage scope, and connect execution to business outcomes. The engineer owns the implementation. The manager owns the direction.

Professors Reporting to Academic Leaders
Faculty sometimes resist reporting to a dean or president who hasn’t taught in their discipline. But academic leaders are responsible for alignment, sustainability, and mission integrity. They don’t need to teach your class. They need to ensure your work fits the institution’s larger goals.

Doctors Reporting to the Chief of Medicine
A cardiologist might ask, “How can the Chief of Medicine evaluate me if they’ve never practiced in my specialty?” But that’s not the job. Chiefs lead across specialties. They uphold standards of care, support system-wide performance, and solve institutional problems. They’re not there to out-specialize the specialists. They’re there to ensure the whole thing works.

That said, supervisors do need to know enough.
Not to do the work, but to value it. To represent it. To make fair decisions, remove barriers, and recognize when something’s off.

You don’t need fluency in every tool. But if you can’t speak the language at all, you can’t lead the people who do.

So how do you supervise subject matter experts?

As you rise in leadership, it becomes the norm; not the exception; to oversee people with more technical knowledge than you. That’s not a weakness. It’s the design.

Here’s how to do it well:

1. Learn enough to hold a credible conversation.
You don’t need to master every discipline. But you must understand what good looks like, ask smart questions, and follow the logic of the work.

2. Define the “why” and the “what,” then let them own the “how.”
You set direction, priorities, and expectations. They decide the method. If you dictate the approach, you lose the benefit of their expertise. If you set no boundaries, you lose accountability.

3. Build systems for visibility, not control.
Dashboards, check-ins, and shared metrics allow you to manage without meddling. You should always know how things are going without having to hover.

4. Use your distance to see what they can’t.
Experts go deep. You go wide. Your perspective connects their work to other teams, larger objectives, and unseen risks. That context is your contribution.

5. Protect their focus.
Shield them from chaos. Remove obstacles. Make their work matter. The best supervisors of experts are not the loudest in the room; they’re the ones clearing the way.

You don’t have to be the smartest person on the team.
You just have to ensure that the smartest people can do their jobs effectively.

That’s supervision. That’s scale. That’s leadership.

Of course you will be replaced. That’s not a betrayal. That’s how continuity works. But if I believed in conspiracy theories, I’d swear this was psyops; engineered to rot the core of workplace trust and quietly sabotage the US economy from the inside out.

This trope paints supervisors as soulless and employees as powerless. It drains purpose from the act of working and recasts accountability as oppression. It turns healthy ambition into something shameful and makes disengagement feel like wisdom.

And while everyone’s reposting it like they’ve cracked some code, the people holding it all together; team leads, frontline staff, mid-level managers; are left exhausted, undermined, and unsure who they can count on.

This isn’t just a lazy take. It’s a dangerous one. Because if enough people believe it, they stop showing up; not just to the office, but to their own potential.

Left unchecked, it could actually undermine the workforce it pretends to protect! this is simply how jobs work. Roles get filled. Teams move on. Payroll keeps running. If that surprises you, you weren’t hired; you were seduced.

It strips people of their agency, their choices, and their ability to build meaningful work with their terms. It tells them the game is rigged, so why bother? That’s not empowerment. That’s paralysis.

• You want purpose? Build it.

• You want loyalty? Earn it.

• You want meaning? Don’t expect the org chart to deliver it.

The problem isn’t that you’re replaceable. The problem is thinking that makes your work worthless. Being replaceable doesn’t mean being pointless. It means you’re part of something bigger than one person. That’s not failure. That’s design.

Boomers were called out of touch. Gen X got branded as cynical. Millennials were deemed entitled. Now it is Gen Z's turn in the hot seat.

Let me be clear. Gen Z is not the problem. They are just the latest generation to make the system uncomfortable. And that discomfort is not dysfunction. It is a signal.

First! They Are Not a Monolith

Some want to move fast and challenge everything. Others want structure, predictability, and a fair deal. Some are career-driven. Others are values-driven. Some are anxious. Others are fearless. That is not generational confusion. That is a range of human behavior showing up unapologetically in the workplace.

What is different is that they are transparent. They ask questions out loud. They expect clarity, not platitudes. They do not wait ten years to point out what does not make sense.

Every Generation Has Its Thing

Gen X perfected the art of detachment. Millennials turned hustle into identity. Gen Z is bringing ambiguity into the open. They have grown up watching systems fail and institutions stall. They are not naive. They are fast learners with strong filters and little interest in performative leadership.

That shows up in the workplace. It can be uncomfortable. But it is also necessary.

They Are Not Rejecting Work. They Are Rejecting Waste

At Unity, the Gen Z team members I work with are some of the sharpest voices in the room. They challenge assumptions. They are allergic to fluff. They want systems that make sense, not rituals that waste time.

That does not mean they lack commitment. It means they value coherence. And they can tell when something exists just because it always has.

They Are Not broken. They Are Just Early

Much of what Gen Z is asking for today will be standard practice tomorrow. Automation. Flexibility. Skills-based learning. Real accountability. Mission that is more than a tagline. These are not quirks. These are the front edge of the workforce redesign.

They are not ahead of the curve. They are the curve. And the rest of us have a choice. Adapt and lead. Or cling to a playbook that has already expired.

Every generation challenges the one before. Gen Z is doing it publicly, digitally, and relentlessly. Not because they want to tear things down. But because they know what collapse looks like and they would rather be part of a rebuild.

If your systems cannot withstand Gen Z, they will not survive what is coming next.

They are not the problem. They are the pressure test. And pressure is what reveals whether you are building for legacy or longevity.