Claire has been talking about innovation for three quarters.

It’s in the strategy deck. It’s the word she uses most in all-hands presentations. She said it twice in the last town hall. Once at the opening, once at the close, bookending forty minutes of quarterly updates with the promise that this was the direction, that the team was building toward something new, that the investment was coming.

The team is waiting. Claire knows they’re waiting. On Sunday nights, in the quiet that arrives when the week ahead starts taking shape, she feels the gap between what she’s been saying and what she’s actually been doing.

Monday: three operational reviews that could have been dashboards. Tuesday: two vendor calls that could have been emails and a budget reconciliation her finance lead was fully capable of owning. Wednesday: a cross-functional sync she’s been meaning to remove herself from since February. Thursday: back-to-back one-on-ones with no agenda that end with “okay great, same time next week.” Friday: email catch-up that consumed the morning and left the afternoon in pieces.

Innovation: zero hours.

It’s not that Claire doesn’t care about it. It’s not that she’s disorganized or undisciplined or bad at her job. Her calendar doesn’t care about strategy decks or town hall promises or Sunday night intentions. It scheduled what she actually chose to do with her time. And what it recorded is not a story about innovation. It’s a story about operational maintenance, accumulated obligations, and the slow buildup of other people’s priorities filling the space where her own should have been.

The calendar isn’t lying. The strategy deck is.

The Lie We Tell Ourselves

“I’ll get to it when things settle down.”

Things do not settle down. The inbox does not reach zero. The operational reviews do not stop requiring attendance. The urgent does not exhaust its supply of material. Waiting for the calendar to clear before working on what matters is waiting for the traffic to clear before leaving for the airport. The longer you wait, the worse it gets, and the plane will not hold.

Leaders have been saying this to themselves their entire careers. It is one of the most reliable lies available because it is always at least partially true. Things really are busy, the timing really isn’t ideal, the current quarter really does have a lot going on. The lie isn’t in the circumstances. It’s in the conclusion (or illusion) that this particular set of circumstances is the obstacle rather than the permanent condition.

“Everything on my calendar is important.”

Some of it is. Most of it probably isn’t, at least not at the level of importance that justifies the hours it’s consuming. The difficulty is that urgency feels like importance. A pinging inbox feels like priority. A meeting request from someone senior feels non-negotiable. The pressure of the immediate is felt physically, in the moment, with social consequences for ignoring it. The importance of the strategic is quieter, more abstract, and seems patient enough to keep being deferred.

The urgent will always crowd out the important unless you build a structure that protects the important with the same ferocity the urgent brings naturally.

“I can’t say no to that.”

Usually not true. Usually the accurate version is: I haven’t decided that the cost of saying yes to this is higher than the cost of saying no to what I should be doing instead. That decision is available. It requires naming the trade-off explicitly rather than accepting the default. The default is always yes to the meeting, the request, the escalation that landed in the inbox at 4pm. Saying no requires a decision. Saying yes only requires inertia.

Here is the thing about prioritization that nobody says in the frameworks and the productivity systems and the time-blocking templates: it is not a planning problem. It is a courage problem. The plan is usually fine. The courage to protect it against everything that doesn’t respect it — that’s where the work is.

The Autopsy: Three Ways Prioritization Fails Before the Week Starts

1. Confusing urgent with important

The distinction between urgent and important is one of the oldest ideas in time management. Most leaders have seen it. Almost none apply it consistently, not because it’s wrong but because the urgent quadrant generates real, felt, immediate pressure and the important quadrant generates none.

Nobody sends a calendar invite for “work on the thing that will matter in six months.” The urgent arrives uninvited and with social consequences for ignoring it. The important sits quietly, available, requiring you to choose it deliberately every day against everything that doesn’t require choosing.

The most expensive hours in most leaders’ weeks live in the urgent-but-not-important quadrant. The meeting that could have been an email. The problem that could have been delegated. The request that feels important because of who sent it rather than what it contains. These hours are where the strategy goes to die incrementally, one accepted calendar invite at a time.

2. Treating everything as a priority

When everything is a priority, nothing is. This sounds like a bumper sticker. It functions like a law.

Organizations that haven’t made genuine trade-offs, that have said yes to twelve strategic initiatives because saying no to any of them felt politically complicated, haven’t prioritized. They’ve distributed dilution evenly across everything and called it strategy. The initiatives all move slowly. None of them move enough. The team is busy everywhere and making progress nowhere.

The honest conversation about competing priorities is almost always the conversation nobody wants to have, because having it requires someone’s initiative to end up on the wrong side of the trade-off. That person is in the room. They have a champion. The project has a history. Saying it shouldn’t be the priority requires someone to absorb the political cost of saying so.

We often avoid this conversation indefinitely. The cost is paid in diluted execution and a team that has quietly stopped believing that stated priorities mean anything.

3. Never asking what to stop

Prioritization conversations almost always focus on what to add. What new initiative, what new goal, what new commitment deserves attention this quarter. Rarely does the conversation start with: what are we going to stop doing to make room for this?

Every yes without a corresponding no is a budget overcommitment. The capacity is finite. The calendar is already full. Adding something without removing something isn’t prioritization. It’s optimism with a project plan attached.

The question most leaders never ask of themselves or their teams is the one that unlocks the calendar: what would we have to stop doing to make this the thing we actually work on? The answer to that question is the real prioritization decision. Everything before it is preparation.

The Napkin Sketch Tool: Three Lenses, One Honest Calendar

Not one framework, three lenses that work at different levels of the problem. Use the one that fits where you are, or run all three in sequence.

Lens 1. The Values Filter: What Should Actually Be on Your Calendar?

Before any matrix or model, one question. Answer it honestly and with actual data rather than memory:

If I looked at my calendar from the last 90 days and circled every hour that went toward my stated top priority, what percentage would that be?

Don’t estimate. Look.

The gap between that number and what you’d want it to be is the prioritization problem in its most honest form. The stated priority and the lived priority are different things. The calendar is telling you which one is real.

Three questions to run the filter:

What is the one thing that would change everything else if I moved the needle on it this quarter? Not the five things. The one. The answer usually exists and is usually uncomfortable, because committing to it means admitting that the other things have to wait. Most of us know the answer (if we ask). Most leaders haven’t said it out loud in a way that commits them to it.

What on my calendar is there because it’s genuinely important versus because it has always been there? The recurring meeting that nobody questions. The standing call that has outlived its purpose. The obligation that calcified into a fixture two years ago and has never been reviewed. When did you last ask whether it still deserves the hour?

What am I doing that someone else could do and what am I not doing that only I can do? The answer to the second question is where the strategic work lives. The answer to the first question is where the calendar space comes from to do it. Both answers require honesty that most leaders find uncomfortable because the first answer implicates either their delegation or their trust in the people around them.

If the values work from earlier in this series (the values audit, the operating system check) revealed what you stand for, this filter is where that shows up in practice, on a Tuesday, when the inbox is full and the meeting request is pending and the choice is right in front of you. The values don’t live in the document. They live in the decision.

Lens 2. The Impact/Effort Matrix: How to Choose Between Competing Initiatives

When the question isn’t what to focus on personally but which initiatives deserve the organization’s attention, the impact/effort matrix makes the trade-offs visible enough to have an honest conversation about.

Two axes. Four quadrants. Simple enough to run on a whiteboard in an hour.

High impact, low effort. Do these first. They’re the quick wins that build momentum, demonstrate that focused execution works, and buy political capital for the harder conversations about the high-effort initiatives. Don’t skip them in pursuit of the ambitious. Momentum is a resource.

High impact, high effort. These are the strategic investments. They deserve genuine resource commitment and protected time. They should be few (one, possibly two, per quarter) because they will always consume more than projected. These are the initiatives worth the trade-off conversation. Make it explicitly.

Low impact, low effort. Do these only after the first two quadrants are served. They’re not the priority. They’re the backfill. Treat them accordingly.

Low impact, high effort. Stop doing these. This is the hardest quadrant to act on because these initiatives always have a history, a champion, and a rationale for why they belong somewhere else on the matrix. They don’t. Name them, thank them for their service, and remove them from the plan.

The matrix is most valuable as a group conversation tool. Running it alone in a spreadsheet produces a tidy grid. Running it in a room with the people who champion each initiative produces the honest conversation about trade-offs that most organizations never have. The discomfort of that conversation is exactly the point. The values of the organization reveal themselves not in the aspiration but in the trade-off. What gets moved to the top of the matrix and what gets moved out tells you more about what the organization actually values than six months of strategy discussions.

Lens 3. The Hyper-Focus Framework: What If You Said No to Everything Else?

This is the most powerful lens and the most avoided, because it requires the most honest answer to the most uncomfortable question.

The premise: you probably already know what you should be working on. The problem isn’t that the answer is hidden. The problem is that committing to it means admitting that everything else has to wait. And most leaders would rather stay busy across many things than be accountable to one.

Four questions. Write the answers down. Don’t rush through them.

What is the one non-negotiable thing I must achieve in the next 90 days?

Not the five things. Not the strategic priorities. The one thing: the thing that if achieved would make the other things either easier or less important. The commitment test is simple and unambiguous: is this goal so important that if I hit it, the other dreams can wait? If the answer is no, you haven’t found the one thing yet. Keep going until you can answer yes without qualification.

The one thing must be a single, non-negotiable sentence. Not a paragraph. Not a direction. A sentence. If it takes more than one sentence to describe, it’s still two things.

How will I know I’ve achieved it?

The finish line: the undeniable, quantifiable proof. Not a feeling of progress. Not a sense of momentum. A number, a milestone, a verifiable outcome that leaves no room for interpretation. Revenue of X. Client retention above Y. Product launched by Z date. If you can’t describe it in one sentence, the goal isn’t clear enough to execute on and the team won’t know when they’ve won.

What are the two or three leading indicators that tell me I’m on track before I get there?

The early signals: the things that will move first if the work is working. These are what you check weekly, not quarterly. They’re the difference between navigation and postmortem. A leading indicator answers the question: if we’re heading in the right direction, what will we see change first? If the only thing you’re measuring is the final result, you’ll find out too late to change course.

What has to stop (or be delegated, or be deprioritized) to make room for this?

This is the question the other three are building toward. Every hour the one thing needs has to come from somewhere. The calendar doesn’t have spare capacity waiting to be discovered. It is already full. Name specifically what moves, what gets delegated, what gets removed. The hyper-focus exercise is complete when you can answer this question specifically. Until then, you have a goal and a full calendar with no ability to be successful, which is what you had before.

Leaders who complete this exercise honestly report the same thing consistently: they already knew the answer. The framework didn’t reveal the priority. It gave them permission to commit to it and showed them what it would actually cost to do so.

The Courage Section

Every prioritization framework assumes the leader is making choices in a vacuum. They aren’t.

They’re making choices inside an organization with politics, with relationships, with people whose initiatives will be deprioritized and who will notice and who will have opinions. The courage required to say no to the senior stakeholder’s project, to the meeting that has been on the calendar since before anyone remembers why, ot to the initiative that everyone agrees sounds worthwhile but that isn’t the most important thing right now, is not something any framework provides.

It is provided by clarity.

The leader who is genuinely clear on what matters most finds the “no” more accessible than the leader who is still deciding. The no is easier when the yes is unambiguous. When you know what you’re protecting and why, the request that threatens it stops being a difficult conversation and becomes a straightforward one: I can’t do that right now because I’ve committed to this, and here’s why this is the right call for us.

Most reasonable people, given a clear rationale connected to shared goals, can accept a no. What they can’t accept and what erodes trust faster than any single decision is the vague deferral, the “let me check my calendar”. Clarity is kinder than accommodation. A clear no respects everyone’s time more than an optimistic yes that the calendar can’t support.

The matrix gives you the visual. The values filter gives you the diagnostic. The hyper-focus framework gives you the commitment. The courage to act on all three is what makes this a prioritization practice rather than a prioritization exercise.

That courage isn’t a personality trait. It’s what clarity produces.

Monday Move

One question to ask: Pull your calendar from the last four weeks. Circle every hour that went toward your stated top priority. Calculate the percentage. Then ask yourself: if my calendar is a declaration of my values, what is it declaring?

One behavior to stop: Stop letting urgency set the agenda by default. The next time a new request arrives such as a meeting invite, project addition, or escalation, pause before accepting and ask: is this genuinely important, or is it urgent? Urgent and not important has a different answer than urgent and important. Make the distinction deliberately. The default is always yes. The deliberate choice is the prioritization.

One action this week: Run the hyper-focus exercise. One non-negotiable goal for the next 90 days. One sentence, write it down. Then answer the question most people skip: what has to stop, or be delegated, or be removed from the calendar to make room for this? Name it specifically. Make the calendar change before the week fills up again. The goal without the calendar change is a wish. The goal with the calendar change is a plan.

Last Call

Claire eventually looked at her calendar.

Not in the vague way leaders look at their calendars scanning for conflicts, checking the time of the next thing. She actually looked at it. Printed four weeks. Categorized every hour. Added up the columns.

The number was not good. She had spent approximately four percent of her working hours in the last month on the thing she had told her team, twice, at the all-hands, was the priority.

She sat with that for a while and finally accepted change was needed.

Then she did something simple and difficult: she named the one thing. One sentence. The commitment test. She ran through the hyper-focus questions and wrote the answers down for the first time. And when she got to question four “what has to stop to make room for this?”, she named the Wednesday cross-functional sync she’d been meaning to leave for six months. The vendor call she’d been taking out of politeness. The three operational reviews that her direct reports were capable of owning if she was willing to let them.

She didn’t restructure her entire calendar in an afternoon. She moved four hours. Four hours from things that were fine to the thing that was important. It wasn’t a transformation. It was a start.

The next week she moved four more.

By the end of the quarter, innovation had gone from four percent of her time to thirty. Not because her circumstances changed, but because she stopped waiting for them to change and started making the choices that the strategy had always required. It was one deliberate decision at a time, against the constant pressure of everything that felt urgent and wasn’t.

The calendar didn’t clear. It never does.

She just stopped letting it fill by default.

That’s the thing. The framework is the tool. The calendar change is the work. The courage to say this, not that, with clarity and without apology, is the practice.

It starts with looking at what your calendar is already saying.

And deciding if that’s what you mean.

If this landed, share it with a leader whose calendar and strategy deck are telling two different stories.

Share

There are two people I’m thinking about this week. One of Them I’d Call at 7pm. One I Couldn’t Find If I Tried.

The first: someone I worked alongside at a company we both left years ago. We disagreed (sometimes sharply) on direction, on approach, on what the right call was in rooms where the stakes were real. There was friction. There were moments where we had to say hard things to each other and come back to the table anyway. The working relationship was not always smooth.

Next week, we’re getting on a plane together for vacation.

The second: someone I also genuinely liked. Pleasant to work with. Talented. The kind of colleague you’d describe warmly at a happy hour. But somewhere underneath the working surface, the trust never fully formed. Feedback landed sideways. Conversations about direction weren’t real discussion. No friction, no disagreement, and no depth.

I couldn’t tell you their current role or company.

Same chapter of my career. Same general era. Two completely different endings. For a long time I chalked it up to chemistry. That mysterious variable that determines who you click with and who you don’t. It took a lot more years to understand that chemistry had almost nothing to do with it.

The Deconstruction: What “Professional” Actually Cost Us

Here’s the rule we absorbed alongside our first business casual wardrobe:

Keep work relationships professional. Don’t blur lines. Functional is fine.

It arrived dressed up as wisdom. It was advice about appropriate distance, about not oversharing, about maintaining the kind of clean separation between personal and professional that would protect you if things went sideways. And on its face, it’s not wrong. Boundaries matter. Context matters.

But here’s what that rule quietly encouraged underneath: optimize for smooth. Keep the surface frictionless. Avoid the conversations that might make things uncomfortable, because discomfort is unprofessional, and professionalism is the goal.

The cost of smooth is depth. And without depth, there’s nothing to hold a relationship once the job, the company, and the org chart disappears. The relationship was a wall that turned out to be decorative versus load-bearing. The moment the building changed, it didn’t come with you.

The relationships I’ve watched fade weren’t bad ones. They were pleasant ones. Functionally successful ones. They just had no real foundation underneath the work, because we’d been so carefully trained not to build one.

The Shift: Conflict Was the Point, Not the Problem

I hired someone once. Built a team around them. Gave them feedback that was genuinely difficult to deliver. The kind where you have to decide if the relationship can hold the weight of the truth. It could. They pushed back sometimes. We disagreed on direction more than once. I eventually handed the whole team over to them when I left.

They’re the person whose place I’m staying at next week.

What I understand now that I didn’t then: the conflict wasn’t a tax we paid on an otherwise good relationship. It was the relationship. Every time we named the hard thing instead of smoothing it over, we were making a deposit into something that had nothing to do with the company we worked for. We were building actual trust, the kind that doesn’t expire when the job does.

The relationships that didn’t survive weren’t the difficult ones. They were the ones where we never got difficult at all. Where the feedback deflected instead of landed. Where the energy in the room shifted when the conversation got honest. Where I came away from certain interactions with a low-grade sense that we were both performing collaboration rather than actually doing it.

You can feel the difference. Most people just don’t trust that feeling enough to name it.

The Reframe: It’s the People that Matter

Here’s the reframe, and it’s less about being a good person and more about understanding what you’re actually building:

The ladder is temporary. The people on it with you are not.

The promotion you were both up for in 2018 is irrelevant now. The reorg that reshuffled everything? Irrelevant. The project that almost ended badly? Irrelevant. What remains is the person, and the question was always whether you treated them like one.

Some practical translations:

Conflict is not the opposite of a good relationship. Avoided conflict is. The relationships that have lasted longest in my life are not the ones that were easiest. They’re the ones where we could say the hard thing and both come back to the table. If you find yourself only having comfortable conversations with someone, you haven’t tested the relationship yet. You’ve just been maintaining the surface.

Feedback tolerance is the most important signal you’re not watching. Someone who can’t receive feedback without deflecting, defending, or going quiet isn’t telling you something about their personality. They’re telling you something about their priorities. They value their self-image over the relationship. Which means the moment the relationship requires them to be uncomfortable, they’ll choose themselves. That’s not a character flaw. It’s just information. Pay attention to it early.

Real over smooth, every time. You don’t build a lasting relationship by being professional. You build it by being real. Appropriately, within context and with judgment, but real. People forget most of what you delivered. They remember, with surprising precision, how you made them feel. Whether they felt seen. Whether you told them the truth. Whether they could trust that what you said in the room was what you actually thought.

The ROI shows up later and it doesn’t look like a performance review. It looks like a travel companion. A spare room in someone’s home. A phone call at 7pm when you’re navigating something hard and you need someone who knew you before the current chapter. It doesn’t show up on a resume. It shows up in the life you’re actually living twenty years from now.

You cannot manufacture this retroactively. You build it in the ordinary moments: the feedback you gave honestly, the conflict you didn’t avoid, the time you stayed in the conversation when leaving would have been easier.

The Closing Shot

Next week I’m getting on a plane with the evidence that how you treated people mattered. Not as a career strategy, but as a life one.

The ROI isn’t on the resume. It’s in the boarding pass.

The promotions came and went. Most of us are at different companies now. What actually transferred, what followed us out of every org chart and into the rest of our lives wasn’t the title. It was the people we were real with when it was hard. Start with those. Build from there.

Share

Subscribe now

At mile thirty of a hundred-mile race, something happens that no training plan fully prepares you for.

The finish line. The thing that got you out of bed at 4am for eighteen months of preparation and that sat on your refrigerator and your screensaver and in the back of your mind during every hard training run is suddenly theoretical. Not gone, but just very, very far away. And the terrain between you and it has stopped resembling the map.

The ultra-marathoner who survives mile thirty isn’t the one with the clearest vision of the finish line. It’s the one with a race plan broken into segments, paced against terrain, adjusted at checkpoints, and built to survive the moment when the original plan meets the actual mountain.

The finish line is the destination. The race plan is how you actually get there.

Remove the race plan and leave only the finish line, and you don’t have a runner with a vision. You have someone standing at the start with good intentions and no idea what to do when the weather changes at mile forty-seven and the path they’d planned stops making sense.

Most organizational visions are the finish line without the race plan.

Leaders spend significant time crafting the vision. The right words, the right aspiration, and the right balance between ambitious and achievable. They present it at the all-hands, reference it in the quarterly business review, put it on the website. Then they return to their offices, and somewhere between the announcement and the execution, between the leadership offsite and the team standup on a Tuesday morning, the thread gets lost.

By the time the vision reaches the person doing the work, the one whose daily decisions will either move the organization toward it or quietly away from it, it has been translated six times, diluted twice, and now exists somewhere in the space between “grow the business” and “don’t mess anything up.”

The vision didn’t fail. The translation system was never built.

The Lie We Tell Ourselves

“We communicated it. They know the direction.”

Communication and comprehension are not the same thing. Announcing a vision is not the same as translating it. Most people in an organization can recite the company’s stated priorities when asked. Far fewer can explain in one sentence, without a slide deck, without a moment of hesitation, how what they’re working on today connects to that priority.

The gap between those two things is the vision not sticking.

The second version of the lie is subtler and more common among leaders who have actually thought hard about strategy: “They’re not aligned because they don’t understand the strategy.”

Often the real problem is different. They understand the strategy fine. They just don’t see how their work connects to it. Understanding and connection are not the same problem and they don’t have the same solution.

Understanding is a communication problem. You fix it with better messaging, clearer narrative, more consistent reinforcement of the direction.

Connection is a translation problem. You fix it with better systems. The graduated cascade from annual direction to quarterly commitment to weekly priority that gives every person in the organization a visible thread between what they’re doing today and where the organization is trying to go.

Most leaders invest heavily in the first fix and barely at all in the second. The vision gets communicated more clearly, more often, with better slides. The translation system never gets built. And the gap between the boardroom and the person doing the work stays exactly where it was.

The Autopsy: Three Reasons Visions Evaporate

1. The vision lives at the wrong altitude

Most vision statements operate at the level of aspiration. Be the leading provider of X. Transform Y for customers. Build the organization people are proud to be part of. These aren’t wrong, aspiration is the point. But aspiration without graduated translation is the space station without a landing strip.

The team can see the sky. They cannot find the runway.

The distance between transform how our customers experience financial services and what should I prioritize in my sprint this week is not a distance most teams can cross on their own. Without something in between such as annual anchors, quarterly commitments, team-level objectives that connect explicitly to the direction, the vision floats above the work, inspiring in the abstract and useless in the specific.

What organizations need is not a better vision. They need a better ladder between the vision and the Tuesday.

2. The objectives aren’t owned, they’re assigned

There is a meaningful difference between a team that has been handed an objective and a team that has participated in defining how they’ll contribute to one. The first executes. The second is committed. Both look the same for the first few weeks. By month three, they look very different.

When people own the metric, when they’ve had a hand in defining what success looks like and how they’ll pursue it, their focus increases in a way that assignment cannot produce. They make better decisions under pressure because they understand the intent, not just the instruction. They flag problems earlier because they care about the outcome, not just the deliverable.

This is not an argument for endless collaboration or consensus by committee. Leadership still sets the direction. The question is whether teams are empowered to define how they’ll contribute to it. Or whether the how arrives from above, already decided, already allocated, already owned by someone else before the team ever touched it.

The organizations where vision sticks are almost always the ones where the answer to what are we doing this quarter and why was partly shaped by the people being asked to execute it.

3. The cadence is wrong

Annual planning in a world that changes quarterly is a calendar problem disguised as a strategy problem.

The direction set in January may be exactly right. The tactics decided in January to achieve that objective are almost certainly at least partially wrong by April. The market shifts, competitors move, and each quarter teaches the organization something it didn’t know when the plan was made. Without a regular cadence of genuine recalibration, the organization keeps executing a plan that has stopped fitting the terrain. This is not just tracking against targets, but honestly asking is this still the right thing to be doing.

The ultra-marathoner doesn’t check the map once at the start and then run. They check it at every aid station, adjust for what’s changed, and make the call on whether the next segment of the plan still makes sense given what the previous segment taught them. The discipline of that recalibration, not the original plan, is what gets them to the finish.

The Napkin Sketch Tool: Vision Narrative Canvas + OKRs

Two tools, run in sequence. The first makes the vision translatable. The second makes it executable.

Part 1: The Vision Narrative Canvas

Before any goal-setting framework, the vision needs to be expressed in a form that can cascade. So that it can travel from the leadership team through the organization and arrive at the team level still meaningful and still connected to the original intent.

Four questions. Every leader should be able to answer them. More importantly, every leader should be able to help their team answer them.

What are we here to do?

The purpose: the why that doesn’t change even when the strategy does. NASA’s purpose was space exploration. That purpose survived the moon landing and every subsequent shift in how they pursued it. Nike’s purpose is inspiring athletes. That purpose survived multiple strategy pivots, divestitures, and market shifts. The purpose is the anchor. Everything else, the strategy, the objectives, the tactics, is how you pursue it in this particular moment.

If your team can’t articulate the purpose without reading from a website, the cascade hasn’t started yet.

What are we trying to achieve right now?

The direction: the what for this period. Specific enough that people can point to it, ambitious enough that it actually moves something, time-bound enough that it creates urgency without becoming wallpaper. This is where the vision lands closest to the work. The thing that, if achieved in the next twelve months, represents genuine progress toward it.

A good direction statement passes the how will we decide test: if you can use it to resolve a resource conflict or a prioritization debate (which of these two options gets us closer to where we said we’re going right now?) it’s specific enough. If it doesn’t help you decide, it isn’t specific enough.

Why does this matter to the people doing the work?

This is the question most leaders skip, because it feels like motivation rather than strategy. It is both. The connection between the direction and the individual: what this means for the person doing it, why their specific contribution matters to the outcome. This is not a feel-good addition to a strategy document. It is the mechanism that turns comprehension into commitment.

The manager in customer support who’s been asked to work on an internal initiative doesn’t need a memo explaining the strategy. They need to understand how this initiative connects to something they care about: the customer experience, the team’s ability to deliver, or the problem they came to work every day to help solve. Without that connection, they execute the task. With it, they pursue the outcome.

How will we know we’re moving toward it?

The leading indicator, not the final result, but the early signal that tells you you’re on course before the results arrive. This is the question most leaders answer last and think about least, and it’s frequently where the translation system collapses.

If the only signal is the end-of-year result, the team is flying blind from January to December. They’re working hard, delivering against tasks, and have no idea whether what they’re doing is moving the needle until it’s too late to change course. The leading indicator, the metric that moves first and predicts the result, is what allows for real-time navigation rather than annual postmortem.

Get clear on this before you set the goals. It changes both what you measure and what you decide to do.

Part 2: OKRs — The Translation System

Once the vision is expressible, once the four canvas questions have clear answers, you need a mechanism to translate it into owned, executable commitments at every level of the organization. That mechanism is OKRs: Objectives and Key Results.

The framework is simple. The discipline required to use it well is not.

The Objective: what are we trying to achieve?

Qualitative and aspirational. Inspiring enough that people know why it matters. Specific enough that everyone is pointing at the same thing. Action-oriented, it starts with a verb and names a direction, not a state.

Dominate the enterprise segment in the Pacific Northwest is an objective. Be good at enterprise sales is not. It describes a characteristic, not a direction, and you can’t point to it when a resource conflict needs resolving.

The Key Results: how will we know we achieved it?

Quantitative, outcome-focused, verifiable. Three to five per objective, maximum. Not tasks, but evidence. This is the distinction that separates the organizations that use OKRs from the ones that are OKR-driven.

Launch three new ad campaigns is a task. If you launch them and nothing changes for the business, you’ve succeeded by this measure and failed by any measure that matters.

Generate 1,500 qualified leads from new campaigns is a result. It can be verified. It connects the work to the outcome. It answers the question: if we do this and it works, what will be different?

Always ask: if we complete this and nothing changes for the customer or the business, have we actually succeeded? If the answer could be yes, you have a task masquerading as a key result. Replace it.

Three principles that make OKRs actually work:

Ruthless focus. Three to five objectives per quarter, maximum. This constraint is the feature, not the limitation. The organizations that struggle with OKRs are almost always the ones that treat them as a comprehensive list of everything they’re working on rather than a declaration of what matters most. Saying yes to the most important things is only possible if you’re genuinely willing to say no to everything else. That willingness is harder than it sounds and more important than it looks.

Bottom-up ownership. Leadership sets the direction. Teams define how they’ll contribute. This is the step that converts assignment into ownership and execution into commitment. Give teams the quarterly intent (our priority this quarter is to stabilize churn to build the foundation for growth) and ask them to draft their own objectives in response. What they come back with will often be more creative and more specific than what a top-down allocation would have produced. And they’ll defend it when it gets hard, which top-down assignments rarely survive.

Regular cadence. The plan is not the strategy. The cadence that keeps the plan honest as the terrain changes is the strategy. Weekly check-ins: fifteen minutes, confidence scores, obstacle identification. Mid-quarter reviews that ask not just how are we tracking but is this still the right thing to be tracking. Quarterly retrospectives before the next cycle begins, so the learning from this quarter shapes the direction for the next one.

An OKR that sits in a spreadsheet unread is not a management system. It is a document. The cadence is what makes it a system.

A Note on What Vision Actually Requires

The vision is not for the leader. It’s for the people executing it.

This sounds obvious. It is rarely practiced. Most vision work is done in a room with the people who already understand the direction and need it least. The test of a vision isn’t whether the leadership team can articulate it; they’re the ones who built it. The test is whether the person three layers below, making daily decisions that either serve or undermine the direction, can articulate how what they’re doing today connects to where the organization is trying to go.

That person is the finish line of the translation system. Everything between the boardroom and their desk is the work. If the thread makes it to them, clear, specific, owned, and connected to something they care about, then the vision sticks. If it doesn’t, the vision lives in slide decks and lobby walls and quarterly all-hands presentations, inspiring in the abstract and absent from the actual work.

The ultra-marathoner finishes because they have both the vision of the finish line and the system that gets them there one segment at a time. The vision without the system is a beautiful destination with no road to it.

Build the road.

Monday Move

One question to ask: Can every person on your team answer, in one sentence, how their current work connects to the organization’s top priority right now? Not the mission statement, but the current priority. If you’re not sure, ask one of them today. Their answer will tell you more about how well the vision has been translated than any strategy document or all-hands replay.

One behavior to stop: Stop treating the annual plan as the strategy. The plan is what you decided in January. The strategy is what you do in April when the plan meets the terrain and one of them has to give. Build the review cadence before you build the plan. Without it, the plan becomes a document you defend rather than a direction you navigate.

One action this week: Run the four Vision Narrative Canvas questions on your current priorities. What are we here to do? What are we trying to achieve right now? Why does this matter to the people doing the work? How will we know we’re moving toward it? Write the answers in one sentence each. If any of them takes more than one sentence, then that’s where the vision is evaporating. And that’s where to start.

Last Call

At mile eighty of a hundred-mile race, the finish line is no longer theoretical. It is close enough to be real, far enough to be genuinely in doubt. Every runner at mile eighty has a vision. Not all of them have the system that gets them there.

The ones who finish are the ones who built the race plan, ran the aid station check-ins, adjusted for the terrain they didn’t predict, and kept the thread intact between the destination and the next mile marker. They didn’t run the finish line into existence through vision alone. They ran it one committed, recalibrated segment at a time.

That’s the work of leading the system. Not the announcement, the translation. Not the destination, the road. Not the aspiration, the owned, specific, regularly recalibrated commitment that connects what happens on a Tuesday to where the organization decided it was going.

Your vision is probably fine. The road between it and your team’s Tuesday is where the work is.

Build the road. Check it regularly. Adjust when the terrain changes.

The finish line will still be there.

If this landed, share it with a leader who has a vision worth translating.

Share

Picture Rocky Balboa on the steps of the Philadelphia Museum of Art.

Arms raised. Bill Conti’s horn section swelling. Months of brutal training compressed into three minutes of screen time. The raw eggs, the frozen meat, the pre-dawn runs through the streets of Philadelphia, all of it building to that single triumphant image of a man who has been transformed.

We grew up on this. The Karate Kid gave us Daniel LaRusso waxing cars and painting fences, and then suddenly a karate master, ready for the tournament. Can’t Buy Me Love gave us Ronald Miller, one wardrobe change away from social transformation. The 80s and 90s handed us a very specific story about how growth works: it happens in a sequence, it’s set to music, the camera pulls back at the end, and when it’s over, everything is different.

Now Instagram serves us the updated version. The 30-day transformation. The silent retreat that rewires your nervous system. The course, the certification, the program that promises to make you a new person by next quarter. Same story. Better lighting. Still a lie.

Because here is what the montage always skips: the part where Rocky loses the fight.

Not the training. The actual fight. Apollo Creed wins by split decision. Rocky doesn’t get the triumphant ending the training sequence promised. He goes the distance, he stays on his feet, and he finds Adrian in the crowd. That’s the real ending. The montage prepared you for a version of the story that didn’t happen, and somehow we remember the steps, not the scoreboard.

Your career is going to work exactly like that. And nobody told you.

Subscribe now

The Deconstruction: Three Versions of the Same Lie

Here’s the story that got installed somewhere between the movies and the motivational content:

Growth is linear. Transformation is visible. Setbacks mean something went wrong.

It arrives in three costumes, and all three of them will cost you something.

The first: expecting the straight line. The plan was up and to the right. You’d get better, get recognized, and then get promoted. Each year a little further along the arc than the last. And then something didn’t go according to that plan. Instead of reading it as a normal part of any real career, you read it as structural failure. Evidence that something was wrong with you. Proof that you’d reached the ceiling.

The straight line was always fiction. Real careers move in spirals, in detours, in sideways moves that look like regression until you’re far enough past them to see what they actually were.

The second: the setback as verdict. The layoff. The project that failed publicly. The role that didn’t work out. We are trained to read these as the story ending, as the moment the narrative reveals where you top out. We are not trained to read them as redirects. As the thing that closes a door so forcefully that you finally notice the other doors.

The setback is data. It is almost never the verdict. But in the moment it arrives, it feels exactly like one. That feeling is what makes the montage lie so expensive. You were supposed to be on the steps by now. Instead you’re back at the bottom of the run, and you can’t hear any music.

The third: waiting for the click. The 30-day program will change you. The retreat will rewire you. The course will unlock the next version. We keep looking for the transformation that arrives all at once. The moment everything clicks into place and the new chapter begins cleanly. Real growth doesn’t work like that. It accumulates slowly, quietly, often invisibly. Then one day you look back and realize you are not the same person who started, and you can’t point to the moment it happened because there wasn’t one. There were hundreds. None of them felt significant at the time.

The Shift: The Detour Was the Route

I’ve had a few versions of the setback. Two in particular still teach me things when I think about them clearly.

The first was a voluntary one: taking a role with a lower title to learn something new. On the org chart, it looked like regression in the currency that professional culture actually trades in: title, seniority, the visible upward line. It looked like the wrong move. And I felt that. The gap between where I was supposed to be and where I was sat in my chest in an uncomfortable way for longer than I’d like to admit.

What it was, in retrospect, was the most important investment I made in that chapter of my career. The thing I went to learn turned out to be foundational to everything that came after. The step back created the range that the straight-line path never would have.

The second wasn’t voluntary. A layoff. It doesn’t care about your plan or your timeline or what you thought was coming next. Disorienting because you didn’t choose the door, it just closed.

What came through the opening was an opportunity I never would have known existed if I’d stayed on the path I was on. The role and the kind of work that doesn’t appear on the straight-line route. I didn’t see that on ramp when I was on a different highway.

Neither of these felt like growth while they were happening. They felt like the music stopping. The arc only became visible in retrospect, which is exactly how non-linear growth works. You can’t see the shape of it while you’re inside it. You can only see it from the other side, looking back at a path that makes sense now and made no sense then.

That is the thing the montage cannot show you. Not because the filmmakers didn’t want to, but because it only becomes legible in reverse. And you are always, while you are living it, in the forward direction.

The Reframe: Non-linear is the only path

Here’s the reframe, and it is the one I come back to every time something goes wrong in a way I didn’t plan for:

Non-linear is not the same as lost.

The plateau is not failure. The step back is not regression. The layoff is not the verdict. These are the parts of the architecture that the straight-line story doesn’t have room for. The fact that they feel like derailment is a function of the map you were given, not the territory you’re actually moving through.

Some practical translations:

Read the setback before you conclude anything. When something goes wrong, a role doesn’t work, a project fails, or a door closes, resist the impulse to immediately interpret it as a verdict on your ceiling. Ask instead: what is this redirecting me toward? What door does this close that I needed closed? What is now possible that wasn’t before? You won’t always have the answer right away. That’s fine. Sit with the question longer than feels comfortable.

The 30-day transformation is a product. Buy it if it teaches you something useful. Don’t expect it to replace the slow accumulation that actual change requires. The real transformation is happening in the background all the time. It’s in the hard conversations you don’t avoid, the projects you stay in past the point of comfort, and the opinions you state before you feel qualified. That’s the montage you can’t see while it’s happening. It’s also the only one that’s real.

A step back can be a strategic move. The lower title, the smaller company, the lateral move into territory you don’t know yet…the professional culture that rewards the visible upward line will not validate these choices. Do them anyway, if the learning is right. The range you build in the detour is often the thing that makes the next chapter possible. The org chart is not the only way to measure forward.

The career you’re building will not look like the plan. Not because you planned wrong, but because you are building it with information you didn’t have at the start. In a world that keeps changing its terms, you’ll always be a person who keeps becoming someone slightly different than the person who made the plan. That’s not failure. That’s a career. That’s life.

And when the music stops, when the setback arrives and the steps feel very far away and there is no triumphant horn section in sight, remember that Rocky didn’t win the fight. He went the distance. He stayed on his feet through the unglamorous middle that no montage can compress.

That’s what growth actually looks like. It’s just harder to set to music.

The Closing Shot

The montage gave you a story about transformation that leaves out the part you’re probably in right now.

The plateau. The detour. The door that closed without asking. The slow, invisible accumulation that won’t reveal its shape until you’re standing somewhere you didn’t plan to be, looking back.

That’s not the absence of the story. That is the story.

Rocky went the distance. He didn’t win on points. He found Adrian in the crowd and that was the actual ending. Not the steps, not the music, and not the transformation complete. Just a man who stayed on his feet through something hard and came out the other side still standing. That’s the version worth training for.

Share

Watch her for a moment.

The room is not easy. A project has gone sideways and in a public way. The kind that involves stakeholders, missed commitments, and a team that is equal parts demoralized and defensive. She’s called the group together. They’re watching her.

This is leadership in difficult moments. It’s not for what she says, but for what she does before she says it.

She takes a breath. Just a beat, deliberate enough to be a choice rather than a reaction. Something shifts in how she’s holding the room before she’s said a word.

She starts by naming what happened. Not who caused it, just what happened. Specific, behavioral, without verdict. The team, braced for blame, relaxes slightly. She asks a question: what do we think got in the way? She listens to the answers. Actually listens, tracks the emotion underneath the words, notices the person in the corner who hasn’t spoken and whose silence is saying something. She asks them directly. Gently. The answer is more useful than everything else combined.

She doesn’t pretend the situation isn’t serious. She doesn’t cushion the standard. She names what needs to change and she states it clearly. But she frames it around where they’re going rather than where they failed, and somewhere in the framing the team stops being an audience for a difficult conversation and starts being participants in finding the way out.

The meeting ends. Something that was stuck starts to move. Not because she said the perfect thing, but because she was present enough, regulated enough, attuned enough to the people in the room that the conversation could go somewhere real.

If you’ve been reading this series, you know exactly what just happened. You watched the Ladder of Inference get checked before the story closed. You watched SBI land inside a high-stakes room. You watched the Trust Equation’s empathy variable show up in the question asked of the person in the corner. You watched the coaching posture hold the space open rather than filling it with answers.

You didn’t see a framework. You saw a leader. The frameworks were underneath, doing their quiet work, the way a foundation does its work. Invisible when it’s solid, catastrophically apparent when it isn’t.

That’s what emotional intelligence looks like when it’s working. Not a personality type, not a natural gift. A set of skills, built deliberately, practiced consistently, visible in the specific choices made in the moments that matter most.

We’ve been building them for last eight articles. This is what we’ve built.

Subscribe now

The Lie We Tell Ourselves

“Either you have it or you don’t.”

It is the most limiting belief in leadership development and the one most likely to go unexamined, because it masquerades as self-knowledge. The leader who says “empathy isn’t really my strength” or “I’m just not naturally attuned to the emotional side of things” sounds like someone who knows themselves well. They’re actually someone who has filed an undeveloped skill under a fixed trait and stopped there.

EQ gets treated as temperament. The warm leader, the emotionally attuned one, or the person who just naturally reads rooms well. Which means leaders who don’t naturally operate that way file it under “not how I’m wired” and move on, leaving the most important variable in their leadership effectiveness unexamined and largely undeveloped.

The second version of the lie, equally persistent: “EQ is about being nice.”

It isn’t. The conflation of emotional intelligence with agreeableness is one of the most reliably wrong ideas in professional development. High EQ leaders are not necessarily warm, easy, or conflict-averse. They are clear, accurate, and effective across the full range of human situations. Including the hard ones, especially the hard ones. The leader who had the crucial conversation in the last chapter wasn’t being nice. The manager who finally stopped doing the 9pm edits and gave real feedback wasn’t being nice. The leader who named their role in the Drama Triangle and changed their behavior wasn’t being nice.

They were being emotionally intelligent. Those are not the same thing.

Every difficult moment in this series has been an EQ moment. Every piece of feedback that landed. Every ladder descended before acting on a story. Every coaching question asked instead of answered. The skill running underneath all of it wasn’t warmth. It was intelligence applied to the emotional and relational dimension of the work, with exactly the rigor most leaders reserve for the technical dimension.

The Framework You’ve Already Been Building

Daniel Goleman’s research on emotional intelligence identified four domains. Two that govern how you manage yourself, and two that govern how you manage your relationships. They build on each other in sequence. And if you’ve been following along, you’ve been developing all four without necessarily having a name for them.

Here they are. With everything you’ve already built mapped inside them.

Domain 1: Self-Awareness

Knowing what you’re feeling, why you’re feeling it, and how it’s affecting your thinking and behavior in real time. Not in retrospect but in the moment while it’s happening, before it becomes your response.

This is the foundation domain. Nothing else works without it. You cannot manage what you cannot see. You cannot read a room accurately if you’re unaware of how your own emotional state is filtering what you perceive. You cannot build real relationships if the version of yourself you’re presenting has never been honestly examined.

The work we’ve already done here:

The personal retrospective and values audit were the beginning. They’re honest examination of where you actually are, not where you intend to be, against the values that are supposed to be running your operating system. The Ladder of Inference work was self-awareness in real time. The practice of noticing when you’ve started filling in gaps with story rather than data, catching it before it becomes a decision. The Drama Triangle work required you to identify your role in a dynamic while you were in it, which is one of the harder self-awareness moves available.

Self-awareness is the domain most leaders overestimate in themselves. The gap between how leaders rate their own self-awareness and how their teams experience their leadership is one of the most consistently documented findings in leadership research. Self-awareness is genuinely difficult and the feedback loops that would correct it are often absent or muted.

The practice: the retrospective isn’t a year-end event. It’s a weekly question. What did I bring into that room that wasn’t about what was in the room? Asked honestly, consistently, over time and that’s the self-awareness muscle being built.

Domain 2: Self-Management

The space between stimulus and response is where leadership actually lives. Self-management is what happens in that space. It’s the regulation of your emotional response well enough to choose what comes next rather than simply react to what just happened.

This is not suppression. The leader who flattens their emotional response until nothing shows is not demonstrating self-management. They’re demonstrating disconnection, and their team reads it as such. Self-management is the ability to feel the thing and still choose the response. To be frustrated and stay curious. To be anxious and stay regulated. To be under pressure and remain present.

The work you’ve already done here:

The ownership absorption chapter was self-management at its most foundational. Learning to distinguish between what’s yours to carry and what isn’t, and putting down what belongs elsewhere before it becomes your team’s problem. The crucial conversation work was self-management under fire. Staying regulated enough to say the thing that needed to be said to the person who made it most expensive to say. The Rescuer to Coach shift required self-management of the most seductive kind. Regulating the impulse to solve, which feels like helpfulness, in favor of the patience to ask, which feels like restraint but produces growth.

Self-management is where the work of self-awareness pays its first dividend. Awareness gives you the data. Management gives you the choice. The leader who can hold a difficult conversation without going silent or going aggressive, who can receive feedback without deflecting or collapsing, who can stay present in an ambiguous situation without defaulting to false certainty, is demonstrating self-management in its most practical and most visible form.

The practice: the next time you feel the pull of a strong reaction such as the urge to fix, to defend, or to close the conversation down, pause long enough to name what you’re feeling internally before you act on it. I’m feeling defensive right now. I’m feeling the urgency to solve. That naming is the gap. The gap is where the choice lives.

Domain 3: Social Awareness

Reading what’s actually in the room. Not what you expect to find. Not what confirms what you already think. What’s there in the emotional reality of the people in front of you, in the dynamic between them, and in the thing nobody is saying that is somehow present in every exchange.

Social awareness is the domain that most directly determines how good your data is. A leader who reads rooms accurately has better information than one who doesn’t. Better information about what the team actually needs, about where the friction is before it becomes a crisis, and about what the person across from them is experiencing beneath the surface of what they’re saying.

The work you’ve already done here:

The Ladder of Inference work built social awareness from the bottom up. The discipline of staying in observable data rather than rushing to interpretation, which is the prerequisite for reading others accurately rather than reading your own projections of them. The active listening work is social awareness in practice. Every time you ran that framework in a real conversation, you were developing the muscle for reading what’s underneath what’s said. The Trust Equation’s empathy variable is social awareness translated into behavior.

Social awareness is the domain that makes problems visible before they become crises. The leader with high social awareness notices the shift in the team before it calcifies into disengagement. They read the meeting for who’s present, who’s performing presence, who went quiet and why. They read it accurately enough to make a real-time adjustment. They hear what isn’t being said with the same attention they give to what is.

The practice: in your next meeting, spend the first five minutes watching before you lead. Not passively, but deliberately. Who is in the room? What’s the energy? What’s present that hasn’t been named? Let what you observe shape how you open rather than leading with the agenda you brought in.

Domain 4: Relationship Management

This is where the first three domains become visible to everyone else. Relationship management is the skill of taking what self-awareness, self-management, and social awareness give you and using it to build, maintain, and repair the relationships that make leadership possible. Deliberately, consistently, and across the full range of human situations.

It is the domain most visible to others and most invisible to the leader. It shows up in whether people bring their best thinking to you, whether they stay when they have options, whether they tell you the truth when the truth is uncomfortable. The cumulative score on relationship management is the answer to the question your team is always answering, even when nobody has asked it out loud: what is it actually like to work for this person?

The work you’ve already done here:

The Trust Equation: the full formula, including the denominator. Building credibility is relationship management. Managing self-orientation is relationship management. The work of identifying which variable is doing the damage in a specific relationship and addressing it directly, that’s relationship management applied with precision. The Drama Triangle and the Empowerment Dynamic were relationship management at the systemic level. Understanding that the roles you play are co-created with the people around you, and that changing your role changes the dynamic for everyone in it. The SBI feedback method is relationship management in its most practiced form. Delivering honest information in a way that the relationship can hold and the person can use. The crucial conversation was the hardest relationship management move. The willingness to say the thing to the person who makes it most expensive to say, because the relationship is worth the discomfort of honesty. The GROW model is the relationship management skill that compounds longest. The coaching conversation that builds capability in someone else, one question at a time, over a sustained period of investment.

The practice: at the end of each week, ask yourself one question about the most important relationship in your team or with your peers right now. What did I do this week that built that relationship? What did I do, or not do, that cost it something? The accounting doesn’t need to be formal. The noticing is what matters.

The Map You’ve Been Drawing

Here’s the all the tools we’ve discussed so far, mapped to the EQ domains.

You didn’t learn these as EQ skills. You learned them as tools for specific problems: the story you made up about your team, the trust that felt off, the meeting nobody wanted to be in, the feedback that wasn’t landing, the conversation you kept avoiding, the person you kept rescuing instead of developing.

The problems were real. The tools addressed them. And underneath all of it, in every chapter, the same four capacities were being built: knowing yourself, managing yourself, reading others, and building relationships that make the work possible.

That’s emotional intelligence. You’ve been doing it the whole time.

EQ Navigates in Every Direction

One more thing before the close, something the frameworks don’t always make explicit.

EQ isn’t applied uniformly. It navigates up, across, and down. And the application looks different in each direction.

Navigating down with your team: is the most practiced direction for most leaders. The majority of our recent articles lived here. The EQ challenge going down is self-orientation: staying genuinely focused on their development rather than your own comfort, your own efficiency, your own need to be the one with the answer. The tools were largely built for this direction. Use them.

Navigating across with your peers: is the direction most leaders underinvest in and most organizations undervalue. Peer relationships are where the Drama Triangle does some of its most reliable work in the background (the alliance that quietly becomes a triangle) and where the Trust Equation becomes most handy (the peer whose trust has been slowly eroded by a pattern neither party has named). The ability to read peer dynamics honestly before they become political problems and to name the thing between equals when there’s no hierarchy to fall back on is social awareness applied laterally. And it’s one of the most valuable and least developed EQ skills in most leadership teams. Invest in it deliberately.

Navigation up with your boss: is the hardest direction and the most avoided. The self-management challenge going up is regulating under a power differential: staying calm enough, clear enough, and courageous enough to say the thing that needs to be said to the person who holds significant influence over your career. Leaders with high EQ going up are not fearless. They are regulated enough to act despite the fear. That’s not a personality trait. It’s the practiced outcome of everything in this section applied in the hardest direction available.

The four domains are the same in every direction. The courage required to apply them changes with the altitude.

EQ Is a Practice, Not a Trait

Here is the most important thing I want to leave you with at the end of this section.

Emotional intelligence is not fixed. It is not a score you receive and carry unchanged through a career. It is not the exclusive territory of people who were born warm, or naturally empathetic, or instinctively attuned to the people around them.

It is a practice. Built through deliberate attention. Developed in real situations. Grown through exactly the kind of honest self-examination and behavioral change that is hard and uncomfortable and worth it.

Every retrospective run honestly is self-awareness being built. Every ladder descended before acting on a story is self-management being practiced. Every time you listened for the assumption underneath the question rather than just the question is social awareness being developed. Every coaching conversation held open when the instinct was to close it with an answer is relationship management being exercised.

That is the program. Not a two-day offsite. Not an assessment with a debrief. Not a competency framework filed in a drawer after the workshop ends. The real situations, engaged with real attention, over a sustained period of time. That’s real EQ development, and that’s the leadership job.

The research is clear and consistently underestimated: unlike cognitive intelligence, which largely stabilizes in adulthood, emotional intelligence is genuinely developable across a career. Leaders who commit to the practice demonstrate measurable improvement over time. The ceiling is not fixed. The work is never fully done.

Both of those things are true. Both of them are good news.

Because it means the gap between the leader you are and the leader you’re capable of being is not a personality problem. It’s a practice problem. And practice problems have a solution: keep going.

Monday Move

One question to ask: Which of the four domains is doing the most work for you right now? And which one, honestly, is where the friction in your leadership currently lives? Not the domain you’ve been told needs work. The one you know, in the specific recurring situation that keeps showing up, is where the gap is. Name it. That naming is self-awareness. Everything else builds from there.

One behavior to stop: Stop treating EQ as a fixed trait in yourself or in the people you lead. The next time you catch yourself saying “that’s just not how I’m wired,” reframe it: that’s a skill I haven’t practiced enough yet. One version is a ceiling. The other is a direction.

One practice this week: Pick one domain. Pick one tool from this section that lives in that domain. Run it deliberately in one real situation. Notice what’s different. Notice what’s hard. Notice what opens up that didn’t before. That noticing is the self-awareness that starts the cycle again. Which is, perhaps not coincidentally, exactly where this whole section began.

Last Call

Go back to the leader in the opening scene for a moment.

She wasn’t born knowing how to hold a difficult room. She wasn’t naturally attuned to the person in the corner whose silence was saying something. She didn’t arrive in the role with a fully calibrated self-awareness practice and a reliable self-management muscle and a set of relationship management skills that made the hard conversations feel manageable.

She built them. In the specific situations that required them, through the tools that gave them shape, over the years it took to move from recognizing the right thing to do to actually doing it reliably, under pressure, in the moments when it mattered most.

That’s the path. Not a straight one. Not a fast one. Not one that ends with a certification or a score or a completed curriculum. A path that runs through every difficult conversation, every honest retrospective, every moment you chose the question over the answer, every time you came down the ladder before you acted on the story, every piece of feedback you gave that cost you something to give and changed the relationship because of it.

Every chapter in this section was a step on that path. Every tool was a waypoint. Every Monday Move was an invitation to take the next step rather than read about it.

You know what the tools are now. You’ve seen them in practice, in the stories of leaders navigating real situations with real stakes and real people watching. You’ve been applying them in your own leadership, in your own team, in the relationships that determine whether the work you’re doing together becomes what it’s capable of being.

Next is where you take what you’ve built and turn it toward the system. It’s the vision that sticks, the decisions that scale, the operating rhythm that keeps the whole thing moving in a direction that matters.

But the system is only as strong as the leader at the center of it. And the leader at the center of it, the one who knows themselves, manages themselves, reads the room, and builds the relationships that make everything possible, that’s who you’ve been becoming.

The work continues. It always does.

That’s not a warning. That’s the point.

If this landed, share it with a leader who has been doing the work and is ready to see what they’ve built.

Share

Subscribe now

If you grew up on 80s, Brat Pack, and even 90s coming-of-age dramas, you absorbed a very specific story about your twenties.

The story went like this: somewhere inside you is the real, authentic, fully-formed version of yourself. Your job is to find her. The right experience will reveal her. The right person will see her. The right moment of clarity will finally confirm that you’e on the right path. That who you’re supposed to be is right there. And when you find her, she will be fabulous.

The pressure was immense and completely unexamined. We watched it play out on screen over and over. The confused young person, the search, the arrival of the self. It looked like a journey with a destination.

Demi Moore’s character Jules in St. Elmo’s Fire captured it with the kind of honesty those movies rarely allowed: “I never thought I’d be so tired at 22. I just don’t even know who to be anymore.”

That line hit different because it was true. The search was exhausting. And nobody stopped to ask whether the premise was wrong, whether there was a self to find at all, or whether the whole thing worked completely different than advertised.

Subscribe now

The Deconstruction: The Same Search, Three Different Costumes

Here’s the lie, installed so early it feels like a personality trait:

Somewhere inside you is the real you. Your job is to find her.

It’s a beautiful story. It’s also completely backwards. And it shows up in three disguises so convincing that most people spend years, sometimes decades, following the search without realizing they’ve been given a broken map.

Costume one: waiting to feel ready. The big opportunity arrives and instead of taking it, you hold back. The confident, capable, fully-formed version of you hasn’t shown up yet. Once she arrives, you’ll know you’re ready. So you wait. The problem is that she doesn’t show up first. She shows up after, built by the thing you were waiting to feel ready for. Readiness is not a prerequisite. It is a byproduct.

Costume two: waiting for it to feel right. The career search as an extended fitting room. You try on roles and industries and directions, waiting for the one that feels like you, the authentic fit that signals you’ve found your thing. The fit never comes before the doing. It comes from the doing. Identity doesn’t precede experience. It accumulates from it.

Costume three: waiting for a signal. The mentor who will confirm it. The personality assessment that will name it. The performance review, the feedback session, the quiet moment of external validation that finally tells you who you are. External signals can reflect. They can offer useful data. They cannot build. The building is always yours to do.

Three costumes. One search. And the search, however sincere, is always pointed in the wrong direction, inward, when the actual work is happening outward. Being you is not waiting and looking for something fixed and pre-existing, it’s through action in real time.

The Shift: That’s not how any of this works.

There was no single moment when this became a realization. It was more like turning around one day and seeing the architecture of it clearly for the first time.

Every version of myself I actually respect was built, not found. And the building materials were not the moments that felt good or clarifying or like progress. They were the other ones.

The hard conversation I didn’t avoid and could have. The project that went wrong and forced a recalibration I wasn’t ready for. The boundary I held under pressure when letting it slide would have been so much easier. The opinion I said out loud before I felt qualified to have it, and had to defend in a room that pushed back. The failure I couldn’t explain away and had to sit with long enough to learn something from it.

None of those felt like identity-building in the moment. They felt like hard things to get through. But looking back, every one of them deposited something into the person I was becoming. The confidence didn’t arrive before the hard thing. It arrived because of it. The clarity didn’t precede the doing. It was a product of it.

The self I spent so much of my twenties trying to find was being assembled the whole time. Not in the moments of introspection, not in the personality tests, not in the searching, but in the doing. In the accumulation of actions taken before I felt ready, in rooms I wasn’t sure I belonged in, on projects I wasn’t certain I could handle.

She was never hiding. She was being built. There is a significant difference.

The Reframe: The Identity Came After the Action. Always.

Here’s the reframe, and it is the one I wish someone had handed me at 25 instead of another coming-of-age movie:

You are not uncovering yourself. You are manufacturing yourself.

And the raw materials are more ordinary than you think.

Every hard conversation you don’t avoid. The feedback that’s uncomfortable to give. The disagreement you name instead of smooth over. The moment you say the true thing when the false thing would have been so much easier. Each one deposits something into the architecture of who you are.

Every project especially the ones that fail. The successes teach you what works. The failures teach you who you are under pressure, which is the more important curriculum. You cannot opt out of the failed projects and expect to build anything real.

Every boundary held when it costs something. Boundaries that cost nothing don’t build anything. The ones that matter are the ones where you held the line and felt the discomfort of it and held it anyway. Those are the ones that tell you and everyone watching something true about what you’re made of.

Every opinion stated before you felt qualified. The room you spoke up in before you were certain. The position you took before you had all the data. The willingness to be wrong in public is not just a leadership skill. It is one of the primary mechanisms by which you build a self worth having.

Every time you stayed in the room past the point of comfort. The meeting that got hard and you didn’t leave. The relationship that needed a difficult conversation and you had it. The moment the easier path was away and you chose toward. Those are the deposits.

Stop waiting for the version of you who is ready, who knows, who has arrived. She is a fiction, and chasing her is expensive. The version of you that is worth becoming is not ahead, waiting to be found. She is being built right now, in real time, by every hard thing you choose to do before you feel ready to do it.

That’s how it works. That’s always how it worked. The movies just forgot to mention it.

The Closing Shot

The person you’re looking for isn’t somewhere inside you, waiting.

She’s the one you’re making, one hard thing at a time.

Go make her.

Jules was tired because the search was exhausting and it was pointed in the wrong direction. You don’t find yourself. You build yourself. And the building starts the moment you stop waiting to feel ready and do the next hard thing anyway.

Share

There’s a version of this I lived.

It looked like this: a member of my team would turn in work that was slightly off. Not the kind of miss that triggers a formal conversation or sets off alarms. Just not quite there. A gap between what was submitted and what needed to go out the door.

I would close the gap. Usually late at night when the world was quiet, and I could tell myself I was being a good manager. I’d open the draft, smooth the rough edges, tighten the structure, send it back with a note that said something like “small tweaks!” Cheerful, low-stakes, completely invisible.

I told myself it was faster. I told myself I had a higher bar, and it was easier to just do it. I told myself I was protecting them from a stakeholder who wouldn’t have been kind about the gap.

Every one of those things was true.

None of them were the real reason.

The real reason was simpler and less flattering: I had confused having the answer with doing the job. I was so practiced at solving problems, so rewarded for knowing what to do, so comfortable in the role of the person who figured things out, that I had built an entire management style on a foundation of my own competence. And the people around me had stopped growing because there was no room. I was standing in it.

I wasn’t a bad manager. I was a very efficient one. But efficiency, applied to the wrong problem, is one of the most expensive habits in leadership.

The Manager and the Leader: Two Different Jobs

Here’s the distinction nobody puts in the job description.

A manager makes sure the work gets done. Tracks the output. Fills the gap when it falls short. Defines success as delivery. The right thing, on time, to the right standard. All of which is necessary and all of which is real work. None of which develops people.

A leader makes sure the people grow. Tracks the person. Holds the standard without absorbing the gap. Defines success not as this deliverable but as the capability built in the process of producing it. It’s not just what came out the door this quarter, but who is walking through the door next quarter, and whether they’re more capable than the person who walked in.

Those are different jobs. They require different skills, different beliefs, different instincts about what to do when someone falls short. Most people who get promoted into leadership were promoted for being exceptional managers. They were promoted for the output, the execution, the getting things done. Then handed a leadership role without anyone explaining that the job had fundamentally changed.

The sports world figured this out a long time ago.

Phil Jackson won eleven NBA championships. He did not score a single point in any of them. He never took a three-pointer in the fourth quarter, never posted up in the paint, never ran a fast break when the game was on the line. His job was to develop the people who did. To build the conditions, ask the questions, hold the belief in his players’ potential long enough and consistently enough that the players started holding it themselves.

Sir Alex Ferguson managed Manchester United for twenty-seven years. He won thirty-eight trophies. He never made a tackle. He never played a through ball or headed a cross. What he did, relentlessly across nearly three decades, was develop players into versions of themselves they couldn’t see yet. He built a culture where growth was expected, standards were held, and the belief that you could be better than you currently were was not a compliment but a requirement.

The best coaches in any sport are remembered not for what they did on the field but for what they built off it. The players are remembered for the performance. The coaches are remembered for making the performance possible.

That dynamic doesn’t change between the pitch and the cubicle. The context is different. The jerseys are different. The principle is identical. Fevelop the person, not just the output.

The Lies We Tell Ourselves

“It’s faster if I just do it.”

True today. Expensive over time. Every time you absorb a gap that belongs to someone else, you make a small deposit in the wrong account. You become slightly more indispensable, they become slightly less capable. Do it once, it’s pragmatic. Do it for a quarter, you have a team that’s stopped growing. Do it for a year, you have a team that’s stopped trying. They’ve built their picture of their own competence on a foundation you constructed for them without their knowledge. That’s not development. That’s a very elaborate fiction.

“I’m protecting them.”

From what, exactly? From the experience of falling short and learning from it? From the accurate feedback that would tell them where they actually are? From the discomfort that has preceded every meaningful growth in every context that has ever produced it?

Protecting someone from their own development is not kindness. It is control dressed up as kindness. The intention is generous. The impact is the opposite. Every gap you absorb invisibly sends a message the other person can’t hear: I don’t think you can handle what’s real. You think you’re having their back. You’re deciding their back isn’t strong enough and never giving them the chance to prove you wrong.

“What if they can’t do it?”

This is the most honest of the three and the one most worth reflecting upon. Because here’s the coaching answer: you won’t know until you ask. Asking with the genuine belief that the answer exists inside the person you’re asking is the act that most often produces the growth. People rise to meet the belief of the people who hold them capable. Not always but more often than the 9pm editor ever found out.

The Shift That Makes Everything Else Possible

Here is the thing about coaching that no model can give you and no framework can install: it only works if you genuinely believe the person across from you can find their own way to the answer.

Not probably, not maybe, but genuinely.

Because people can feel the difference between a leader who is asking questions to guide them to a predetermined destination and a leader who is asking questions because they’re actually curious about what’s there. The first feels like a maze. Technically open-ended, actually constrained. The second feels like a conversation with someone who is on your side and believes, without needing to perform it, that you’re capable of more than you’re currently doing.

That belief is the coaching mindset. Everything else, the model, the questions, the structure, is the technique that gives the belief a shape.

The manager asks: how do I get this done?
The leader asks: how do I develop this person?

Both questions are legitimate. Only one of them compounds.

The Napkin Sketch Tool: The GROW Model

Four stages. Four sets of questions. Simple enough to remember under pressure, structured enough to keep the conversation from drifting into advice.

One note before we start: GROW only works when the leader is genuinely curious about the answers. Run it as a structure for arriving at the answer you’ve already decided on and the person across from you will feel it within the first exchange. It will feel like a maze, not a conversation. Curiosity is not a technique. It is a mindset the model gives shape to. Hold the mindset first, learn to listen, then use the model.

G — Goal: What Are We Actually Trying to Achieve?

Not the task, but the outcome. The distinction matters. Tasks are assigned, outcomes are owned, and coaching works on ownership.

The goal question is about getting clear on what success looks like for this person, in this situation, beyond the immediate deliverable.

Try:

• “What would a great outcome look like for you here?”

• “If this went exactly as you hoped, what would be different?”

• “What does success look like not just for the work, but for you in this?”

This phase often takes longer than leaders expect and is almost always worth it. People aren’t usually clear on what they’re actually trying to achieve beyond the surface task. Slowing down here isn’t inefficiency, it’s the work. A coaching conversation without a clear goal is a conversation with nowhere to go.

A good sports coach doesn’t start practice by drilling without a purpose. They start by naming what winning looks like in the specific context of this game, this opponent, this week. The goal phase is that conversation. Get it clear before anything else.

R — Reality: Where Are We Actually Starting From?

Honest, specific, and without verdict. This is where the SBI skills from the feedback article do their work inside the coaching conversation. Stay on the bottom rung of the Ladder of Inference, describe what’s observable, resist the interpretation.

The reality question is where the Rescuer instinct is hardest to hold back. The gap is visible. The solution is right there. The leader knows exactly what needs to happen.

The coaching move is to ask anyway.

Try:

• “What’s actually happening right now?”

• “What have you tried so far?”

• “What’s working? What isn’t?”

• “What do you think is getting in the way?”

Because the person’s own honest assessment of their reality is more useful than yours. Not because you’re not right, but because that act is itself part of the growth. It’s the act of naming it honestly, out loud, with someone who is listening rather than waiting to solve it. People who can accurately assess their own reality can improve it. People who have always had it assessed for them can’t.

The football manager who does all the tactical analysis for the player and just tells them where to stand produces a player who is dependent on being told where to stand. The one who asks the player to read the game and then helps them understand what they’re seeing produces a player who can read it next time on their own.

O — Options: What Are the Possible Paths Forward?

Not the right path. All the paths. This is the generative center of the GROW conversation. The phase where most people, given real space to think, surprise themselves and the leader sitting across from them.

Try:

• “What options do you see?”

• “What else could you try?”

• “What would you do if the obvious constraint wasn’t there?”

• “What would you tell someone else to do in this situation?”

That last one has an extra bonus and worth considering. People consistently give better advice to hypothetical others than they give to themselves. The question sidesteps the self-doubt and accesses the thinking that was already there. The thinking the person couldn’t reach directly because their own situation felt too close and too charged.

The leader’s role in the Options phase is to expand, not to direct. Add to the list “have you considered X?”, but never collapse it to the option you prefer. The person needs to own the choice that comes out of this phase. Ownership requires real selection, and an authentic selection requires a list that wasn’t quietly narrowed to one before the choice was offered.

This is the part the Rescuer finds most difficult. The answer is right there. The efficient move is to name it. The coaching move is to hold the space open long enough for them to find it , and to stay curious about whether what they find might be better than what you had in mind. Sometimes it is.

W — Will / Way Forward: What Are You Actually Going to Do?

Commitment, specificity, and timeline. This is where the conversation graduates from thinking to action. It’s also where many coaching conversations dissolve into vagueness if the leader doesn’t hold the close.

Try:

• “What are you going to do, and by when?”

• “How committed are you to this on a scale of one to ten?”

• “What might get in the way, and how will you handle it?”

• “What do you need from me to make this happen?”

The commitment scale is more useful than it looks. A six or seven says something is still unresolved, and it’s worth finding out what before the conversation ends. A nine or ten is a genuine commitment the person has arrived at themselves. That’s a fundamentally different category of accountability than one assigned from above.

The last question “what do you need from me?” is the one that redefines the leader’s role in the relationship. They’re not the solver, not the fixer, but the resource. The person whose job is to remove the obstacles between this person and what they’re capable of.

That’s the job. That’s always been the job. It just took a model to make it visible.

The Tools That Brought You Here

This is the last full tool in my current kit on leading others. This one is about coaching, and it’s here at the end because coaching is where everything before it becomes a practice rather than a concept.

You cannot coach someone you’ve misjudged. The Ladder of Inference runs underneath every GROW conversation. You have to be genuinely curious about their reality rather than collecting confirmation of the story you’ve already written about where they are and what they’re capable of.

You cannot coach without trust. The Trust Equation determines whether the person across from you is in the conversation or in self-protection. The empathy variable and the self-orientation check from that chapter “whose interests are really being served here?” are alive in every coaching exchange.

You cannot coach from inside the triangle. The Rescuer asks questions to get to the answer faster. The Coach asks questions because they believe the answer exists in the person. The questions can look identical. The belief underneath them is completely different. That difference is what the person across from you can feel.

You cannot coach without listening. GROW is a listening structure. The reflect-validate-empathize sequence is what happens between the questions. It’s how the person knows you heard the Reality phase before you moved to Options, how they know the Goal they named was received, how they know the commitment they made in the Will phase was witnessed by someone who was actually present.

You cannot coach without honest feedback. The Reality phase of GROW is where the SBI method lives inside a coaching conversation. If you haven’t developed the ability to name what you observe specifically and without verdict, the Reality phase drifts into vagueness and the conversation loses its ground.

And you cannot coach someone whose crucial conversation you’ve been avoiding. If there’s something unsaid between you, something that’s been managed around rather than addressed, it will sit in the room during every coaching conversation you try to have, taking up the space where trust should be.

Coaching is not a separate skill. It is what leadership looks like when all the other skills are working.

Monday Move

One question to ask: Think of someone on your team you’ve been quietly carrying. When did you last give them accurate information about where they actually are? Not the cushioned version, the real one. That honest conversation is not the opposite of coaching. It is the beginning of it.

One behavior to stop: Stop giving answers to questions that haven’t been asked yet. The next time someone comes to you with a problem, run the Goal question before you go anywhere else. “What would a great outcome look like for you here?” Wait for the answer before you say anything. The answer will tell you more about what they need than the solution you were already forming.

One practice this week: Run one GROW conversation. Pick someone working on something that matters. Take them through all four phases. In the Options phase, resist the collapse, don’t let the list narrow to your preferred answer. Hold the space open and see what they find. Then notice what it feels like to watch someone arrive at their own answer to a question you already knew the solution to.

That feeling, more discreet than pride and more satisfying than solving it yourself, is what the job actually is.

Last Call

I want to tell you what happened to the person I used to fix things for at 9pm.

When I stopped, not through any principled decision, but because I genuinely ran out of capacity to keep doing it, something happened that I did not predict. He got better, fast. Not because the feedback I finally gave him was magic, but because it was real. Because for the first time he could see the actual gap, and seeing it meant he could do something about it.

Within a quarter he was producing work I wouldn’t have touched. Within six months he was the person others were going to with questions.

He grew. He just needed someone to stop standing between him and the truth of where he was. Then he needed someone to believe, genuinely, and in the form of questions rather than answers that he could close the gap himself.

That’s what the GROW conversation is. Not a framework applied to a problem. A structured expression of a belief. That the person across from you has more capability than they’re currently accessing, and that your job is to ask the questions that help them find it rather than provide the answers that prevent them from looking.

The best coaches in sport are remembered years later in player interviews. Not for the tactics or the drills or the halftime speeches. For the thing they said that the player didn’t believe yet but the coach did. And kept believing, through the missed shots and the bad games and the slow quarters, until the player started believing it too.

My coach believed I could do things I didn’t believe yet.

The belief, that the person in front of you is capable of more than they’re currently doing, that has to be yours. Genuinely. Before you open your mouth. Build the belief first. The model gives it a shape. The questions give it a voice.

That’s the job description. In sport and in the cubicle, across every team in every industry, it doesn’t change.

If this landed, share it with a manager who is ready to become a leader.

Share

It’s somewhere past midnight.

The conference room has been our world for the better part of a year. Every inch of wall space is covered: poster-sized printouts of mockup designs, roadmaps, checklists, retrospectives from sprints that feel like they happened in a different lifetime. The conference table is ringed with laptops and cold coffee and people who haven’t slept properly in days. The energy in the room is palpable. The kind of tension that hums at a frequency just below conversation.

We are in the final hours before go-live on a global eCommerce relaunch for a top global brand. A year of work. A team of people who have given this project more than they probably should have. Now we are here, in the middle of the night, because going live at 2am minimizes downtime, and minimizing downtime is the kind of thing that matters when you are this deep in it.

Then word comes through: someone passed out. Then: someone else has gone to the hospital.

The project manager, the person responsible for holding this whole thing together, looked up from his laptop. There was a beat of silence. And then he slammed his fist on the table.

“We’re just selling shoes, people.”

The room exhaled. Someone laughed. The real kind, not the nervous kind. Just like that, the hum dropped about forty notches, and we remembered, for the first time in days, that we were human beings working on a website and not a surgical team with someone’s life on the table.

We’re just selling shoes.

The Deconstruction: Three Beliefs That Built the War Room

Nobody walked into that project intending to end up in a hospital. Nobody sat down on day one and decided that sleep was optional and health was negotiable. It happened gradually, through a set of beliefs so normalized in professional culture that we stopped seeing them as beliefs at all.

The first: urgency equals importance. The deadline was real. The client expectations were real. The pressure from above was real. All of that reality created a gravitational field that bent everything toward the same conclusion: this is critical, this is essential, this cannot wait, this cannot slip. Urgency is a legitimate signal. The problem is that we treat it as proof of importance, and it isn’t. A thing can be urgent and not particularly important. A thing can be important and not particularly urgent. Confusing the two is how you end up with a room full of exhausted people treating a website launch like it’s the D-Day invasion.

The second: sacrifice equals commitment. Somewhere in the culture of professional achievement, martyrdom became a metric. The person who didn’t sleep became the person who cared most. The all-nighter became a badge worn with a particular kind of pride. I gave everything, I was all in, I bled for this. Nobody interrogates this. Nobody asks whether the person who went home at a reasonable hour and came back sharp and functional the next morning might actually be more committed to the outcome than the person running on fumes and adrenaline making decisions of increasingly questionable quality. The suffering gets measured. The output doesn’t.

The third: the longer you’re in it, the harder it is to see out. The war room walls were covered in paper. After enough days, those walls become the entire world. The project, the deadline, the client, the go-live, these stop being a part of your life and become the whole of it. Perspective isn’t something you lose dramatically. It erodes. Gradually, quietly, one late night and one skipped meal at a time, until the thing you are working on feels like the only thing that exists, and the stakes feel correspondingly infinite.

Three beliefs. Compounding on each other. Building the pressure until someone passes out and someone else ends up in the hospital, and a project manager has to slam his fist on the table to remind a roomful of talented people of something they always knew.

We are just selling shoes.

The Shift: Five Words That Became a Leadership Tool

The go-live happened. The site launched. The brand moved on to the next initiative. Most of the people in that room have long since moved to other companies, other projects, other war rooms of their own. The year of work receded into a line on a resume.

The phrase never left.

I have heard it in my head dozens of times since that night not as a memory, but as a tool. As a recalibrating instrument that I reach for whenever the proportions in a room start to go wrong.

When an executive tries to invoke urgency that the situation doesn’t warrant, tries to inject crisis energy into something that is genuinely important but not genuinely critical, I hear it. We’re just selling shoes. Not dismissively. Not to minimize the work. But as a quiet recalibration: let’s be accurate about what this actually is.

When someone I’m mentoring is white-knuckling a project, running on panic, letting the stress of the deadline colonize their whole nervous system, I say it to them. Not those exact words, necessarily. But that exact idea. This matters. It is not everything. You are allowed to be a person while you do it.

Because here is what the PM understood that the rest of us had lost in the fog of the war room: naming reality is not the same as dismissing it. He wasn’t saying the project didn’t matter. He was saying it didn’t matter that much. Not enough to hospitalize people, not enough to treat human beings like inputs to be run at maximum utilization until they fail. He saved the room from itself with five words, and he did it not by minimizing the work but by restoring its actual proportions.

That is a leadership skill. It might be one of the most underrated ones I’ve ever seen deployed.

The Reframe: Urgency Matters, Perspective Matters More

Here’s the reframe, and I want you to take it seriously even though it sounds simple:

Urgency is a signal. It is not a permission slip to abandon proportion.

Some practical translations:

Learn to distinguish urgency from importance and say so when the room can’t. They are not the same thing. A deadline creates urgency. It does not automatically create existential stakes. Part of your job, as you develop as a leader, is to be the person who can name that distinction out loud when the room has lost it. Not to minimize. To recalibrate. The team that goes home at a reasonable hour and comes back with functioning brains will outperform the team that grinds itself into the floor every time.

Martyrdom is not a metric. The hours you don’t sleep are not evidence of your commitment. They are evidence of unsustainable resource allocation. Start tracking outcomes, not suffering. The question isn’t who gave the most, but it’s what actually got delivered and at what human cost. Those are different conversations, and the second one is the one worth having.

Find your “just selling shoes” sentence. Every high-stakes context has a version of it. The phrase that restores proportion when the pressure has bent everyone’s perspective out of shape. Know yours before you need it. It might be about the work itself: this is a quarterly report, not open-heart surgery. It might be about the timeline: this deadline is real and it is also not the last deadline that will ever exist. Whatever it is, keep it close. You will need it.

Pass it forward. The most useful thing a leader can do in a pressure moment is be the person who names reality before the hospital visit, not after. When you see someone in your orbit losing proportion (a peer, a direct report, someone you’re mentoring) give them the exhale. Not because the work doesn’t matter. Because they do.

The project manager in that war room didn’t save the project that night. We did that ourselves. What he saved was the room: the people in it, the energy, the capacity to actually finish the thing we’d spent a year building. Five words. A fist on the table. The whole room changed.

You will be in rooms like that one. Be the person who says the thing.

The Closing Shot

The site launched. The brand moved on. The all-nighters faded into a story we told later, laughing.

What stayed was the sentence. What stayed was the exhale. What stayed was the reminder that the work is real and the people doing it are more real, and that no deadline, no client, no go-live in the history of ecommerce has ever been worth a hospital visit.

We’re just selling shoes.

Write it on a Post-it. Put it somewhere you’ll see it when the walls start closing in.

The project shipped. The company moved on. Somewhere right now there is a war room with paper on every wall and people who haven’t slept, convinced that this, this thing, this deadline, this launch, is the most important thing that has ever existed. It isn’t. Somebody in that room needs to say so. Maybe that somebody is you.

Share

Subscribe now

She’d had the conversation so many times she could have delivered it from memory. She’s had it in the car on the way home, in the shower on Tuesday mornings, lying awake at 2am with the particular clarity that arrives at 2am and dissolves by 7. She knew the specific moments she’d reference. She knew the impact she’d name. She knew how she’d open, how she’d stay calm, how she’d keep it about the work and not let it become about everything else it had slowly become about over two years.

She knew exactly what she would say.

She had never said it.

Her boss, the VP, was what her peers called a seagull. A term that required no explanation to anyone who had worked in an organization for more than eighteen months. He was not malicious. That would almost be easier. Just consistently, reliably present in the worst possible way: absent during the work, then descending without context at critical moments to drop opinions, redirect priorities, and undermine decisions already made. Then flying off again, apparently satisfied, leaving the team to clean up the mess and Maya to explain what had just happened.

He wasn’t a bad person. That was the part that made it harder for Maya to reconcile. He cared about the work. He was trying to be helpful in the way that people are trying to be helpful when they haven’t been told that what they’re doing isn’t, well, helpful. He had no idea what the landing looked like from below. Because nobody had told him. Because Maya hadn’t told him. Because every time she got close to the conversation, the calculus kicked in.

What if he gets defensive? What if it makes things worse? What if it follows her to her next review, her next project, her next opportunity? What if she’s wrong about how it’s landing? What if she’s right about how it’s landing and nothing changes anyway?

The what-ifs won. Every time. Reliably and completely.

And every time they won, something else happened. The team started hedging. Not dramatically, incrementally, in the way that slow damage works. It’s not committing fully to decisions they’d learned might get overridden without warning. It’s the team only half finishing because they knew they’d have to rework at the last minute anyway. It’s Maya stop bringing her best thinking forward, because the energy required to protect an idea from being redirected mid-execution wasn’t always worth the cost of losing it. She started spending more time managing around the dynamic than doing the work she’d been hired to do.

She complained about it. To peers, in the parking lot conversations that happen between work and life. To her partner at home, in the half-conversations that start over dinner and trail off because there’s nothing new to say. She had, on three separate occasions, updated her resume.

She had not said a word to the VP.

Two years in, she had started to forget what the job felt like before the managing around started. She couldn’t remember the last time she’d walked into his office with an idea she was genuinely excited about. She couldn’t remember the last time she’d felt fully present in a meeting rather than half-present and half-monitoring for the next descent.

She was still there. She just wasn’t all the way in anymore.

That’s what the avoidance cost looks like. Not in one moment, but in installments, slow burning. Small enough to absorb, large enough to compound, invisible enough that nobody including the VP knew it was happening.

The Lie We Tell Ourselves

Ask someone why they’re not having the conversation they need to have and the answers come quickly. They’ve been rehearsed too.

“It’s not the right time.”

It is never the right time. The project is always at a critical point. The relationship is always delicate. The quarterly review is always either just passed or just approaching. The right time is not a moment on the calendar. It’s a story the avoidance tells to stay comfortable, and it is extraordinarily convincing because it is always at least partially true. There is always a reason. The reasons are real. They are also, if you’re honest, never actually the reason.

“It probably isn’t as bad as I think.”

The gaslight we apply to ourselves. Said most often when the evidence is clearest and the conversation is scariest. When minimizing the problem is cheaper, in the short term, than addressing it. You don’t rehearse a conversation in the car for two years about something that probably isn’t that bad. The minimizing isn’t an honest assessment. It’s the avoidance finding new material.

“What if nothing changes?”

This one is different from the others. It isn’t a lie. It’s a fear. Specific, legitimate, and worth taking seriously rather than dismissing. The risk that you name the thing, make yourself vulnerable, absorb whatever defensiveness comes back, and the answer is that this is just how it is. That fear keeps more crucial conversations unspoken than any other single thing. And it deserves a real answer, not a reassurance.

We’ll come back to it.

The Autopsy: Why the Upward Conversation Is the One Nobody Has

Leadership development has produced an entire industry around the downward conversation. The performance discussion. The behavior feedback. The person who isn’t working out. There are models, scripts, frameworks, HR guidance, and whole chapters of books dedicated to saying hard things to the people who report to you.

Almost none of it addresses the conversation going the other direction.

This is not an accident. It’s a reflection of where the power sits, and power shapes what gets named and what gets managed around.

The stakes are different going up.

Feedback delivered downward carries some professional risk. Feedback delivered upward carries a different category of risk entirely. One that includes your performance evaluation, your visibility to senior leadership, your access to the opportunities that determine the trajectory of your career. The stakes of the upward conversation are not imagined. They are real. Any framework that doesn’t acknowledge that is a framework for a situation that doesn’t exist.

And yet. The cost of not having the conversation is also real. It compounds. It is paid in the currency of your energy, your engagement, your best thinking, and eventually your willingness to stay.

The seagull doesn’t know they’re a seagull.

This is the part that makes the avoidance feel rational, and the part that makes it most costly.

The VP in Maya’s story was not performing malice. He was operating from a model of engaged leadership that felt, from his vantage point, like exactly what a good VP should do. He descended because he cared. He redirected because he thought he was adding value. He had no data, none, suggesting that the landings were doing damage, because the person closest to the damage had decided the risk of providing that data was too high.

So the behavior continued. Not because he chose to continue it. Because the information that would change it never arrived. The conversation Maya wasn’t having wasn’t just costing her. It was costing him the chance to understand something important about his own leadership. Both of them were losing something. Neither of them knew it.

The longer you wait the harder it gets.

Every week the thing goes unsaid, the gap between the current dynamic and the conversation required to change it widens. The resentment accumulates in the way interest accumulates. Compounding quietly and consistently until the balance is much larger than the original deposit. The relationship calcifies around the avoidance. The pattern solidifies. Having the conversation starts to feel not just risky but structurally impossible. Like trying to move something that has been load-bearing for too long to touch.

This is the cruel arithmetic of avoidance: the longer you wait, the more you need the conversation and the harder it is to have. The window doesn’t stay open indefinitely. It narrows. And one day you realize the window has closed. Not because of a dramatic moment, but because you updated your resume for the fourth time and this time actually sent it somewhere.

The Napkin Sketch Tool: Three Things Before You Walk In

The Crucial Conversations framework, developed by Patterson, Grenny, McMillan, and Switzler, is built on one foundational insight: conversations fail not because of what gets said but because of what happens to safety before it gets said.

When people feel unsafe, they stop engaging with the content and start protecting themselves. They go silent like Maya, absorbing and managing around. Or they go aggressive, escalating in ways that confirm every fear about what happens when you name the thing. Either way, the actual issue disappears into the dynamic and nothing changes.

Everything in what follows is oriented toward keeping safety intact long enough for the real conversation to happen.

Step 1: Get Your Head Right Before You Open Your Mouth

The model calls this Start with Heart, and it’s the step most people skip because they’re so focused on what they’re going to say that they never examine why they’re going to say it. The what is the easier question. The why is the one that determines whether the conversation produces something or just produces a reaction.

Two questions. Answer them honestly, before anything else.

What do I actually want from this?

Not what you want to say. Not what you want the other person to understand. What outcome are you genuinely hoping for? A specific behavior change? A shared understanding of how the dynamic is landing? A different working arrangement? Clarity on whether this relationship can function in a way that works for both of you?

The answer to this question shapes everything about how you walk into the room. Someone who wants to be heard walks in differently than someone who wants the behavior to stop. Someone who wants to understand what the VP is trying to accomplish walks in differently than someone who wants to deliver a verdict.

Clarity on what you want is not a small thing. It is the difference between a conversation and a confrontation.

What do I want for this relationship?

This question matters especially in the upward conversation, where the power dynamic can turn the conversation into something adversarial before anyone intends it to be.

Do you want this working relationship to function well? Do you want to find a way to operate together that works for both of you?

If the answer is yes, then the goal isn’t to win. It isn’t to be right. It isn’t to have your experience validated. It’s to build something that works. Holding that goal in your body before you walk in changes the conversation in ways that no technique can replicate.

If the answer is no, you’re in a different situation that requires a different kind of honesty.

Step 2: Open the Room Before You Walk Through It

The VP’s instinct when Maya names this will be defensiveness. Not because he’s a bad person, because being told that your leadership behavior is landing badly is uncomfortable for everyone. Discomfort without safety produces self-protection rather than curiosity. His first move, internal and probably invisible, will be to construct a threat. Your job, before you say the thing you came to say, is to dismantle the threat before it finishes forming.

Two tools for opening the room.

Contrasting: Name what you’re not saying before you say what you are.

“I’m not raising this because I don’t value your involvement in the team’s work. I do. I’m raising it because I think there’s a way for us to work together that gets better outcomes for both of us, and I want to find it.”

That sentence does something important: it removes the interpretation the other person’s defensiveness will otherwise provide. Left to construct their own frame, people hear the beginning of a difficult conversation as an attack. Contrasting gives them a different frame before the attack they were preparing for arrives, and a different frame produces a different response.

Shared purpose: Connect the conversation to something you both care about before you name the problem.

“I want to talk about something because I think it’s affecting the team’s ability to deliver, and I know that matters to both of us.”

Us. That word is doing work again, the same way it did in the feedback article. It places the conversation in a shared stake rather than an individual grievance. The VP isn’t being called into a complaint. He’s being invited into a conversation about something that costs both of them. That framing doesn’t guarantee a good conversation. It makes one possible.

Step 3: Name the Pattern Without the Verdict

This is where the Ladder of Inference and the SBI method do their work inside the crucial conversation. Stay on the bottom rung. Describe what you’ve observed. Do not lead with what you’ve concluded.

Not: “You don’t trust me to lead my team.”
But: “When decisions we’ve made get redirected at the last minute without context, the team loses confidence in their work and I lose the ability to hold them accountable to it.”

Not: “You micromanage.”
But: “When you come directly into the team’s work without looping me in first, it creates confusion about where decisions get made. And I think it costs us both in ways that are worth talking about.”

The behavior is observable. The verdict is a conclusion arrived at after several rungs of inference. Name the behavior. Connect it to the impact. Frame it around the shared goal. Ask a question. “I wanted to share what I’m experiencing, and I’d want to understand what you’ve been trying to accomplish in those moments. I think there might be a gap between the intent and the impact.” Then (and this is the part most people forget in the relief of having finally said the thing) stop talking.

Then listen. Actually listen. Not to confirm what you already think. To find out what’s actually there. The answer might matter in ways you haven’t anticipated, and the conversation only goes somewhere useful if both people are in it.

The Question Underneath Everything: What If Nothing Changes?

Before you have this conversation. Before you finalize the opening, before you rehearse the SBI, before you book the thirty minutes. Sit with this question privately and honestly.

If I have this conversation and the VP’s behavior doesn’t change, what then?

Not as a catastrophe. Not as a threat you’re planning to deliver. As a genuine reckoning with your own situation and your own options. Because the answer to this question. the real answer, changes what you bring into the room.

Someone who has honestly answered it walks in differently. They’re clearer. Less desperate for a particular outcome. More able to have the conversation as a genuine exchange rather than a plea, because they’re not dependent on a specific response to be okay. They can stay curious. They can listen to the VP’s perspective without needing it to immediately validate theirs. They can hold the conversation open longer, which is when conversations actually go somewhere.

Here is what most people discover when they sit with the question honestly away from the avoidance and the 2am calculus: they have more options than the avoidance has been telling them. Options they haven’t fully examined because examining them would make the current situation feel less like a trap and more like a choice. A choice implies responsibility for what happens next.

You might discover you’re willing to stay and keep working on the dynamic if the conversation opens something. You might discover there are structural changes, a different working agreement or a different cadence of involvement, that would change enough to be workable. You might discover that if nothing changes, you will eventually leave. Knowing that, honestly, makes you less afraid of the conversation because the worst case is something you’ve already decided you can navigate.

The fear of the answer keeps the question unasked. Answering it, even privately, even imperfectly, changes the conversation before it starts. It moves you from someone avoiding a conversation they feel powerless in to someone with a choice and responsibility in having a conversation. That shift is not small. It is, in many ways, the whole thing.

The Conversation That Almost Didn’t Happen

Here’s what it could look like when Maya decides to stop rehearsing.

She doesn’t ambush him. She asks for time, “I’d like thirty minutes to talk about how we’re working together. There’s something I want to raise and I’d rather do it properly than let it sit.” He says yes, slightly wary. Fine. Wariness is appropriate. She’d be wary too.

She starts with contrasting. She names the shared goal: the team’s ability to deliver, the outcomes they both care about. She describes three specific moments: situations, behaviors, impacts. No verdict. No character assessment. Just what happened, and what it cost.

He is defensive for about four minutes. She expected this. She doesn’t fill the silence with reassurance or walk the feedback back to make the room more comfortable. She lets him sit with it.

Then something shifts. He didn’t know the last-minute redirects were landing the way they were. He thought he was adding context. He wasn’t aware the team had started hedging. He’d noticed less initiative than he expected but had attributed it to something else. He asks a question. A real one. She answers it honestly.

They don’t solve everything in thirty minutes. They don’t arrive at a perfect new operating model or a transformed relationship. What they arrive at is a shared understanding that something has been happening that neither of them had fully accepted, and a tentative agreement to work on it differently.

Maya walks out of the room having done the thing she’d been telling herself for two years she couldn’t do. She discovers something the parking lot rehearsals never could have taught her: the conversation was survivable. It required much more courage than the rehearsals implied. But more useful than all of them combined. The VP didn’t become a different person. But something that had been calcifying started, slowly, to move.

The seagull didn’t disappear. But he called before he landed.

Monday Move

One question to ask: What has the avoidance actually cost you so far? Not what it might cost you to have the conversation, but what it has already cost you? Time, energy, your best thinking, your willingness to be fully present. Add it up honestly. The avoidance has never been free. It has just been billing you in small amounts on a schedule you stopped checking.

One behavior to stop: Stop mistaking the rehearsal for the conversation. Most people have had the crucial conversation many times. They’ve played it out in the car, in the shower, and at 2am with the particular clarity that evaporates by morning. The rehearsal feels like progress. It isn’t. It’s the avoidance wearing productive clothing. The conversation only exists when the other person is in the room.

One action this week: Answer the underneath question before anything else. If I have this conversation and nothing changes, what then? Write the answer down. Not as a plan, as a private reckoning. Then answer the first question: what do I actually want from this conversation? Write that down too. See if the conversation you’ve been avoiding feels as impossible as it did before you started. It probably doesn’t. The impossibility was never the conversation. It was the unanswered question underneath it.

Last Call

There is a version of your career in which you have the conversations you need to have, with the people who need to hear them, before the silence becomes the relationship.

It doesn’t mean every conversation goes well. It doesn’t mean every VP becomes coachable, every dynamic becomes workable, every avoided thing becomes resolved. Some conversations don’t change the situation. They change you. They provide you clarity about what you will and won’t absorb, and they provide you knowledge that you said the thing rather than spending years wondering what would have happened if you had.

That knowledge is worth something. More than the resume updates. More than the parking lot rehearsals. More than the managed-around version of a job you were otherwise doing well in.

The conversation you keep avoiding is not going away. The situation it addresses is getting more expensive every week you don’t have it. The person who needs to hear it might, with that information, become a better leader than they currently are.

You know what you would say.

The only thing left is to say it to the right person.

If this landed, share it with someone who has been rehearsing a conversation it’s time to actually have.

Share

Subscribe now

I was reading Morgan Housel’s The Psychology of Money when the sentence stopped me cold.

The book is ostensibly about personal finance. How we think about money, why we make irrational decisions with it, how to build wealth in a way that actually sustains a good life. If you haven’t read it and you’re early in your career, stop here and go get it. Genuinely one of the most useful books I’ve encountered, and not just about money.

The argument that stopped me was this: don’t save for the specific house, the specific vacation, the specific version of the future you’ve mapped out at 25. Build for financial independence instead. Because the person you’ll be at 40 will want things you cannot imagine right now, and the most valuable thing you can give her is options.

I put the book down. He had articulated a belief and a truism I always had but never could put into words.

But also, it wasn’t just about the house fund. It wasn’t just about the vacation account. It was about every plan I had made for a life I hadn’t lived yet. The career path mapped out with such confidence. The identity I had locked in before I had enough data. The beliefs I held with certainty at 25 that turned out, in the fullness of actual experience, to be a first draft.

You weren’t wrong to plan. You were just planning for a version of yourself who hadn’t happened yet.

The Deconstruction: The Same Trap, Three Different Stages

Here’s the rule, and it comes in three acts:

Act one: you commit too early.

You choose the path before you have enough life to know what actually fits. Whether it’s the career or the story you tell about who you are and where you’re going, you anchor to that identity. This is not a failure of judgment. It is a failure of information. You did the best you could with what you had. The problem isn’t the early commitment. The problem is what comes next.

Act two: you stay too long.

At some point the thing you chose stops fitting the way it did. Maybe gradually, maybe all at once. Instead of updating, you double down. Because changing now feels like admitting the original choice was wrong. We dress this up as commitment, as resilience, as seeing things through. Sometimes it is those things. And sometimes it is loyalty to a version of yourself that has already quietly left the building, while the current version stands in the old plan like a house that no longer fits.

Act three: you build for the wrong target.

You skill up for the specific role, the specific industry, the market as it currently exists. You optimize for the destination rather than the range. Then the destination moves. And it always does, because markets shift and companies restructure and the job you trained for gets automated or offshored or simply stops being the job you want. You discover that specialization, which felt like security, was actually a narrowing.

Three acts. Same trap. The common thread is this: we were taught that a good plan, executed with discipline, leads to a good outcome. What nobody mentioned is that the person executing the plan keeps changing. And eventually, if you’re not paying attention, you’re executing someone else’s plan. The someone else is just a younger, less informed version of you.

The Shift: When the Life Reorganizes the Values

There was a period in my life when something happened that quietly reorganized everything I thought I knew about what mattered.

It wasn’t dramatic in the way life events are supposed to be dramatic. It didn’t announce itself as a turning point. It just arrived, and in its aftermath I found that the map I’d been using no longer matched the territory.

Things I’d treated as essential turned out to be optional. Things I’d deferred as optional turned out to be the point. The hierarchy of what I was working toward shifted in ways I couldn’t have predicted and didn’t choose.

The plan didn’t survive the execution of actual life.

That was not a failure. It was data. The updated version of me that emerged on the other side of that period was not evidence that the earlier version had gotten it wrong She had gotten it exactly as right as anyone can with the information available at the time. But the information changed. The experience changed. And so, necessarily, the plan had to change too.

The Psychology of Money has a line that I’ve returned to more than once since: “The most important part of every plan is planning on your plan not going according to plan.” Housel’s point is about financial resilience, but it is also, if you let it be, about the entire architecture of a life. The goal was never to execute the original plan perfectly. The goal was to remain capable of adapting when the plan met reality.

The Reframe: A plan is a starting point

Here’s the reframe, and it is the gentlest one I have to offer:

Build for optionality, not the target.

Housel’s financial independence argument translated directly into career terms: the skills that will serve you across every version of your future self are not the ones specific to the role you want right now. They are the ones that transfer. Judgment. Communication. The ability to read a room, navigate ambiguity, influence without authority, regulate yourself under pressure. The human skills we keep mislabeling as soft. These are the ones that compound. These are the ones that survive the market shift, the layoff, the pivot you didn’t plan for, the life event that quietly reorganizes everything.

Some practical translations:

Changing your mind is not inconsistency. It’s updating. The same instinct that makes a good strategist applies to the plan you made for your own life. You revise when new data arrives. The person who holds the same beliefs at 45 that she held at 25, without revision, has not been consistent. She has been incurious. New experience is data. Use it.

The sunk cost is not a reason to stay. The years you spent in a direction that no longer fits do not obligate you to spend more years there. I know how this feels — like leaving would mean the earlier investment didn’t count. It counted. It built the version of you capable of recognizing that it’s time to go. That’s what it was for.

Audit your skills for transferability. Look at what you’re building and ask honestly: if the specific role I’m in disappeared tomorrow, what would I have? The answer should include things that work anywhere such as the human capabilities, the pattern recognition, the relationship capital. If the answer is mostly role-specific, start widening the portfolio. Not because the role will disappear, but because the person who has options is the person who can choose.

Give yourself the same grace you’d give a friend. If she came to you at 40 and said the path she chose at 25 no longer fits, you would not tell her to stay in it because she’d already come so far. You would tell her she gets to choose again. You are allowed to do the same. The earlier plan was not a contract. It was a starting point.

The Closing Shot

The point of financial independence was never to accumulate the specific thing you wanted at 25. It was to be free enough at 40 to choose whatever you actually want then.

Same for the career. Same for the identity. Same for the beliefs.

The goal was never the plan. The goal was the optionality to keep becoming.

Ask yourself which parts of your plan were made for the person you were and which ones are still being made for the person you’re becoming.

Share

Subscribe now

Alex had two managers in four years who gave her feedback she still wonders about.

Not because it was good. Because it was so precisely wrong in the same way that it taught her something the right feedback never could have.

The first one called her in after a quarterly review. He was generous with his time. That part was genuine, and he’d clearly prepared. He had thoughts about her visibility in senior meetings, her executive presence, her readiness for the next level. He talked for twenty minutes about how to position herself for the promotion he assumed she was working toward.

Alex listened carefully. She thanked him. She walked out and thought about it for approximately as long as it took to get back to her desk.

She wasn’t working toward the promotion. She had never been working toward the promotion.The thing that actually got her out of bed, the thing she found genuinely satisfying about the job was building the best team she’d ever had. That’s what she was working toward. Watching people grow. Solving hard problems alongside people she respected. Producing work she was proud of. The next rung on the ladder was not, and had never been, the point.

The feedback was well-intentioned, specific, and delivered with care. It was also advice for someone else’s life. Because it was built entirely on an assumption about what she wanted that he had never once thought to verify.

The second manager had a different angle. His feedback was about style. She should consider being more like Sarah — warmer, more expressive, more visibly enthusiastic in the way that reads well in a large room. Sarah was well-liked. Sarah lit up a space. He’d seen Alex present twice in the last quarter and she came across as measured. Reserved. He wanted to see more energy.

What he hadn’t looked at but should have given that the data was available were Alex’s numbers. Her revenue performance was stronger than Sarah’s. Her client feedback was consistently excellent. Her employee retention was significantly higher than the team average. Considerably higher than Sarah’s.

The people who worked with Alex every day would not have described her as reserved. They would have described her as someone who was in the trenches with them. A leader who led by example and whose trust you earned because she earned yours first. Someone whose team would have walked through a wall for her, or at least dug in deep on a difficult project. Not because she was the most charismatic person in the room, but because she was the most present.

The feedback wasn’t about Alex. It was about his impression of Alex, formed from a distance, filtered through a preference for a style that wasn’t hers and a set of metrics he hadn’t thought to pull.

She thanked him. She filed it in the place she kept feedback that had nothing to do with her. And she went back to her team.

The Lie We Tell Ourselves

There are two versions of the lie, depending on which side of the feedback you’re on.

If you’re giving it: “I’m doing this for their own good.”

Maybe. But whose definition of good? Feedback built on an assumption about what someone wants, who they are, or what success looks like for them isn’t development. It’s projection. The most common version is the one Alex experienced twice. It was assuming the person in front of you shares your ambitions, your style, your definition of what a good leader looks like, and calibrating the feedback to an assumption that doesn’t exist.

You’re not giving them feedback for their own good if you haven’t established what their own good actually looks like.

If you’re receiving it: “This says more about them than it does about me.”

Sometimes true. Also the most convenient exit ramp available when feedback is uncomfortable. The problem is that it works equally well on feedback you should dismiss and feedback you should sit with. Which means it’s not a filter, it’s a defense. And a defense that’s always available is one that never lets the useful stuff through.

The skill on the receiving end isn’t deciding what to accept and what to file away. It’s learning to stay with it long enough to find what’s true. Even in feedback that’s imperfect, even from someone whose vantage point is limited, even when your first instinct is to explain why they’ve got it wrong.

The Autopsy: Three Reasons Feedback Fails Before Anyone Speaks

1. The Assumption of Shared Goals

This is the one that does the most damage and gets examined the least.

Feedback is calibrated, consciously or not, to a destination. When the destination the feedback-giver has in mind isn’t the destination the recipient is actually heading toward, the feedback doesn’t land wrong. It lands irrelevant. Irrelevant feedback doesn’t just fail to help, it quietly communicates that the person giving it hasn’t been paying enough attention to know what you’re actually trying to do.

Here’s the thing about shared goals that Alex’s second manager got wrong and that her first one missed entirely: you don’t have to be close to someone for shared goals to create the conditions for useful feedback.

Even in a project team where trust is new and relationships are thin, feedback framed around a shared outcome can land productively. “I want to share something I noticed because I think it affects what we’re all trying to achieve here”. That sentence does something the performance review version never does. It makes the feedback about us rather than about you. It removes the evaluation dynamic and replaces it with a partnership one. The recipient isn’t being judged. They’re being invited into a conversation about shared success.

Alignment on goals is the foundation. Not because everything else is irrelevant, but because without it the feedback has no address to be delivered to.

2. The View From a Distance

The manager who sees someone once a quarter has data. They have an impression. What they don’t have is a full picture. The gap between impression and reality is exactly where the most damaging feedback lives.

Style feedback is the most common casualty here. Presence. Energy. Cultural fit. These are the categories where a limited vantage point does the most harm, because they’re also the categories where the person receiving the feedback has the least ability to action them. Often, none of it moves the needle in a way that would help the receiver’s or the giver’s goals.

The people best positioned to give useful feedback are almost never the ones furthest from the work. They’re the ones close enough to see what’s actually happening. Peer, direct report, or leader, the hierarchy matters less than the proximity.

3. The Relationship Isn’t Ready

Feedback delivered in the absence of trust doesn’t land. It stings, or it’s dismissed, or it’s received with a polite nod and filed quietly away. The technique cannot manufacture the relationship.

This is the part the feedback systems miss entirely. You can train every manager in SBI. You can build the most elegantly designed feedback platform available. You can set quarterly reminders and completion targets and calibration sessions. None of it creates the thing that makes feedback actually change behavior. Which is a relationship in which the recipient believes, based on evidence, that the person giving the feedback is genuinely in their corner.

That belief is built over time. In small moments. In the consistency between what someone says and what they do. In whether they showed up when it cost them something. It cannot be replicated by a well-structured feedback form delivered on a schedule.

The Napkin Sketch Tool: The Foundation + SBI

Three parts. The second one only works if the first one is solid. The third is owned by the receiver.

Part 1: The Foundation

Three questions to answer before you give feedback to anyone.

1. Do we share a goal?

Not do you share a goal with them, but do they know you share a goal with them? The alignment needs to be established, not assumed. If you’re on a project team and the outcome is clear, name it before the feedback. “I want us to deliver this well, and I noticed something I think is worth talking about because I think it affects that.” If the relationship is ongoing, the investment is in understanding what they’re actually trying to build. Their version, not yours.

This is the question that changes the feedback from evaluation to partnership. It is also the question most feedback-givers skip because they assume the answer is obvious. It rarely is.

2. Am I close enough to the work?

Honest answer required. Not am I senior enough, not do I have the authority. Am I close enough to what’s actually happening to comment on reality rather than impression?

If the answer is no, say so. “I want to share something I’ve noticed, and I want to acknowledge I don’t have the full picture. I’d want to hear your perspective first.” That sentence is not weakness. It is the most disarming thing you can say before feedback, because it signals that you’re not coming in with a verdict. You’re coming in with an observation and a genuine willingness to be wrong about it.

3. Is the relationship ready?

If there’s no trust yet, build some before the feedback. Not as a manipulation, as a prerequisite. The relationship work isn’t the detour from the real work. It is the real work. Feedback lands in the context of a relationship. Invest in the context.

Part 2: The SBI Method

When the foundation is solid, SBI (Situation, Behavior, Impact) is the structure that makes feedback specific enough to act on and safe enough to receive.

Situation: anchor it to something specific

Not a pattern. Not a general observation. A concrete moment.

“In last Tuesday’s team meeting...” not “You often seem to...”
“When you presented to the client on Thursday...” not “Your communication style tends to...”

Specific situations make feedback discussable. They give the recipient something to engage with rather than something to defend against. General observations feel like verdicts. Specific situations feel like data, and data can be examined together.

Behavior: describe what you saw, not what you concluded

This is the line between feedback and judgment, and it matters enormously.

“You cut Jamie off twice before she’d finished her point” is a behavior.
“You don’t respect the junior members of the team” is a conclusion, one that has climbed several rungs of the Ladder of Inference from the observable moment to the character assessment.

Stay on the bottom rung. Describe what happened. The behavior is what you both have access to. The conclusion is yours alone, and the moment you lead with it, the recipient is no longer engaging with feedback. Instead they’re defending against a characterization.

Impact: connect it to something that matters

Not to embarrass. Not to assign blame. To make the connection between the behavior and its visible effect on the team, on the work, or on the shared goal you established at the start.

“It made it harder for others to contribute, and I noticed a few people go quiet for the rest of the meeting.”

“The client picked up on the hesitation and it created more questions than it resolved.”

“It left me with less confidence going into the deadline than I’d like to have.”

Impact is information, not punishment. It answers the question the recipient is always asking but rarely says out loud: why does this matter? Give them the answer. Frame it around the shared outcome whenever possible. The feedback isn’t about them as a person. It’s about a behavior and its effect on something you’re both trying to achieve.

The frame that carries it all:

The feedback Alex received that she still thinks about was never framed as here’s what you’re doing wrong. It was framed as here’s what I’m seeing, and here’s what I think it costs us when it happens.

Us. That word is doing significant work. It changes the entire dynamic of the conversation from evaluation to partnership. Try it.

Part 3. Receiving Feedback. The Skill Nobody Teaches.

Most feedback development focuses entirely on the giver. The receiver gets a brief mention. “Be open, be curious” and then everyone moves on.

This is a problem because receiving feedback well is genuinely hard and genuinely learnable, and the default response to feedback that stings is almost always the wrong one.

The default response is defensive dismissal. They don’t know the full picture. They have their own agenda. This says more about them than it does about me. All of which may be partially true. None of which helps you find what’s actually useful in what just landed.

Here are the two questions worth asking instead. Not in the moment if it is too charged. But afterward, when the initial reaction has settled:

Is there any version of this that’s true?

Even imperfect feedback from a limited vantage point contains data. Even the “be more like Sarah” feedback. As wrong as it was in its framing and its evidence, it contained a signal worth examining. Was there something underneath the style observation that had some truth to it? Maybe. Is there something the team needs that I’m not doing? Probably. The question isn’t whether to accept the feedback wholesale. It’s whether to throw out the signal with the framing.

Most feedback that stings contains at least a partial truth wrapped in a delivery that made it hard to receive. The work is separating the two. The delivery is their problem. The signal is yours to decide what to do with.

How can I respond in a way that’s grateful and gets me more?

This one reframes the entire dynamic. Instead of closing the conversation with a polite thank-you that goes nowhere, open it.

“Thank you for saying this. Can you tell me more about the specific moment where you noticed it?”

“I want to make sure I understand what you’re seeing. Can you help me connect this to the outcome you’re hoping for?”

“I’m taking this seriously. What would better look like from your perspective?”

These questions do two things simultaneously. They signal genuine engagement rather than defensive deflection. And they get you more data, more specificity, more of the raw material you need to decide what the feedback is actually worth.

Even feedback from someone you don’t fully trust, framed around a goal you both share, becomes more useful when you ask one more question instead of closing the door. The conversation that starts with can you tell me more has a different trajectory than the one that ends with a polite nod and a silent verdict.

Monday Move

One question to ask: Before you give feedback to someone this week, ask yourself: do we share a goal, and does this person know we share it? Not what you assume they’re working toward, but what you’ve asked about or what they’ve told you. If the answer is unclear, start the conversation there. The feedback can wait two minutes for the alignment that makes it land.

One behavior to stop: Stop giving feedback from a distance as though it’s feedback from up close. If you haven’t been close enough to the work to comment on reality rather than impression, say so before you say anything else. The acknowledgment of your own limited vantage point is not a disclaimer; it’s the thing that makes the rest of the conversation possible.

One practice this week: Think of a piece of feedback you recently received that stung or that you dismissed. Sit with it long enough to ask: is there any version of this that’s true? You don’t have to accept the framing. You don’t have to agree with the delivery. But before you file it away entirely, give it one honest look. What’s the signal underneath the noise? What question could you ask that would get you more? The feedback that’s hardest to receive is sometimes the one most worth examining.

Last Call

Alex eventually found the feedback that changed something.

It didn’t come from either of those managers. It came from a peer she’d been working alongside on a cross-functional initiative. Someone with no stake in her career trajectory, no hierarchy over her, no performance review to file. Someone who had been close to the work long enough to see her clearly.

He didn’t prepare a framework. He didn’t schedule a meeting. He said it in the hallway after a project debrief, with the casualness of someone who wasn’t performing feedback. Who was just saying something true because it needed to be said.

“I noticed that when the conversation gets heated you go quiet. And I think when you go quiet people read it as disengagement. I don’t think it is. I think you’re processing. But the room doesn’t know that.”

She stood in the hallway for a moment after he walked away.

He was right. Not about everything, but about that specific thing, in that specific context, framed around a shared outcome they both cared about. He’d been close enough to the work to see what was actually happening. He’d named a behavior, connected it to an impact, and said it because he thought it would help. Not because it was on a schedule or in a system or because someone had told him to.

She thought about it for a long time. Not defensively. Genuinely.

That’s the thing about feedback that lands. It doesn’t feel like an evaluation. It doesn’t feel like a verdict rendered from a distance by someone who’s decided what you should be.

It feels like someone who has been paying attention handing you a mirror and saying “I thought you might want to see this.”

The technique matters. The relationship matters more. The shared goal is what makes both of them possible.

Build that first. Everything else follows.

If this landed, share it with someone who has feedback worth giving and a relationship worth giving it in.

Share

Subscribe now

It started as a drinking game.

Vacation. Friends. A guilty pleasure reality show that shall remain nameless… the kind where everyone is beautiful and everyone says they’re looking for love and a partner. Yet nobody, it turns out, is actually doing those things. Someone suggested we drink every time a contestant said “genuinely.”

We ran out of drinks before the episode ended.

We lost count somewhere around the second elimination, which is its own kind of metaphor. Here were people on national television, performing sincerity for cameras at maximum resolution, saying the word genuinely so often it stopped meaning anything at all. They were genuinely there for the right reasons. They were genuinely falling for someone. They were genuinely blindsided. Meanwhile, their hair was professionally styled at 6am, their confessionals were shot seventeen times for the best angle, and the person they were genuinely falling for was simultaneously genuinely falling for four other people in a fantasy suite.

Genuinely has no basis here. And yet. The word was everywhere.

Somewhere between the third episode and the bottom of the wine bottle, the question crept in uninvited: if genuinely is the word we reach for when we want to signal authenticity, why do we need to signal it at all? Why is the performance of sincerity so much louder than sincerity itself? And what are we all actually looking for when we say we want it?

The Deconstruction: “Authentic” Is a Poster. Belonging Is a State.

Here is the rule that was handed to you somewhere around the time corporate America discovered vulnerability as a brand:

Bring your whole self to work. Be authentic. You belong here.

It arrived on values posters and in onboarding decks and in the keynotes of leaders who had communications teams polish their “authentic” remarks before delivery. Organizations discovered that belonging was a thing employees wanted, so they added it to the culture deck. Authenticity became a performance requirement. One more thing to optimize for, one more box to check on the way to being a well-rounded professional.

We learned to play along. We learned the vocabulary. We nodded at the right moments. We shared the appropriately vulnerable anecdote in the team meeting. Personal enough to seem real, sanitized enough to be safe. We mirrored the energy of whatever room we were in, filed down the edges that didn’t quite fit, and called it fitting in.

Fitting in is a strategy. Belonging is a state. And you can execute the strategy flawlessly. Know all the right words, hit all the right notes, yet you still feel completely alone in the room.

Here’s the distinction that took me longer than it should have to understand: fitting in requires you to assess the room and adjust accordingly. It is fundamentally an act of reading the environment and conforming to it. Belonging requires nothing of the kind. Belonging is what happens when you show up as the real version and the room receives it. Not because you performed correctly, but because something true passed between people and landed.

You cannot manufacture belonging. You can only create the conditions for it. And the first condition is that someone in the room has to stop performing first.

The irony, genuinely, is that we are all desperately looking for connection while working very hard to present the version of ourselves least likely to actually connect. The curated version. The professionally appropriate version. The version that has read the room and made the necessary adjustments. That version is very safe. It is also very lonely.

The Shift: The One-on-One That Got Real

I had a boss once. Smart. High standards. The working relationship was functional, professional, productive, getting the job done. We had our regular one-on-ones. I answered the how-are-you with fine. They answered the how-are-you with fine. We moved to the agenda.

Then one day, we didn’t.

I don’t remember exactly how it started. I don’t think either of us planned it. But at some point the surface-level how-are-yous gave way to the real question underneath it: why aren’t things working, and how do we actually work better together? The conversation went somewhere that conversations between a manager and a direct report aren’t really supposed to go. Honest. Uncomfortable. The kind where you say the thing you’ve been carrying around for months and then wait to see what happens.

What happened was not what I expected.

It didn’t collapse. Nobody got defensive. What happened instead was that the conversation became real. Genuinely real, not reality-show real. And in the aftermath, something had shifted. Not fixed, not resolved into tidiness, but changed in the way that things change when two people have finally seen each other clearly instead of performing at each other from across a conference table.

I now recognize these times as the ones I genuinely feel belonging in a professional relationship. Not when things were smooth. When things were honest.

Every lasting connection I can trace back follows the same pattern. The real stuff happened when it was difficult to say. Not the vulnerability performance. The actual difficult thing: the conflict not avoided, the feedback given honestly, the moment someone put the real situation on the table instead of the managed version of it. Those are the moments the connection became real.

The Reframe: Belonging requires your willingness to be uncomfortable

Here’s the reframe, and it’s going to feel counterintuitive after everything you’ve been told about professional polish:

The rooms worth being in are the ones where the real version of you takes up space.

Not the unfiltered version. Not the radical transparency version where you say everything you think at full volume without regard for context. Authenticity at work is not the absence of judgment. It is the presence of your actual point of view, your real read on the situation, your honest response to what is happening in the room.

Some practical translations:

Stop performing authenticity and start practicing it.

The difference is small and enormous at the same time. Performing authenticity is saying “I genuinely feel...” because you’ve learned that emotional language lands well. Practicing authenticity is actually deciding what you think before you walk in, and then saying it. Even when it’s inconvenient, even when it might land sideways.

The signal is in how you feel leaving the room.

Not whether the meeting went well in the professional sense. Whether you feel more like yourself or less. Rooms where you are fitting in will drain you in a way that’s hard to name. Rooms where you belong will do the opposite. Learn to tell the difference. Trust the data.

Real conflict is not the enemy of belonging. Avoided conflict is.

Every relationship in my life that has become genuinely lasting (there’s that word again, earned this time) got there through a conversation that was hard to have. Not despite the difficulty. Through it. The willingness to say the real thing, and to stay in the room while the other person processes it, is the foundation of actual trust. Smooth relationships are pleasant. Real ones are load-bearing.

You cannot belong somewhere that only wants the curated version.

This is the hardest one. Some rooms are genuinely not set up for real connection. Some organizations mean the poster but not the practice. Some managers want the performance of openness without the inconvenience of actual honesty. Learning to identify those rooms, and to stop working so hard to belong in them, is some of the most important career work you will do.

The right rooms are out there. They are the ones where something true can be said and received. Where the how-are-you occasionally becomes something more. Where the difficult conversation makes the relationship stronger rather than ending it.

Find those rooms. Then stop performing in them.

The Closing Shot

The contestants on that show were looking for love while doing everything in their power to avoid being seen. Most of us do the same thing at work for twenty years before we figure out that fitting in was never going to get us there. Belonging is on the other side of the real conversation you’ve been putting off.

Somewhere on that vacation, in the wreckage of a reality show and an empty bottle of wine, I remembered what the word is supposed to mean before it got deployed on camera seventeen takes in a row.

Genuinely: in a genuine manner. Actually. Truly. Without performance.

It’s a good word. We just have to mean it.

Share

Subscribe now

The meeting was twelve minutes long.

Jordan had it on the calendar as a thirty-minute one-on-one. Protected time, no conflicts, the kind of slot that signals this matters. But her manager, David, was efficient. He was known for it. Twelve minutes in, the problem had been identified, the solution had been provided, and David was already mentally in the next thing. Which you could tell because he started angling his chair slightly toward the door in the way people do when they’ve decided a conversation is complete.

Jordan thanked him and left.

David leaned back, satisfied in the way you feel when a meeting ends eight minutes early. Productive. Clear. Decisive. He’d heard the situation, recognized the pattern and delivered the answer with confidence and minimal ceremony. He’d seen this before, maybe four times in his career. Good meeting. On to the next.

Jordan walked back to her desk, opened a message thread with her colleague and typed four words:

He didn’t hear me.

Not four words about the solution, which was fine as far as it went. Not four words about David’s intentions, which were good. Four words about the experience of being in the room with someone who was present in the way that furniture is present: physically occupying space, technically available, but not actually there.

Here is what David heard: a project has stalled because of a resource constraint. Solution: reallocate from the Q3 buffer.

Here is what Jordan said: a project has stalled because of a resource constraint. And also, the team is demoralized, and also, she’s been covering for two people who are underperforming and hasn’t said anything because she didn’t want to seem like she was complaining, and also, she’s not sure she has the authority to make the call she thinks needs to be made, and also, she’s been losing sleep about it.

David solved the thing Jordan said first. Jordan needed someone to understand everything she said after that.

They had a twelve-minute meeting. They had two completely different conversations. Both of them left certain about what had just happened.

This is not a David problem. David is every leader who has ever been good enough at their job to recognize a problem before the other person has finished describing it. Which is most of them. Which might be you.

The Lie We Tell Ourselves: I’m a good listener.

The first lie, a belief that almost every leader holds about themselves, almost entirely unexamined: “I’m a good listener.”

It is the most universally held and least verified claim in leadership development.

Ask leaders to rate themselves on listening and the scores are high. Ask their teams \ anonymously, in a safe environment and the picture gets complicated quickly. Not because leaders are dishonest. Because the gap between what listening looks like from the inside and what it feels like from the outside is wider than almost anyone realizes.

From the inside, listening looks like: not interrupting, maintaining eye contact, nodding at appropriate intervals, waiting for the other person to finish before speaking. All of which is fine. None of which is listening.

From the outside, listening feels like: does this person actually understand what I’m trying to tell them, or are they just waiting for me to stop so they can say what they were going to say anyway?

The second lie, specific to experienced leaders: “I already know what they’re going to say.”

Sometimes true. Frequently an assumption dressed as pattern recognition. And when the assumption is wrong, when the thing they’re actually saying is different from the thing you decided they were saying before they finished the second sentence, you’ve just had a very efficient conversation about a problem that wasn’t the problem. You’ve delivered a solution to the wrong question with complete confidence. The other person leaves. You feel productive. The actual issue is still exactly where they left it when they walked into your office.

Efficiency is not the same as effectiveness. Nowhere is that distinction more expensive than in a conversation where someone needed to be understood before they needed to be helped.

The Autopsy: Three Ways Leaders Stop Listening Without Knowing It

Nobody decides to stop listening. It happens faster than a decision. Here are the three ways it happens most reliably to people who genuinely believe they’re paying attention.

1. Solution Mode: The Occupational Hazard

This is the one that gets leaders fastest, because it’s built from something real. Experience. Pattern recognition. The hard-won ability to see around corners that newer leaders can’t see yet.

The moment a problem becomes recognizable, the brain does something automatic and well-intentioned and slightly catastrophic: it pivots to response. The solution starts forming. The recommendation starts taking shape. The leader is now half in the conversation and half somewhere else, running the solution against the incoming facts like a spell-checker scanning a document, looking for confirmation rather than comprehension.

They miss the nuance. They miss the emotion. They miss the part that comes at the end of the second paragraph, after the person has warmed up enough to say the thing they actually came to say.

David solved Jordan’s resource problem. He missed the part where she was exhausted, covering for two people, and quietly drowning. The resource constraint was the opening sentence. The rest was the conversation.

2. Autobiographical Listening: The Subtle Hijack

The other person is talking. Something they say connects to something in your own experience. And before you’ve made a conscious choice, the conversation has pivoted.

“That reminds me of when I was managing the West Coast team in 2019...”

The leader’s experience is real. Often relevant. Occasionally exactly what the other person needs to hear. But the moment it becomes the center of the conversation, the other person has been quietly relocated from protagonist to audience. They’ll spend the rest of the meeting nodding politely while internally noting that they came here to be heard and ended up at a TED talk.

Autobiographical listening feels like connection. From the inside of the experience it is. From the outside of it, it’s a redirect. Often a well-meaning one, but a redirect nonetheless.

3. Selective Listening: The Confirmation Trap

If you’ve already formed a view about the person, the project, or the problem (we covered in the Ladder of Inference how quickly and quietly that happens), you will hear the data that fits the story and let the rest pass through.

You’ll track the parts that confirm what you already think. You’ll mentally fast-forward through the parts that complicate it. You’ll nod at the evidence and float past the counterevidence, not dishonestly, but inevitably.

The result: a conversation that felt complete and produced a response that addressed the story you’d already written rather than the one the other person was actually telling.

These three (solution mode, autobiographical listening, selective listening) are not character flaws. They are the predictable byproducts of experience, intelligence, and a leadership culture that has consistently rewarded fast answers over deep understanding. You didn’t develop them by accident. You developed them because they worked. They’re just working on the wrong thing.

The Napkin Sketch Tool: Two Levels, One Practice

Real listening has two levels. Most leaders operate somewhere in the vicinity of the first and have never been introduced to the second.

Level 1. Listen Beyond the Facts: The ABEI Framework

The default listening mode captures content. The logical structure of what’s being said, the facts as presented, the surface layer of the problem. That’s necessary and insufficient.

Underneath almost every meaningful workplace conversation are four layers that contain more information than the facts do. Learning to listen for them changes what you hear, which changes what you respond to, which changes the quality of almost every conversation you have.

Assumptions: What are they taking for granted?

Every problem gets framed through a set of premises the speaker hasn’t made explicit, often because they don’t know they’re there. Jordan assumed she didn’t have the authority to make the call she needed to make. She never said that, but it shaped everything she did say.

Listen for the invisible premise underneath the framing. What would have to be true for this to be the problem they’re describing? Often the assumption is more addressable than the problem built on top of it. You’ll never find it if you’re already in solution mode.

Beliefs: How do they see this situation?

Not just what happened, but what they make of it. What does their framing tell you about how they see themselves, the team, the organization? Jordan believed she was alone in the problem. That belief, not the resource constraint, was what was keeping her up at night.

The belief layer is where the emotional contract lives. You can solve the presenting problem without touching the belief, and the person will leave with their problem solved and their worldview intact and unchanged.

Emotions: What are they feeling that they haven’t named?

This is the layer most leaders are the most uncomfortable listening for, because naming emotions feels like therapy and therapy feels like not their job. It is their job. Not as a clinical practice, as a human one.

Jordan was exhausted. Demoralized. Quietly resentful of two people she’d been covering for and hadn’t told anyone about. None of that made it into the twelve minutes. Not because she was hiding it, because David never slowed down long enough for it to surface.

The emotional layer doesn’t always need to be addressed directly. But it needs to be heard. An unheard emotion will quietly run the rest of the conversation regardless of whether it’s been named.

Implications: What are they not saying that they might mean?

The thing people are circling before they say it directly. The downstream concern they’re approaching from the side because saying it straight feels too exposed, too risky, too much. What am I afraid might happen here? What do I need that I haven’t asked for?

Jordan’s implication: I’m not sure I can keep doing this without something changing. She didn’t say that. She said the project had stalled. Both were true. Only one of them was the conversation she needed to have.

How to use ABEI in practice:

You don’t run a checklist mid-conversation. You develop a listening orientation. It’s the background awareness. The facts are the surface and there’s something underneath worth being curious about. After someone finishes speaking, before you respond, run a quick internal check: What assumption did I just hear? What emotion is underneath this? What are they implying that they haven’t said directly? One question, asked genuinely, will usually surface more than ten minutes of solution delivery.

Level 2. Listen So Others Feel Heard: The Deeper Listening Practice

This is where listening becomes active. Where the other person experiences, often for the first time in a professional context, what it actually feels like to be understood. Three moves. Each with language you can use starting Monday.

Move 1: Reflect

Play back what you heard in your own words. Not a transcript, a translation. One that shows you were tracking meaning, not just content.

• “What I’m hearing is... Is that right?”

• “It sounds like the real issue for you is... Am I understanding that correctly?”

• “Let me make sure I’ve got this. You’re saying that X, and underneath that there’s a concern about Y?”

The reflect move accomplishes two things at once. It confirms your understanding before you respond to it. This is how you avoid the expensive mistake of solving the wrong problem efficiently. Also, it signals to the other person that you were present enough to track what mattered, not just what was said.

That signal is rarer than it should be. Most people have had the experience of leaving a conversation and realizing the other person heard the words and missed the point. The reflect move is how you make sure you’re not that person.

A note: the reflect move will occasionally reveal that you heard something different from what they meant. This is not a failure. This is the entire point. Better to surface the gap now than to close the meeting, execute the wrong solution, and reconvene in three weeks to figure out what happened.

Move 2: Validate

Acknowledge that what they’re experiencing makes sense. Without necessarily agreeing with every element of their interpretation. Without endorsing every conclusion they’ve drawn. Validation is not agreement. It’s recognition. The signal that their experience of the situation is real and understandable and has been received.

• “That makes sense given what you’ve been navigating.”

• “I can see why that landed the way it did.”

• “That sounds genuinely frustrating and understandably so given the context.”

Here is why leaders skip this move: it feels slow. It feels like a detour from the real work of the conversation. It isn’t. An unvalidated person will spend the rest of the conversation trying to get you to understand how they feel, because they need that to happen before they can engage with what to do about it. Thirty seconds of genuine validation saves ten minutes of circular conversation where the emotional temperature keeps climbing and nobody is sure why.

Validation also doesn’t require you to agree with their read of the situation. You can validate the experience “I understand why this felt like a step backward” without endorsing the interpretation “and I think there’s a different way to look at what happened.” The sequence matters. Validation first. Reframe after. Not simultaneously. Not in reverse.

Move 3: Empathize

Go one level deeper than validation. Not just “that makes sense” but “I understand what that costs you.” The difference between the two is the difference between acknowledging a situation and acknowledging a person.

• “That’s a hard position to be in, especially when you’ve been carrying it alone.”

• “I imagine that’s been weighing on you more than you’ve let on.”

• “That kind of uncertainty is exhausting to sit with over a long stretch.”

Empathy doesn’t require you to have had the same experience. It requires you to be curious enough about theirs to name it specifically. Generic empathy “that sounds tough” sounds like a form being filled out. Specific empathy “carrying two people’s workloads while pretending everything is fine is exhausting” sounds like a person who was listening closely enough to see what was actually happening.

That specificity is what makes the difference. It’s also what makes people feel, sometimes for the first time in a long time, that the person across from them was actually in the room.

Level 3. The Clarifying Question: The Most Underused Tool in Leadership

Before solutions. Before advice. Before the answer you’ve been holding since the third sentence. Ask one more question.

The options, in rough order of impact:

• “What would be most helpful from me right now?”

• “What am I missing about this?”

• “What’s the part you haven’t said yet?”

That last one deserves its own paragraph. Most people arrive at a conversation carrying the real thing underneath several layers of safer content. They lead with the facts: the project, the deadline, the resource. Those feel less exposed than the thing underneath. They circle the actual concern for several minutes, waiting to see if the environment is safe enough to say it directly.

A leader who notices the circling and names it will get to the real conversation faster than the one who solved the presenting problem and sent someone away unheard. “What’s the part you haven’t said yet?” will get there not by being smarter or more experienced but by being more present.

The clarifying question is also the antidote to the most common listening failure of all: responding to what you heard instead of what they meant. You might have heard correctly. You might not have. The only way to know is to check before you act on it.

Even when you’re certain. Especially when you’re certain.

Monday Move

One question to ask: In your next one-on-one, after the other person finishes speaking, before you respond, ask yourself: what did I just hear, and what might I have missed? Run a quick ABEI check. What assumption was underneath the framing? What emotion was in the room that didn’t get named? What were they implying that they didn’t say directly? You don’t need to address all four. You need to notice them before you decide what to respond to.

One behavior to stop: Stop solving before you’ve reflected. The next time someone brings you a problem, make the first thing out of your mouth a reflection or a question, not an answer. “What I’m hearing is... Is that right?” takes fifteen seconds. It will save you from the expensive efficiency of solving the wrong problem well.

One practice this week: In one conversation, just one, try the full sequence. Reflect what you heard. Validate the experience. Ask what you’re missing before you offer anything. Notice what happens to the quality of the conversation after you do. Notice also how hard it is to resist the pull toward the answer you already have. That resistance is the work. The answer can wait two more minutes. The person in front of you has been waiting longer than that.

Last Call

There’s a version of this story that ends differently.

Same Jordan. Same resource constraint. Same stalled project. But this time David doesn’t angle his chair toward the door at minute eight. He hears the resource piece. He still recognizes the pattern, the experience doesn’t disappear. However, instead of delivering the solution he reflects it back.

“What I’m hearing is that the project is stalled and it’s been frustrating to not have the resources to move it. Am I getting the full picture?”

And Jordan, who has been waiting to see if there was room for the rest of it, says “No. Not exactly.” And then she says the thing she actually came to say.

David doesn’t solve everything in that meeting. But Jordan leaves having had the conversation she needed to have, with a leader who was present enough to notice that the resource constraint was the opening sentence, not the whole story.

That’s not a small thing. In a working life full of meetings where people perform listening while loading responses, a leader who actually hears you is the kind of rare that people talk about years later. The kind that makes someone decide to stay when they were thinking about leaving. The kind that turns a twelve-minute efficiency exercise into the conversation that changes something.

It costs nothing except the willingness to slow down long enough to understand before you respond.

That, and the humility to ask what you’re missing before you assume you’ve got it.

The answer can wait. Listen first.

If this landed, share it with the leader who keeps having the same conversation and getting the same result. Because they keep solving the problem they heard instead of the one that was there.

Share

Subscribe now

The enrollment page is open.

You’ve read the program description three times. You’ve done the math on the tuition. You’ve checked whether your company will reimburse it, drafted the justification email in your head, and convinced yourself that this one will finally give you what the last one almost did. This framework, this executive cohort, this advanced certification is the one with the authority.

The authority to speak up without your hands shaking or your stomach knotting.

I know this page. I’ve had my cursor hovering over versions of it more times than I care to count. An MBA. Three leadership programs. Each one valuable. Each one genuinely worth something. And each one, if I’m being completely honest, partially chosen because it felt safer than the alternative. Which was walking into the room with what I already knew and being willing to be wrong about it out loud.

The programs didn’t give me my voice. I had to do that part myself. It just took me a while to understand that’s how it works.

The Deconstruction: The Preparation Paradox

Here’s the rule so deeply installed you probably don’t hear it running anymore:

Credibility is something granted to you by an institution. Authority flows from credentials. When you have enough of them, you’ll feel ready.

We absorbed this early. It has been reinforced often from every grading system, every graduation, every degree requirement, every job posting that asked for certifications we’d never heard of. It became the operating assumption underneath everything. Do we really need a ceremony at kindergarten to tell us we’re ready to be taught? But it’s the signal we know.

You want to speak with authority? Get more qualified. You feel uncertain? Go learn more. You’re not ready yet? There’s a program for that.

The insidious part is that it masquerades as ambition. Continuous learning sounds like growth. And it is growth, right up until the moment it becomes a delay tactic. A delay tactic wearing a blazer.

Here’s the tell: if you’re enrolling in something because you’re genuinely curious and want to develop a specific capability, that’s learning. If you’re enrolling because the alternative is sitting in a room and shipping an opinion that might be wrong and having someone notice, that’s the Preparation Paradox. You’re using the enrollment page as a shield against the exposure of actually being seen.

The paradox is this: the thing you’re trying to earn through credentials cannot be granted by an institution. Authority, confidence, the right to take up space, that’s on you. No program has that power. The MBA gave me frameworks. The leadership cohorts gave me language and a cohort of people who were wrestling with the same questions. They gave me more confidence, genuinely. But the willingness to speak up? The decision to stop waiting for someone to hand me permission? That had to come from me. Every single time.

The Scarecrow in the Wizard of Oz already had a brain. He’d been demonstrating it the whole movie: reasoning, problem-solving, navigating a genuinely dangerous situation with creativity and care. The diploma the Wizard gave him at the end didn’t add a single new neural pathway. What it did was give him a piece of paper to point to when his own conviction wasn’t enough. Which means the real problem was never his brain. It was his belief in it.

You are not short on capability. You are short on the willingness to bet on yourself without a certificate as a safety net.

The Shift: The Executive Who Didn’t Know the Jargon

There’s a type of person you’ll meet as you get further into your career. Senior. Accomplished. Absolutely commanding in a room.

And completely uninterested in the latest framework.

I’ve sat across from leaders who couldn’t have told you the current vocabulary. Whatever methodology was trendy that quarter and whatever acronym the consultants were selling, they didn’t know it. Didn’t pretend to. It didn’t matter at all, because what they had instead was something no program teaches directly: two decades of pattern recognition, the accumulated scar tissue of decisions made under ambiguity, and a practiced, almost casual willingness to be wrong in public and keep moving.

They didn’t prepare their way into authority. They showed up and took it, repeatedly, until the uncertainty stopped being a reason not to.

That’s not recklessness. It’s a different kind of credential. One that gets built not in a classroom but in the accumulation of moments where you said the thing anyway. Where you raised your hand before you were sure. Where you sat at the table before you felt you’d earned it and discovered, afterward, that the earning happens in the sitting.

The confidence I was chasing with every program? It didn’t arrive at graduation. It arrived in moments that had nothing to do with what I’d studied. It was the meeting where I named what nobody else was saying, the project where I made the call without the playbook, the conversation where I told the truth when a more credentialed version of myself might have deferred. The programs gave me scaffolding. The reps gave me the building.

The Reframe: The Practice is the Confidence

Here’s the reframe, and I want you to read it twice:

Readiness is a decision, not a destination.

Nobody feels ready the first time. The executives who look certain in the room have simply been wrong in public enough times that the uncertainty stopped stopping them. They didn’t arrive at confidence. They practiced through it.

Some practical translations:

Audit the enrollment honestly. Before you register for the next program, ask yourself one question: is this going to develop something I genuinely need, or is it going to delay the moment I have to prove what I already know? Both answers are valid data. Only one of them is worth the tuition.

The reps are the credential. Every time you voice an opinion in a room that makes you nervous, you are building the thing no certification can give you. Every time you stay in the conversation past the point of comfort, you are accumulating the pattern recognition that the senior leaders across the table spent decades earning. You cannot get there any other way. The classroom is preparation. The room is the work.

Credentials are scaffolding, not the building. My MBA and my leadership programs were worth it. I mean that without qualification. They gave me frameworks, language, and cohorts of people who sharpened my thinking. But they were inputs, not the outcome. The outcome was built in the moments when I chose to act on what I knew instead of waiting until I knew more. The scaffolding helped me build faster. It was never the structure itself.

The diploma won’t save you in the room. When the conversation gets hard, when someone pushes back, when the stakes are real and the room goes quiet waiting for someone to say the thing… nobody in that moment cares what’s on your resume. They care whether you have a point of view and the conviction to hold it under pressure. That particular muscle only develops one way.

Close the enrollment page. Not forever, not if the program is genuinely the next right thing. But if the honest answer is that you’re hovering over “Register” because the room is scary and learning feels safer than leading, then what you need is not another credential.

What you need is to go be wrong about something important, in front of people who matter, and find out that you survived it.

The Closing Shot

The Wizard didn’t give the Scarecrow a brain. He gave him a diploma, an unearned piece of paper to quiet his imposter syndrome. The Scarecrow did the rest.

The table is waiting. You already have what you need to sit down.

You know enough to take the first rep. Go take it.

Share

Subscribe now

That was how she thought about herself, and she wasn’t wrong. In eleven years of leading teams she had built a reputation for being the one who figured things out. The one who picked up the phone, who stayed late, who never said “that’s not my problem” because frankly she found that phrase morally objectionable. People trusted her. People relied on her. New employees learned within their first month that if something was stuck, she was the one to find.

She was proud of this. It was, she believed, what good leadership looked like.

It took her longer than she’d like to admit to notice the pattern.

Marcus came to her every week. Different content, different people, same pattern. Something had gone sideways, someone wasn’t cooperating, the process wasn’t working, the system was broken. She’d listen, she’d help him think through it, she’d occasionally make a call on his behalf because she knew the right people and it would get resolved faster. He’d leave looking lighter. She’d feel useful. Same time next week.

Then there was Diane, who brought her the interpersonal friction. And James, who brought her the resource constraints. And a rotating cast of others who had learned, as Marcus had, that bringing her a problem was a faster path to resolution than solving it themselves.

One afternoon, a Tuesday, she looked at her calendar and realized she had spent fourteen of the last twenty working hours in conversations that were not her problems to solve. Fourteen hours. She did the math on the month. Then she stopped doing the math because it was making her feel something she didn’t have language for yet.

It wasn’t burnout exactly. It was closer to the feeling of being a door everyone walked through on the way to somewhere else: useful, necessary, never quite wherever the destination was.

She had spent eleven years believing she was helping. She had spent eleven years, it turned out, being the box that other people’s avoidance ran on.

She wasn’t a bad leader. She was a Rescuer. And she had no idea those were different things.

The Lie We Tell Ourselves: I’m Helping

The Rescuer’s signature line is delivered in complete sincerity, every time, in organizations all over the world:

“I’m just trying to help.”

And it’s true. The helping is real. The intention is genuine. It feels like virtue. It feels like exactly what a good leader should do.

What it doesn’t feel like, from inside the role, is a dynamic that’s making the problem worse.

The Persecutor has a version of this too: “I just have high standards.” Also often true. Also not the whole story.

The Victim’s version is the most honest of the three, and the most worth reflecting on: “This keeps happening to me.” When something keeps happening to you across different teams, different organizations, and different relationships, the circumstances are worth examining. But so is the common denominator. You.

Here is the thing about workplace conflict that leaders spend entire careers avoiding:

You are never just an innocent bystander in the dynamic you’re complaining about. The conflict didn’t find you. The triangle formed around three people who each played a role in building it. It stays intact because all three keep playing their roles, often without knowing they have one.

The triangle needs three points to exist. You are one of them.

That’s not an accusation. It’s the most useful thing you’ll hear, because it means you have more power to change the situation than you’ve been giving yourself credit for.

The Triangle: Three Roles Nobody Auditioned For

The Drama Triangle was introduced by Stephen Karpman in the 1960s and it remains one of the most accurate maps of dysfunctional workplace dynamics ever drawn. Not because it describes exotic behavior, but because it describes ordinary behavior so precisely that most people recognize themselves in it on the first read.

Three roles. Each one feels justified from the inside. Each one needs the others to survive.

The Persecutor: The one who thinks they’re just being direct

The Persecutor isn’t always a bully, though sometimes they are. More often they look like the highest performer in the room. The one with the clearest vision, the most urgent drive, the least patience for why things aren’t moving faster. They set high standards and they mean them. They push hard because they genuinely believe the work demands it.

What they don’t see is the environment they’re creating in the process.

The Persecutor prioritizes being right over being effective with people. When something goes wrong, accountability lands on someone else. Their agenda moves first in a meeting. Their timeline determines the pace. Their opinion closes the conversation rather than opening it.

They create Victims not through malice but through consistency. Over time, the people around a Persecutor learn that initiative is risky, that raising concerns is expensive, and that waiting to be told what to do is safer than guessing wrong and being blamed for it.

The tell: when something fails, who is responsible? If the answer is reliably someone or something outside themselves, you’re looking at a Persecutor.

The Victim: The one who has outsourced their agency

Before anything else: the Victim role is not a character flaw. It is frequently a rational response to an environment that has consistently punished initiative or rewarded helplessness. People arrive at this role through experience, through working for Persecutors, through organizations that blame loudly and credit quietly, through years of learning that taking ownership of problems is how you end up owning the consequences of things you didn’t cause.

That context matters. But it doesn’t change what the role costs them.

The Victim avoids decisions because decisions carry risk. They seek validation and rescue because those things are available and feel safer than self-determination. They experience problems as things happening to them rather than things they have any power to shape. Life becomes a series of weather events: external forces and circumstances beyond their influence.

What makes this role so difficult to exit is that it’s often invisible from inside it. The person in the Victim role isn’t performing helplessness. They genuinely feel it. And every Rescuer who steps in to solve the problem confirms, in the most well-intentioned way possible, that the feeling was accurate.

The tell: the problem is always happening to them, never with them. And the cast of villains and circumstances shifts, but the shape of the story stays the same.

The Rescuer: The one leaders most need to examine

This is the role that looks most like leadership and does some of the most reliable damage.

The Rescuer steps in. They solve the problem. They take the call, make the introduction, smooth the conflict, carry the weight the other person put down. Their intentions are genuine. They care about the people they’re helping, and the help is real in the moment. They are often the most competent person in the dynamic, which makes stepping in feel not just natural but responsible.

What they’re not seeing: every time they solve a problem someone else could have solved, they build a higher wall, layer another brick, in the power dynamic. They make themselves more indispensable and the other person more dependent. They confirm, with their actions, that the Victim was right not to try, because trying wasn’t necessary when the Rescuer was available.

The Rescuer is also running a hidden cost on themselves. Fourteen hours a week of other people’s problems. A calendar full of urgencies that aren’t theirs. A quiet resentment that builds over time toward the very people they’ve been helping. At some level they know the help isn’t working, even if they can’t yet name why.

The tell: the same people keep bringing the same category of problem. Nothing resolves. The relationship deepens but the people’s capability doesn’t grow.

If you are a leader and this sounds familiar, don’t despair, stay with it. Because this is the role that has the most to teach you about the next phase of your leadership, and it’s the direct path to the chapter we’ll cover on coaching.

Why the Triangle Is So Hard to Exit

Here is the thing nobody tells you about the Drama Triangle: it’s stable.

Not healthy, but stable. Every role is being maintained by the responses of the others. The Rescuer needs someone to rescue. The Victim needs someone to take the weight. The Persecutor needs someone to absorb the blame. Remove one role and the system pushes to fill the gap.

This is why having the conversation doesn’t fix it. Why resolving the specific conflict doesn’t fix it. Why the same dynamic keeps appearing with different content, different people, slightly different costumes. The roles are intact even when the material changes.

It’s also why you cannot exit a triangle by winning the argument. You can only exit by changing your role. And when you change your role, everyone else in the triangle has to adjust. Which is uncomfortable enough that the system will push back before it rebalances.

That pushback is not a sign that you’ve done something wrong. It’s a sign that the change is real.

The Napkin Sketch Tool: The Empowerment Dynamic

David Emerald’s Empowerment Dynamic offers the exit ramp. It doesn’t eliminate the roles, but replaces each one with an empowered equivalent. The shift isn’t dramatic. It’s directional. A different question asked at the right moment. A different belief held about the person across from you.

Victim → Creator

The Creator doesn’t pretend the circumstances aren’t hard. They just refuse to let the circumstances be the last word.

The shift is in the question. The Victim asks: why is this happening to me? The Creator asks: what can I do about this? Same situation. Different orientation. The Creator has the same constraints, the same difficult colleagues, the same organizational friction. They move differently inside all of it because they’ve kept their agency rather than outsourcing it.

For leaders who find themselves in the Victim role: the next time you’re cataloguing what’s being done to you, stop the inventory and replace it with one question. What is one thing I can do that is within my control? Not everything. One thing. The Creator doesn’t solve the whole problem at once. They take the next available action and see what opens up.

If you’re dealing with a Persecutor above you: the Creator response is not confrontation for its own sake. It’s boundary-setting: clear, calm, and specific about what you will and won’t absorb. That combined with an active choice about how to move forward rather than waiting to be rescued from the situation.

Rescuer → Coach

This is the shift most leaders in this series need most, and it is harder than it sounds because it requires changing a behavior that has been rewarded for years.

The Coach still cares. That part doesn’t change, and it shouldn’t. What changes is the belief underneath the care. The Rescuer, beneath all the genuine warmth and competence, doesn’t fully believe the other person can figure it out without them. The Coach does. That belief changes everything about the interaction.

The shift is from solving to asking.

Not: “here’s what I’d do” but instead: “what have you tried?”

Not: “let me handle that” but: “what do you need to figure this out yourself?”

Not: “I’ll make a call” but: “who do you think you should talk to?”

The Coach listens just as actively as the Rescuer. They show up just as fully. But they hold the problem where it belongs with the person who owns it. They use questions to help that person find their own way to the answer rather than providing one.

This is the first step toward coaching your people rather than managing them, a distinction we’ll go much deeper on later in this series. For now: the next time someone brings you a problem, ask before you answer. The question you ask will tell you more about what they actually need than the solution you were already forming.

Persecutor → Challenger

The Challenger keeps everything the Persecutor values: the high standards, the directness, the refusal to accept mediocre work. But they change the direction of the energy.

The Persecutor’s energy points at people. The Challenger’s energy points at problems.

The difference often lives in a single question: after I raise this, does the other person feel more capable or less? A Challenger names the problem clearly, without softening it into uselessness, and then turns the conversation toward what can be done rather than who is to blame. They create accountability without creating Victims. They hold the standard and hold the relationship at the same time.

This is the hardest shift because it requires the Persecutor to do something their operating style has never required: be interested in other people’s experience of them. .

A word of warning before you try any of this:

When you shift roles in the triangle, the people around you will not immediately celebrate.

They’ll be destabilized. The Victims you’ve been rescuing may be frustrated or even angry. The rescue isn’t coming in the usual form. The Persecutor who has been relying on your Victim response will escalate before they adjust. The system you’ve been part of will push against the change because the change requires everyone else to shift too, and nobody signed up for that.

Tell people what you’re doing. Not as a manifesto, but as a simple statement of intent. “I’m working on how I support people. I’m going to start asking more questions instead of jumping in with answers. Bear with me while I figure it out.” That sentence removes the mystery, reduces the threat, and gives the people around you something to hold onto while the triangle rebalances.

The triangle doesn’t break all at once. It breaks one role shift at a time.

Monday Move

One question to ask: Think of the conflict or difficult dynamic you keep returning to. The one that hasn’t resolved despite multiple conversations and multiple attempts. Ask yourself honestly: what role am I playing in keeping this triangle intact? Not what role the other people are playing. Yours.

One behavior to stop: Stop solving problems that belong to someone else. The next time a direct report or peer brings you a problem, ask a question before you offer a solution. What have you tried? What do you think the options are? What do you need to move forward? The answer will tell you whether they need your expertise or your belief in their ability to figure it out. Those are different things and they call for different responses.

One action this week: Name the triangle you’re currently in with a peer, a direct report, your own leader, or a team dynamic that keeps cycling through the same conflict. Write down your role. Then write down the one question you could ask, or the one behavior you could change, that would begin to move you toward the empowered version of that role. The triangle doesn’t need a dramatic intervention. It needs a different choice, made consistently, until the dynamic shifts.

Last Call

She figured it out on a Thursday afternoon about six months after that Tuesday.

She was in her fourth consecutive problem-solving conversation of the day. Marcus again, a new version of the same shape and she heard herself start to give the answer before he’d finished the question. The way she always did.

She stopped mid-sentence.

“Actually,” she said, “what do you think you should do?”

Marcus looked at her the way people look at a vending machine that has unexpectedly asked them a question. A long pause. Some recalibration.

And then he answered. Not perfectly. Not with the confidence of someone who’d been solving his own problems for years, because he hadn’t been. But he answered and the answer was, largely, right. He had known. He had just learned, over the course of a long working relationship with someone who always had a better answer faster, not to bother finding out.

She didn’t fix everything that Thursday. She didn’t stop caring, didn’t stop showing up, didn’t become the kind of leader who tosses problems back at people and calls it empowerment. The care was the part she kept.

What she let go of was the belief that her help was the only help available. That the people she led needed her to solve it. That being needed was the same thing as being effective.

It wasn’t a comfortable shift. Marcus needed time to trust that she wasn’t abandoning him. She needed time to resist the pull of just answering, which was faster and felt better in the moment and left everyone exactly where they started.

But something changed. He started coming to her differently, not with problems to hand off but with thinking he wanted to test. She started having a different kind of time, more spacious in a way the previous years hadn’t been.

She was still the person people came to.

Just not for the same reason.

You’re not an innocent bystander in the dynamic you’re complaining about. The triangle needs three points to exist. You are one of them.

If this landed, share it with the leader who’s been helping so hard they forgot to ask if the help was working.

Share

Subscribe now

I once worked for a company that shouted its “Unlimited PTO” policy from the rooftops. We wanted the same hip vibe as other tech companies. We touted it in our recruiting deck as a shiny symbol of our high-trust culture.

In the three years I worked there, I took exactly one week off.

It wasn’t because I was a martyr. It’s because the “unlimited” nature of the policy meant there was no structural floor. There was no “use it or lose it” deadline to force a conversation with my boss. Instead, there was just an invisible expectation of dedication that meant I was never off.

When I finally did take that one week, I spent four days of it on “emergency” calls with a new CEO who didn’t understand, or didn’t care, that I was technically OOO. I was sitting on a balcony with a view I wasn’t looking at, squinting at a laptop screen. That’s when I realized that “unlimited” actually meant “undefined.”

And in a corporate environment, undefined is dangerous.

The Deception of the “Perk”

We’ve been told that Unlimited PTO is a benefit for the employee. The data tells a different story.

Studies consistently show that employees at companies with unlimited policies take less time off than those with traditional accrual plans (often only 13 days a year compared to the traditional 15 or more). When the boundaries are removed, high-performers don’t relax. They default to the cultural norm.

If the norm is “always on,” then unlimited PTO is just a fancy way for the company to strike a liability off its balance sheet. Since they don’t have to pay out unused days when you leave, the benefit is all for them.

We trade the clarity of a contract for the anxiety of an unwritten social code.

The Shift: Perks are a Proxy; Managers are the Reality

Younger me thought the Benefits page of the offer letter was the cherry on top. I thought a gym stipend and a flexible vacation policy meant the company “got it.”

I was wrong.

The most expensive “HR benny” in the world cannot protect you from a manager with a broken leadership style. A flexible workplace with a boss who emails at 9:00 PM on a Saturday is not flexible. It’s a prison with better snacks.

The structural reality of your life is determined by two things:

1. The expectations of your manager. What boundaries does your manager set and live by?

2. The leadership style of the person they report to. How do the executives behave?

If your manager views presence as productivity, no policy in the handbook will save your weekend. If your CEO thinks “emergency” is a synonym for “I just thought of this,” your vacation is just a remote office with a worse Wi-Fi connection.

The Alternative: Interview the Manager, Not the Handbook

When you’re looking at the next move, stop looking at the HR perks web page and start auditing the Expectation Architecture.

Before you sign, ask the manager these three things:

1. “When was the last time you took a full week off, and what did your communication with the team look like during that time?” (If they haven’t unplugged in a year, you won’t be allowed to either.)

2. “How do you define ‘done’ for my role?” (Without a definition of ‘done,’ you can never justify being ‘off.’)

3. “Tell me about a time a project hit a snag while a key stakeholder was out. How was it handled?”

The Closing Shot:

Stop falling in love with the perks and start interviewing for the environment. A company with a “boring” 3-week vacation policy and a manager who respects a “hard stop” is infinitely more valuable than a disruptive org with unlimited PTO and a CEO who thinks your time is his inventory.

A perk without a boundary isn’t a gift; it’s an unpaid debt you’ll never collect. You don’t owe a company your burnout as a deposit on your dedication.

Share

Subscribe now

You know the one.

It’s on the calendar every week, same time, same people, same vague title that tells you absolutely nothing about why you’re there. You’ve been in it so many times you could reconstruct the seating chart from memory.

Someone always arrives two minutes late and apologizes in a way that suggests they’re not actually sorry. Someone else opens a laptop and spends the next forty-five minutes pretending to take notes. Or worse, they’re dialing in remote on Zoom, but off camera and not even pretending. The agenda, if there is one, was sent eleven minutes before the meeting started and contains items like “updates” and “other business.”

The meeting ends. Nothing was decided. Someone says “great discussion” with the energy of a person who has been awake since 5am and has three more of these before lunch. Everyone files out, returns to their desks, and quietly resumes the work that the meeting just interrupted.

See you next week.

If this sounds familiar, you are either in this meeting or you are running it. Possibly both. And if you’re running it, here is the uncomfortable news: your team has a name for it, and they use that name in the Slack thread that opens approximately four minutes before it starts.

The good news is that this is entirely fixable. Not with a new app. Not with a standing desk. With three questions, asked in the right order, before you touch the calendar.

The Lie We Tell Ourselves: Alignment is the Only Justification You Need

Ask a leader why they hold a meeting that produces nothing and they’ll give you the same answer every time.

“We need to stay aligned.”

Alignment is real. Alignment matters. Alignment has also become the all-purpose justification for every meeting that doesn’t have a better reason to exist. It is the leadership equivalent of “we should grab coffee sometime”. Sincere in the moment, rarely followed through on, not a plan.

Here’s the test: if you cannot state, in one sentence, the decision your meeting will make or the problem it will solve, you are not ready to have the meeting. You are ready to send an email. Possibly a very short one.

The second lie is gentler but equally convenient: “some people just don’t like meetings.” This is true. Introverts exist. Deep-focus workers exist. People who do their best thinking alone and find group processing somewhere between exhausting and theatrical, they exist. They are valuable, and they are probably your highest performers.

But the resentment most teams carry isn’t about meetings as a format. It’s about meetings as a pattern. A pattern of evidence, accumulated over months, that the person who called the meeting didn’t think hard enough about whether it was worth the room’s time before putting it on the calendar.

That’s not a personality preference. That’s a trust signal. And it compounds.

Pick Your Poison: The Three Meetings Everyone Dreads

Bad meetings come in many varieties. Here are the three that do the most damage, and why.

The Weekly Staff Meeting That Has Become a Hostage Situation

It started with good intentions. Someone, probably a well-meaning leader who had just attended a management training, decided the team needed a regular touchpoint. A rhythm. A space to stay connected.

That was four years ago. The “touchpoint” has since calcified into a ritual that bears no relationship to what the team actually needs in any given week. It happens because it has always happened. The agenda is a round-robin of updates, each person performing relevance for eight minutes while the others wait for their turn and contribute nothing of substance to a function they don’t run.

Eight people. Sixty minutes. A combined hourly cost that would make the finance department weep if anyone ever calculated it. Zero decisions made.

Status is not a meeting. Status is a pre-read, a dashboard, a shared channel, a document that people can consume in three minutes on their own schedule. The moment your weekly becomes a report-out, it has stopped being a meeting and started being a tax. Paid in the most finite currency your team has: time.

The All-Hands Where Leadership Congratulates Itself

In theory, the all-hands is a gift. A chance to connect every person in the organization to the bigger picture. To make people feel seen, informed, and part of something worth showing up for on a Monday.

In practice: a row of senior leaders at the front of a room or a grid of Zoom squares, delivering business updates in the cadence of a quarterly earnings call, to an audience of people who do not own stock and are wondering if this could have been an email. Followed by a round of applause for a milestone that a few people in the room actually achieved, delivered by the people in the front who are accepting the applause.

The all-hands fails when it’s designed for the leaders delivering it rather than the people receiving it. When there’s no genuine attempt to engage the room. When questions are taken at the end in a slot so short that asking one feels like an imposition. When the session ends and someone in the back row has learned nothing that changes how they’ll do their job tomorrow.

People don’t disengage from all-hands because they don’t care about the company. They disengage because the format has taught them that their participation isn’t actually required.

The Offsite That Generates Excellent Photography

The offsite is the highest-stakes meeting in the leadership calendar. It is also the most reliably broken.

Not because the ideas aren’t good. Not because the energy isn’t real. It usually is, at least until day two after lunch when the sugar crash hits and someone suggests an icebreaker. The offsite fails because the strategy generated in a hotel conference room has no structural connection to the system it needs to land in by Tuesday morning.

The Post-its get photographed. The whiteboards get summarized. The team departs with genuine optimism and a tote bag. And then the calendar fills back up, the quarterly fire starts, and the brilliant strategic direction agreed upon at the retreat exists now only in a slide deck that nobody can find and a group chat that went quiet in October.

The offsite without a follow-through system isn’t a strategy session. It’s a very expensive team-building exercise dressed in business casual.

The Autopsy: Why Meetings Erode Trust Before Anyone Says a Word

Here is what your team learns before the meeting starts.

They learn it from the calendar invite with no description. From the agenda that arrived nine minutes before the start time. From the recurring block that has never once had its purpose revisited. From the offsite invitation that says “strategic planning” and includes a ropes course.

They learn that you did not think carefully about this before you put it on their calendar.

And in the framework of the trust equation, which we covered in the last chapter, that is a self-orientation signal. Not a dramatic one. A quiet, consistent, accumulated one. The leader who runs meetings that waste their team’s time isn’t cruel. They’re just not thinking about the people in the room as the primary design consideration.

Meetings are where your trust score is run live, in real time, in front of everyone. The leader who arrives prepared, starts on time, makes space for real disagreement, ends with clear owners and a one-sentence summary of what was decided, that leader’s trust account goes up a little every single week. Compounded over a year, the difference between that leader and the one running the hostage situation is enormous.

You cannot build a high-trust team in an environment where the most recurring shared experience teaches people that their time doesn’t matter.

The Napkin Sketch Tool: The High-Performance Meeting Framework

Three phases. Every meeting, every type, every time. The framework your meetings have been missing is not complicated. It is just deliberate which turns out to be the rarest thing in a calendar.

Before: The Clarity Check

One question. Non-negotiable. Before any meeting gets scheduled:

What is the one decision we need to make, or the one problem we need to solve?

If you can’t answer that, the meeting isn’t ready. Cancel it. Send a memo. Schedule it again when you can answer the question. This single habit will eliminate approximately thirty percent of the meetings currently on your calendar, and your team will notice immediately.

Four things to confirm before the invite goes out:

• This meeting is necessary. Not habitual, not reflexive, not “we’ve always done a Monday check-in”

• The outcome is stated clearly in the invite, not implied

• The right people are in the room, and only the right people

• Anyone who isn’t deciding or doing something doesn’t need to be there

That last one is worth dwelling on. Meetings bloat because leaders add people out of courtesy, politics, or vague anxiety about someone feeling left out. Every person in the room who doesn’t have a decision to make, a problem to solve, or key input on either is an observer. Observers don’t improve meetings. They make them longer, more performative, and more expensive.

The pre-read requirement: if it can be read, it should not be presented. Status updates, project summaries, financial reviews, these go in a document, distributed twenty-four hours before the meeting. The meeting is for what to do about what was read. Not for reading it together, out loud, to adults.

During: Managing the Room

Three roles, assigned before the meeting starts. Not during. Before.

The Facilitator keeps the discussion from disappearing down rabbit holes and ensures every voice gets heard not just the loudest ones.

The Scribe captures decisions and actions in real time, on a shared screen where everyone can see them. Not minutes. Not a transcript. Decisions and actions. If it isn’t written where everyone can see it, it didn’t happen. Yes, we can have AI help document after the fact, but seeing it live and acknowledged real time is where real alignment happens.

The Timekeeper gives a two-minute warning for each agenda item and holds the time budget. This role is an excellent development opportunity for an emerging leader, give them the authority to actually use it and watch them grow three inches.

Two things that change the room immediately, starting with your next meeting:

Open by stating the purpose out loud: “Today we are here to decide X. I’m looking for healthy conflict, not consensus.”

That second sentence does more work than it looks like. It gives permission to the three people in the room who have reservations but were planning to stay quiet. It signals that you want the real version of what people think, not the version that makes the meeting end faster. It is an invitation, and most teams have been waiting for one.

Then: if everyone agrees within the first five minutes, the facilitator plays devil’s advocate. Unanimous early agreement is not alignment. It is usually artificial harmony. The organizational equivalent of everyone nodding at the dinner table to avoid the conversation nobody wants to have. Artificial harmony produces decisions that don’t survive contact with reality. Test the consensus before you trust it.

The Parking Lot is the most underused tool in meeting management and the one that will most visibly demonstrate to your team that you respect the agenda you built. When a topic surfaces that matters but isn’t on today’s agenda, name it clearly: “That’s important. Let’s put it in the parking lot and schedule it properly.” Then actually schedule it. A parking lot that items go into and never come out of is just a landfill.

After: The Accountability Loop

Before anyone closes their laptop or reaches for the door, answer three questions. Out loud. Together.

One: What is the one-sentence summary of what we decided?

Two: Who outside this room needs to know and who is responsible for telling them?

Three: Who owns each action item?

On that third question: one person. Not “the team.” Not “Sarah and David.” One person. The throat to choke, so to speak, which is vivid enough that nobody forgets it.

The twenty-four-hour recap goes out from the Scribe within a day of the meeting: three bullet points maximum. Decisions made. Actions assigned with owners and due dates. Next meeting date. If the recap requires more than three bullets, the meeting produced more outputs than the team can execute on, which is a different problem worth addressing.

The cascading communication question (who outside this room needs to know what we decided?) is the one most leaders skip because it feels like post-meeting homework. It is actually the moment the strategy or solution either takes root or dies. When a leadership team walks out of an offsite without answering this question, the strategy immediately splits into as many versions as there are people who attended. By the time it reaches the people responsible for executing it, it has been filtered through six different interpretations and resembles the original about as much as a game of telephone resembles the source.

Decide what to communicate. Assign who communicates it. Leave the room in agreement about what actually happened in it.

Monday Move

One question to ask: Look at your recurring meetings for next week. For each one, answer in one sentence: what decision will be made, or what problem will be solved? If you can’t answer it, you have some cancellations to make. Your team will not be upset about this.

One behavior to stop: Stop using meeting time for status updates. Move status to a pre-read, a dashboard, or a shared channel. Reserve the room for the friction, the decisions, and the disagreements that actually require other humans in real time. Everything else is a document.

One action this week: Pick the meeting your team dreads most. Run the Before checklist before it happens. State the decision at the top. Assign a Timekeeper. End with the three accountability questions. Notice what your team’s face looks like when it ends on time with a clear owner on every action.

They will look confused at first. That’s normal. Give it three weeks.

Last Call

Here is the thing about meetings that nobody says out loud but everyone already knows.

A meeting is not a productivity tool. It is a leadership demonstration. The recurring weekly that has no agenda is not a neutral event. It is weekly evidence about how you think about your team’s time. The all-hands where nobody gets to speak is not just a missed engagement opportunity, it is a message, delivered at scale, about whose voice matters in this organization. The offsite that generates beautiful slides and zero follow-through is not just inefficient, it is proof that the big conversations your team invested their energy in don’t actually connect to the world they go back to on Monday.

Your team is not dreading the meeting. They are dreading what the meeting has come to represent.

The fix is not complicated. It is not expensive. It does not require a consultant, a new platform, or a mandatory workshop on effective communication. It requires answering one question before you touch the calendar: what decision are we making or what problem are we solving?

Answer that first. Design the meeting around the answer. Treat the hour like it belongs to the people you’re asking to show up for it. Because it does.

Do that consistently and something will shift. The meeting goes from the thing your team manages around to the thing that actually moves the work forward. Trust compounds. The calendar starts to feel like a tool instead of a sentence.

And somewhere, in a Slack thread that opens four minutes before your next weekly, someone types: “Actually looking forward to this one.”

That’s the goal. It’s more achievable than you think.

If this landed, share it with the person who keeps scheduling the meeting that should have been an email.

Share

Subscribe now

You may have seen the story.

Eight years at Atlassian. A layoff notification. Vasilios Syrakis responded the way most of us have fantasized about at least once: he recorded a 40-minute YouTube video walking through the company’s technical architecture.1

The internet lost its mind. Legend. King. He did what we all wanted to do.

I read the comments. I understood every single one of them.

And then I kept reading past the cheering section to the other themes in the comments and social posts. A quarter of responses from the people who said, not with cruelty but with the flat certainty of someone who has made this call before: “I wouldn’t bring him in.”

Not because he was wrong. Because they were now asking a different question entirely.

The Deconstruction: The Story You Leave Behind

Here’s the rule that feels like justice in the moment you’re furious:

They broke the contract first. So all bets are off.

Years of late nights, struggles, decisions, solutions, and institutional knowledge quietly accumulated and it ends. The rage is real. The sense of betrayal is real. The feeling that you are owed something (a scene, a statement, a record of what you actually built) is completely human.

I’m not here to tell you it isn’t.

What I’m here to tell you is that the industry is a small town dressed up as a big one. The org chart changes. Companies restructure, spin off, get acquired. Leaders move. The people you worked with including the ones who made your life difficult, including the ones who signed the layoff paperwork, have a long and inconvenient habit of showing up again.

When they do, they won’t remember your output. They’ll remember your exit.

Here’s what every future employer is quietly asking when they Google your name, read your LinkedIn, hear your name in a reference call: “Can I trust this person with our company?”

Not your technical skills, those are on the resume. The question is about your judgment under pressure. About what you do when you’re hurt and angry and the audience is watching and the match is right there in your hand.

Your exit answers that question whether you mean it to or not.

The Shift: The Client I Almost Never Had

I spent a stretch of my career working in IT for a county government. My team served a lot of departments, HR, Public Safety, Assessor, et al. The one that made my jaw tight was Public Works and Engineering. The kind of department that had been doing things their way since before I arrived and intended to keep doing them that way indefinitely.

The working relationship between IT and Engineering had been strained for years before I got there. I inherited that strain like a piece of furniture nobody wanted but nobody had thrown out. The leaders in that group were dismissive. Meetings felt like they were doing me a favor by showing up. I left more than one interaction feeling invisible, or worse, like I was an obstacle they were tolerating.

I had a whole story built about who those people were.

I moved on. Went into consulting. One of my very first projects landed me across the table from a leader I recognized immediately, someone from that Engineering department. Former county colleague, now my formal client.

First meeting. Conference room. The kind of silence where you can hear everyone deciding how this is going to go.

We talked about how we work together. Mutual goals. What success looked like for both of us. And something shifted, not with a speech or an apology, but in the way that happens when two people stop performing the roles they were assigned and just talk.

Our working relationship was excellent. One of the better client engagements I had in those early consulting years.

The story we’d been carrying about each other was the one built entirely from a strained institutional context, from inherited friction, from meetings where we were playing roles neither of us had chosen. That story had nothing to do with who either of us actually was. The context had changed. So had the people, or at least our ability to see each other clearly.

If I had said something ill-willed or snarky on my way out of that job, if I had let the frustration of that working relationship become part of my exit, I would have walked into that first consulting meeting already defeated. The client would have been a liability instead of a relationship. The project would have started in a hole.

The emotion was real. The frustration was valid. But acting on it would have cost me something I didn’t even know yet that I would need.

The Reframe: Play the Long Game

Here’s the reframe, and it’s less about being the bigger person and more about being the smarter one:

Rage is information. It is not instructions.

Feel it fully. Write the email you’ll never send. Call your most trusted person and say every word you want to say. Process it completely, because it’s real and it deserves to be processed. Then, before you do anything permanent, ask yourself one question: Is this the story I want to have told about me in five years?

Some practical translations:

The ladder you’re climbing is circular. The people you work with today will appear again as clients, as peers at new companies, as references, as the hiring manager at the place you want to work next. The org chart is not a fixed document. It is a living system, and it reshuffles constantly. Every exit is a first impression somewhere else.

There are ways to reclaim your narrative that don’t burn the house down. Document your contributions. Build your portfolio. Write about what you know framed as your expertise, not their exposure. Vasilios clearly had deep knowledge worth sharing. That knowledge he highlighted well. The video title he chose now may be reframing his actions and intent into a liability question in every future interview room.

The context was never the whole story. The Engineering leaders who made me feel invisible weren’t villains. They were people operating inside a strained institutional relationship that predated me, with their own pressures and priorities I couldn’t see from where I was sitting. The consulting relationship showed me that. Almost every difficult working relationship has a version of this underneath it, you just usually don’t get to find out unless you leave the door open.

Your reputation is the longest project you’ll ever manage. It is built slowly, over decades, from hundreds of small decisions that mostly happen when you’re tired or frustrated or feel like you have nothing left to lose. The exit is one of those decisions. It is not the time to finally say everything you’ve been holding. It is the time to be exactly the professional you want to be known as. Because that version of you will walk into every room that comes next.

The Closing Shot

You don’t get the satisfaction of the match and the freedom of the open road. You have to choose. The one you choose on your worst day is the one that travels with you into every one that follows.

Somewhere out there, a leader from a strained working relationship is about to become your next client, your next reference, or the person who decides whether you get the room. Leave the door open. You’ll be glad you did.

There were four of them on the leadership team.

All reporting to the same executive. All smart, all capable, all brought in to run their respective businesses and collectively move the organization forward. On paper it was a strong team. In the room it was something more complicated.

One of them, call him Richard, was genuinely talented. Nobody questioned his expertise. In his own domain he was sharp, decisive, and consistently delivered. If you’d asked the executive whether Richard was performing, the answer would have been yes, mostly, with some caveats about cross-functional execution.

If you’d asked the other three whether they trusted him, the answer would have been no. Quickly, and without much hesitation.

But ask them to explain why and they’d struggle to find a clean answer. Because it wasn’t one thing. There was no dramatic betrayal. No stolen credit in a public forum. No moment you could point to and say: “there, that’s when it broke.”

It was smaller than that. And it had been accumulating for a while.

In planning meetings and offsites, Richard would scroll his phone while others presented. When it was his turn, he expected full attention and full engagement. He’d built deep expertise in his function and almost none in anyone else’s. Not out of malice, just a consistent absence of curiosity about what the other leaders did.

When his strategy stalled, which it did repeatedly, because strategy rarely executes without the support functions, the diagnosis always pointed outward. Sales hadn’t prioritized it. The technology team just didn’t understand. Recruiting hadn’t kept up.

He never learned how those functions worked. He never asked. He needed every one of them to succeed and he never once made them feel like partners in that success.

The other three had quietly learned not to count on him for anything beyond his own lane. They stopped bringing him into early conversations. They worked around him when they could, over him when they had to, and they did it without.

Nobody could name exactly what was wrong. They just knew something was.

The trust equation would have named it on the first meeting.

The Lie We Tell Ourselves: Trust is Just a Feeling

Ask a leader why a relationship or a team feels off and you’ll usually get one of two answers.

The first: “I just don’t trust them.” Said with certainty, acted on with consequence with less access, less candor, less inclusion in the conversations that matter. It is rarely examined further. The feeling is treated as the finding.

The second, harder to admit: “I’m not sure my team trusts me, but I don’t really know why.” Said quietly, usually only to a coach or a particularly honest peer. This leader has been working hard, delivering results, showing up consistently. And they’re genuinely confused by the distance they sense between themselves and their people.

Here’s the lie underneath both: trust is too ambiguous to diagnose.

It isn’t. We’ve just been measuring the wrong things.

Leaders who feel vaguely distrusted tend to audit their performance. They look at their competence, their reliability, their track record. These things are visible. They show up in results and in reviews and in the record of whether you did what you said you’d do. They are real and they matter.

But they’re also the easier half of the equation. And the easier half is rarely where the damage is.

The Formula Most Leaders Have Never Applied

David Maister introduced the Trust Equation in The Trusted Advisor and it remains one of the most useful diagnostic tools in leadership development precisely because it does something feelings can’t: it separates trust into its components so you can see which one is doing the damage.

The equation: Trust = (Competence + Reliability + Sincerity + Empathy) / Self-Orientation

Five variables. Two categories. And one structural feature that changes everything.

The numerator builds trust. The denominator divides it.

That distinction matters. Self-orientation isn’t one variable among five. It’s the denominator. Which means it doesn’t subtract from trust. It divides it. A high self-orientation score doesn’t chip away at what you’ve built. It collapses it. You can score well across every credibility measure and still have a team that doesn’t trust you if the denominator is doing its quiet, consistent work underneath.

Let’s walk each variable, but honestly in the way the textbook version usually doesn’t.

The Credibility Variables: Easier to See, Easier to Fix

These three live in the numerator and they’re the ones leaders tend to audit naturally because they’re observable. When they’re off, people can usually tell you specifically what’s wrong.

Competence: Can you actually do the work?

This is the entry-level variable. You need it to get in the room. Without it, nothing else matters because people won’t follow someone they don’t believe is capable.

But here’s what leaders miss about competence: it’s domain-specific and it has a shelf life. The expertise that earned your credibility three years ago isn’t automatically transferring to the new scope, the new industry, the new level.

Richard was genuinely competent in his function, in his lane. His competence score in his own domain was high. His competence in understanding how the organization actually worked, in knowing how to lead cross-functionally, was something else entirely. He’d never invested in building it because he’d never had to.

Competence trusted in the wrong context is still a trust problem.

Reliability: Do you do what you say?

The gap between intention and follow-through is where reliability lives, and it’s death by a thousand small cuts. Leaders rarely lose reliability in one dramatic failure. They lose it in the accumulated pattern of the thing that was supposed to be done by Thursday and arrived Monday. The commitment made in the room that wasn’t mentioned again. The response that required a follow-up, and another one, before it finally came.

Reliability is particularly tricky because the person depleting it usually has a good explanation for every individual instance. The Thursday thing was a legitimate fire. The commitment got buried under a genuine priority shift. Taken one at a time, each miss is defensible. Taken together, they form a pattern the other person has already named, even if they haven’t said it out loud.

Sincerity: Do you tell the truth?

Not just the absence of lying. Sincerity is proactive honesty. Do you name the hard thing or manage around it? Do you say what you mean in the room or save it for the parking lot conversation afterward? Do you give feedback directly or bury it in language so careful it loses its meaning?

The clearest signal of low sincerity isn’t deception. It’s vagueness. Leaders who hedge, who qualify, who tell people what they want to hear in the moment and correct course later, are the ones that read as insincere long before anyone can articulate why. The team stops believing what they say not because they’ve been caught in a lie but because nothing they say feels quite solid.

Competence, reliability, sincerity. These three are the variables most leaders can diagnose with reasonable accuracy when they’re low. Someone can usually tell you what’s wrong. The output is poor, the follow-through isn’t there, the communication feels slippery. They’re addressable because they’re visible.

The next two are different.

The Relationship Variables: Harder to See, Where the Real Damage Lives

These variables don’t show up in deliverables or track records. They show up in how it feels to be in a room with you, to work for you, to depend on you. Which makes them harder to observe, harder to diagnose, and much harder to give feedback on. Most people won’t tell you your empathy is low or your self-orientation is high. They’ll just quietly stop trusting you and you’ll wonder why.

Empathy: Do people feel heard by you?

Not emotional performance. Not the theatrical version of care that gets deployed in all-hands meetings and forgotten in one-on-ones. Real empathy in a leadership context is simpler and rarer: do the people around you feel genuinely heard when they talk to you?

Richard didn’t. The phone scrolling during presentations was a signal, but it was the visible version of something more pervasive. He wasn’t listening in the meeting because he wasn’t particularly interested in what the other person was carrying. Not cruelly, it just wasn’t where his attention naturally went. He was thinking about his own agenda, his own strategy, his own next point. The room could feel it.

Low empathy rarely announces itself as low empathy. It announces itself as a leader who always seems to steer conversations back to their own territory. Who asks questions but doesn’t really wait for the answer. Who is technically present but somehow not quite there. The team experiences this as distance, then as disinterest, then eventually as evidence that this person doesn’t actually care about them. Which, in terms of the relationship, amounts to the same thing whether it’s true or not.

Self-orientation: And here’s the one that changes everything.

Self-orientation is the denominator. Not because it’s the most important variable, though it may be, but because of what it does mathematically to everything else. A leader with high competence, solid reliability, reasonable sincerity, even genuine warmth can have all of that divided into near-nothing by a self-orientation pattern that the team has quietly noted over months.

And here’s what makes it so difficult: self-orientation is almost always invisible to the person carrying it.

Richard would not have described himself as self-oriented. He would have described himself as strategic, focused, and efficient. He had goals. He had a function to run. He needed results. In his own accounting, he was doing the job.

What the team saw was different. They saw who got the credit when things went well. They watched what happened when his timeline and someone else’s timeline conflicted. They noticed where the accountability landed when his strategy didn’t execute. They observed, over many months, whose interests consistently won when there was a genuine choice and they drew the conclusion that the math eventually forces.

Self-orientation doesn’t usually show up as selfishness. It shows up as a consistent pattern of small decisions that, taken individually, each have a defensible rationale, but taken together tell the team something clear about whose interests are really being served.

That’s what makes it the silent killer. It doesn’t feel like a betrayal. It feels like business as usual. Right up until the trust is gone.

The Napkin Sketch Tool: The Trust Equation as a Diagnostic

Two uses. One for diagnosing what’s happening in a relationship. One for diagnosing yourself.

Use 1: When your gut says something is off

Name the relationship. Score each variable 1–5, not a formal exercise just a gut-check that forces separation. Where does the score drop? That’s where the conversation or the behavior change starts.

Most people find this clarifying in a way that surprises them. The vague sense that something is wrong sharpens almost immediately into a specific variable once you’re forced to score them separately. And a specific variable is something you can actually address. You can’t fix “I don’t trust him.” You can have a direct conversation about a reliability pattern. You can name a dynamic where someone’s orientation seems to consistently favor their own interests over the team’s. You can address what empathy looks like in practice for a particular person.

Name the variable. Work the variable.

Use 2: Audit your own trust account

This is the harder use and the more important one.

Score yourself across each variable from your team’s perspective. Not how you intend to show up, but how you likely land. Better yet: ask someone who will tell you the truth to score you. The gap between your self-assessment and how others experience you is where the real information lives.

Most leaders, when they do this honestly, are surprised in the same place. The credibility variables (competence, reliability, sincerity) they’ve thought about. They have a sense of where they are. The relationship variables are different. Empathy scores are almost always more complicated than leaders expect. And self-orientation is the one where the gap between self-perception and team perception is consistently the largest.

The self-orientation audit: five questions worth sitting with:

• In the last month, when a decision went against what I wanted, how did I respond?How did the team experience that response?

• Whose timeline wins when mine and another’s conflict?

• When something goes wrong, where does the accountability land publicly versus privately?

• When did I last invest real time in understanding a function or person I depend on, purely to understand them better?

• When did I last do something that cost me something and benefited only someone else?

You don’t need to score these. You just need to answer them honestly. The pattern they reveal is usually clear enough.

Monday Move

One question to ask: Think of a relationship where trust feels low: a peer, a direct report, a boss. Run the equation. Score each variable 1 to 5. Which one is actually doing the damage? The credibility variables will be easier to name. Push yourself to score the relationship variables too. That’s where the answer usually lives.

One behavior to stop: Stop treating trust as binary. It isn’t there or not there. It’s high or low across five specific dimensions, and each one can be worked. The next time your gut signals something is off, resist the urge to manage around it. Get specific. A self-orientation pattern is addressable. Vague distrust isn’t.

One action this week: Run the self-orientation audit. Five questions, honest answers, fifteen minutes. If you’re genuinely not sure how you’d score, find someone who will tell you the truth and ask them. The gap between what you think and what they’ve experienced is not a comfortable conversation. It is a useful one.

Last Call

Richard eventually left the organization. Not fired, a mutual decision. The kind that gets announced with carefully worded language about pursuing new opportunities and leaves everyone nodding without saying what they actually think.

The executive was reflective about it afterward. He’d seen the dynamic for a long time. He’d coached Richard on strategy, on execution, on cross-functional relationship building. He’d given feedback on specific behaviors. He’d never named the actual variable. The self-orientation that sat underneath all of it, dividing every strength Richard had by a denominator that the team had been calculating long before management caught up.

Here’s what I want leaders to carry from this: the trust equation doesn’t ask you to be someone you’re not. It asks you to be honest about which dimension is doing the damage in your relationships and in yourself.

The credibility variables are visible. When they’re off, you’ll usually hear about it, or see it, or feel it in the results. They’re fixable because they’re concrete.

The relationship variables are quieter. They live in the space between what you intend and how you land. In the pattern of small decisions that accumulate over months. In the denominator that’s been crushing the calculation while you were measuring the numerator.

Your gut already knows when trust is low. The equation tells you where to look.

Most of the time, if you’re honest, you already know too.

If this landed, share it with a leader who’s been wondering why they just don’t trust that one over there.

Share

Subscribe now

It’s a Tuesday. Late morning. I’m sitting on a bench at Salt Creek Beach in Dana Point, notebook open, watching the Pacific do its thing.

I want to be clear: I earned this bench. The morning had been genuinely productive. I was up early and in the zone. That flow where the ideas and the words come out clean and you don’t have to fight them. So when I decided to take a long lunch and drive down to the park, I had receipts. I could justify it. I was, in the language of high-achievers everywhere, allowing myself a break.

That’s when I noticed the surfer.

Late 30s, maybe early 40s. Just done with his turn of trying to catch a break, still damp, drying off on the grass nearby. He was on the phone with a tone of voice that said wife or mother, the specific register used when explaining themselves to someone who has standing to ask. I wasn’t trying to eavesdrop. But then he said it, clear as anything:

“On Tuesdays I play. I work hard. I’m entitled.”

— A stranger who didn’t know he was writing my next article

He wasn’t defensive, just matter of fact. And then he continued his conversation, completely unbothered.

I sat with that for a long time.

The Deconstruction: The Guilt Is Not a Moral Signal

Here’s the rule we absorbed so early it feels like oxygen:

Rest must be earned. Downtime must be justified. Play is what happens after everything else is done, which means it almost never happens.

For high-achievers, and especially for ambitious women who were handed the “lean in” manual before they had any idea what they were leaning into, this runs bone-deep. We were rewarded so consistently and so early for output (gold stars, GPAs, performance reviews, promotions) that our nervous systems learned to read stillness as danger. If I’m not producing, I’m falling behind. If I’m falling behind, I’m failing. If I’m failing…

You know the spiral.

The guilt you feel taking a Tuesday afternoon isn’t a character flaw. It’s a conditioned response, installed so thoroughly that it masquerades as a conscience. It tells you that the beach is irresponsible, that the long lunch is indulgent, that the people who are serious about their careers are at their desks right now while you are watching waves.

It’s lying to you.

And here’s the tell: I had earned my bench that morning, and I was still, quietly, keeping score. Still tracking my hours like I owed someone a report. Still treating the water and the air and the hour of actual breathing as a transaction I needed to justify rather than a decision I was allowed to make.

The surfer wasn’t keeping score. That’s the whole difference.

The Shift: Cameron’s the Warning. Ferris Is the Point.

Bear with me for a second, because we’re going back to 1986.

Ferris Bueller’s Day Off is not, despite what your high school vice principal believed, a movie about getting away with things. It’s a movie about two completely different relationships with being alive.

Ferris understood something his best friend Cameron could not: that the good stuff doesn’t get easier to claim later. That waiting until you’ve really earned it, until the conditions are perfect, until you’ve proven enough, that’s not a plan. That’s a postponement. “Life moves pretty fast,” he tells the camera. “If you don’t stop and look around once in a while, you could miss it.”

Cameron spends the entire movie rigid with anxiety. Cataloguing what could go wrong. Waiting for the other shoe. He can’t enjoy the Art Institute or the baseball game or the Ferrari or any of it. Not really. Because he’s too busy bracing for the consequences of having taken the day. He hasn’t internalized the right to just be somewhere good.

I was Cameron for a long time.

I went to the beach on a Tuesday and I still wrote myself a permission slip first. The surfer just went to the beach on a Tuesday. The gap between those two things is not ambition. It’s the quiet, expensive belief that you have to purchase your own life in installments of productivity before you’re allowed to actually live it.

That belief will take more from you than any missed deadline ever will.

The Reframe: Sometimes you need to play, even on a Tuesday.

Here’s the reframe, and I want you to take it seriously even though it sounds simple:

Play isn’t the opposite of productivity. It’s the infrastructure underneath it.

No engineer would run a system at 100% utilization indefinitely and expect it to stay stable. You don’t get better performance by eliminating recovery time. You get a system that runs hot, degrades quietly, and fails at the worst possible moment. You are not exempt from this because you’re ambitious. You are more susceptible to it because you’re ambitious.

Some practical permissions:

You don’t have to earn a Tuesday. You have to decide it. The surfer wasn’t rewarding himself for a good week. He wasn’t banking rest against future output. He had decided, at some point, that Tuesdays were for playing and then he did it. And then he defended that decision to whoever was on the phone without a flicker of apology in his voice. That’s not laziness. That’s self-knowledge.

The guilt is data, not instructions. When you feel the pull to justify the walk, cut short the lunch, check the laptop before you’ve finished your coffee, notice it. That’s the conditioning talking. You can acknowledge it without obeying it. Of course it feels uncomfortable. It was designed to feel uncomfortable. That doesn’t mean it’s right.

Unstructured time is where your best thinking lives. I had my most productive writing morning in weeks. Then I went and sat by the ocean and let my brain wander, and I came home with the seed of three more ideas. That is not a coincidence. The brain doesn’t generate insight under continuous pressure. It generates insight in the exhale. You need the exhale.

The Closing Shot

You are not behind. You are not failing. You are a person who occasionally needs to go sit by the water on a Tuesday. Or sing a Wayne Newton song in the middle of a parade. That is not a reward, it’s a job requirement.

The surfer dried off, finished his call, picked up his board, and walked back to his car. He looked like a man who had his life approximately figured out. I watched him go and thought: yeah. On Tuesdays, play. You’ve earned it. More importantly, you don’t have to.

Share

Subscribe now