Not a profanity. Just an ordinary engineering term (one syllable) describing something my teams deliberately built and quietly benefited from for years. It didn’t appear on some list of banned vocabulary, and it didn’t need to. You learned within one or two review cycles which words helped you out in front of an executive audience and which ones sank the room. This particular word sank the room immediately, every time.

I will tell you the word in a moment, but first I want to show you what it does, because I am currently sitting inside a demonstration of it.

I am writing this on a train from Munich to Salzburg, and I am watching the minutes to my connection with a wariness I earned honestly.

Last year, while traveling through Germany, my wife and I missed connections that should have been easy. The issues came from the fact that the Deutsche Bahn network has spent years being asked to do more than it was built for. The trains run close together, and the timetable assumes nothing goes wrong. So when anything does go wrong anywhere in the system, the delay doesn’t stay where it started. It propagates. A ten-minute problem in one city becomes a missed connection three cities away, and the passengers absorb what the system could not.

The Swiss, famously, run their trains differently. Their timetable builds in margin: a little room at connections, a little breathing space between services. The trains are on time not because Swiss trains are magic, but because the system does not require perfection to deliver punctuality. When something slips, the slack absorbs it, and the failure stays local instead of cascading across the country.

Two networks. Two philosophies. One runs at the edge of its capacity and transmits every shock to every passenger, while the other holds something in reserve and delivers the thing everyone actually wants: arriving when you said you would.

The word for what the Swiss build into their timetable is “slack”: deliberately reserved capacity, held back on purpose, so the system can absorb what the plan did not predict.

That is the word I could never say at Amazon.

In front of an executive audience, especially an Amazon audience, “slack” does not sound like engineering. It sounds like slacking. In a company with “frugality” printed on the wall as an operating principle, where every headcount was fought for in writing and every dollar was defended in a document, the suggestion that you were deliberately not running at full capacity was close to heresy. Anyone who mentioned it would be quietly put on trial by their audience.

Now, you could build it. You could benefit from it. Smart teams did this. But you could not name it, because the name confessed to holding something in reserve instead of optimizing every inch of the process. And reserve sounded like waste to people whose job was hunting waste.

Amazon ran under what I think of as “The German System,” but other organizations I worked for had a more “Swiss” approach. I spent thirty years watching these two philosophies run inside software organizations. I know which one I always built, and I also know what it cost me to defend it in rooms where its true name was unsayable.

At Amazon, I ran the Appstore’s backend services. Around us, plenty of teams lived in a familiar rhythm: dates slipping, operational load climbing, engineers paged at two in the morning, heroics celebrated in the retrospective, and then the same fire the following month.

In contrast, my teams hit their dates. They aligned cleanly with partner teams, and they were not woken up in the middle of the night. All because we had spent real engineering effort making sure of it.

None of that was luck, and none of it was because my engineers were smarter than anyone else’s. It was because we deliberately built what the Swiss build into their train system: margin. We invested in infrastructure before it was on fire. We automated the operational work that was eating people. We fixed root causes instead of celebrating the person who patched the symptom at 3am. We did not schedule ourselves to one hundred percent of capacity, because we knew something would arrive that was not on the plan, and something always did.

When the surprise came, and it always did, it landed on the margin instead of on someone’s weekend. The delay stayed “local.” It did not cascade.

Here is what I learned about systems that run at their limit, and it applies to railways, to service architectures, and to teams: a system with zero slack does not fail gracefully. It fails everywhere, all at once. Anyone who has watched a queue at full utilization knows the shape of it; the math does not degrade politely; it goes vertical. The organization that schedules every person to capacity and every date to the optimistic case has not eliminated waste. It has arranged for the next surprise to become a catastrophe.

Building in “slack” required serious translation work. Actually building the thing was the easy half. But funding it, review after review, required speaking in code.

Instead of the word-that-must-not-be-named, I said “resilience.” I said “operational excellence.” I said “capacity headroom,” “sustainable pace,” “reduced operational load,” “availability engineering,” etc.

All of these words were true; all of these words were accurate. But all of these words were a euphemism tax I paid so that the room would never hear that one dreaded syllable that would have killed the investment in our work. The same document, with “slack” written where “resilience” stood, would have been dead by the second page. The word for deliberately reserved capacity and the word for laziness are close enough cousins that the concept becomes indefensible the moment you name it honestly.

So, I learned to camouflage it in a more palatable vernacular.

“Slack” was not alone on the unwritten banned list, either. “Technical debt” lived nearby, distrusted for the same underlying reason: both words admit out loud that the optimistic plan was never the whole truth. That one deserves its own essay someday.

It is strange to spend effort disguising good engineering as something other than what it is, but I understood the instinct I was working around. In a culture that measures delivered results, reserved capacity looks like waste, because its entire value lives in the “what if?” The outage that hasn’t occurred yet, the date that hasn’t slipped. There is no line on a dashboard for disasters that have yet to arrive. But arrive they do. They always do.

This is why, in my experience, it is so often the quiet leader who ends up building the slack. Building margin requires thinking in second-order effects, caring about what happens after the launch instead of at it, and being willing to advocate for a future that nobody else in the room can see. It also requires being at peace with a hard truth: if you do this well, it will look like nothing.

That is the trap: Prevention is invisible, and firefighting is loud.

The team that ships heroically at 2am generates war stories, visible urgency, and promotion-document material. The team that quietly built enough margin so that nothing catches fire generates a calm that gets misread. I watched it happen to my own teams. Our smoothness was sometimes mistaken for having it easy, as if the absence of crisis meant the absence of difficulty. As if the lack of disaster was a product of pure luck rather than intentional engineering.

Some organizations, without ever intending to, end up rewarding the arsonist with the firehose. The person whose corner of the system is always dramatically on fire, and who always dramatically extinguishes it, out-narrates the person whose corner never burns. If your promotion process cannot tell those two people apart, your best builders of margin will eventually leave, or worse, learn to start fires.

The wrinkle here is that too much slack really is waste. A system padded everywhere is a system that has stopped making important choices, and an organization can absolutely hide laziness inside the vocabulary of “resilience” and “readiness.” I have seen padded estimates that were just fear, and buffers that were just an unwillingness to commit.

So the answer is not a number. There is no universal amount of slack to build in. Anyone who gives you a percentage is selling something. The answer is simply a question you can continually ask about your own system, whether it is a service architecture, a team’s calendar, or a national railway:

“When the last surprise arrived, what absorbed it?”

If the answer is designed margin, the shock stayed local, and the system kept its promises, you have slack. If the answer is someone’s weekend, someone’s health, or a cascade of missed commitments three teams away, you have a system running at its limit, and the efficiency you are so proud of is a loan against the next surprise, at an interest rate you have not calculated.

The Swiss trains are on time because the timetable does not demand that every train be perfect. The German trains are perfectly on time until one slip throws them into utter chaos.

There is a version of one of these that lives in your organization.

Which one is it? And what is the cost?

We were there for training, and part of that training was sitting beside the representatives while they took live calls. Some of the calls were about our product, the Amazon Appstore, while others were about retail orders.

One call I will never forget. A woman phoned in about an item that had arrived broken, and she came in armed for bear. Not quite yelling, but intense, loaded, and ready for the fight she was certain was coming.

The representative I was paired with took the customer’s information, pulled up the order, and issued the refund while the woman was still venting. Then she waited, calmly, for the storm to finish. And when it did, she said, in a quaint Scottish accent I can still hear: “Miss, thank you for the information, and I am sorry you have had this issue. I have already issued your refund. You do not need to return the item. Would you like me to order another one for you, or is there anything else I can help with?”

You could almost hear the wind leave the caller’s sails. A sigh, and then gratitude. The fight she had prepared for never happened.

I have admired the poise of that room ever since. The representative absorbed a storm without matching its volume, acted before she spoke, and let the action do the arguing. The quietest person in that exchange held all the power.

But the individual representative is not the whole story. The refund was already processed before the customer finished talking, and that wasn’t just because of the representative’s kindness. It was part of the company’s design.

Not every company is designed like this.

Recently, I spent the better part of two weeks trying to cancel a business phone service.

The website would not let me. Cancellation required a phone call; the phone call required a hold; and the hold led to a person whose job was to offer me discounts I had not asked for before finally, reluctantly, opening a ticket. Even after the ticket was filed, the billing page still showed the renewal charge, scheduled and ready, contradicting the cancellation banner two inches above it.

None of that is an accident. Somebody designed that flow. They looked at the churn numbers, understood exactly what a phone call plus a hold plus a retention script does to cancellation rates, and approved it.

The two experiences I am sharing are not simply different levels of customer service. They are different beliefs about customers, rendered as workflows.

The phone service company believes that the customer is an adversary to be outlasted. Every barrier is a bet that you will give up before they do, and if you are too frustrated to continue the fight, they take that as a win.

The Amazon/Edinburgh model, by contrast, believes the customer is telling the truth. The refund-first design is that belief, operationalized.

Amazon does have (and had) real safeguards against genuine bad actors who were gaming refunds, and those safeguards ran separately, but the default stance was to trust the customer. The design choice was “set the default to trust, and handle the exceptions as exceptions.” When companies set the default to suspicion, every honest customer pays the cost.

This is a leadership decision, not a ground-level customer service quirk.

I know something about where the customer service friction road ends, because I worked at a company that had already driven it.

Years before I joined, AOL was caught making it extraordinarily difficult for customers to cancel their dial-up service. The FTC acted, gave them a fine, and sent down a mandatory training for every single employee on why and how not to do that to customers.

This training even reached me. I joined years after the decision, and I still had to sit through the training built to atone for it.

Think about the accountability arithmetic there. The executives who chose friction were optimizing a retention metric, and it worked, on the spreadsheet, for a while. By the time the consequences arrived, they had moved on. The fine landed on the company. The training landed on people like me, who had nothing to do with it.

The accountability arrived, but at the wrong address. The lesson was absorbed by everyone except the people who needed it.

I think about that whenever I see a company quietly install a cancellation maze. The leadership implementing it knows their decision isn’t harmless; they just know the consequences are deferred. Their retention rates will get an artificial boost, and the brand damage or regulatory action will be someone else’s problem.

There is a second cost of friction that companies also need to take seriously.

On that same Edinburgh trip, we listened to an Appstore call from a customer who had received more than twenty confirmation emails for a single app purchase and was, understandably, worried he had been charged twenty times. He had not been, and the representative confirmed it, but the emails never made that clear.

I took that call back to our teams in London, and when we dug in, we found a genuine edge case in the purchase flow: when the connection to the bank was failing intermittently, retries could each trigger a confirmation email while the charge itself sat unresolved. It was not in our use cases or test plans, and I doubt any amount of internal review would have found it because nothing was technically “broken” from our side of the glass.

The customer’s confusion served as the bug report.

That is what a call center actually is, and what high-friction customer service flows are missing: a fine-tuned sensor array. It is the only instrument a company has that measures reality as customers experience it rather than as systems report it. A company that makes customers fight to reach a human is not just spending goodwill; it is blinding itself to the signals it most needs. Edge cases and confusions that do not show up on dashboards show up in customer service calls. If the customers carrying that signal give up on hold, the company will never receive it.

Friction does not just cost you customers. It costs you information that could have made the product better. A company that makes customers fight to be heard loses its most valuable source of feedback.

And if that mechanism sounds familiar, it should. It is the same filter that operates inside organizations, one layer down. A meeting culture that rewards volume does exactly the same thing to its quietest people, and pays the same price: the edge cases, the early warnings, the truths that do not survive the barrier. Friction and loudness are one filter wearing two uniforms. Organizations that build either one are choosing comfort over signal, and the bill arrives later, itemized as surprises.

One rule I hold personally is to never be critical of the person in the call center, not even the person at the phone company that made me fight for two weeks. They did not write the policy. They were handed a script and a metric, and the friction I am angry about lives several layers above their desk. I make that distinction explicit to them every time.

I only get frustrated with them if they start personally defending the policy. That is the moment they stop executing a decision and start owning it.

Criticize the rule, never the person handed the rule. It is a small ethic, but I have found it maps onto almost everything inside organizations too. The person absorbing the complaint is almost never the person who caused it, and treating them as if they were is both unfair and useless. Accountability lives with whoever wrote the rule. Aim there.

The question I would leave with you is this, and I do not think it resolves cleanly:

Some friction is legitimate. Real bad actors exist, and safeguards against them are responsible engineering. So how does a leader tell the difference between friction that protects the business from genuine abuse and friction that protects a metric from genuine customers?

The uncomfortable answer is that the spreadsheet looks identical either way. Churn improves. Losses drop. The dashboard cannot tell you which kind of friction you built.

The only reliable test I know is the one the woman in Edinburgh passed without thinking: would the person in front of you recognize the policy as fair if you explained it to them plainly? The refund-first design survives that explanation. The cancellation maze does not, which is why nobody ever explains it plainly to anyone, including themselves.

That test cannot be run from the executive floor. You have to sit next to the person taking the call.

I was the CTO of a startup, a year or so before I moved across the country to Amazon, and the conversation was about the direction of the business. I know what was said, what I said back, and the four better things I could have said instead. I have run through it enough times that the improved versions are now more vivid than what actually happened. Nobody else in that room remembers it, and I would bet they could not tell you the year that it happened.

I should admit that I could not tell you the exact date either. To figure out the year, I had to work backward from which desk I was sitting at. The mental loop keeps the words and throws away the calendar, which tells you something about what the loop thinks it is for.

I rehash everything. Every interaction, every decision, every meeting. What I said, what I should have said, what I would say if it happened again tomorrow.

For most of my career, I considered this a defect. However, I have since decided it is closer to a tool that arrived without instructions.

If you lead quietly, I suspect you know exactly what I am describing.

The quiet leaders I have worked with and coached tend to share this. It is part of the same internal equipment that makes them good: they process before they speak, they read the room carefully, and they consider second-order effects that faster people skip. That machinery does not switch off when the meeting ends. It keeps running on the transcript.

This is why the same trait produces both the best judgment on the team and, at two in the morning, a fifth pass through a hallway exchange that everyone else forgot by lunch.

The strength and the affliction are two programs running on the same machine.

Last week, I wrote about the loop that runs before a decision, when two things you value are colliding and more deliberation will not settle it. This is the loop that runs after: the same machinery, pointed backward. And it has the same failure mode: it feels like thinking long after it has stopped producing any useful thoughts.

Here is why this failure mode is genuinely a problem. I want to name it plainly because it costs people careers.

The replay can substitute for the act.

I have known quiet leaders who deliberate so thoroughly that the moment passes while they are still chewing on their plan. They compose the perfect intervention, refine it, anticipate the objections, and by the time it is ready, the decision has been made by someone with a worse answer who said it out loud.

The rehearsal replaces the performance. It’s like locking yourself in your room for days to practice your song or dance routine, and then not stopping to leave for the show.

This feels like diligence from the inside, which is what makes it dangerous. It produces the sensation of effort and the air of responsibility, and it leaves no evidence of failure because nothing was ever attempted.

I have watched this cost people promotions they had earned on every other dimension. Their judgment was the best in the room, but nobody ever heard it in time.

What eventually helped me was not stopping. I tried that, and it doesn’t work. You cannot simply decide to do less of the thing your brain is built to do.

What actually helped was asking a question about the replay itself:

Is there something to learn here, or am I just thrashing?

That is the whole tool. It is unglamorous, and I have used it for years.

If there is something to learn, the loop is doing its job. Let it run. There is real information in the second or third or even fourth pass: the thing you missed, the reaction you misread, the sentence that landed differently than you intended. That is the machinery working as designed.

However, if I am on the fifth pass of the same conversation and arrive at the same conclusion, the loop is no longer analysis. It is anxiety wearing analysis as a costume.

The tell is repetition without new output. Analysis produces something you did not have before, while thrashing produces the same conclusion, felt more sharply each time.

One practical addition for the loops that refuse to close on their own:

Write the lesson down. A single sentence is enough. The brain replays because it is trying to make sure the lesson survives, and it does not trust memory to hold it. Give the brain a place to store the lesson, and the loop will often let go because its job is done. I have ended ten-year replays with one line in a notebook.

I still thrash, but the difference is that I usually catch it now. The reflex does not leave; you just get better at telling which version of it you are in.

I have a theory about why the loop exists. It’s not a serious theory, but I think it points at something true.

Somewhere way back in our history, we had an ancestor who replayed that day’s hunt in his or her head. If “Crog” had just swung left and stabbed upward, that sabertooth would have gone down easier. Because of that replay, he improved on the next hunt. He went out the next morning with a better plan. The one who thought “you win some, you lose some” and slept soundly went out with the same plan and had another failed hunt.

That’s where we inherited our tendency to replay scenarios.

I am joking, but only partly.

We carry a great deal of machinery that was installed for conditions we no longer live in. The replay was built for a world where the same threat recurred, where the lesson from Tuesday applied directly on Wednesday, and where the cost of getting it wrong twice was much more than a bruised ego.

Most of what we replay now does not recur in that form. The meeting will not happen again, the person has moved on, and the specific configuration of that conversation will never reassemble itself.

Which is exactly why the loop needs supervision rather than obedience. It is a good tool running in an inappropriate context, and it does not know that.

There is one more thing worth saying, because otherwise the advice becomes “think less,” and that is both impossible and wrong.

Some replays deserve years.

I have decisions I have turned over for a decade that still produce something new when I return to them, usually because I have changed enough to see them differently. That is not thrashing. That is the slow work of understanding your own history, and it is necessary.

The distinction is not how long you have been at it; it is whether the replays produce anything new.

A loop that has yielded new understanding three times across ten years is producing insight. A loop that has produced the same feeling four times since Tuesday is just producing anxiety.

The question I would leave with you:

Right now there is a conversation running somewhere in the back of your head. There usually is.

Ask it directly: what have I learned on this pass that I did not have on the last one?

If you have an answer, keep going. The machinery is earning its keep.

If you do not, write down the one thing you already know, and let the loop empty itself out.

The meeting is over. You are the only one still in it.

Now that I have this time, one realization keeps surfacing: some of what I remember as the hardest decisions of my life were not hard at all. They were instant. They only look difficult in the retelling.

The reason is that I already knew what my priorities were, whether or not I could have written them down at the time. The decision may have been important or heavy or pressured, but it didn’t actually challenge my priorities. There was nothing to think about or deliberate on. The decision was obvious.

After those decisions were made, however, their importance or the pressure I felt at the time made me file them away in my emotional memory as “tough decisions,” even if the decisions themselves weren’t tough at all.

In all of the examples I am thinking of, anyone who knew me well would have predicted every one of those calls. “Of course Dave will do that. It’s who he is.”

That is a comforting sentence when the decision was a good one. It is considerably less comforting when the thing I did without hesitating was unwise.

Here is the flattering example.

My mother was dying of cancer. I took a few months under FMLA to be with her.

I was a son who loved his mother, and there was nothing to decide. There was never a question. The decision was easy.

Now here is the unflattering one.

At Amazon, I owned the Appstore backend services. We depended on another team’s entitlement system, and we were building around its inadequacies rather than getting them fixed. My team was absorbing work that, architecturally and from an ownership standpoint, belonged somewhere else. We were on a tight timeline.

It was not fair. So I pushed.

I was told no by the senior manager. So I went to his director, who also told me no. So I went to his VP, who told me no as well.

Three levels of the same answer, but I kept going because I knew I was right.

I will be honest with you: I still think I was right. The architecture argument holds up. The ownership argument holds up. If you put the design on a whiteboard today, I would make the same case.

But this pushing cost me. It cost weeks I did not have on a timeline I could not move. More expensively, it cost relationships with three people I would need later, and rebuilding those took considerably longer than it took my persistence to destroy them.

Here is what I could not see at the time: that team was not being unreasonable. They had their own priorities, their own timeline, and their own leadership telling them what mattered. From inside their world, my urgent problem was someone else’s roadmap request.

And underneath that was something larger. Amazon ran on an ownership model where every team builds what it needs. I never fully accepted it, and I still have reservations, because it collided with priorities I had spent twenty years building as a software architect: Reuse. Clear boundaries. Do not make ten teams solve the same problem badly.

I was not fighting the entitlement team. I was fighting the operating model, one senior manager at a time, without ever quite admitting that was what I was doing.

Both of those decisions were instinctive; instant.

The pull toward my mother and the pull toward the fair architecture came from the same place, arrived at the same speed, and felt identical from the inside. Certain. Obvious. Not really decisions at all.

They are not two different traits. They are one trait, pointed at different targets.

Sometimes, it is a trait I am glad to have. Other times, it has cost me time, credibility, and momentum. The uncomfortable part is that in the moment, I could not tell them apart. Both felt like integrity.

If you want to know why some decisions are easy, the mechanism is not complicated.

A decision is easy when your values are already ranked, and the situation only touches one of them. There is nothing to weigh, because nothing is competing.

A decision is genuinely hard when two things you actually value collide, and you have never before had to find out which one sits higher.

This is why difficulty and stakes are almost uncorrelated. Not many agonize about whether to be with a dying parent, but many people agonize for weeks over whether to cut a project someone loves, whether to tell a strong performer they have plateaued, or whether to say the thing in the meeting that everyone is already thinking. Those look small from the outside and feel enormous from the inside, because two real values are grinding against each other.

When you are stuck on a decision like that, the instinct is to gather more information. More data, another conversation, one more week of thinking. It almost never helps, and now I understand why: the problem was never information. You are being asked to publicly demote something you value, and in a way that has real impact.

That is why it hurts, and why the deliberation loop can run indefinitely without producing anything. You are not analyzing. You are refusing to rank.

I do not think there is a clean way through that. I have never found one. But knowing what the stall actually is has, at minimum, stopped me from mistaking endless deliberation for diligence.

There is a specific version of this that every senior leader eventually meets. My entitlement fight was mine.

At some point, your personal hierarchy will collide with the one your organization rewards.

Mine ranked architectural integrity and fairness across teams near the top, while Amazon ranked ownership and delivering results. Neither ranking is wrong. They are simply different, and I spent an embarrassing amount of energy treating a difference in priorities as a failure of reasoning that the right argument could fix.

It could not. You cannot argue an organization out of its ranking, because the ranking is not an opinion. It is whatever the promotion committee rewards, and it has years of momentum behind it.

What you can do is know your own priorities well enough to see the collision coming, and then choose deliberately: adapt, absorb the cost, or leave. All three are legitimate. What is not legitimate, or at least not effective, is the approach I used at Amazon: continuously escalating in the belief that someone would surely see it my way.

This brings me back to that decision I opened with, taking time off to be with my mother.

Taking those months off cost me. Not “officially,” of course. Amazon followed the letter of the law, and I am not accusing anyone of anything.

But culture and policy are two different things. In a culture that prioritizes delivering results, a person who steps away for a few months to sit with their mother has, in the only language that system reads fluently, stopped delivering results. That shows up later. It showed up for me. It slowed down my career progress at Amazon.

Was that fair?

Maybe. Maybe not.

But the cost was real. However, I would make the same call again and again without hesitation. That is what happens when your priority ranking is already settled.

One more thing, because otherwise this sounds more fixed than it is.

Priorities shift. Mine have. The ones I hold at fifty-nine are not identical to the ones I held at thirty-five. Some of that is growth, while some of it is simply that circumstances changed and different things rose to the top.

What has not changed is that testing priorities clarifies them. Every time a decision arrives and you watch yourself answer it instantly, you learn something true about your own hierarchy that no amount of abstract reflection would have told you. Those moments do work that introspection cannot.

The question I would leave with you:

Think of a decision you made instantly that other people would (or did) describe as hard.

Then think of a fight you picked instantly that other people thought you should have let go.

Both of those came from the same place. What is it?

Answer honestly and you will know something about your own priorities that most people never bother to check. You will also start to see it in the people around you. Everyone has priorities, and they become visible in the moments they act without deliberating.

Then look at the decision actually sitting in front of you this week. If it has been too hard for too long, you are probably not missing information.

You are refusing to rank two things you care about.

If you don’t rank them intentionally, someone else will rank them for you.

They always mean it kindly, but what they are picturing is the Hallmark version: people who show up for each other, who forgive the bad quarter, and who stay through the hard part because that is what families do. Belonging. Loyalty. Care.

I think the metaphor of company as family can be accurate, but not for those Waltons-esque, Leave It to Beaver reasons.

Families are also where you find the parent who cannot be corrected, the sibling rivalry over a finite supply of approval, the guilt deployed as a management tool, and the one person who does most of the work and is thanked for none of it. Families are where people tolerate treatment they would never accept anywhere else because leaving costs so much.

If you look at things that way, “Our company is a family” doesn’t seem so inaccurate after all.

The same thing happens with the other favorite comparison. A certain type of leader also loves to say that the company is a team, referring to a championship roster. They aren’t talking about the type of team I grew up watching in Ohio…the 0-16 Cleveland Browns were also a team. The Bundys from “Married… with Children” were a family.

But these aren’t the types of families and teams they are referring to, even if they are the more accurate comparisons.

The metaphor alone tells you nothing. A company can be a good family or a bad one, a good team or the Browns. And calling the company a family or a team doesn’t move it any closer to being the kind of family or team that leaders want it to be.

Families and teams both have a culture that bonds them or breaks them. When a leader reaches for one of these metaphors, they are describing the culture they wish they had.

The trouble is that culture is not something you describe. It is defined by what gets rewarded.

What does your organization reward?

Not what it says it rewards. Not the values on the wall, the laminated card, the slide in the onboarding deck. What behavior, when someone exhibits it, results in that person getting promoted?

That is your culture. All of it. Everything else is decoration.

I spent seven and a half years at a company with genuinely good leadership principles. I am not being sarcastic; I embraced them. They were clear, memorable, and unusually well written, and thousands of people could recite them from memory, which is more than most companies achieve.

But when it came time to evaluate someone, or to promote them, one principle dominated everything: deliver results.

The others were honored. You had to demonstrate no obvious weakness in any of them. But deliver results is what the room actually argued about, what the documents were built around, and what carried a candidate over the line. I know this because I wrote those documents. When I put someone up for promotion, I led with their results, because that is what the system could read. I was describing my people in the language that would get them what they had earned.

Here is the part that should bother you, and something that still bothers me.

I watched more than one leader get promoted while running over forty percent annual turnover on their team.

Forty percent. Meaning that in a year, four out of ten people decided that whatever was happening there was not worth staying for. That is not ambiguous. It is one of the few things in a large organization that is unambiguously measurable, and it sat right there in the data while the promotion went through, all because results were being delivered.

This practice obviously went against the stated principle to hire and develop the best people. The issue is that hiring is easily measurable, while development is not.

Those leaders hired constantly. They had to; they were replacing four out of ten people every year. So they had hiring volume, hiring bar raiser participation, requisitions closed, headcount grown. All of it visible, countable, and defensible in a document.

Develop is the other half of that principle, and it is nearly invisible. It happens in one-on-ones nobody records. It shows up two years later in someone else’s promotion, usually credited to that person’s current manager. It has no metric attached to it that survives contact with a review committee.

So the principle was satisfiable by half of itself. Hire enough people and the sentence is technically true, and the turnover you generated becomes evidence of your hiring prowess rather than evidence of your failing leadership.

A company can print “develop the best” on the wall in forty-point type, but if the promotion committee cannot measure it, it is not a value. It is a wish.

When you see this in action, it is pretty hard to believe that the company is similar to a family in any positive regard.

There is a sharper version of this, and it is the one that convinced me the problem is structural rather than personal.

I watched capable senior managers sit on the bubble for promotion, get told they looked light on hiring and developing the best, and suddenly conjure up a cohort of mentees. Suddenly there were promotions being pushed forward for people on the team, multiple all at once, from someone who had not promoted anyone in two years.

Right as the promotion document was being assembled… this is not a coincidence.

I am not saying that these people were acting cynically. I do not believe they were. They had spent two years all-in on delivering results, because that is what the organization had shown them would determine their trajectory. When they learned that a second thing would be checked, they addressed it. Efficiently.

That is not a character failure. That is a competent person responding accurately to a measurement system.

And it reveals the actual rule of organizational culture: whatever is rewarded at the core gets the majority of your time, every day, for years. Everything else can be caught up on in the few months before your document goes forward.

The mentees were real. The promotions were real, and I expect the three people who got promoted were happy about it. But four mentees acquired in a quarter is not a leader who develops people. It is a leader who has been given a new rubric.

I should tell you what this system taught me personally.

One year, I broke my arm. Badly enough for real painkillers. Within days, I was back in the office, still on oxycodone, because I believed I needed to be there to make sure my team delivered.

Think about that decision. Nobody ordered me in. I drove myself there, medicated, because somewhere along the way I had absorbed exactly what the system valued, and the calculation felt obvious rather than insane.

My manager said nothing at the time. No conversation, no question about whether I should be there, no suggestion that I go home.

It came up months later, in my annual review, as an observation. Something about seeming out of sorts, and sometimes slurring my speech.

I have thought about that for years. People saw that something wasn’t right and retained it, but it didn’t serve them to acknowledge it in the moment. It would have cost them something and helped me, so they saved it for later, for the forum designed for judgment rather than help.

That is not a failure of leadership principles. Every principle on our wall would have told him to send me home. It is an incentives failure. Nothing in the system paid him to intervene, and the review document had a box for his observation.

So what do you do with this if you lead people?

Stop auditing what your culture says. Audit what it pays.

Look at your last several promotions and ask what those people actually had in common. Not what the promotion document claimed, but what was actually true about them and their work. If it is one thing, that thing is your culture, and every value you list alongside it is a preference at best.

Then look at the values you claim that nobody can measure. Developing people is almost always on that list, along with judgment, long-term thinking, and integrity under pressure. If you cannot describe what evidence of that value would look like in a promotion decision, you have not committed to it. You have decorated with it.

When you do look at the evidence, look at the dates. A leader who has developed people has been doing it for years, quietly, in ways that are hard to assemble into a list. A leader who discovered the requirement in March will have a very tidy list, all of it from this year.

You do not have to make everything measurable. Some of the most important things a leader does will never be legible to a committee, and pretending otherwise produces worse metrics rather than better cultures. But you should at least be honest with your people about which of your stated values will actually carry them, and which ones are aspirations you have not yet built a way to see.

That honesty is rarer than it sounds, and people can handle it. What they cannot handle is being told that development matters, doing the development, and then watching the person with forty percent turnover get the promotion.

The question I would leave with you:

Think about the last person your organization promoted.

What did they actually do to earn it?

Now compare that to what your organization says it values.

If those two answers match, congratulations. You have a real culture.

If they do not, then you already know what your people know, and you have known it longer than you have admitted:

Your company is not a family, and it is not a team. It is a system that pays for certain behaviors and tolerates the rest.

The good news is that this makes it changeable in a way families and teams are not. You cannot lecture a culture into existence, and you cannot name it into existence either. But you can decide, deliberately, what the next promotion says about what matters in your organization.

That decision is the only culture statement that matters.

He later applied the same advice to my dating life, with the same dry delivery.

I learned just this week, riding a train through Alaska with him, that his father had given him the same advice. I have relied on it my entire life. So has he, apparently.

I have applied it to job interviews, negotiations, vendor contracts, and more situations than I can count. It is the single most durable piece of advice I have ever received, and it is durable because it is not actually about cars, or dating, or interviews.

It is really about what desperation does to your judgment, and what the appearance of desperation gives to the other side of the negotiation table.

Just because the advice is sound, simple, and broadly applicable does not mean it is easy. Let me tell you about the time the advice was hardest to follow, because it is easy to sound wise about walking away when nothing is at stake.

Lycos laid me off a few weeks before Christmas. The dot-com bubble was bursting, the market for people like me was shrinking by the week, and I had three kids under seven at home. I had some savings, and I did the math on exactly how long they would last. The math was not comforting.

By any honest accounting, my situation was desperate. Or close enough that the difference did not matter at two in the morning.

Here is what I understood, standing in that December: my circumstances were desperate, but nobody I interviewed with needed to know that. Desperation is a fact about your situation, but broadcasting it is a choice about your behavior. It is a choice that will have a tangible impact on the dynamics of the deal.

A candidate who projects desperation accepts the first number, oversells to every question, agrees with everything, and radiates a need that interviewers immediately identify as reduced leverage. Worse, desperation is frequently mistaken for something else: weak judgment, or a lack of other options, which reads as a lack of quality. The desperate candidate is not just easier to underpay: they are easier to pass on entirely.

So I interviewed as if I had options, because even though my situation was desperate, I truly did. I knew what I was willing to walk away from, I evaluated companies as much as they evaluated me, and I asked real questions. My need was none of the interviewer’s business.

But I also did have to concede some things. I let go of holding onto my manager title in a collapsing market. I knew what I would walk away from, but I also knew what I could be flexible on to increase my chances of getting a job I badly needed.

Before Christmas, I had two offers. Both came with a higher base salary than I had earned as a manager at Lycos. If I had been the “desperate guy”, I am not sure I would have received those offers.

I want to be careful with that ending, because it can sound like a tidy moral: “stay calm and the universe rewards you.” That is not the claim. The market could have stayed frozen. They could have passed on me. Any number of things could have happened.

The claim is that interviewing without desperation did not cost me anything, and it removed a liability in my profile. I was controlling what I could so that I didn’t make things worse. You never want to show all your cards, especially if your hand isn’t very good.

made this point recently about executive interviews, where the stakes and the scrutiny are highest, and he is right. At that level, the evaluation is substantially about judgment under pressure, and visible desperation is not a positive sign. But I have come to believe the principle applies at every level and in most rooms that matter: negotiations, promotions, client renewals, fundraising, even difficult conversations at home.

“Ready to walk away” is widely misunderstood as a bluffing tactic, and that is not what my father meant. A bluff is a performance of leverage you do not have. Being truly ready to walk away is an internal state, not an external display. It means you have actually done the work of answering: what is my alternative if this falls through? What am I unwilling to accept? At what point does leaving become better than staying?

Once you genuinely know those answers, something changes in how you carry yourself. It cannot be faked and does not need to be announced. You ask better questions because you are actually evaluating rather than auditioning. You pause before answering because you can afford to think. You decline to chase, and the other side notices.

The paradox my father understood while buying a car with a teenager was this: the person ready to walk away almost never has to. Readiness to leave is what makes staying a choice, and the other side can feel the difference between someone choosing them and someone clinging to them.

There is a harder version of this that I want to name, because “be ready to walk away” can sound like advice for people with cushions.

Sometimes you genuinely cannot walk away, or the walk is brutally expensive. The savings are thin, the market is bad, the timing is terrible. December 2000 was close enough to that for me to remember the feeling permanently.

Even then, the principle holds in a reduced but real form: you may not be able to change your alternatives, but you can always decline to advertise their absence. The other side of the table knows your situation only as well as you present it. Desperation kept private is a private problem to be managed. Desperation displayed becomes a term of the negotiation.

And there is one more thing, the part that took me longest to learn: being ready to walk away sometimes means walking away from a version of yourself. The thing I released that December was the manager identity I thought I had to defend. Holding it would have narrowed a shrinking market to almost nothing, and letting it go is what created the options that let me interview like a person who had them.

Sometimes the thing you have to be ready to leave is not on the other side of the table. It is the thing you brought in with you.

The question I would leave with you:

Somewhere in your life right now, there is a negotiation. A role you want, a deal in motion, a situation you are holding onto tightly.

Do you actually know your walk-away point? Not a feeling. The actual answer: the alternative you would accept, the line you will not cross, the moment when leaving beats staying.

If you do not know it, the other side is negotiating with someone who cannot leave. And whether or not you have said a word about it, they can usually tell.

There are always other cars.

The loudest leaders in an organization — the ones who dominate every discussion and have never met a silence they did not want to occupy — frequently go completely quiet in the one moment their voice would actually matter: when someone who works for them needs meaningful feedback.

They are loud when making a point because the volume reflects on them, and they know it. Visibility is currency, and speech is how it gets minted.

But then a direct report sits down for a one-on-one, a review, or a career conversation, and the fountain of words runs dry. What comes out instead is vague, high-level, and hollow. “Keep doing what you’re doing.” “You’re on the right track.” “No major concerns.”

The person who could talk for forty minutes about a strategy or slide deck cannot manage four specific sentences about your performance.

I have written before about what quieter folks should do to receive better feedback from their managers. Namely, ask specific questions, ask for criteria instead of affirmation, and avoid ambushing a manager who has not prepared, because an ambushed leader retreats to generalities every time. That advice stands, but it puts all the work on the person receiving the feedback, and today I want to talk about the other side of the equation.

On the manager’s side, the feedback void is not a communication problem. It is a courage problem, and occasionally a cruelty problem, and the people it damages most are the ones performing well. Especially the quiet ones.

Somewhere along the way, our industry decided that all feedback must be “constructive,” and constructive quietly came to mean “not positive”. “Feedback” became a formal permission to deliver criticism, and praise became seen as something soft or suspicious that might make people complacent.

Many of us absorbed this long before we started working. If you grew up with parents who ran primarily on negative reinforcement, the pattern feels natural by the time you first enter a workplace. Attention means something is wrong, silence means you are fine, and praise is for children.

Based on this, we built organizations where the entire feedback apparatus points one direction. And the result is a workforce that hears from leadership only when something breaks. Praise is nowhere to be found.

Now, I am not calling for hollow praise. Hollow praise is worse than silence; people detect it instantly, and it devalues every honest word that follows. What I am pointing to is the total absence of the real thing: specific, earned recognition of something that mattered.

Think about the best people you have worked with. How often did anyone tell them, concretely, what they were doing well and why it mattered? In my experience, almost never. We assume excellence is self-aware, but it usually is not. The strongest people I have managed were frequently the least certain about which of their behaviors actually made the difference.

My default correction to this “praise void”, built over a long time and after getting it wrong plenty, is simple: correct in private, praise in public.

A remarkable number of leaders today run the opposite configuration. They correct in public, sometimes deliberately, on the theory that visible correction teaches the whole team at once. It does teach the whole team something: to hide mistakes, avoid risk, and manage their exposure to the leader. It doesn’t necessarily teach them whatever the leader intended as the lesson. Public correction produces fear, and fear produces silence. This silence can eventually cause the leader who inspired it to be blindsided by the information their team was too afraid to share.

I will occasionally correct someone in public, but only in two specific situations.

The first is when a mistake has been repeated enough times that the team needs to see the process change, not just the singular action. Even then, the target of my correction is the process. The individual may still feel some discomfort, and their peers will understand why, precisely because I do this so rarely that it carries meaning.

The second is during a crisis, when everyone needs to learn the lesson in the moment. I once had someone sit on a problem during an incident and present it late, after trying to resolve it quietly. I deliberately corrected that in front of the room, not to punish the person, but because everyone needed to hear the principle immediately: during a crisis, bring me the problem the moment you see it. I will never be upset that you raised something that turned out to be nothing. I will absolutely be upset by information that arrives late. In a crisis, more information is almost always better than less, and the room needed to learn that before the next hour of the incident, not in a retro two weeks later.

Outside those two cases, correction happens behind a closed door, where the person can actually hear it instead of performing their reaction to it.

Praise is the other half of the feedback ecosystem, and it is the half that costs almost nothing, yet gets spent almost never.

The mechanics of praise are not complicated: Catch something real, name it specifically, and say why it mattered. That is the entire skill.

In public, it can be one sentence in a team meeting: “X did more here than I expected, and it moved the whole timeline. That is what exceeding expectations looks like.” Ten seconds. The person remembers it for a year, and the team learns what good looks like without anyone being diminished in the process of teaching it.

In private, the most effective version I know is even shorter. A specific example, then five words: “That. Do more of that.”

I have watched that small sentence redirect careers. Not because it is clever, but because it solves the problem I named earlier: your best people frequently do not know which of their behaviors is the differentiating one. They are running twenty behaviors and guessing.

This is where the primary misconception about praise comes into play: Specific praise is not a reward. It is information. It tells a high performer where the signal is.

The leaders who withhold this are sitting on the cheapest, highest-leverage tool they have, usually for the simple reason that praise feels awkward in their own mouths. That awkwardness is worth examining and challenging because, while the discomfort is ours, the cost of it is paid by someone else.

I want to return to the inversion I opened with. I do not want to let it off the hook.

A leader who has volume for every status meeting but none for your development is telling you something about where their attention actually goes. Speaking to the room builds their standing, while speaking to you, specifically and privately, builds yours. One of those is an investment in themselves; the other is an investment in you. The ratio between how much a leader invests in themselves and how much they invest in you is the most honest measure of a leader there is.

If you lead people, the ratio applies to you. It applies to me.

The question I would leave with you:

Think of the strongest person on your team. Not the loudest. The strongest.

When did you last tell them, specifically, what they do well and why it matters?

If you cannot remember, they cannot either. And the silence you think of as “no news is good news” is being read, on their side of the desk, as no news at all.

They will not ask. The strong ones rarely do.

Telling them is on you.

He described spending fifteen years at companies where volume dominated the environment. If you did not take up space, you got overwritten. So he adapted. He built a loud, dominant presence that was not natural to him because the environment rewarded it. It worked. Then, he internalized the culture so thoroughly that he began to assume everyone else’s success had to look like his: vocal, immediate, filling the room.

Then, leading an engineering organization slowly untaught that assumption. He watched his own leader, a quieter person, move decisions forward by walking in with a clearly written proposal that had been thought through for weeks. He didn’t push things through with volume; he did it with clarity. While working for this leader, Krishnan found himself catching the old reflex mid-meeting. He noticed that he would reach to fill a silence or speak loudly when he should have just sent the memo first.

Krishnan wanted to change that impulse, but he shared his challenge with me: “The habit lags behind the insight.”

Then he asked me: “What actually changed the habit for you? Not the insight. I already have that part. The habit. How can I move from knowing something to changing my behavior?”

It is the best question anyone has asked me about this work of developing quiet leaders because it identifies what almost every piece of leadership writing skips: Insight is cheap. The gap between knowing and doing is where the entire difficulty lives, and most of us pretend that gap closes on its own once we know what to do.

It does not.

And for me, it took a long time to close that gap.

I began to understand, sometime in my thirties, that I was speaking in meetings for the wrong reasons. I wasn’t speaking up because I had something the room needed, but because the silence had gone on too long and someone needed to fill it. If it wasn’t me, I would look absent.

I knew exactly what I was doing, in the moments I was doing it, and I felt conflicted. But I kept doing it for years.

I did not lack the insight. I had it in high resolution. But my behavior didn’t change. That is the reason Krishnan’s question resonated so deeply with me. I had been facing the same challenge two decades ago.

It took an embarrassingly long time for my behavior to catch up with my insight, and the mechanism I used to finally change is small, simple, and even a bit uninspiring.

Here is what actually moved it:

Before anything left my mouth, I asked myself one question: “Am I adding noise, or am I having an impact?”

If it was noise, I let the silence stand. If it was impact, I spoke, as forcefully as the moment required.

This question works in real time because it doesn’t fight the instinct to contribute. We don’t want to fight that instinct. But this question aims the instinct. The impulse still arrives, but you route it through a filter before you blurt it out.

The first hundred times I asked myself this question, I was slow and I got it wrong in both directions. I stayed silent on things I should have said and I talked myself into believing noise was impact when I wanted to be heard. This technique is not a magic switch that works immediately and every single time. It is a practice, and practices are bad before they are good.

But even as I was bumbling through the early days of this practice, I started to notice some payoff coming from an unexpected direction.

I had assumed that speaking less would cost me something. Less airtime, less presence, a smaller footprint in the room, etc. What actually happened was the opposite. People paid more attention to me when I spoke.

When you only speak because you have something that matters, the room learns to listen differently. Constant input trains people to half-listen; they know most of what you say is filler, so they filter you by default. Scarce, focused input trains them to lean in, because they have learned you do not waste their attention.

It makes it so that every time you do speak, it lands, because you have spent your words carefully enough that the room knows you do not spend them idly.

That is not a consolation prize for being quiet. It is the actual mechanism by which quiet people generate outsized influence. And this mechanism is available to anyone, including people who have spent years or decades building the opposite habit.

There is something else in what Krishnan wrote to me that I think is more important than anything I told him.

He mentioned that he had been thinking about an essay I wrote on James Madison, the quietest person at the Constitutional Convention, who shaped the outcome through preparation rather than oratory. And then he said something that should probably embarrass me, but instead struck me as exactly right: watching his own leader do this well has done more for him than reading about Madison.

Of course it has.

Madison is an argument. His leader is proof. And proof rewires behavior in a way an argument never does, because the nervous system does not update on essays. It updates on repeated observation of a real person, in a real room, getting a real result you can see with your own eyes.

If you are trying to close a habit gap, the highest-leverage thing available to you is almost certainly not another framework. It is finding the person in your organization who already operates the way you want to, and watching them with deliberate attention. Watch what they do while everyone else is filling the air, and observe how they decide that the moment to speak has arrived.

I have read a great deal about leadership, but nearly everything I actually changed, I changed because I watched someone do it in front of me. Real-life examples are orders of magnitude more impactful than essays or books.

I want to be honest about where this leaves Krishnan’s question, because I do not think it is fully resolved.

The gap between insight and habit narrows, but I am not convinced that it ever truly closes. I still catch the old reflex to “fill the space” thirty years on, usually when I am tired or when the room contains someone whose approval I want more than I would like to admit. My checkpoint mechanism is faster now, catches more, and recovers more quickly, but the impulse has never gone away, and I have stopped expecting it to.

What changed is not that I became a person without the reflex to make noise. It is that I have become a person who notices it and catches it most of the time.

That may sound like a small return on twenty years. It is not. The difference between a reflex that runs you and a reflex you observe is the entire difference between being operated by your habits and operating with them.

And being someone who operates with their habits instead of being controlled by them is possibly the highest leverage change any leader or operator can make.

So when Krishnan says the habit lags the insight, I would only add this: the lag is not failure, and it is not a temporary condition you are supposed to clear. It is the interval in which the new self is under construction, and that construction has no completion date. It has a direction, and you keep moving.

The question I would leave you with is this:

There is something about how you show up, something you already know and could describe accurately right now, something that you would like to change, but you keep doing it anyway.

You do not need another insight about it. You have the insight.

What you need is a question small enough to ask in the half second before you act, and a person in front of you who already does it well.

Have you found either one yet? Or are you still waiting for some new insight? Is “waiting for more information” what you tell yourself you are doing so that you can avoid the discomfort of change?

I had shared the idea a week earlier in a smaller meeting. I was organized and presented the data, and it landed the way things usually did for me: polite reception, brief acknowledgment, and then the conversation moved on. No pushback or real enthusiasm, just a nod and a shift to the next agenda item.

A week later, in a larger meeting, someone else said the same thing and the room came alive. Heads nodded, the senior leader leaned in, and within ten minutes it had become the team’s new direction. But it was being attributed cleanly and completely to the person who said it in that meeting... not to me.

They hadn’t built on my idea or shared a variation; they just repeated exactly what I’d said a week earlier.

I sat there feeling the heat rise in the back of my neck. My idea had won, but it had won without me. And everyone in the room believed it had started somewhere it hadn’t. That it came from someone it hadn’t.

I said nothing.

Correcting the record in that moment would have looked petty, territorial, and insecure, so I swallowed it, and I told myself it didn’t matter.

But it did matter, and pretending it didn’t is exactly how quiet leaders make themselves disappear.

Let me be precise about what happened, because the precision is where the lesson lives.

The person who said it second did not steal my idea. I’ve thought about this for years, and I’m confident it wasn’t theft. He may have arrived at the same conclusion independently, or he may have absorbed my earlier comment without consciously registering where it came from. He may have heard it, agreed with it, and simply restated it with more conviction than I had.

His actions didn’t require malice, which is what makes them so common and so corrosive across organizations.

Unintentional idea theft is so common because ideas do not carry their origin with them. Once a thought leaves your mouth, it becomes untethered from you. It travels through the room, gets picked up, reshaped, and re-expressed, and it attaches itself to whoever says it at the moment the room is ready to hear it.

I call this acoustic attribution: credit flows not to whoever had the idea first, but to whoever said it at the frequency and the moment the room could finally receive it.

Acoustic attribution is the reason you can be right, early, and completely uncredited all at once. I have been all three more times than I can count.

Here is the part that took me years to admit, and it’s the part that turns this from a complaint into something useful.

I contributed to my own erasure.

When I raised the idea the first time, I raised it the way quiet leaders often do. Once. Softly. Without taking responsibility for how it landed. I said my piece, watched it get a polite nod, and let the conversation move on. I didn’t want to force it, so I treated having said it as the same thing as having communicated it.

They are not the same thing.

Saying something into a room that doesn’t receive it is not communication. It’s whispering into the void. The idea lingered in the air for a moment, then dissipated because I did nothing to anchor it. No follow-up document, no conversation with the people who would be in the larger meeting, and no written summary that permanently put my name next to the idea.

I had done the hard part. I had the insight. But I skipped the part that would have protected it because it felt like self-promotion, and self-promotion felt like a betrayal of the values that made me who I am.

That’s the trap. The quiet leader’s “integrity” becomes the mechanism of their own invisibility.

I want to sit with the anger for a moment before I move to the fix, because the anger is honest.

It is genuinely unfair. You do the thinking. You do it first, and often you do it better, but then you watch the recognition flow to someone who is louder, faster to speak, and more comfortable taking up space. Over a career, that pattern compounds. The louder person’s reputation grows on the strength of ideas they articulated but didn’t originate, while your reputation stays flat despite a history of great ideas.

This gap grows silently, one unattributed idea at a time, until one day you look up and someone with half your judgment is two levels above you. That is worth being angry about. I was, for years. And the anger was not a character flaw. It was an appropriate reaction to a real dynamic.

But the anger can’t change the dynamic. The dynamic exists whether I rage or not, and the system is not going to become fair because I resent its unfairness.

So the anger, however justified, is only useful as fuel. What it fuels has to be something productive.

What quiet rage needs to fuel is a different way of working. Not a louder way, but an earlier, more deliberate one.

The idea in your head is vulnerable. The idea you said once in a room that wasn’t ready is barely less vulnerable. But the idea you documented, shared with two or three trusted people before the meeting, and put in writing with your name attached is structurally protected.

I learned this too late in the meeting rooms of my career, but I learned it thoroughly. Every patent I hold, and there are fourteen, was collaborative and documented from the beginning. Nobody ever fought me for credit on those because the structure made attribution unambiguous. The co-inventors were named, the contributions were recorded, and the idea was anchored to its origins before anyone had the chance to unconsciously reattribute it.

That is the entire lesson. Not “speak louder” or “fight for credit in the moment,” which never works and always looks petty. The lesson is to anchor the idea to yourself before you release it into a room, because once it’s in the room, it belongs to whoever says it at the right time.

Share it early, in writing, with people you trust. Put your name next to the thought while it’s still yours. Then let it travel. It will still get reshaped and re-expressed, but there will be a record, and the record is what protects you when the acoustic attribution kicks in.

I don’t want to pretend this fully solves it. It doesn’t.

Even with documentation, even with early sharing, sometimes the louder voice will still capture the visible credit. The record will show you were there, but the room will remember who spoke with conviction. That gap between the record and the memory is one quiet leaders have to make a kind of peace with.

But there is a difference, an important one, between a gap you can point to and an erasure you cannot. When you’ve documented your thinking, the credit gap becomes visible enough to address. You can reference the earlier document in a follow-up, or a trusted colleague can note that you raised the idea first. The truth has a foothold. It may not win the room’s memory every time, but it exists, and its existence increases the chances that it does.

What I experienced in that meeting was what happens when there is no record: Total erasure. Nothing to point to or lean on. Just my idea, winning without me, and my own silence sealing the outcome.

I can’t get that moment back. But I got the opportunity to make sure it never happened again, and now, so do you.

The question I’d leave with you:

The last time one of your ideas won a room without you, did you have anything to point to? A document, a message, a record that showed the thought was yours before it became someone else’s?

If you didn’t, the loss wasn’t really in the meeting. It was in the week before, when you had the insight and let it slip away because claiming it felt like bragging.

It isn’t bragging to make sure the truth has a place to stand.

And your ideas deserve at least that much from you, even when the room gives them nothing at all.

But I never said any of this out loud.

The new CEO brought in a friend to be the VP of Engineering. This was a perfectly reasonable decision from his perspective; he was new, he needed people he trusted, and nobody had told him that someone on the existing team wanted the role and was already doing most of the work.

I didn’t tell him because I assumed it was obvious. I assumed the situation spoke for itself.

It didn’t.

When the new VP arrived, I prompted a meeting and asked where he saw the company and the team headed. He wasn’t certain, so I shared what I knew about the technical landscape, the team dynamics, and the priorities as I understood them. He listened with genuine interest.

Near the end of the conversation, he asked the standard question: “So where do you want to be in the next few years?”

I pointed at his chair.

I told him, directly and without softening it, that I had expected to be leading this team. It was one of my more direct moments, and I don’t necessarily recommend the delivery, but what it accomplished was immediate and important: from that moment forward, he knew I was ambitious. He knew I wasn’t content to simply execute, and that the quiet, steady person who had been holding the team together had aspirations that extended beyond what my demeanor communicated.

The irony is that I then spent the next several months trying to make him successful. I gave him everything I knew about the team and the right approach going forward. He listened and he tried, but his interests pulled him toward building rather than leading. Within weeks, he had dived into a technical problem, writing an entire Perl library to pull reporting data and present it to the CEO, while I continued managing the people on the team by default. He was a good person, probably a quiet leader himself, but he fell into the trap of doing far more building than leading.

He left in less than a year.

The lesson I carried from that experience was not about the outcome. It was about the silence that preceded it. I had ambition, capability, and a legitimate case for the role, but by the time I made them visible, the decision had already been made.

This pattern has repeated throughout my career in different forms, and I suspect it has repeated throughout yours.

Quiet leaders deliver. We stabilize teams. We solve problems without creating new ones. We are the people that managers never have to worry about, which, as I’ve written before, means we are also the people that managers never think about.

And because we don’t broadcast our ambitions, organizations fill in the blank with an assumption: “this person must be satisfied with where they are.”

It is a reasonable assumption. If someone never signals that they want a different role and never makes their aspirations known in the conversations where career decisions are shaped, the default conclusion is that they don’t have aspirations. Or that their aspirations are modest. Or that they’re content to keep doing what they’re doing.

There’s that phrase again. “Keep doing what you’re doing.” The organizational equivalent of “we’ve stopped wondering what you want.”

I want to name why this happens, because understanding the mechanism matters more than resenting the outcome.

Organizations track ambition through signals. Explicit signals, like saying:

“I want to be considered for that role.”

“I’d like to lead that initiative.”

“Where do I stand for the next promotion cycle?”

These are the signals that loud leaders send naturally. They advocate for themselves the same way they advocate for their ideas: directly, vocally, and early enough to influence the outcome.

Quiet leaders often don’t send these direct signals. They often believe they are sending signals, even though the organization is not receiving any.

They think they are sending signals when they take on additional responsibility without being asked. They believe they are signaling ambition, but the organization just sees reliability.

Or they think they are signaling readiness for leadership by mentoring others and building team capabilities, but the organization just sees a strong team player.

More than anything, the quiet leader thinks they are sending signals about their ambition when they deliver consistently quarter after quarter. They believe they are signaling readiness for more, but the organization sees someone who is well-suited to their current role.

In each case, the quiet leader’s behavior is genuinely admirable, but ultimately unhelpful to driving their career. Behavior does not communicate ambition; behavior communicates competence. Ambition requires words.

The gap between actions and explicitly stated intentions is one that quiet leaders often leave open because it feels like self-promotion. For people whose entire leadership identity is built on substance over performance, self-promotion feels like a betrayal of their values.

I’ve felt this resistance myself. At Amazon, I spent years building teams, shipping products, earning patents, and delivering results that I believed would speak for themselves. And they did speak. They said: “David is reliable, technically excellent, and runs a strong organization.”

They did not say: “David wants to lead a larger organization.” Or: “David has ideas about where this part of the business should go.” Or: “David should be in the conversation when we discuss who leads the next major initiative.”

And I didn’t say those things clearly enough.

The feedback I received more than once across my career was some version of “we need to see more leadership presence” or “you need to be more visible in cross-functional settings.” What those phrases actually meant, decoded from corporate language into plain English, was: “We don’t know what you want because you haven’t told us, and we’ve stopped trying to guess.”

This feedback was completely accurate.

At Warner Bros. Discovery, I watched this dynamic play out with leaders I coached. Talented, thoughtful people who were doing exceptional work and receiving average reviews. People whose managers genuinely liked them and genuinely had no idea they were frustrated, ambitious, or considering leaving.

The conversations I had with these leaders often followed a predictable pattern:

“Does your manager know you want that role/project/responsibility?”

“They should. I’ve been performing at that level for over a year.”

“But have you told them?”

Silence.

Over and over again, their performance was visible and their ambition was invisible. And in every case, the manager had just filled the gap with the most convenient assumption: this person is satisfied.

Not maliciously or carelessly, just humanly. Managers have limited attention, and they spend most of it on the people who are creating problems or making demands. The quiet leader who creates no problems and makes no demands becomes the person whose career gets the least deliberate investment. And then they suffer the consequence: stagnation.

There is a deeper cost to this pattern that goes beyond missed promotions and modest raises.

When an organization consistently fails to ask what you want, and you consistently fail to tell them, something shifts in how you see yourself. You start to wonder whether your ambitions are legitimate. You start to question whether wanting more is compatible with leading quietly. You internalize the assumption that was made about you and begin to believe it might be true: maybe you are satisfied. Maybe this is enough. Maybe the fact that you aren’t fighting for more means you don’t want it badly enough.

That internal narrative is corrosive. It takes a legitimate structural problem, the organization’s failure to see your ambition, and converts it into a personal doubt: “Maybe I’m not ambitious enough.”

You are. You just haven’t made it visible.

And I want to be direct about this: making your ambition visible is not self-promotion. The same way you would advocate for a team member whose contributions were being overlooked, you need to advocate for yourself. Not loudly or performatively, but clearly, specifically, and in settings where the information can actually influence decisions. This is good career stewardship.

The practice is not complicated. It is uncomfortable, which is different. Here is how you can break it down step by step.

Tell your manager what you want. Not in vague terms like “I’d like to grow”, but in specific ones (”I want to be considered for a director role within the next year. What would need to be true for that to happen?”). Ask for criteria, not affirmation.

Tell them early. Don’t wait for the performance review cycle. By the time formal reviews happen, the decisions about promotion slates and role assignments have already been influenced by months of informal conversations. If your name wasn’t in those conversations because nobody knew you were interested, the review is too late.

Tell more than one person. Your manager is the most obvious audience, but they are not the only one who needs to know about your goals. Peers, skip-level leaders, mentors, and the partners you trust all play a role in how the organization perceives your trajectory. When multiple people know what you want, the information travels through the informal channels where career decisions actually get shaped.

For the managers reading this: ask. Don’t assume that your steady, reliable, high-performing, quiet leader is satisfied. They may be the most ambitious person on your team and the least likely to tell you about their goals. The question “what do you want next?” costs you nothing and might be the most important question you ask all year.

I think about the Lightningcast moment often. Not because of the outcome, but because of how long I waited to say something that should have been said immediately.

When the previous leader left and I was already doing the job, one clear conversation with the incoming CEO could have changed everything.

“I’ve been leading this team. I want to continue leading it. Here’s what I’ve built and here’s where I think we should go.”

Three sentences. Thirty seconds. Instead, I waited, assumed, and watched the opportunity go to someone who was simply more visible to the decision-maker.

The new VP wasn’t more capable than me, and he wasn’t more ambitious. He was just more known to the CEO. He was the more obvious choice. And in organizations, being known is often more important than being qualified.

Organizations aren’t perfect systems; they are human systems. In a human system, the people making decisions can only consider the information they have. If your ambition is information they don’t have, it cannot factor into their decisions.

The question I’d leave with you:

Does the person who most influences your career trajectory know what you actually want?

Not what you’re willing to accept or what you’d be fine with—what you want.

If the answer is no, that is not their failure. It is an action you haven’t taken yet.

Only you can make your ambition visible.

James Madison did not command a room. He didn’t have the physical presence of Washington, the rhetorical fire of Hamilton, or the philosophical grandeur of Jefferson. He was short, slight, soft-spoken, and by most accounts, a genuinely poor public speaker.

He was also the most consequential architect of American history.

Not an architect of buildings, but of systems. The Constitution, the Bill of Rights, the Federalist Papers, and the structure of the presidency itself all carry Madison’s fingerprints, but most Americans couldn’t tell you what he did (beyond being the fourth president).

Most Americans know much more about Washington, Hamilton, and Jefferson. That gap between contribution and recognition should feel familiar to every quiet leader reading this.

Madison’s path to the Constitutional Convention was not the one that gets dramatized. There was no stirring speech, no dramatic gesture, and no moment of visible heroism, but there was a mountain of preparation.

While other delegates were still debating whether to attend the Convention at all, Madison was doing the pre-meeting work. He had spent months studying every confederacy and republic in history: the Amphictyonic League, the Achaean League, the Swiss cantons, the Dutch republic, and more. Then, he cataloged the structural failures of the Articles of Confederation with the precision of an engineer performing a postmortem. He had mapped the weaknesses, identified the patterns, and arrived in Philadelphia with a framework already drafted.

His framework was called the Virginia Plan, and it became the foundation of every serious constitutional discussion that followed.

This is what quiet leaders do. They don’t arrive at the meeting to discover what the conversation will be about; they arrive having already shaped it. Madison didn’t need to dominate the room in Philadelphia because he had done the work that made the room’s best thinking possible. That was how he left his impact on this country.

But the loud voices at the Convention are the ones history remembers. Gouverneur Morris is remembered for speaking more than anyone. Hamilton gave a famous six-hour speech advocating for a system that was rejected almost entirely. Luther Martin talked so long that other delegates left the room.

Madison spoke comparatively little, but his ideas were so precisely constructed that they consistently redirected the conversation and ultimately influenced the final outcomes of the Convention that shaped our nation. He didn’t compete for airtime; he chose his moments deliberately, and each intervention shifted what happened next.

He made his mark not through force or volume, but through judgment applied at exactly the right moment.

Madison’s impact showed up not in how much space he took, but in how deliberately he used it.

He listened more than he debated, and while others were performing their positions for the room, Madison was taking detailed notes on every argument, every objection, and every shift in the Convention’s thinking. Those notes became the primary historical record of what happened there.

Leading up to the Convention, the Virginia Plan involved months of solitary intellectual work on Madison’s part, but it became the framework for the entire discussion. Without it, the delegates may have spent weeks arguing about process before they ever reached substance.

Another one of Madison’s quiet leader attributes is that he built coalitions through private conversation rather than public persuasion. He understood that the room’s decisions were actually shaped in the margins, not at the podium. This is the pre-meeting influence that quiet leaders are uniquely equipped to exercise because of our intense preparation: sharing our thinking with the right people, in the right setting, before the formal discussion begins.

Madison also let others carry the visible credit. The Constitution is not called “Madison’s Constitution” in popular culture, even though scholars consistently credit him as its primary architect. Washington presided over the Convention, Franklin provided the elder statesman’s blessing, and Hamilton championed ratification with the most visible public advocacy. But Madison did the structural work that made all of this possible, and he is the least remembered of all.

Despite Madison’s clear impact, I don’t mean to imply that he achieved all of this alone. The partnership between Madison and Hamilton during the ratification debate is perhaps the clearest historical example of the quiet side / loud side dynamic that I have talked about being so helpful in previous writing.

Together with John Jay, they wrote the Federalist Papers: 85 essays arguing for ratification of the Constitution. Hamilton wrote 51 of them. Madison wrote 29. Jay, slowed by illness, wrote 5.

Hamilton’s essays were passionate, forceful, and politically charged. They made the emotional case for a strong federal government with the kind of rhetorical energy that moved public opinion.

Madison’s essays were structural. Federalist No. 10, his argument about factions and the design of a republic large enough to contain them, is widely considered the single most important piece of political writing in American history. It didn’t persuade through passion; it persuaded through architectural reasoning so thorough that the counterarguments simply couldn’t find purchase.

Hamilton got more essays published, but Madison wrote the ones that made ratification a done deal.

This is the pattern every quiet leader will recognize. The loud partner produces volume while the quiet partner produces the thing that lasts. Both are necessary, but the world tends to remember the volume first and sometimes forgets the foundation entirely.

The evidence is here in pop culture: Hamilton now has a Broadway musical while Madison has a university in Virginia that most people don’t even associate with him. The asymmetry would be funny if it weren’t so precisely representative of how credit flows.

Though I am celebrating him now, Madison paid real costs for his quiet approach.

In an environment that rewarded oratory, his inability to project in a large room limited his direct political influence. He was not a campaigner, and he could not move a crowd the way Patrick Henry or Hamilton could. And though he became president, his presidency is generally considered unremarkable by historians, in part because the skills that made him the greatest political architect of his generation did not translate into the performative demands of the executive role.

This is the cost quiet leaders often bear: the skills that produce the most durable contributions are not the skills that produce the most visible careers. Madison’s framework has outlasted every speech Hamilton ever gave, but Hamilton’s career trajectory was faster, more dramatic, and more celebrated during their lifetimes.

The quiet leader’s bargain is accepting that the arc of impact and the arc of recognition operate on different timelines. Sometimes those timelines converge, but often they don’t. Madison lived long enough to see the Constitution endure, but he did not live in an era that would have called him its architect. That label came later, assigned by historians with the distance to see what contemporaries, dazzled by louder voices, could not.

I think about Madison when I watch quiet leaders struggle with the same tension he embodied.

The leader who builds the system and then watches the person who presents the results receive the recognition. Or the leader who does the pre-meeting work that shapes the decision and watches the loudest voice in the room get credited. Or the leader who writes the document that reframes the problem, only to watch someone else summarize it and own the conclusion.

These are not failures of the quiet leader’s approach. They are the structural cost of operating in systems that attribute ideas to whoever expressed them most visibly. Madison’s experience proves that this cost is not new. It is as old as organized human endeavor.

But Madison’s legacy also proves something else: the framework outlasts the speech. The system outlasts the personality. The architecture outlasts the applause.

Every speech Hamilton gave is a historical artifact, but the Constitution is a living document. That is not a coincidence. It is the difference between what performance produces and what intentional architecture produces. The former produces a moment, while the latter produces much more.

If Madison were operating in a modern business, he would be the person who arrives at the offsite having already mapped the strategic landscape. He would be the one who writes the document that reframes the quarterly debate before anyone else has articulated the question. He would build the systems, the processes, and the frameworks that everyone else operates on without thinking about who built them.

He would also be the one whose name doesn’t come up in succession conversations, all because the people making those decisions never saw his capability performed in a way they could easily recognize.

The question Madison’s story raises for quiet leaders is not whether your approach is effective. The historical record answers that definitively. The question is whether you can sustain the patience required to let your work prove itself, even when the room is applauding someone else.

That patience is not passive. It is the most active form of restraint there is: continuing to build the thing that matters while knowing the recognition may arrive late, arrive attributed to someone else, or never arrive at all.

Madison’s story matters for quiet leaders because it offers the rarest thing in the leadership conversation: proof at scale.

Most leadership philosophy operates on anecdotes—a story about a meeting, a team, a company. Madison’s story offers proof at the scale of a nation. The quietest person at the Constitutional Convention built the most durable political framework in modern history. His preparation outperformed every speech, his architecture outlasted every personality, and his influence, exercised through private conversation and structural thinking rather than public persuasion, shaped a document that has governed hundreds of millions of people across nearly two and a half centuries.

If quiet leadership can produce that, the question of whether it “works” is settled.

The remaining question, and it is one Madison himself could not have answered, is whether you will be recognized for what you build. History suggests that you may not be, but history also suggests that what you build will still be standing long after recognition ceases to matter.

Further Exploration

If this Quiet Icon resonated with you, here are places to explore Madison’s life, work, and leadership more deeply:

• James Madison: A Life Reconsidered by Lynne Cheney: a biography that foregrounds Madison’s intellectual architecture rather than his political career

• The Federalist Papers, particularly No. 10 and No. 51: Madison’s structural arguments in his own words

• Plain, Honest Men by Richard Beeman: the story of the Constitutional Convention with attention to how the quieter delegates shaped the outcome

What I was not prepared for was the thing nobody told me.

My predecessor had been a loud American leader. “Caustic” was the word I eventually heard, though it was months before anyone used it. His approach had generated such deep mistrust of American leadership that by the time I arrived, the entire team had already decided who I was before I opened my mouth.

They assumed I would be the same. They assumed I was there to “get things moving” in the way he had, which apparently involved temper tantrums, unilateral decisions, and a general disregard for the expertise that the European teams had built over the years.

But nobody told me any of this when I first walked in. Not my peers, not my direct reports, and not the people I was meeting for the first time. They were polite, professional, and guarded in a way I initially mistook for that classic British reserve.

But this wasn’t reserve. It was self-protection. They had learned the hard way that trusting the American leader was dangerous… and they applied that lesson to me before they had a reason. Our working relationship was based on a defense mechanism.

As a result, I spent months operating inside an information gap I didn’t know existed. I thought I was quietly building relationships while they were keeping me at arm’s length—managing the “risk” of having me around.

This information gap can be a trap for quiet leaders, and it works in both directions.

Your team knows things about you, about the organization, and about how your leadership is landing that you cannot see from where you sit. They know which of your messages are landing clearly and which are being misinterpreted. They know which of your decisions have built trust and which ones have quietly eroded it. They know what the team says about you when you’re not in the room.

And most of them will never tell you unless you create the conditions for that honesty to surface.

This is not unique to quiet leaders, but quiet leaders are particularly vulnerable to it because the same energy that makes you trustworthy over time—your steadiness, your consistency, and your lack of reactivity—can also make you harder to read. When your team can’t easily tell what you’re thinking or how you’ll respond to difficult information, they default to caution. They hold back the things they think might land poorly, and they wait to see how you handle small pieces of the truth before they risk sharing larger ones.

The result is a leader who believes they have a clear picture of what is going on and a team that knows that picture is incomplete.

It took me a long time to learn this.

I have stood in front of teams believing they understood what I was doing and why. I thought I was being clear, and I thought my actions were communicating my intent. I thought that because I knew the reasoning behind a decision, the team must also see it.

They didn’t. Not because they weren’t paying attention, but because I wasn’t explaining myself with the clarity they deserved.

Quiet leaders often assume that their behavior speaks for itself. We believe that consistent action over time communicates our values, our priorities, and our intentions. And to some degree, it does. But behavior is ambiguous in a way that words are not. The same action, viewed from different perspectives, can communicate very different things.

A quiet leader who absorbs a difficult meeting without visible reaction might be seen as steady by one person and disengaged by another. A quiet leader who lets a team debate without intervening might be seen as trusting by one person and indifferent by another. The behavior is the same, but the interpretation depends on information the observer may not have.

That gap between your intent and the team’s interpretation is the information you’re missing, and that gap grows silently until something forces the information out into the open.

In London, the forcing function was time. Over months of consistently showing up differently than my predecessor, the team’s assumptions gradually loosened, and they started sharing things they had been holding back. Small things at first: context about why a process worked the way it did, history about decisions that predated my arrival, honest reactions to directives from our American offices.

However, as trust built, the information they shared became more substantive. Peers started telling me what my leadership style looked like from the outside, direct reports started sharing how the team was actually experiencing my decisions, and I started to receive honest feedback. Not all of which was glowing.

While I had earned their trust, they wanted more from me. Specifically, they wanted me to push back more forcefully against unilateral decisions made by our American offices. These were decisions that were often made without understanding the European context, the regulatory landscape, or the operational realities on the ground, and the team needed someone who would represent them upward, not just manage them downward.

That feedback changed how I operated for the next few years. I started to question uninformed decisions from above and enabled our European teams to have a genuine voice, while still driving toward the business objectives we were accountable for. But I was only able to make that adjustment because people finally trusted me enough to tell me what they needed.

Had I relied on my own assessment of how things were going, I would have continued believing I was doing well enough. The team would have continued performing, but the gap between what they needed and what I was providing would have persisted, invisible to me and corrosive to them.

The lesson I took from London, and the one I now coach other leaders on, is this: you cannot wait for trust to develop organically and then hope the information will flow. That works eventually, but “eventually” can take months or years, and in that time, you are leading with an incomplete picture.

Instead, you have to prompt the information. Actively, directly, and repeatedly.

This feels unnatural for quiet leaders. We prefer to create the conditions for openness and then let people come to us on their own terms. That instinct is not wrong, but it is insufficient. The people who most need to tell you something difficult are the ones who are least likely to volunteer it. They need an invitation, and sometimes they need the invitation more than once.

Some leaders I’ve coached have written what amounts to an operator’s manual for themselves: a document they share with new teams that explains how they work, what they value, how they prefer to receive information, and what they need from the people around them. I’ve never done this formally, but I understand the impulse. It’s an attempt to proactively close the information gap by telling the team who you are rather than waiting for them to figure it out.

What I have done, and what I wish I had done sooner in London, is introduce myself more deliberately. Not once, but multiple times. The first introduction is noise—people are too busy forming their own impressions to absorb what you say. The second and third introductions, delivered in smaller settings over the first few weeks, are where the real message lands.

Beyond introductions, the ongoing practice of prompting information is straightforward, but it requires discipline.

Ask your direct reports, in one-on-ones, how your leadership is being experienced. Not “how am I doing?” which invites empty affirmations. Instead: “What am I not seeing about how the team is operating right now?” or “Is there something the team needs from me that I’m not providing?” or “How did that decision I made last week actually land with people?”

These questions feel vulnerable because they are. That’s the point. You are signaling that you want the real answer, not the comfortable one, and you are creating a pattern where honest feedback becomes expected rather than exceptional.

There is a dimension to this that connects to the Leadership Energy Archetypes I’ve been developing.

The Anchor’s shadow is passivity. Anchors create stability, which teams value deeply, but stability can become stagnation when the Anchor isn’t actively seeking information about what the team needs to change. The team feels safe but unchallenged. They trust you but don’t tell you the hard things because the environment you’ve created is so steady that disrupting it feels wrong.

The Observer’s shadow is detachment. Observers read rooms brilliantly, but they can mistake their own observations for complete information. The Observer sees the dynamics, reads the unspoken tensions, and forms a sophisticated internal picture. But that picture is still just their interpretation. Without checking it against the team’s actual experience, the Observer operates on a model of reality that may be elegant but incomplete.

Both of these shadows create the same outcome: a leader who believes they understand the situation and a team that knows the leader is missing something important.

The fix for both is the same: ask, and make it safe to answer honestly.

I want to address something that quiet leaders sometimes resist about this practice.

The resistance goes something like: “If I have to ask for feedback, it means the environment I’ve built isn’t open enough for people to offer it freely.”

I understand that concern. It feels like asking for feedback is an admission that your culture of openness has failed.

It isn’t. It is a recognition that even the healthiest teams have information asymmetries, and your position as the leader inherently limits what people will tell you. This isn’t because they don’t trust you, but because the power dynamic makes certain kinds of honesty feel risky regardless of how safe you’ve made the environment.

Asking for feedback doesn’t mean your culture failed. Asking means you understand how organizations actually work, and you’re compensating for a structural limitation.

The leaders I’ve admired most over thirty years were not the ones who built cultures so open that feedback flowed freely without prompting. Those cultures don’t exist. The leaders I admired were the ones who asked for feedback consistently, received the answers without defensiveness, and visibly acted on what they heard enough to show that their interest in getting feedback was genuine.

That cycle- ask, receive, act, and repeat- is what closes the information gap over time.

The question I’d leave with you:

What does your team know right now, about you, about the organization, about how your leadership is landing, that they haven’t told you?

The information is there. It’s been there. The only thing between you and that information is a question you haven’t asked yet.

And for the quiet leader who prides themselves on reading the room: the room is also reading you. The question is whether you’ve given them enough to read accurately, or whether they’re filling in the gaps with assumptions you aren’t addressing.

It is the moment, usually days before the meeting happens, when the decision starts to take shape in conversations you weren’t part of.

At Amazon, at Warner Bros. Discovery, and at every large organization I’ve worked in, the pattern was the same. By the time a decision-making meeting begins, the key players have already been briefed. The people who are going to influence the outcome have already had their conversations, positions have been staked, alliances have been formed, and the frame through which the room will evaluate the decision has already been set.

The decision-makers do not walk into the meeting cold. There is always a level of understanding, a set of prior conversations, and a direction that has momentum before anyone sits down.

This is not necessarily malicious. It is simply how organizations operate at scale. People prepare, socialize their ideas, and test their arguments with people who matter. They build support before the room convenes.

This can be the downfall of the quiet leader.

The quiet leader walks into that meeting with good data and a sound position, expecting the discussion to be decided on the merits of the arguments presented in the room.

That is almost never how it works. The room decided before you spoke. The question is whether you were part of that process or arrived too late to shape it.

What I am describing may sound cynical, but it isn’t.

Pre-meeting influence is not manipulation; it is preparation. It is the recognition that important decisions are too complex to be resolved in a single meeting, and that the people making those decisions need time to understand the data, consider the trade-offs, and form their thinking before they’re asked to commit.

The loud leaders in your organization understand this intuitively. They are having hallway conversations, sending pre-reads with their framing baked in, and scheduling brief one-on-ones with decision-makers before the meeting happens. They are not doing this because they are scheming. They are doing it because they understand that influence is a process, not an event.

Quiet leaders tend to treat the meeting as the moment of influence. They prepare their data, refine their arguments, and arrive ready to make their case. And then they discover that the room’s energy is already moving in a direction that was established before they walked in.

The frustration of having the right answer and watching the room choose a different path is one that every quiet leader I’ve coached has experienced. What they often don’t realize is that the failure didn’t happen in the meeting—it happened in the days before, when the conversations shaping the outcome took place without them.

Early in my career at Amazon, I learned this lesson the hard way.

I was in a cross-functional meeting about a launch decision. I had spent days with the data, understood the trade-offs better than anyone else in the room, and was confident that the direction the group was heading would create problems downstream.

But by the time I was ready to make my case, the conversation had already coalesced around a different approach. The loud voices had established the frame early, and the energy of the room was moving with conviction.

I waited for the right moment to introduce my perspective, but that moment never came.

The decision was made, and no one in the room even knew I disagreed. A peer pulled me aside afterward and said, “If you had something, you needed to say it in there.”

He was right about speaking up in the meeting, but I’ve come to understand that the real failure happened before the meeting started. The people who shaped the outcome had done their work in advance. They had briefed the decision-makers and socialized their position, and by the time the room convened, their direction already had momentum.

I had the better argument. They had the better process.

I wish I could tell you I learned the lesson completely that day. I didn’t.

Years later, still at Amazon, I wrote what I believed was a well-argued, data-driven document recommending that the Alexa team replicate the entitlement and purchase systems that our Appstore team had built over the previous three years. The technical case was clear: Alexa could clone our code, build it themselves, and operate independently. Independent operation was a core best practice at Amazon, and tightly coupling two organizations was, in my experience, a recipe for slowdowns, dependencies, and friction that would hurt both teams.

The document was thorough, the data was sound, and the recommendation was technically correct.

But by the time my document made the rounds, the team had already decided to do something entirely different.

What I didn’t know, because I hadn’t done the pre-meeting work, was that there had been extensive discussions within the Appstore organization about positioning our systems as a platform that Alexa would use. This would tightly couple the two organizations, which was exactly what I was arguing against. But for the Appstore, it also meant something I hadn’t accounted for: the new funding that was flowing toward Alexa would now flow through Appstore’s systems. The organizational incentive to couple was enormous.

When I presented my clear, well-articulated, technically correct document, the discussion that followed surprised me. The decision had been effectively made before I walked in, shaped by conversations about funding, organizational strategy, and political positioning that had nothing to do with the technical merits I had so carefully documented.

The first time, at that launch meeting, I failed by not speaking and not socializing my idea. This time, I spoke clearly, with data, in a well-structured document, and I still lost. This was because I didn’t account for the organizational forces that had already shaped the decision.

I disagreed, and I committed. I made Alexa successful in the alternate approach because that is what the decision required. But the lesson stayed with me: pre-meeting influence is not just about getting your data in front of people. It is about understanding what forces are already in motion. The technically correct answer and the organizationally viable answer are not always the same thing, and the quiet leader who prepares only for the technical argument is only doing half the work.

The tricky part, and the part that quiet leaders need to invest in understanding, is mapping the room before you’re in it.

Every important meeting has a structure that isn’t on the agenda. There are the people who will make the decision, the people who will influence those decision-makers, and the people who have no real bearing on the outcome.

Knowing who is who changes everything about how you prepare.

If you can identify the two or three people who will most influence the outcome, and have a conversation with them before the meeting, you can shape the frame through which the decision will be evaluated. You don’t need to lobby or manipulate, but you do need to share your data, explain your reasoning, and help them understand why your position matters.

This is influence, and it is where quiet leaders can be remarkably effective if they understand that the work happens before the meeting convenes.

A quiet leader who has a thoughtful, data-rich one-on-one conversation with a key decision-maker two days before the meeting has more influence than a loud leader who makes a passionate case in the meeting itself. By the time the meeting starts, the decision-maker has already absorbed the quiet leader’s perspective. It is already part of their thinking, so it doesn’t need to be said loudly in the room.

This is the quiet leader’s advantage, deployed correctly. You don’t need to dominate the room; you need to have done the work that influences the decision before the meeting starts.

There is a practical discipline to this that I want to make concrete, because abstract advice about “influencing stakeholders” is not useful.

Before any meeting where a decision will be made, ask yourself three questions.

First: who will make the decision? Not who is in the room, but who actually decides. In many organizations, the person who decides is not the most senior person present. It is the person whose opinion the most senior person trusts. Identifying that person is the first step.

Second: what frame will the decision be evaluated through? Every decision has a lens. Is this a cost decision? A risk decision? A speed decision? A customer impact decision? The person who sets the frame often determines the outcome, because once the room agrees on what matters most, the “right” answer becomes obvious. If you can shape the frame before the meeting, you can shape the decision.

Third: who will advocate for your position if you are not the loudest voice in the room? This connects directly to the partnership dynamic I’ve written about before. Quiet leaders need champions. Not because their ideas are weaker, but because the mechanism of organizational decision-making often rewards volume. If you can brief a trusted colleague who carries more vocal energy, someone who understands your data and will represent it with conviction, you’ve extended your influence beyond what your own voice can reach.

These three questions take fifteen minutes to think through before each important meeting. That investment is worth more than any amount of preparation on the content itself, because content without positioning is invisible in a room where the positions have already been set.

I want to name something that I think quiet leaders resist hearing, because it challenges a belief that feels core to their identity.

The belief is this: “The best idea should win on its merits. If I have to play politics to get my idea heard, then the system is broken.”

I understand that belief. I held it for years, and there is truth in it. Organizations should be better at evaluating ideas on their substance rather than the volume at which they’re presented.

But holding that belief while the room decides without you is only holding you back.

Pre-meeting influence is not politics. It is communication, and it is making sure the people who need to understand your perspective have the opportunity to do so before they’re in a room with fifteen other voices competing for attention. That is not a corruption of the process. It is respect for the complexity of the decision and the limitations of the meeting format.

A sixty-minute meeting with twelve people in the room gives each person an average of five minutes of speaking time. In practice, three or four people will use most of that time, and the quiet leader will use very little of it. If you are relying on those few minutes to convey a complex, data-driven perspective that challenges the room’s existing momentum, you are setting yourself up for exactly the experience I had at Amazon: watching the wrong decision get made while holding the right answer.

The meeting is not where influence happens. The meeting is where influence is confirmed. The actual work of influence happens in the conversations before and after, in the documents shared in advance, and in the relationships built over time that give your perspective weight before you ever open your mouth.

I’ve used this approach many times at Amazon, Warner Bros. Discovery, and at smaller companies where the dynamics were less complex but equally real. The principle scales in both directions.

At Amazon, the six-page document culture created a natural pre-meeting influence mechanism. The document was shared before the meeting, and the first twenty minutes were spent reading in silence. This structure inherently favored thoughtful, well-prepared contributors over those who relied on verbal dominance. The quiet leader who wrote a clear, well-structured document had already shaped the room’s thinking before anyone spoke a word.

Not every organization gives you that structure, but you can create your own version of it. A pre-read shared two days before the meeting, a brief one-on-one with the key decision-maker, or a clear email that frames the trade-offs and your recommendation are all ways of placing your thinking into the room before the meeting begins.

There is one more dimension to this that I want to address, because it connects to a pattern I see repeatedly in the leaders I coach.

Quiet leaders often wait to speak in meetings because they are still processing. The loud voices move fast, stating positions with confidence before the quiet leader has fully evaluated the options. By the time the quiet leader is ready to contribute, the conversation has moved past the point where their input would redirect the discussion.

This is not a flaw in how quiet leaders think. It is a mismatch between how they process and how meetings are structured. Meetings reward speed of response, and quiet leaders favor depth of analysis. These two timelines rarely align.

Pre-meeting influence solves this problem entirely. If you’ve already shared your analysis before the meeting, your thinking is in the room even when your voice is not. The decision-makers have already absorbed your perspective at their own pace, in a format that allows for the depth you naturally bring. The meeting becomes a confirmation of work already done, not a race to be heard.

This reframe is essential: the meeting is not your moment of influence. Instead, it is the culmination of influence that happened elsewhere.

The question I’d leave with you:

Think about your last important meeting that resulted in a decision you disagreed with.

Did you share your perspective with the key decision-makers before that meeting? Did you help them understand your data and your reasoning in a setting where they had time to absorb it?

Or did you arrive with the right answer and hope the room would find its way to you?

If it was the second, the room didn’t fail you. Your process did. Luckily, your process is something you can change.

Every time, it sounded like praise. Every time, I left the conversation feeling like I was on track. And every time, when my review came back average, or my promotion didn’t happen, or my raise was modest, I was confused. I was doing what they told me to do. I had kept doing what I was doing.

It took me years to understand what was actually happening in those conversations, and what “Keep doing what you’re doing” actually means.

“Keep doing what you’re doing” is not feedback. It is the absence of feedback, wrapped in words that feel complimentary. For quiet leaders who are unlikely to push back and ask “what does that actually mean?”, it is one of the most damaging phrases a manager can deliver.

It tells you nothing about where you stand, nothing about what’s working at a level that matters, and nothing about what gaps exist between where you are and where you need to be. It is a closed door hidden behind a smiling face.

And it should feel like poison on a manager’s lips!

Before I continue, I do want to be honest about this failed feedback from both sides, because I’ve been on both.

As a manager, I caught myself saying it once to one of my direct reports. The words came out before I could stop them, and I heard them linger in the air between us. This person was doing excellent work. They were reliable, thoughtful, and trusted by their team. There was nothing to correct.

So what could I say, other than “Keep going”?

But there were gaps in visibility that I knew about, and they didn’t. There were perceptions forming above my level that would affect their trajectory, and “Keep doing what you’re doing” addressed none of them.

I’m glad it felt terrible as I heard it, because that discomfort made me follow up immediately with something real. I told them where the gaps were, what the people above me were seeing and not seeing, and I gave them something they could actually act on.

That follow-up took five minutes, and that empty compliment would have cost them months of promotion trajectory.

When I look back at the managers who used this phrase with me, I’ve come to understand that they weren’t all being lazy or dishonest. They were operating under pressures I couldn’t see at the time, and they didn’t know how to communicate this with me. But the effect was the same regardless of the intent.

I’ve identified three reasons managers default to this phrase, and each one requires a different response from the quiet leader on the receiving end of it.

The first is productivity. Your manager may tell you to “Keep doing what you are doing” because they genuinely like your work product. You get things done, and you don’t create problems that demand their attention. If they do nothing and you change nothing, that’s a perfectly acceptable outcome for them. From their perspective, the system is functioning.

The problem is that when “nothing changes,” that includes your career trajectory. A manager who is satisfied with your current level of output has no incentive to invest in your growth. You’re solving their problems without creating new ones, which makes you valuable in your current role and invisible for the next one. “Keep doing what you’re doing” in this context means “you’re making my life easier, and I’d prefer that to continue.” If investing in your growth would require more effort or attention, they are likely to avoid it. That is normal and human.

Quiet leaders are particularly vulnerable to this dynamic because they tend to deliver consistently without demanding attention. The manager never has to worry about you, which means the manager never has to think about you. The issue is that the person they never think about is rarely the person they advocate for when promotion conversations happen.

The second reason managers opt for the “Keep doing” feedback is a genuine lack of competence. Some managers say “Keep doing what you’re doing” because they genuinely don’t know how to give useful feedback to someone who is generally performing well. Perhaps all they ever received from their own managers were empty compliments like this one, or perhaps they lack the vocabulary to articulate what “good” looks like at the next level. Perhaps they don’t perceive the gaps that do exist, or perhaps they don’t know how to describe them.

This is more common than most people realize. Giving precise, developmental feedback is a skill, and it is one of the most underdeveloped skills in management. Managers are promoted for their technical ability, their operational results, or their tenure; rarely are they promoted because they demonstrated an ability to develop other people. The result is an entire layer of leadership that defaults to vague affirmation because they lack the tools to do anything else.

The third reason is avoidance. This is the most corrosive reason, and the hardest to detect from the receiving end.

Some managers use “Keep doing what you’re doing” because there are harder messages they need to deliver, and they are not prepared to deliver them. The feedback might be that your visibility is low, or that your style doesn’t match what the organization rewards, or that there are structural barriers to your advancement that have nothing to do with your performance. This is uncomfortable feedback to give, so many managers will avoid it.

Giving feedback like this requires the manager to be honest about things that reflect poorly on the organization, on themselves, or on the system they represent, and “Keep doing what you’re doing” is the escape hatch that lets them avoid all of it and still feel like they’ve had a development conversation.

I discovered, years after the fact, that one manager who used this line with me knew that layoffs were coming. They weren’t emotionally prepared to give meaningful feedback because, in their mind, the feedback wouldn’t really matter given what they knew was ahead. I carried a negative impression of that manager for years, but when I finally learned the full picture, I realized my judgment had been unfair.

But here is the thing: even when the reason is understandable, the effect on the quiet leader is the same. You walk away believing you’re on track, and you continue operating as you have been. Then, when the outcome doesn’t match the feedback, you’re left questioning your own judgment rather than questioning the feedback itself.

With all of this in mind, here is what I wish someone had told me earlier in my career:

When a manager tells you to “Keep doing what you’re doing,” that is not the end of the conversation. It is the beginning.

That phrase, delivered to a quiet leader who is performing well, almost always means one of two things. Either the manager genuinely cannot see the gaps, which means you need to help them see what they’re missing. Or the manager can see the gaps and is choosing not to name them, which means you need to create the conditions where the truth can surface.

Neither of those is your manager’s job alone, and waiting for them to do it is how quiet leaders end up in the same role for years, performing excellently, receiving empty praise, and watching louder colleagues advance past them.

The practice I recommend to every leader I coach is to make “Keep doing what you’re doing” impossible for your manager to say.

You do this by changing what you ask for.

Don’t ask “how am I doing?” That question invites exactly the vague affirmation you don’t need. It’s too open and too easy to deflect.

Instead, ask a question that demands specificity: “Am I performing at the level required for the next role?” That question forces your manager to compare your current performance against a specific standard. It surfaces the gap, if one exists, in a way that “how am I doing?” never will.

If your manager says yes, follow up: “What would make my promotion case undeniable? What would need to be true for the decision to be obvious?” Now you’re not asking for feedback; you’re asking for criteria. That’s a conversation most managers can have, even if they struggle with open-ended developmental feedback.

If your manager hesitates, that hesitation is the most valuable feedback you’ve received. It tells you there’s a gap they can see but haven’t named. Your job is to make it safe for them to name it by saying something like, “I’d rather hear something difficult now than be surprised later. What are you seeing that I’m not?”

This feels uncomfortable for quiet leaders. It requires you to advocate for yourself in a way that may not come naturally, but the alternative is another year of “Keep doing what you’re doing” followed by another year of wondering why nothing changed.

I want to connect this to something broader, because the “Keep doing what you’re doing” problem is not just a feedback problem, it is a visibility problem.

Quiet leaders who receive this feedback often interpret it through the lens of their values: “My work should speak for itself. If I’m doing good work, the right people will notice.” That belief is sincere. It is also, in most organizations, dangerously incomplete.

Your work does not speak for itself. Your work is silent, and it needs someone to speak for it. If your manager’s version of speaking for it is “Keep doing what you’re doing,” then no one is speaking for it at all.

This is where the feedback problem connects to the credit problem, the partnership problem, and every other dynamic I’ve written about in this newsletter:

Quiet leaders build real value, but the systems that distribute recognition, advancement, and opportunity are not designed to find that value unless someone makes it visible.

Your manager should be that someone. When they’re not, you have a choice: wait and hope, or change the conversation yourself.

I waited for most of my career. I don’t recommend it.

To the managers reading this, Keep this in mind:

“Keep doing what you’re doing” feels kind. It feels supportive. It feels like you’re affirming someone who is performing well and doesn’t need correction.

It is none of those things.

It is the feedback equivalent of a participation trophy. It communicates that you have noticed the person exists and that they have not caused you a problem. But that isn’t development; it’s maintenance.

The quiet leader on your team who receives this feedback will probably not push back, and they will probably not ask what it means. They will take it at face value, continue performing at the same level, and gradually fall behind their louder peers who are demanding and receiving the specific coaching that drives advancement.

When you eventually have to explain to this person why they didn’t get the promotion, or why their review was merely satisfactory, or why someone with less experience moved ahead of them, you will not be able to point to a single conversation where you told them the truth.

Because you didn’t. You told them to keep doing what they were doing.

And they did.

The question I’d leave with you:

When was the last time someone told you to “Keep doing what you’re doing”?

And did you accept it as a compliment, or did you ask what it actually meant?

If you accepted it, there is a conversation you still need to have. Not about what you’re doing wrong, but about what you’re not being told. That missing information is shaping your career whether you ask for it or not.

The only question is whether you’ll shape it back.

“AI is automating tasks. AI is disrupting jobs. You need to master the tools or be replaced by someone who has.”

There is truth in that conversation. The productivity gap between people who use AI tools well and people who don’t is real and growing. Mastering the tools matters. I use them every day, and I encourage every leader I work with to do the same.

But there is something missing from the conversation. Something that matters more than tool mastery, and that almost nobody is talking about clearly:

The tools are getting easier to use.

Every month, the bar for “mastering AI” drops. What required a software engineer last year requires a natural language prompt today. Within a few years, using AI effectively will be as unremarkable as using a search engine. It will be table stakes. Not a differentiator.

When everyone has the same tools, the advantage shifts. It shifts away from the people who use the tools fastest and toward the people who know what to do with the output. The people who can apply judgment, build trust, read a room, and make decisions under ambiguity.

In other words, the advantage shifts toward skills that quiet leaders have been developing for decades.

We didn’t develop them because we were preparing for AI; we developed them because leading quietly required us to build exactly these capabilities.

Let me be specific about what I mean, because this is not a motivational claim. It is a structural argument.

When you lead without the natural advantages of volume, charisma, or performative confidence, you are forced to develop a different set of tools. You learn to listen with precision because you cannot dominate a room. You learn to read what isn’t being said because you spend more time observing than speaking. You learn to build trust through consistency rather than charm.

These are not personality traits; they are practiced skills, developed over years of operating in environments that did not reward your natural energy.

And they are precisely the skills that AI cannot replicate.

AI can draft the memo, but it cannot feel the shift in the room when someone stops contributing. AI can analyze sentiment in text, but it cannot sense the unspoken fear behind a confident presentation. AI can generate options, but it cannot make the judgment call that requires weighing relationships, politics, organizational history, and the specific humanity of the people involved.

Every list of “AI-resistant skills” that I’ve seen from researchers, executives, and thought leaders converges on the same set of capabilities: judgment, emotional intelligence, trust-building, navigating ambiguity, reading unspoken dynamics, and making decisions that require human context.

Now read that list again through the lens of your own career.

If you are a quiet leader, you have been building those skills for ten, twenty, even thirty years. Not as a strategy, but as a necessity.

I’ve been thinking about this using the Leadership Energy Archetypes framework I introduced in an earlier essay, because the AI-resistance of different leadership energies is not uniform.

The Observer reads unspoken dynamics. This is the leader who notices the pause before someone chooses not to speak, who senses the shift in team morale before it surfaces in any metric, and who picks up on the misalignment between what someone says and what they mean. AI can process language, but it cannot read the space between words in a live conversation. The Observer’s energy is built on exactly the kind of real-time human perception that AI cannot access.

The Anchor builds trust through steady presence under pressure. As AI accelerates the pace of everything around a team, decisions come faster, more information flows, and expectations shift quickly. In this environment, the leader who slows the room down and makes people feel grounded becomes more valuable, not less. AI creates speed, and Anchors create the stability that makes speed sustainable. Without the Anchor, moving fast becomes reckless.

The Architect designs systems that endure. As organizations rush to implement AI, the leader who insists on structural integrity over speed of adoption prevents the kind of technical and organizational debt that compounds quietly until it collapses. AI builds fast, but Architects build to last. The judgment to know when speed serves the outcome and when it jeopardizes the future is not something a tool can provide.

The Connector navigates relational complexity between people. As AI handles more transactional communication, drafting emails, summarizing meetings, and generating status updates, the genuine human relationships that hold cross-functional work together become more visibly important. The Connector who maintains real trust across teams becomes the bridge that no tool can replace.

Now consider the energies that are more exposed.

The Performer who leads through energizing visibility may find that AI-generated content and AI-assisted presentations narrow the gap between their output and everyone else’s. When everyone can produce polished deliverables, the Performer’s advantage erodes. The energy that once set them apart becomes the baseline.

The Catalyst who thrives on introducing disruption may find that AI itself provides all the disruption organizations can absorb. Teams overwhelmed by the pace of technological change do not need a leader who shakes things up further. They need a leader who steadies them. The Catalyst’s instinct, which was valuable in stagnant organizations, becomes counterproductive in organizations already destabilized by the tools themselves.

This is not a clean binary. Every archetype has AI-resistant qualities and AI-exposed qualities. But the pattern is unmistakable: the energies that quiet leaders most naturally carry are the ones whose core strengths are hardest for AI to replicate.

The skills the market has historically undervalued in quiet leaders are becoming the scarcest resource in this market.

I want to ground this in something concrete, because abstract arguments about “the future of work” are easy to dismiss.

I recently built a complete web application. A real product, with authentication, cloud infrastructure, database management, media processing, and a deployment pipeline across multiple environments. I haven’t written production code in nearly thirty years. I did it in about ten days, working with AI as my engineering team.

The AI wrote the code. Every line of it.

But here is what the AI did not do: it did not decide what to build. It did not evaluate whether the architecture would scale. It did not recognize when a design choice was creating technical debt that would compound over time. It did not know when to stop adding features and start refactoring. It did not make the judgment calls about what mattered and what didn’t.

I did, using thirty years of engineering leadership experience that had nothing to do with writing code and everything to do with understanding systems, making trade-offs, and knowing what “good” looks like.

The AI was the tool; I was the craftsman.

That experience confirmed something I had suspected but needed to live through to fully believe: the future belongs to the people who can direct, not the people who can execute. And directing well requires exactly the skills that quiet leaders have spent their careers developing. Listening carefully, thinking systemically, exercising patience, and making deliberate decisions rather than reactive ones.

There is an irony here that I want to name, because I think quiet leaders need to hear it directly.

For most of your career, the skills you built were undervalued. You watched louder colleagues receive recognition for being decisive when you were being thoughtful. You watched people who spoke first get credit for ideas you had been developing more carefully. You were told to “be more visible,” to “speak up more,” and to “show more leadership presence,” as if the problem were your energy rather than the organization’s ability to recognize what you brought.

That was real, and it was costly. I’ve written about those costs in previous essays, and I don’t want to minimize them.

But the world is shifting in a direction that changes the calculus.

When everyone has access to the same tools, the people who can think clearly, build trust, and exercise judgment under ambiguity become the differentiators. Not the people who can use the tools fastest or perform confidence most convincingly, because the tool advantage is temporary and AI-generated confidence is indistinguishable from the real thing when it’s just words on a screen.

The differentiators are the people who bring something that cannot be generated: genuine human judgment, earned through years of practice.

So the story of your career is not that you were falling behind while louder leaders captured attention. In fact, you were building the foundation that is about to matter more than anything else.

You were training for this.

I don’t want to end with false reassurance. The shift I’m describing will not happen automatically, and it will not happen for every quiet leader.

The skills you’ve built are genuinely AI-resistant. But they are also genuinely invisible, which is the same problem quiet leaders have always faced. Having judgment, trust, and relational intelligence means nothing if the people making hiring, promotion, and investment decisions cannot see those qualities in you.

The visibility problem doesn’t disappear just because your skills become more valuable. If anything, it intensifies because the competition for roles that require human judgment will increase as more technical roles are automated. More people will compete for fewer positions, and the ones who can articulate their strengths will still have an advantage over the ones who quietly embody them.

So the charge is the same one I keep returning to across these essays: know your energy, understand its value, and make it visible in the moments that matter. Not through performance, but through deliberate, strategic presence.

The skills are yours. They’ve been yours for decades. The question is whether you’ll make them visible enough for the market to recognize what you’ve been building all along.

The question I’d leave with you:

If you set aside the anxiety about AI replacing jobs and sat instead with what you’ve actually built over your career... the judgment, the trust, the relational intelligence, the ability to make good decisions under pressure, etc.

Would you trade those skills for the ability to use any tool faster than anyone else?

I wouldn’t. And I suspect, if you’re honest with yourself, neither would you.

The tools will keep changing. The skills you’ve built will not.

That’s the advantage you’ve been developing this whole time.

A concept I once raised in a smaller meeting reappeared a week later in a larger one, articulated with more confidence and received with more enthusiasm. A strategic direction I once suggested showed up in a deck with a different name attached. An approach I once outlined in a document surfaced later in a conversation where I wasn’t present.

All of these ideas were then credited to the person who said them out loud.

This is not a complaint. It is a pattern. And every quiet leader I’ve coached has experienced some version of it.

The instinct is to call it theft and to assume that someone deliberately took your idea and presented it as their own. That does happen, and when it does, it’s worth confronting directly.

But more often, something subtler is at work. Something structural. Understanding the structure matters more than assigning blame, because blame doesn’t solve the problem. However, changing how you operate might.

In startups, getting credit for your ideas was rarely an issue for me. The teams were small enough that everyone saw the origin of a concept. If you proposed an approach in a room of eight people, there was no ambiguity about who brought it forward.

At Amazon and Warner Bros. Discovery, everything changed.

In large organizations, ideas travel through layers. A thought you share with a peer gets discussed with their team, refined in a meeting you weren’t invited to, and presented to leadership by someone three steps removed from where it started. By the time it lands, the attribution has shifted. Not through malice, but through distance. Each person who touched the idea added or reshaped something, and in doing so, absorbed a little bit of ownership.

The louder the person at the end of that chain, the more likely they are to be perceived as the originator of the idea. Not because they claimed it dishonestly, but because people respond to confidence and volume. The idea is heard most clearly in the voice that expresses it most forcefully. And once attribution sticks to a name, it rarely gets corrected.

I’ve come to think of this as a form of “acoustic attribution”: credit flows not to whoever had the idea first, but to whoever said it at a frequency the room could hear.

Here is the part that quiet leaders rarely examine, and it’s the part that matters most for changing the pattern:

We contribute to the problem.

Quiet leaders tend to ideate in isolation. We think deeply, refine our concepts internally, and wait until the idea feels fully formed before sharing it. That instinct toward thoroughness is a genuine strength in many contexts. But in the context of organizational credit, it is a vulnerability.

When you develop an idea alone and share it only when it’s polished, you create a gap between when the idea existed and when it became visible. In that gap, other people are having conversations, exploring adjacent territory, and arriving at similar conclusions through different paths. By the time you present your refined version, someone else may have already said something close enough that the room sees overlap rather than originality.

The idea wasn’t stolen. It was independently discovered, partially overheard, or simply arrived at by someone who was thinking out loud while you were thinking in private.

The quiet leader’s instinct to perfect before publishing is what makes their ideas vulnerable to exactly this kind of misattribution.

I learned this lesson through a different channel: patents.

I hold fourteen issued patents. Ten from my time at Amazon and four from previous companies. Every single one of them was collaborative.

The process of developing a patent taught me something that transformed how I think about credit. When we were ideating at Amazon, it was never one person arriving with a finished concept. It was a group of co-inventors sitting together, bouncing ideas off each other, building on each other’s contributions, and refining the concept through collective pressure-testing. By the time the patent was filed, the idea had been shaped by multiple minds, and the documentation reflected that shared authorship from the very beginning.

Nobody fought over credit for those patents. Not because the people involved were unusually generous, but because the structure made attribution clear. The co-inventors were listed. The contributions were documented. The collaboration was the process, not an afterthought.

That experience showed me that you need to build attribution into the structure of how ideas are developed, rather than hoping it will sort itself out after the fact. Because it almost never sorts itself out after the fact.

The practice I’ve adopted, and the one I recommend to the leaders I coach, is deceptively simple:

Get the idea out of your head and into a trusted circle as early as possible.

Not when it’s finished. Not when you’ve anticipated every objection. Early. When it’s still rough and incomplete.

Find two or three people you trust. Share the concept. Let them push on it, reshape it, improve it. Write it down together. Create a shared document, even an informal one, that captures the idea and the people who developed it.

This feels counterintuitive for quiet leaders. We want to arrive with something polished. We want the idea to be undeniably good before we expose it to scrutiny. But that desire for perfection is precisely what creates the attribution gap. The longer an idea stays in early phases, the more vulnerable it is to being independently discovered, partially overheard, or unconsciously absorbed by someone who then presents it as their own.

Everyone wants to be Michelangelo, working alone in the studio, emerging with something perfect. But even Michelangelo had a workshop full of apprentices and collaborators. The myth of solitary genius is exactly that: a myth. And it’s one that costs quiet leaders disproportionately, because it reinforces the instinct to work in isolation that makes the credit problem worse.

I want to connect this to the Leadership Energy Archetypes framework I’ve been developing, because the credit problem does not affect all leaders equally.

Leaders who carry the Architect’s energy are particularly vulnerable. Architects build systems, frameworks, and structures that other people stand on. Their contribution is foundational, and foundational work becomes invisible once something is built on top of it. Nobody looks at a building and credits the foundation; they credit the facade. The Architect’s work disappears into the infrastructure of the organization, and the people who operate on that infrastructure receive the recognition.

Leaders who carry the Anchor’s energy face a similar pattern. Anchors stabilize teams, absorb uncertainty, and create the psychological safety that allows others to take risks. When those risks pay off, the risk-taker gets the credit. The Anchor, whose steadiness made the risk possible, is rarely mentioned. Their contribution is felt but not seen or credited.

On the other side of the dynamic, certain archetype shadows create the conditions for credit absorption. The Performer’s shadow, when unchecked, can lead to presenting collaborative work as individual achievement. Not out of dishonesty, but because the Performer’s energy naturally draws attention and the room naturally attributes the work to whoever is presenting it. The Catalyst’s shadow can lead to claiming every change as their initiative, even when the change was seeded by someone else’s quieter suggestion.

None of this is about good people and bad people. It is about structural patterns in how different energies interact with the mechanisms of organizational recognition. Understanding these patterns is the first step toward navigating them deliberately rather than being shaped by them unconsciously.

There is a harder truth underneath all of this that I want to name directly.

Even when you do everything right... document your ideas, collaborate early, build shared ownership... the louder person in your partnership or your team may still receive the majority of the public credit. That is the structural reality of how visibility works. It may not be fair, but it is predictable.

The question is whether that visibility gap is tolerable.

In my experience, it is tolerable when the private truth is intact. When your partner, your manager, or your collaborator acknowledges your contribution honestly, even if that acknowledgment never reaches the broader audience.

What is not tolerable is erasure. When your contribution is not just under-credited but genuinely unrecognized. When the person who benefited from your thinking does not even know, or has stopped caring, that the idea started with you. That is the moment when the credit problem stops being a professional inconvenience and becomes a career-shaping force.

Erasure changes how organizations invest in you, how they promote you, how they calibrate your compensation, and how they assess your potential. Over a thirty-year career, the cumulative effect of systematic misattribution is not a series of small frustrations. It is a fundamentally different trajectory.

So what do you do?

You cannot control how the world distributes credit, but you can control three things that materially affect the pattern.

First, share earlier. The idea in your head is vulnerable. The idea in a shared document with three co-authors is protected. Not perfectly, but structurally. Get your thinking out of isolation and into collaboration before it’s polished. The rough version shared with trusted people is safer than the perfect version shared too late.

Second, document deliberately. Not obsessively, not defensively, but consistently. When you contribute an idea, follow it with a brief written summary. When a meeting produces a direction you helped shape, send the follow-up email that captures the contribution. This is not self-promotion; it is clarity. And it serves everyone, not just you, because it creates a record that the organization can reference when attribution matters.

Third, choose your partners carefully. This connects directly to the partnership essay I wrote last week. The right partner sees your contribution clearly and says so, at least privately. The wrong partner absorbs your contribution and eventually believes it was their own. You cannot always choose your manager or your peers, but you can choose where you invest your deepest collaborative thinking. Invest it with people who see you clearly.

There is one more thing I want to say, and it’s for the quiet leaders who are reading this and recognizing themselves:

Wanting credit is not vanity.

It is not ego or insecurity. It is a rational response to a system that uses attribution as the basis for advancement, compensation, and opportunity. Telling yourself that you should be above caring who gets the credit is a form of self-erasure that serves those who benefit from your invisibility.

You can be humble and still insist on accuracy, generous and still expect acknowledgment, and quiet while still making sure the record reflects the truth.

The goal is not to become louder. The goal is to make sure your ideas don’t have to be loud to be heard.

The question I’d leave with you:

Which of your ideas are still locked in your head right now, waiting to be perfect before you share them?

And how many of your past ideas are living somewhere in your organization, credited to someone else, because you shared them too late or too quietly?

The first question is something you can change starting tomorrow.

The second is something you carry. Not as a grievance, but as a lesson about what happens when quiet leaders don’t protect their own contributions with the same care they bring to protecting their teams.

The world has a theory about leadership partnerships that goes like this: the visionary has the ideas, the builder makes them real, and the credit goes to whoever is holding the microphone.

It is a clean story. It is also, in my experience, almost always wrong.

I’ve spent nearly four decades in some version of this partnership. The most important has been with , my closest friend and professional collaborator. We’ve known each other since college, worked together across four companies, and built a coaching practice, a course, and a professional community together.

Ethan is vocal, energizing, and extraordinarily effective in front of a room. He motivates teams, drives momentum, and communicates with a clarity and force that corporate America rewards immediately. He is, by any conventional measure, the louder leader.

I, on the other hand, am the one who built the production studio where we record our courses and content. I also designed the technical infrastructure behind our courses. When a system needs to be architected, a plan needs to be structured, or a complex problem needs to be quietly worked through before it’s ready for the room, that work tends to land with me.

From the outside, the story writes itself: “Ethan is the visionary, David is the builder.”

But that story misses something fundamental.

I have visions too. I have ideas, strategies, and creative instincts that are every bit as ambitious as anything Ethan brings forward. The difference is not the quality or originality of the thinking; it is the difference in the volume at which it gets expressed.

And the world, reliably and repeatedly, attributes ideas to whoever says them loudest.

This is not a complaint. It is a structural observation about how credit flows in organizations, in history, and in the stories we tell about leadership. This structure has real consequences for every quiet leader who has ever watched their own idea come back to them in someone else’s voice and then heard the room respond as if it were new.

This observation is for them.

The classic partnership story isn’t all wrong—many partnerships do have a louder partner and a quieter partner. But what makes a partnership like this work is not that one person leads and the other follows. It is that both people bring genuine vision, genuine capability, and a willingness to let the work determine who steps forward in any given moment.

Ethan and I have extraordinary trust. When he asks me to get something done, I will get it done. When I ask something of him, he does the same. That trust has been built through decades of showing up for each other, delivering on commitments, and never competing for the credit.

The most important element of this trust is that Ethan knows the ideas come from both of us. He recognizes my contributions, supports my growth, and has never confused his public image with sole authorship. The recognition may not always be public, because that is simply not how visibility works, but it is always private and always genuine.

That private recognition is what holds the partnership together.

When it is present, the quiet leader can accept that the world sees one name more than the other, because the person who matters most—their partner— sees the truth. When this recognition is absent, and if the visible partner starts thinking the ideas really were all theirs, the partnership fractures. Usually not with a dramatic break, but with a slow erosion of trust that eventually hollows out the collaboration.

I have been fortunate. Ethan is not like that. But I have watched other partnerships collapse when the louder partner began to think that they were worth more.

This dynamic is not unique to my career, though. It runs through history in ways that are both well-documented and systematically overlooked.

Consider George Marshall.

Marshall is arguably the most consequential American military leader of the twentieth century. He built the army that won the Second World War. He selected the commanders, including Eisenhower. He designed the strategic framework that guided the Allied campaign in Europe, and after the war, he created the reconstruction plan that rebuilt the continent. The Marshall Plan bears his name, but even that undersells his contribution, because the plan was merely the most visible expression of decades of strategic thinking that shaped the modern world.

Here is how this relates to partnership: when President Roosevelt offered Marshall the command of D-Day, perhaps the most visible military role in the history of warfare, Marshall deferred. He believed Eisenhower was the right person to be the public face of the invasion. Not because Marshall lacked the capability, but because he understood that the institution needed him where he was, doing the work that only he could do, in a role that would never carry the same recognition.

Eisenhower went on to become President, and Marshall became, in Truman’s words, “the greatest living American.” However, most Americans today could not tell you what he did.

That is the quiet leader’s bargain: do work that matters and that only you can do, accept that it may never be seen clearly, and trust that the partnership serves something larger than either person’s reputation.

Marshall’s story survives in the historical record because the scale of his contribution was too large to erase entirely. But how many partnerships of this kind have existed where the quiet side’s contribution was never recorded at all? Where the visible leader received the credit and the quiet partner simply disappeared from the story?

The absence of evidence is not evidence of absence. It is evidence that quiet leadership is often invisible to anyone who was not in the room.

Omar Bradley offers a different angle on the same pattern.

Bradley commanded the largest body of American combat troops in the European theater during WWII. He was known as “the Soldier’s General” because he led through care for his troops rather than personal theater. He was steady, methodical, and deeply trusted by the men who served under him.

However, George Patton is the general that history remembers from that campaign. His personality, his controversies, and his dramatic style made for better storytelling. Even though Bradley outranked him and outperformed him by most strategic measures, he is remembered less vividly because his leadership did not generate spectacle.

This contrast is instructive. Patton’s leadership was loud and visible while Bradley’s was quietly effective. The world gave Patton the movie.

For every quiet leader reading this who has watched a louder colleague receive disproportionate recognition, Bradley’s story will feel familiar. Not because the loud leader was incompetent—Patton was genuinely brilliant, but because the mechanisms of recognition naturally favor the person who made the most noise.

Back in the business world, Steve Wozniak and Steve Jobs represent perhaps the most widely known version of this partnership, and the most commonly misunderstood.

The standard narrative is that Wozniak built the technology and Jobs sold it. Builder and visionary. Quiet engineer and loud entrepreneur.

That narrative is incomplete in a way that matters deeply.

Wozniak had vision. He imagined what personal computing could become, and he designed machines that were elegant, innovative, and years ahead of what anyone else was building. His importance was not limited to execution; he creatively conceived possibilities that did not yet exist.

But Jobs had volume. He could articulate the vision in a way that made the world respond. He could communicate an idea in a way that would attract investors and customers. His gift was not that he had better ideas than Wozniak. It was that he expressed ideas at a frequency the market could hear.

The partnership worked as long as both understood this distinction, but it fractured when the public narrative changed the dynamic. When the world decided that Jobs was the mind and Wozniak was merely the hands, their partnership began to fray. Public perception influenced how both men viewed the partnership.

Every quiet leader who has been called “the executor” when they were actually “the originator” will recognize this pattern. Being consistently misclassified changes how organizations invest in you, promote you, and value your contribution over the course of a career.

I want to name something that quiet leaders feel but rarely hear articulated, because I think it is central to understanding why these partnerships matter and why they are so fragile:

The quiet partner wants recognition.

They may not want the spotlight, applause, or a magazine cover, but they do want the acknowledgment that the ideas were shared, that the vision was collaborative, and that the work was not merely the execution of someone else’s imagination.

This desire can be complicated by a sort of false stoicism that exists in the quiet leadership space. This philosophy says you should be content with the work itself, that needing recognition is a form of vanity, and that the truly enlightened leader doesn’t care who gets the credit.

I don’t believe that.

Humans need recognition. This is not vanity. Recognition materially influences how careers advance, how opportunities flow, and how compensation gets calibrated. Telling quiet leaders to stop wanting it is asking them to accept a structural disadvantage and wear it as a personal virtue.

While institutional recognition is both emotionally and materially important, what I have learned is that the recognition that matters most comes from the partner, not the audience. When Ethan acknowledges my contribution—when the person I trust most sees the work clearly—the public credit becomes less important. Not unimportant, but less urgent. The private truth can sustain the partnership even when the public narrative is incomplete.

Marshall and Eisenhower had this. Eisenhower never pretended that Marshall’s strategies were his own. The credit flowed to Eisenhower anyway, because that is how visibility works, but the relationship survived because the private truth was respected.

When that private truth breaks, the partnership dies. Not loudly, but quietly. Which is fitting, given who is usually the one doing the leaving.

If you are a quiet leader, I would offer this:

Look for the partner who sees you clearly. Not the one who needs you to be louder, but the one who understands what you provide and values it honestly. That partnership, when you find it, will produce more than either of you could build alone. Not because one of you is incomplete, but because the combination of different energies, directed toward a shared purpose with mutual trust, creates something that neither volume nor silence can achieve independently.

If you are a louder leader, I would offer this:

Look for the quiet leaders around you and ask yourself honestly whether you know where your ideas actually come from. Whether the strategies you articulate were truly yours alone, or whether they were shaped, refined, and sometimes originated by someone who never claimed them publicly. If you find that person, protect them. Champion them. Make sure the private truth is spoken, even if the public narrative never catches up.

And if you are in a partnership where the private truth has broken, where credit has been absorbed rather than shared, or where one person’s visibility has been confused with sole authorship, that is worth confronting. Discuss it together.

The question I keep returning to is one that cannot be answered with data:

How many of these partnerships exist right now, in organizations around the world, where the quiet side is doing the work that makes the visible side possible?

And how many quiet leaders are sitting with the same tension I have felt: proud of the work, grateful for the partnership, and quietly wondering whether the world will ever see the full picture?

The honest answer is that the world may never see it. The mechanisms of recognition are structurally biased toward volume. That will not change quickly, and it may not change at all within our lifetimes.

If that is the case, the question becomes whether the partnership, the trust, and the work itself are enough.

For me, they have been. Not always comfortably, but consistently.

Have the partnership and the work been enough for you?

I was in a leadership meeting at Amazon. It was a cross-functional debate about a launch decision, the kind where multiple teams had competing priorities and the path forward wasn’t obvious. The room was full of strong voices, and multiple people were making their cases with conviction. They were building momentum behind their positions and signaling certainty.

I had a perspective on the question at hand. I’d spent time with the data, and I believed the group was converging on the wrong trade-off: they were optimizing for speed at the expense of a structural risk that would cost more to fix later.

But the energy of the room was clearly moving in that direction.

So I waited. I listened and looked for the right moment to introduce a different framing…but that moment never came.

Then, before I knew it, the decision was made and the room moved on. My perspective never entered the conversation. I was being thoughtful and exercising restraint, and the result was silence that looked exactly like agreement.

Afterward, a peer pulled me aside and said something I’ve never forgotten: “If you had something, you needed to say it in there. No one knew you disagreed.”

He was right. And the uncomfortable truth was that my restraint hadn’t served the team. It had served my comfort.

I tell that story because I think it demonstrates something that quiet leaders rarely admit, even to themselves:

Staying quiet is sometimes a defense mechanism.

I’ve written about restraint as a leadership tool, as the discipline to let silence carry weight. I believe all of that. I’ve seen restraint create space for others to lead, prevent reactive decisions, and model the kind of steadiness that teams need from their senior leaders.

But I also need to be honest about its shadow.

Restraint can all too easily become an excuse for avoidance, and the line between the two is not always visible to the person exercising it.

From the inside, restraint feels principled. It feels like patience, like wisdom, and like choosing the long view over the reactive one.

But from the outside, restraint can look like passivity or disengagement. At its worst, it can look like a leader who doesn’t care enough to fight for a position. In organizations that reward visibility, decisiveness, and vocal conviction, that perception has real consequences.

Here is the trade-off I want to name directly, because I think the people who are drawn to Leading Quietly feel it but rarely see it articulated:

Restraint is philosophically sound and politically dangerous.

The quiet leader who pauses before reacting, who doesn’t dominate the room, and who waits for the right moment to speak, is often the one whose name doesn’t come up in succession conversations. This is because the people making those decisions never saw the leader’s capability in action. They saw composure but interpreted it as absence.

I’ve watched this happen to leaders I’ve coached. People with exceptional judgment, deep technical knowledge, and the full trust of their teams are passed over because the executives above them couldn’t distinguish between restraint and passivity. The feedback was always some version of “we need to see more leadership presence” or “you need to be more visible in cross-functional settings.” What that actually meant was, “We need you to perform your competence in a way we can easily recognize.”

I’ve had that feedback myself. More than once.

The instinct, at this point, is to frame this all as someone else’s problem. To say that organizations should get better at recognizing quiet leadership, that the bias toward volume is a cultural failure. It is so easy to say that the system needs to change.

And there’s truth in that. The bias is real. Organizations do over-reward confident self-promotion and under-reward the people who stabilize teams, prevent crises, and make everyone around them more effective. That pattern is well-documented and genuinely damaging.

But sitting with that critique, however valid, doesn’t solve the problem for the leader who is living it right now.

If you are a quiet leader in an organization that rewards volume, you face a choice that doesn’t have a clean answer. You can either maintain your natural posture and accept that you will sometimes be misread. Or you can grow your range and adapt your visibility to match the environment.

Neither option is costless.

What I’ve learned, through my own career and through coaching others, is that the answer isn’t to choose one or the other; it’s to develop the judgment to know which moments require your voice and which ones require your silence.

Not every meeting needs your perspective. But some do, and the cost of withholding it in those moments is greater than the discomfort of offering it. The decisions that shape your team’s direction, your organization’s strategy, or your own career trajectory require you to show up in a way that others can see.

The key skill is knowing which situation is which, which is harder than it sounds.

I think about my own career and the times when restraint served me well. At WBD, during the chaos of the merger, my steadiness was an asset. Teams needed someone who wasn’t reacting to every shift in organizational politics, and who could absorb uncertainty without transmitting anxiety. That was genuine restraint, deployed in a context where it was needed and recognized.

But I also think about the moments where I stayed quiet when I should have spoken. Strategy discussions where I had a contrarian view, but let the room’s momentum carry the decision. Talent conversations where I should have advocated more forcefully for someone on my team. Organizational debates where my perspective would have mattered, if anyone had known I held it.

In each of those moments, I told myself I was being strategic; I was exhibiting restraint.

Sometimes that was true, but sometimes it was a story I told myself to avoid the exposure that comes with visible disagreement.

Knowing the difference between those two, between strategic restraint and comfortable avoidance, is the charge of every quiet leader who wants to drive more impact. And it’s work that never finishes, because the conditions change with every room, every decision, every shift in organizational context.

There is a version of this essay that ends with reassurance. It tells you restraint is a superpower and the world will eventually catch up; that the quiet leader’s time is coming.

I don’t think that’s honest.

The truth is that choosing restraint means accepting a set of costs that louder leaders don’t pay. You will be misread, you will be passed over for things you deserved, and you will watch less thoughtful people capture attention you could have earned.

The question isn’t whether those costs are fair. They’re not. The question is whether the alternative costs more.

For me, the answer has consistently been yes. Performing urgency I don’t feel, manufacturing visibility for its own sake, and optimizing for perception over judgment erode something in me that I’m not willing to give up. They erode the alignment between who I am and how I lead, and once that alignment breaks, the leadership that follows is hollow, no matter how visible it becomes.

But I want to hold that conclusion loosely, because I know the cost of restraint is not evenly distributed. A quiet leader with positional authority can afford it more easily than one who is still building credibility. A leader whose organization values substance can practice it more freely than one embedded in a culture that cannot see past volume.

Context matters, and any philosophy that ignores context becomes empty dogma.

So where does this leave you?

I don’t have a clean resolution, but I do have a practice. It goes like this:

1) Know what restraint is costing you. Not in the abstract, but in specific circumstances. Ask yourself: “Which conversations did I stay silent in this month that mattered? Which opportunities did I let pass because showing up felt like performing? The cost may be worth paying, but you should pay it knowingly, not just out of habit.

2) Honestly distinguish between restraint and avoidance. When you choose not to speak, ask yourself: “Am I creating space, or am I protecting myself?” The answer will change depending on the day. The question should not.

3) Choose your moments. You cannot show up at full visibility in every setting without exhausting yourself and diluting your signal, but you can identify the three or four moments each quarter where your voice genuinely matters. Commit to being heard in those moments. Strategic visibility is not performance; it is stewardship of your impact.

4) Accept the tension. Quiet leadership in a loud culture will always involve friction. That friction is not a sign that you’re doing it wrong; it is just the inherent cost of leading from a posture that the environment doesn’t automatically reward. The goal is not to eliminate the friction, but to ensure that what you preserve by accepting it is worth more than what you lose.

Restraint is not weakness. I believe that fully.

But restraint practiced without self-awareness, without honest assessment of its costs, without the willingness to break from it when the moment demands, is not strength either.

It is your comfort zone wearing the mask of principle.

The work is learning to deploy your voice and your restraint in the most beneficial ways. Not once, but continuously. In every room, every decision, and every moment where the choice between speaking and staying silent carries consequence.

And that work is never finished.

The question I’d leave with you is one I still ask myself:

When you choose restraint, are you serving the moment... or avoiding it?

And how would you know the difference?

But principles are style-layer artifacts. They describe what leaders should do. They say nothing about what leaders need to radiate in order to enable the best outcomes. And that energy, what leaders put out into the world, is where cultures really take shape.

In the months and years that followed the acquisition, I watched my peer VPs implement the stated leadership principles in completely different ways. I sat through some meetings where the leaders brought the principles to life in the room, and many others where they were simply decorations on the wall.

Two specific meetings stay with me years later, both run by VPs who led large technical organizations. If asked, both VPs would describe their leadership the same way: collaborative, empowering, results-oriented. Both were operating under the same published principles.

But their meeting rooms felt completely different.

The first VP asked good questions, listened to the answers, and let the team arrive at decisions together. The pace was unhurried, and people leaned in to the discussion. When someone disagreed, the room absorbed it without tension. You left the meeting feeling like you’d been part of something that mattered.

The second VP also asked questions, listened, and let the team weigh in, but there was an undercurrent. A tightness. The questions all felt like tests, and the listening felt like an evaluation. When someone disagreed, there was a tiny pause... just long enough for the room to register that the disagreement had been noted, and then the discussion moved on. People contributed, but carefully. You left the meeting feeling like you’d been managed.

Same principles. Same style description. Entirely different experience.

I once heard a VP say, in front of peers and in reference to the leadership principles, “I know that’s what’s written down, but we have to be practical and get the work done.” That sentence tells you everything about the gap between style and energy. The principles were acknowledged, but the energy dismissed them. And everyone in the room understood which one was the real determining factor for the culture.

What a leader radiates as they approach the work is what I’ve come to think of as leadership energy, and I believe it’s the most undertrained dimension of leadership development today.

Most of what we teach leaders falls into the category of “style”—how to delegate, how to coach, how to give feedback, how to run a meeting, etc. When to be directive and when to be participative, you get the point. These are behavioral patterns, and they matter. They are the visible layer.

Beneath them, however, is something harder to name and harder to change: the emotional and relational presence you bring into a room. The pace at which you operate, the way you hold tension, the quality of your attention. Whether people feel expanded or contracted in your presence.

That’s energy, and it shapes the experience of your leadership far more than your chosen methodology does.

The key difference is that you can borrow a style. You can read about servant leadership on a flight and try it in your next one-on-one, or learn coaching frameworks and apply them in skip-levels. Style is transferable.

But you can’t fake energy for long. A leader who adopts a coaching style but carries anxious energy will ask questions that feel like interrogation. A leader who practices servant leadership but carries controlling energy will create dependence rather than empowerment. The style says one thing, but the energy says another. And people always, always believe the energy.

I’ve been developing a framework around this idea, and I want to share the core of it here. It isn’t a finished system, but it is a way of thinking that I’ve found useful for myself and the leaders I coach.

The framework starts with a distinction that sounds simple but has real implications: leadership operates on three layers, not one.

The first layer is values. This is why you lead. Your sense of purpose, your ethical commitments, and the things you’d protect even at personal cost. Values are deep and relatively stable. They’re the foundation.

The second layer is energy. This is how you show up. Your natural tempo, your emotional register, and the way you hold space under pressure. Energy is rooted in temperament and self-regulation. It can be developed, but it can’t be manufactured or pretended. It’s the layer that people experience most viscerally.

The third layer is style. This is what you do. The behavioral patterns, decision-making approaches, and communication methods you use to translate your values and energy into action. Style is the most visible layer and also the most adaptable.

Most leadership development lives entirely at the style layer. It almost always teaches people what to do differently, but it rarely helps them understand the way they make people feel or why the same technique works beautifully for one leader and falls flat for another.

The answer, almost always, is energy.

To make this concrete, I’ve identified ten energy archetypes that describe the different ways leaders naturally show up. These aren’t personality types, and they’re not fixed categories. They’re patterns of presence, each with its own strengths and its own shadow.

I won’t walk through all ten here. But three of them illustrate the concept well enough to be useful.

The Architect leads through structured clarity. Their energy is systematic, deliberate, and oriented toward building things that last. In a meeting, the Architect is the one who organizes the chaos into a framework before the group can move forward. They bring calm to ambiguity by imposing order on it.

The Architect’s strength is that they create systems people can rely on. Their shadow is rigidity. When the Architect’s energy goes unchecked, structure becomes control. Process becomes the point rather than the means, and the team starts optimizing for the system rather than the outcome.

The Anchor leads through steady, grounding presence. Their energy is calm, consistent, and deeply supportive. The Anchor is the leader people seek out when things get chaotic, not because they have the answers, but because their presence makes the problem feel manageable.

The Anchor’s strength is trust. Teams feel safe around them. Their shadow is passivity. When the Anchor’s energy goes unchecked, steadiness becomes inertia. The team feels supported but not challenged. Conflict gets absorbed rather than addressed. The Anchor holds the space so well that nothing inside it moves.

The Catalyst leads through adaptive momentum. Their energy is change-oriented, forward-leaning, and responsive to the environment. The Catalyst is the leader who senses when a team is stuck and introduces just enough disruption to get things moving again.

The Catalyst’s strength is that they keep organizations from stagnating. Their shadow is inconsistency. When the Catalyst’s energy goes unchecked, adaptability becomes instability. The team never feels settled. Direction shifts before the previous direction has been fully explored. People begin to wonder if there’s a steady hand on the wheel at all.

If you recognized yourself in one of those descriptions, that recognition is the point.

Most leaders, when they encounter these archetypes, have an immediate felt sense of which one fits. Not because someone told them, but because they’ve been living it. They know what their energy feels like from the inside. What they often lack is language for it, and awareness of how it lands on others.

That’s the gap this framework is designed to address.

Because here’s what I’ve observed over thirty years of leading and coaching: the leaders who struggle most are not the ones with the wrong style; they’re the ones whose energy is misaligned with their context, or whose energy is operating in its shadow without their awareness.

A natural Architect leading a team through a period of rapid experimentation will create friction, not because their instincts are wrong, but because their energy is pulling toward order in a moment that requires tolerance for mess. A natural Catalyst leading a team that needs stability and predictability will generate anxiety, not because they’re incompetent, but because their energy is introducing disruption where the team needs grounding.

Neither leader needs to abandon their energy. But both need to see it clearly enough to regulate it. They need to know when their natural posture is serving the moment and when it’s working against it.

This is where the three-layer model matters most.

If you change style without adjusting energy, you get friction. The words say “coaching” but the presence says “evaluation.” The principles say “collaborative” but the energy in the room says “I’ve already decided.” Or, as that VP at WBD put it plainly: I know that’s what’s written down, but we have to be practical. The style was a mask, and the energy never changed at all.

If you manage energy without clarity of values, you drift. You become adaptable but unprincipled—smooth but empty. People feel comfortable around you, but don’t know what you stand for.

If you align all three—values, energy, style—you get presence. This is the kind of leadership that people remember not because of what was said, but because of what it felt like to be in the room.

That level of alignment is rare because it requires a self-awareness that most leadership development never cultivates. We spend years teaching leaders what to do and almost no time helping them understand what they radiate.

I want to be honest about where this framework stands. It’s a work in progress. The ten archetypes need further refinement. The relationships between energy and style need more mapping. The practical applications for coaching and team development are still emerging.

But the core distinction, that energy and style are different layers and that energy is the more powerful of the two, is one I’m confident in. I’ve seen it explain dynamics that traditional leadership frameworks can’t account for. I’ve watched leaders who were “doing everything right” fail because their energy was undermining their behavior. And I’ve watched leaders with imperfect technique succeed because their energy created trust that compensated for tactical gaps.

Style is what you do; energy is what people feel, and when the two are misaligned, people always go with what they are feeling.

The question I’d leave with you:

If you set aside what you’ve been trained to do as a leader, and sat instead with how your presence actually lands on others... what would you discover?

And would your team’s description of your energy match the style you think you’re practicing?

He was consistently dismissive of other people’s work. Not hostile, exactly, but casually condescending in reviews, architecture discussions, and the small daily interactions that either build trust or destroy it. His attitude was slowly creating rot in the team, the way a small leak eventually damages a foundation.

Everyone saw it, and as the leader, I told myself I was “monitoring the situation.”

What I was actually doing was hoping it would work itself out. I knew he was a great engineer, and I respected his technical ability. Sitting across from him and telling him that his brilliance was damaging the team felt like a confrontation I wasn’t ready for. Plus, confrontation felt like the opposite of the kind of leader I wanted to be.

So I was too soft. I hinted, suggested, and gave feedback that was careful enough to be ignored. And I hoped.

But hope is not a strategy.

While I was hoping and waiting, this engineer’s unchecked confidence wasn’t just alienating people; it was silencing them. Being so critical of other people’s work meant that others stopped offering their opinions for fear of his criticism. Other engineers who saw problems wouldn’t raise them because the social cost of challenging this person was too high. The team’s immune system, its ability to catch mistakes through honest peer review, quietly shut down.

And then it caught up with all of us.

A scaling issue went into production. It was a straightforward problem that several engineers on the team had seen coming, but none felt they could confront the person responsible—the talented engineer. The result was that we couldn’t publish to the site for several hours. It was a preventable failure, caused not by a lack of talent on the team, but by a culture of avoidance that I had allowed to take root.

After the incident, the engineer was defensive and embarrassed, and we finally had the hard conversation I should have initiated months earlier. Things started to get better, but only through sustained, direct feedback. This was the kind of feedback that I had not given forcefully enough before; the kind I had avoided because it felt uncomfortable.

In the end, the damage was deeper than it needed to be. Not just to the team, but also to the engineer himself, who had been operating without honest correction for months. He deserved better, and the team deserved better. I had failed both of them because I had disguised my avoidance as patience.

This is the trap that quiet leaders fall into most often.

We are comfortable with listening, observing, and creating space. These are genuine strengths that serve teams well in many contexts. But they become liabilities the moment a situation requires direct correction. The same instinct that makes us patient can also make us slow and avoidant.

The quiet leader’s shadow aggression is delay, and when an action needs correction, delay is not neutral. It is a decision to sacrifice the team’s needs to your own comfort.

There’s a common belief among quiet leaders that goes something like this:

“If I create the right environment, people will self-correct. If the culture is strong enough, if the expectations are clear enough, if the feedback mechanisms are healthy enough... individuals will see the gap between their behavior and the standard, and they’ll close it on their own.”

Sometimes that’s true. Mature professionals in healthy teams can self-correct, but it requires two conditions that are less common than we’d like to believe: the person must be aware of the gap, and they must have the skill and motivation to close it.

When either condition is missing, waiting is not patience; it is a leadership failure.

I’ve done this more than once. Lycos was the earliest and most instructive failure, but not the last. There were other times that I convinced myself that patience was a higher-order leadership behavior than directness; that restraint was always the more sophisticated choice.

That is an incomplete leadership philosophy that, applied without judgment, becomes its own kind of failure.

The leaders I’ve admired most over thirty years were not the ones who avoided hard conversations. They were the ones who had them early, clearly, and with genuine care for the person on the other side.

At Amazon, I worked with multiple leaders who could deliver difficult feedback in a way that left the recipient feeling respected rather than diminished. The conversation was direct, the expectations were specific, and the tone communicated something essential: I am telling you this because I believe you can do better, and because this team needs you to.

That combination of directness and belief is what separates correction from criticism. Criticism is about the leader’s frustration, whereas correction is about the other person’s growth. The words might sound similar, but the energy is entirely different.

I have also worked with leaders who confused bluntness with honesty. These leaders delivered feedback like a verdict rather than a conversation, and they used directness as a weapon disguised as “being transparent.” The effect of this style was that their teams learned to perform compliance rather than internalize standards. The behavior changed on the surface, but the culture underneath did not.

The lesson I took from both types of leaders was this:

How you correct matters as much as whether you correct. But “how” cannot become a reason to avoid “whether.”

Here is the tension I want to name directly, because I think quiet leaders feel it acutely and rarely hear it articulated.

If you over-correct toward kindness, standards erode silently. The team watches you tolerate what you said you wouldn’t tolerate, and they adjust their expectations downward. They stop believing that the bar is real, and the people who are meeting the standard start to wonder why they bother.

If you over-correct toward bluntness, trust fractures. The team watches you deliver feedback without warmth, context, or care, and they learn that vulnerability is dangerous. Then they stop bringing you the early signals, the half-formed concerns, and the emerging problems. They stop telling you when they are struggling because those conversations feel like exposure rather than partnership.

Neither failure is dramatic, and neither happens in a single moment. Both accumulate quietly until the culture has shifted in ways that are difficult to reverse.

The quiet leader’s challenge is holding both of these in view simultaneously. Not choosing kindness over directness or directness over kindness, but understanding that the real skill is knowing which one the moment requires, and having the discipline to act, even when it’s uncomfortable.

I think about a conversation I had years ago at Warner Bros. Discovery. A senior member of my team was underperforming, not in a way that was visible to people outside the team, but in a way that was creating real drag on the people around them. Deadlines were being missed, communication was inconsistent, and other team members were quietly picking up one person’s slack.

I had the necessary conversation, and I remember the specific moment when I almost softened it into uselessness. I had prepared my points, I knew what needed to be said, and as I sat across from this person, I felt the pull to cushion, to qualify, to surround the core message with so much context that it would lose its edge.

This time, I caught myself. I remembered what had happened at Lycos. What I had let happen. I knew what would happen if I let my avoidant instincts win. The conversation would be more comfortable and far less effective. Ambiguous feedback, in the context of performance, is cruelty dressed up as compassion. It allows the problem to continue while you feel like you “had the conversation.”

So I said what I needed to say. Clearly. Specifically. And then I said something else: that I believed they could close the gap, that I wanted to help them do it. I told them that the conversation was happening because they mattered to the team, not because they didn’t.

The correction landed because it was honest, and because it came from someone the person trusted to have their interest in mind.

That, I think, is the part that quiet leaders underestimate. The hard conversation does not have to be a departure from your leadership style; it can be an expression of it.

If you lead through trust, direct feedback is an act of trust. You are trusting the person to hear it, absorb it, and grow from it. Withholding the feedback is the opposite of trust; it is a judgment that they cannot handle honesty.

If you lead through care, then correction is an act of care. You are caring enough to risk discomfort, yours and theirs, because the alternative is watching someone fail in slow motion while you maintain the illusion of a supportive environment.

If you lead through restraint, your restraint is expressed in choosing the moment carefully, preparing the message deliberately, and delivering it with the precision that quiet leaders are uniquely equipped to bring.

If you ignore these hard conversations, your team won’t see every moment of avoidance. But they will feel its consequences in the slow erosion of standards. They will feel it in the quiet resentment of the people carrying others’ weight and in the gradual realization that the bar is negotiable.

Quiet leadership is not the absence of hard conversations. It is the discipline to have them well.

The question worth sitting with:

Is there a conversation you’ve been “monitoring” that your team needs you to have?

And what is your silence teaching them about the standard you’re willing to hold?