The ShowMust Go On

Every company that uses this phrase means it sincerely. That's what makes it so dangerous. They genuinely believe they have built something warm and human and loyal inside a legal entity whose primary obligation is to its shareholders. They have not. What they have built is an environment where emotional language is used to extract professional sacrifice.

In a real family, the relationship is unconditional. You can disappoint them, fail them, go through a rough year, and they don't put you on a performance improvement plan. In a corporate family, the love is conditional on performance, budget cycles, and whether a more efficient version of you exists offshore. The language is familial. The relationship is contractual.

Family rhetoric is deployed most aggressively in two moments: during hiring, to attract people who will overextend themselves because they feel the pull of belonging, and during a crisis, to ask people to sacrifice something — a salary cut, unpaid overtime, a cancelled bonus — that they would never accept from a stranger but might accept from family.

"We're all in this together" is the crisis version. It surfaces when the company needs something from you that the employment contract doesn't cover. It's an appeal to loyalty that the company has not necessarily earned and will not necessarily return.

Because humans are wired for belonging. Because the office is where many adults spend the majority of their waking hours. Because it actually does feel like something, working closely with people toward a shared goal. That feeling is real. The company just didn't create it — you and your colleagues did. The company is taking credit for a dynamic it happened to house.

The tell is always what happens when the family metaphor stops being convenient. When layoffs come, when the acquisition closes, when the restructuring begins, nobody in HR calls it a family separation. The language shifts instantly to professional, legal, and emotionally clean. The family only exists in the direction that serves the company.

People who believe they are in a corporate family make different decisions than people who know they are employees. They work longer hours without asking why. They absorb unreasonable requests because family members don't nickel-and-dime each other. They don't negotiate as hard, advocate for themselves as loudly, or leave as quickly as they should. And when it ends — and it always ends — the grief is disproportionate to the relationship. Because they treated it like a family. The company did not.

It works like this: once or twice a year, you sit across from your manager and discuss your performance in the third person. You call it a "conversation," though it has already been decided. The forms were submitted last week. HR approved the ratings. The manager is not here to discover something about you. They are here to deliver a verdict and have you sign something saying you heard it.

If you are performing well, you leave the review knowing you are performing well — which you already knew. If you are performing poorly, you leave knowing that too — because your manager has either been hinting at it for months or refusing to address it for months, both of which are more informative than any formal document.

The performance review was invented to solve a real problem: people need structured, honest feedback on their work. It fails at this because the structure and the honesty are in direct conflict. Honest feedback is uncomfortable. Structured reviews are documented. Documented discomfort is a legal liability. So the feedback gets softened into language so carefully calibrated it loses all meaning.

"Meets expectations" means fine. "Exceeds expectations" means good. "Does not meet expectations" means we are building a case. In between those three phrases, the entire range of human professional performance collapses into a bureaucratic signal that tells you almost nothing and tells HR almost everything they need to manage your departure if it comes to that.

The performance review doesn't optimize for your development. It optimizes for legal defensibility, manager comfort, and the appearance of a fair process. Real feedback — the kind that changes how someone works — happens in real time, in small moments. It happens when a manager says "that approach isn't working, here's why" on a Tuesday in October, not in a formal document that lands in February.

The review also generates a permanent record that runs in parallel to your actual experience of the year. You might have had a brilliant stretch from March to November and a rough Q4 because your project got cancelled. The review captures Q4. It rarely captures the context.

Stopping is scarier than continuing. If a company eliminates performance reviews, it has to answer for what replaces them. And the answer — "continuous, honest, manager-led feedback" — requires managers willing to have hard conversations without the scaffolding of a formal process. Most are not. The review exists, in part, to give conflict-avoidant managers a scheduled reason to say things they should have been saying all year.

Agreement implies a meeting of minds. Alignment implies a meeting ended. You can be aligned on something you fundamentally disagree with, and frequently are. Alignment does not require that you believe the decision is correct. It only requires that you behave as though you do — at least until the next meeting.

This is why "we need to get aligned on this" is one of the most ominous phrases in corporate life. It means: there is a gap between what different people think, and rather than resolving that gap through genuine deliberation, we are going to resolve it through repetition, escalation, or attrition. Whoever stops pushing first becomes aligned.

An enormous amount of corporate activity exists to manufacture alignment. Workshops, offsites, stakeholder sessions, working groups, steering committees — these are all alignment mechanisms. They take people who disagree and run them through a structured process until they produce a shared document. The document is then called "our aligned position."

What the document rarely captures is the room temperature during the process. Who had to concede. Who left the meeting smiling because they won, and who left planning to relitigate the decision in a different forum with different people. Alignment is a surface condition. The disagreement lives underneath it, waiting.

Fragile alignment breaks at the moment of execution. Two teams are "aligned on the strategy" but discover they had entirely different mental models of what the strategy meant when they try to implement it. A decision is made in a leadership meeting and everyone nods, then those same people instruct their teams in subtly different directions because each person left with a slightly different version of what was decided.

Because "we disagree but we're moving forward anyway" is true and uncomfortable. Because "we have not resolved this and we're going to keep fighting about it in different arenas" is also true and uncomfortable. Alignment is the diplomatic fiction between those two truths. It also distributes the risk. If something fails, no single person disagreed with the plan — everyone was aligned. The alignment absorbs the accountability. Which might be the most honest thing about it.

The word arrived from the startup world, where it had a specific and defensible meaning: a company learning from early market feedback and changing direction before running out of money. In that context, a pivot is a rational and necessary response to reality. It happens fast, driven by data, when the original hypothesis is disproved.

In the corporate world, the word kept the prestige and lost the meaning. A pivot became what you call any significant change in strategy — regardless of whether it was driven by learning, desperation, new leadership, or simply the need to announce something that sounds like momentum.

A real pivot starts from an honest assessment: we were wrong about something specific. Here is what we learned. Here is what we are doing differently and why. The before and after are clearly named.

A theatrical pivot starts with a rebrand. Or a new leadership hire who "brings fresh perspective." Or a company offsite that produces a shiny new strategy deck with a different set of priority pillars. The old direction isn't admitted to have failed — it's described as having "laid the foundation" for the new direction. The foundation metaphor is doing a lot of work here. It's saying: we didn't fail, we just completed phase one of a plan that never existed.

Every pivot produces a class of people who were hired for the old direction. They had the right skills for what the company said it wanted eight months ago. In a genuine pivot, this is addressed directly. In a theatrical pivot, these people are kept on while the company figures out what to do with them, which can take years. Meanwhile, new people are hired for the new direction. The organization splits — old guard and new guard, each with different tribal knowledge about which version of the company is real.

Pivots are often announced externally before they are understood internally. A press release describes a bold new direction. Employees read it over their morning coffee and spend the rest of the day trying to figure out what their job is now. Leadership has been working on the narrative for weeks. The people responsible for executing it heard about it this morning, same as you. This is why most pivots feel chaotic from the inside even when they look confident from the outside.

For about a decade, certain corners of the professional world worshipped at the altar of the grind. Five-hour sleep schedules. Founder origin stories measured in sacrifice. The implicit promise that if you worked hard enough and visibly enough, you would be rewarded. The hustle was the point.

Then the pandemic happened, several high-profile figures publicly burned out, and suddenly hustle culture was something you were allowed to criticize. Companies rushed to distance themselves from it. Wellness programs launched. "Work-life balance" became official policy. The grind, apparently, was over. But the expectations didn't change. Just the language.

Busyness. Constant, ambient, never-quite-explainable busyness that functions as both a status signal and a shield. Being busy is different from working hard. Working hard is about outcomes. Being busy is about the appearance of being in demand — of having more to do than hours to do it, which implies you are important, required, indispensable.

The busy person has seven meetings today, three of which overlap. They have three hundred unread emails and mention this often. They respond to messages at 11pm, not because they're working late but because they want you to know they could be. Their calendar is a performance of their own relevance.

Because busyness is visible and outcomes often are not. In most organizations, the person who spent three months quietly thinking through a critical problem and produced a two-page document is harder to evaluate than the person who was in every meeting, replied to every email, and shipped a deck a week. The former might have created more value. The latter is easier to see creating value. So organizations drift toward rewarding the signal.

Deep work — the kind that produces things that actually matter — requires sustained, uninterrupted concentration. The busy culture makes this structurally impossible and then wonders why the organization keeps failing to produce new ideas, better products, smarter strategy. You cannot think at the level an organization needs while managing an inbox, running three recurring syncs, and maintaining the social labor of being seen to be engaged.

What most organizations have built, without meaning to, is an environment that is maximally hostile to the kind of thinking they most need. And then they hire consultants to figure out why innovation keeps stalling.