The Foundationsof the Performance

The logic sounds reasonable: build momentum, show early progress, earn trust before tackling the complex stuff. In theory, quick wins are a warmup. In practice, they are the whole workout — repeated indefinitely, because the complex stuff never becomes less complex and the momentum from quick wins never quite accumulates into the courage to address it.

Here is the question nobody asks: if it's a quick win, why wasn't it already done? The answer, almost always, is that it wasn't a priority. Which means calling it a quick win is really just a way of doing something unimportant and calling it strategy.

New leaders need quick wins most. You've just arrived, you haven't earned trust yet, and the board wants to see that you're doing something. The quick win exists to satisfy this need. It is a proof of life — visible activity that demonstrates momentum before you've had time to understand what actually needs to change.

Consultants need them too. The engagement has a timeline. The deliverables need to look like progress. A twelve-week consulting project that concludes with "the problems here are structural and will take years to fix" does not generate repeat business. Twelve quick wins in a slide deck does.

Organizations develop a tolerance for quick wins the way people develop a tolerance for anything that feels good and requires no real sacrifice. Each one delivers a small hit of visible progress. The status update looks good. The town hall slide is green. The leader can point to momentum. The uncomfortable reality — that the structural problem is still sitting there, untouched, now twelve months older — gets described as "the next phase."

The next phase rarely comes. Or it comes with a new leader, who arrives, surveys the landscape, and suggests starting with the quick wins.

They get more expensive. A broken process that costs the company a million dollars a year in friction costs two years later when it has compounded. A culture problem that needed a direct conversation in year one needs a full organizational redesign in year three. The things organizations avoid through quick-win culture do not wait patiently. They grow.

The cruelest version: a company successfully executes every quick win on the list and then has to confront that nothing fundamental has changed. The metrics look cleaner. The decks look sharper. But the product is still mediocre, the customers are still leaving, the teams are still dysfunctional — because none of the quick wins touched the thing that was actually broken.

The role is real. The ambiguity is also real, and it is not accidental. The Chief of Staff exists precisely because some things inside organizations don't fit neatly anywhere — cross-functional problems with no clear owner, executive capacity that keeps running out, trust that can't be delegated through a normal reporting line. The Chief of Staff is the answer to all of those problems simultaneously, which is why the job description reads like it was written by three different people who never spoke to each other.

In practice, the role is a mirror of the executive it supports. A disciplined leader with clear priorities produces a Chief of Staff who runs tight processes and drives real decisions. A scattered leader who avoids decisions produces a Chief of Staff who is busy every hour of every day and cannot point to a single thing they caused to happen.

The Chief of Staff does the work the executive cannot delegate to a department and does not want to do themselves. They attend every meeting the executive attends and several they don't. They know everything. They decide very little — not formally, anyway. Informally, they are often the person through whom the executive's actual views get translated into the organization's actual behavior.

This creates a strange political position. The Chief of Staff speaks, but it's unclear whether they're speaking for themselves or for the executive. When they push for a decision, is that their judgment or an instruction from above? Nobody is quite sure, including sometimes the Chief of Staff. This ambiguity makes them enormously effective in some situations and quietly toxic in others.

Every Chief of Staff is, in some sense, a symptom. The role emerges when an organization's complexity has outgrown its structure — when there are more decisions than decision-makers, more problems than owners, more coordination required than the org chart provides for. A well-designed organization with clear accountability doesn't need a Chief of Staff. Organizations hire one when the design has failed quietly and nobody wants to say so.

The role either becomes too much or too little. In the "too much" version, the Chief of Staff absorbs every problem nobody else wants to own, has no formal authority to resolve any of them, and burns out in eighteen months while the organization treats their departure as a staffing issue rather than a structural one. In the "too little" version, they are a very expensive communications relay between people who could have emailed each other.

And when the executive they support leaves — which they will — the Chief of Staff almost always goes too. The role was never attached to the institution. It was attached to a relationship. That's the last thing the job description mentions and the first thing that matters.

Key Performance Indicators were a genuinely useful idea. Pick the vital signs. Track them religiously. If they move in the right direction, the body is healthy. The insight behind this is sound — you cannot manage what you cannot measure, and organizations are complex enough that you need forcing functions to stay honest about performance.

What happened in practice is that "key" became a courtesy title. Organizations added metrics for every initiative, every team, every new priority — and never removed the old ones when the priorities changed. The average company's KPI dashboard is a sedimentary record of things leadership once cared about, layered on top of each other over years until nobody can explain why half of them are still there.

There is a principle called Goodhart's Law: when a measure becomes a target, it ceases to be a good measure. The moment people know they are being evaluated on a number, they optimize for the number — not for the underlying reality it was supposed to represent.

Customer satisfaction scores go up because support teams learn to ask for five stars at exactly the right moment. Active user counts grow because the definition of "active" quietly expands. Sales cycles shorten because reps learn to mark deals as closed before every condition is met. Each of these is technically true. None of them means what the metric was supposed to mean.

Sit in on a weekly KPI review. Watch what happens when a number goes down. Watch how much time is spent explaining why the number went down versus discussing what would actually fix the underlying thing the number represents. In most organizations, the explanation gets most of the time. The fix — if it comes at all — becomes an action item for a future meeting.

Now watch what happens when the same number goes back up. Watch whether anyone investigates why, or whether the green just gets accepted as confirmation that the previous explanation was correct. The dashboard becomes a Rorschach test: we see in the numbers what we were already inclined to believe.

Honest metrics require you to define failure in advance. Before you launch a thing, you have to say: here is specifically what would convince us this isn't working. That is a harder conversation than picking metrics that will probably be fine. So organizations pick metrics that will probably be fine, and then express confusion when the metrics are fine and the business isn't.

The narrative is one of rescue: experienced operators step in, eliminate waste, sharpen strategy, install professional management, and return a healthier business to the market at a profit. Sometimes this is true. More often, "unlocking value" is a description of what happens to a company when it has been optimized entirely for its next sale rather than its long-term function.

The mechanism matters. Private equity firms acquire companies primarily using borrowed money — a leveraged buyout — and place that debt on the company being acquired. The company now owes money it didn't choose to borrow, using cash flows it was already generating. Before anything changes operationally, the company's financial position has gotten worse. Everything that comes after is shaped by the pressure of servicing that debt.

PE firms operate on hold periods — typically three to seven years, after which they need to sell. This is not a secret. Everyone involved knows it. Which means every decision made inside the company during that window is being evaluated against a single question: does this make the company more attractive to sell?

Long-term investments — R&D, talent development, customer relationships that take years to compound — are hard to justify inside a three-year hold period. They cost money now and pay off later, and later is someone else's problem. What gets justified instead: cost reductions, margin improvements, and any initiative that produces a number that looks better in a pitch deck.

The acquisition is announced with language about partnership, shared vision, and commitment to the team. Then a consulting firm arrives to conduct an operational review. Then the findings are presented to new leadership. Then the restructuring begins — the word used when the findings conclude, as they almost always do, that the company is overstaffed relative to its revenue potential.

What remains after the restructuring is a smaller organization with significantly more institutional knowledge walking out the door than the headcount numbers suggest. The people who stayed worked alongside the people who left for years. They know what was lost even when the org chart doesn't show it.

The most clarifying version of the PE model is the secondary buyout — when one PE firm sells a company to another. And sometimes a third. Each transaction adds more debt. Each owner extracts value during their hold period. By the time the company reaches a strategic buyer or goes public, it requires years of patient reinvestment just to function normally again. Nobody in any of those transactions did anything illegal. The math worked every time. The company just stopped being a company somewhere along the way.

The intention is genuine, usually. Leadership wants employees to feel informed, connected to the company's direction, and heard. These are real and reasonable things to want. The problem is that the format built to deliver them is structurally incompatible with actually delivering them. You cannot have an honest, unfiltered conversation with eight hundred people about things the communications team has been workshopping for a week.

What you can do — and what all-hands meetings reliably do — is demonstrate what leadership wants the organization to be thinking about. The topics chosen, the time allocated to each, the questions answered versus deflected: all of it is a signal. The all-hands is a map of the official narrative. The gap between that map and the actual terrain is where the real information lives.

The most informative part of any all-hands is what is conspicuously absent. An acquisition is rumored; the all-hands doesn't mention it. A team has been underperforming for two quarters; the metrics slide for that area is vague. A senior leader recently departed; their name doesn't come up, or comes up once, warmly and briefly, and then the slide moves on.

The second most informative part is how uncertainty is described. "We're navigating a dynamic environment" means we don't know what's coming. "We're making some structural changes to set us up for the next phase" means layoffs are coming or have already been decided.

Most all-hands Q&A sections were not as spontaneous as they appeared. Questions submitted in advance get curated. The ones selected are answerable. The hard questions arrive live, submitted anonymously, and get answered with the specific kind of careful non-answer that sounds substantive if you're not listening closely and reveals nothing if you are.

The quality of a Q&A is an accurate proxy for the health of trust inside an organization. Companies with genuine psychological safety get real questions — pointed, specific, uncomfortable — and answer them directly. Companies where people don't feel safe get softballs or silence, and leadership interprets both as evidence that everything is fine.

Because the alternative — not communicating at all — is worse. The information vacuum created by silence fills with rumors that are almost always darker than the truth. The all-hands, even a mediocre one, provides a floor. But it is not transparency. Transparency would mean saying what is uncertain when it is uncertain. Most organizations can't do that — not because their leaders are dishonest, but because the incentives for an executive being honest at scale are genuinely complicated, and the downside risks are real.