This week, you’ll get:

• The hidden meeting killer: your first opinion becomes everyone else’s ceiling

• A 7-minute meeting rep: The Speak-Last Rule (how to extract intelligence, not perform it)

• One sentence that makes bad news safe (and leadership real)

• Four reads that sharpen the “question leader” muscle

THIS WEEK’S THEME

If you speak first, you set the ceiling.

Most leaders don’t run “collaborative” meetings. They run anchoring sessions.

You walk in prepared (good).
You share your take early (normal).
And without meaning to, you tell the room: “We’re thinking inside my frame today.”

That’s why you keep getting “alignment” instead of better thinking.
Not because your team is weak. Because your design is.

Midweek gut-check:
Are you building a smarter room… or a room that’s good at agreeing with you?

YOUR 2% MOVE THIS WEEK

The Speak-Last Rule

A 7-minute reset that turns a meeting from performance → extraction.

Step 1 — Prime the room (2 minutes).
At the top of the meeting, drop this prompt and go silent:

• “In one minute: What do you see?”

• “In one line: What’s the risk we’re ignoring?”

• “In one idea: What would you do next?”

Everyone writes. Cameras on or off doesn’t matter. Pens moving matters.

Step 2 — Round-robin the thinking (3 minutes).
Each person shares one line from their notes. No debate yet. No fixing yet.
Your job is to listen for patterns and tension, not to respond.

Step 3 — You speak last (2 minutes).
Now you say:

• “Here’s what I heard.”

• “Here’s what changes my mind.”

• “Here’s the decision we’re making (or the question we’re answering next).”

• “Owner is ___, next step by ___.”

This is the move: your voice becomes the synthesizer, not the ceiling.

ONE SENTENCE TO USE THIS WEEK

When someone asks, “So what do you think?” before the room has spoken:

Say it calmly. Then shut up long enough for someone to actually answer.

THIS WEEK’S READS

1. “The Surprising Power of Questions” — Questions don’t just gather info—they change behavior, trust, and outcomes.

2. “Most Managers Don’t Know How to Coach People. But They Can Learn.” — The fastest way to stop being “the answer” is to become the coach.

3. Brainwriting Template — Silent idea generation beats “whoever speaks loudest wins.”

4. “What is the ladder of inference?” — It shows how teams jump from data → assumptions → certainty… fast. Use it to strengthen “What am I missing?” into a real practice.

GO DEEPER IN THE LAB

The Sunday Lead went straight at the ego-trap: needing to be the smartest person in the room.

Midweek, your rep is simpler: design one meeting so your team’s thinking shows up before yours does.

If you missed the Sunday edition, start there, then come back and run the Speak-Last Rule once.

QUICK CHECK-OUT

Reply (or comment) with one leadership question you’re willing to ask this week.
Not a “thoughts?” question. A real one.

Example: “What am I missing that would embarrass us later?”

See you Sunday. Pleasantries.
— Chibundu

Happy Mother’s Day.

Before we get into meeting culture and the three questions that change rooms, I want to start with the people who were doing all of this before it had a name.

Think about the best version of a mother’s guidance.

Not the version that does the homework for you.

The version that sits beside you and asks: What do you think this problem is asking?

The version that already knows the answer and chooses the question anyway. Because she understands something most leaders take a decade to learn:

Her job is not to demonstrate her intelligence.
Her job is to develop yours.

That is intellectual humility in its most elemental form. And for a lot of us, we received it long before we ever got promoted, read a framework, or sat through a leadership training.

Many of the most formative leaders in most people’s lives were not executives or mentors.

They were mothers. Women who held the standard firmly, asked before they told, and found a way to believe in the person in front of them before that person believed in themselves.

Today is the right day to name that. And it’s also the right frame for everything we’re about to build.

🧱 Being the Smartest in the Room Is a Fragile Strategy

I have been the most prepared person in a room and used that preparation to shut the room down.

Not intentionally. Not cruelly. But I’ve sat in meetings where I knew the issue well enough that I:

• answered questions before they were fully formed

• redirected ideas that weren’t going where I’d already decided we were going

• moved the conversation forward at a pace that left people behind

I called it efficiency.

What it actually was (I realized later) was a subtle message to everyone in the room: This meeting will move at my speed, and my conclusions are the destination.

Many of the people in those rooms were talented. Some were sharper than me on a few of the specific problem we were working through.

But I had engineered the environment to produce my thinking instead of the room’s best thinking.

That is the trap. Not the loud, obvious arrogance. The quiet version that looks like competence and functions like a ceiling.

Let me say the uncomfortable part plainly:

And in some leaders, it becomes an addiction.

Because being the smartest in the room is one of the most socially acceptable ego strategies in professional life.

We reward it with promotions. We call it “high standards.” We celebrate it as “exceptional judgment.”

But individual brilliance and organizational capability are not the same thing. In fact, they can be inversely related.

When a leader needs to be the smartest in the room, they tend to (often unintentionally):

• hire for comfort instead of challenge (people who don’t threaten the top spot)

• run meetings as performances (to display mastery, not extract intelligence)

• solve problems faster than their team can develop (and then wonder why ownership is low)

• become the bottleneck (and call it “being essential”)

Then around year three or four, they hit a wall:

“My team isn’t taking ownership.”
“We keep firefighting.”
“Everything runs through me.”

Yes. Because you built it that way.

Your knowledge has a ceiling. Your bandwidth has a ceiling. Your patience has a ceiling.

Leadership strategies that depend on one person’s brilliance are one bad quarter away from crisis.

🧠 This Hits Differently Depending on Who You Are

Here’s what most leadership content about humility avoids saying:

For leaders of color, for women, for leaders without formal titles or institutional cover, the advice to “stop being the expert” lands in a completely different context than it does for someone whose competence is assumed by default.

Because in a lot of rooms, the person who is most prepared and most credible holds back, not from ego, but from learned experience:

• expertise displayed too confidently gets labeled as “arrogance”

• directness gets read as “aggression”

• certainty gets translated as “not being a team player”

So let me be clear:

Intellectual humility is the discipline of building a room that is genuinely smarter than any single person in it, including you, and then trusting that room to produce better outcomes than your solo brilliance ever could.

If you want the quick self-audit, ask:

• Am I holding back because the room doesn’t feel safe? (That’s a leadership context problem.)

• Or am I holding back because I’m trying to extract the room’s intelligence before I anchor it with mine? (That’s intellectual humility.)

Different reasons. Different solutions.

🔑 The 3-Question Leader

The shift from performing expertise to extracting intelligence starts with three questions.

They are simple.

They are not easy to ask genuinely.

And if you had a mother (or mentor) who asked before they told, you already know what these questions produce.

📦 The 3-Question Rep

(Copy/paste this into your next meeting agenda.)

1) “What do you see?”
2) “What am I missing?”
3) “What would you do?”

Now let’s make them practical.

1) “What do you see?”

Not “Do you agree with what I see?”
Not “Here’s my take… thoughts?”

This is an open-field question. It invites analysis before your view anchors the room.

Most leaders pollute this question by telling the room what to think first. Ask it clean. Then go quiet long enough for the real answer to surface.

2) “What am I missing?”

This is the question most leaders can’t ask authentically because it requires believing you might be missing something.

And here’s the part that matters:

If you ask this question and then immediately defend your original position, the question wasn’t real. It was theater.

The real version sounds like:

• you ask

• you stay quiet

• you consider

• and sometimes you say the sentence that changes meeting culture:
  “That actually changes how I’m thinking about this.”

If you never say that sentence, it’s worth asking why. Because either (a) you’re never missing anything (unlikely), or (b) the room doesn’t feel safe telling you, or (c) you’re asking for input you don’t intend to use.

3) “What would you do?”

This is delegation disguised as consultation.

It transfers ownership before the meeting ends. It moves someone from having opinions to taking positions.

That movement is where capability gets built.

This is also where a lot of leaders panic, because you will get answers that are different from what you would do.

Not worse. Different.

If you can’t tolerate “different,” you can’t build leaders. You can only build assistants.

🗣️ Meetings Are Either Performances or Extractions

Every meeting is either:

• a performance of intelligence, or

• an extraction of intelligence.

And the leader makes that choice, usually without realizing they’re making it.

A performance meeting looks like:

• the direction is set before the room arrives

• questions are treated like interruptions

• the leader talks most

• the output could have been an email

An extraction meeting looks like:

• the leader comes with questions, not conclusions

• preparation is used to ask better questions, not give longer explanations

• silence isn’t awkward, it’s productive

• the best idea often comes from someone who isn’t the most senior person in the room

Here’s the uncomfortable truth:

Performance meetings are deeply satisfying for the person running them. There is real pleasure in demonstrating mastery.

But that pleasure is self-referential. It serves the leader’s ego and drains the team’s ownership at the same time.

This is why problem-delegation matters.

Most leaders delegate tasks:
“Here’s what to do. Here’s how to do it. Execute.”

Leaders practicing intellectual humility delegate problems:
“Here’s what we’re trying to solve. Bring me your thinking on the approach.”

One produces compliance. The other produces capability.

And yes: it is slower at first.

It is also the only way to build a team that can function without you.

One small rep you can steal this week

Open your next meeting with:

“I’m holding my view until I hear yours. Here’s the decision we need by the end. What do you see?”

Then do the hardest part: stop talking.

🧪 THE LAB REPORT

Work through these honestly. The hardest ones are the most important.

🔍 On Your Current Pattern

1. In my last three meetings, the ratio of my talking to my listening was approximately: _________________________
   …and if I’m honest about what that produced, it was: _________________________

2. The last time someone on my team said something that genuinely changed how I was thinking was: _________________________
   …and my response in the moment was: _________________________

3. A place where I’m consistently over-functioning (solving things my team should be solving) is: _________________________

🔁 On the 3-Question Practice

1. The meeting I have this week where I could ask “What do you see?” before sharing my own analysis is: _________________________

2. The person whose thinking I most consistently underuse is: _________________________
   …and the reason I underuse it is probably: _________________________

3. One problem (not a task, a problem) I could delegate this week and trust the outcome of is: _________________________

⚡ On the Honest Edge

1. If I examine my pattern honestly, am I practicing intellectual humility or performing it?
   The evidence that tells me the truth is: _________________________

2. The question I’m most afraid to ask my team because I might not like the answer is: _________________________

🎯 THE 2% CHALLENGE

In your next meeting, ask:

“What am I missing?”

And mean it.

Not as a rhetorical close. Not as a performance of openness.

Ask it. Go quiet. Sit in the answer long enough to actually consider whether it changes your thinking.

Then, if it does, say so out loud:

“That changes how I’m thinking about this.”

Not to perform vulnerability. Because your team needs to see what it looks like when a leader actually updates.

One question. Genuinely asked. Genuinely received.

Questions scale leadership. This is where it starts.

🧡 One Last Thing

The leaders who are most remembered are almost never the ones who were the most brilliant in the room.

They are the ones in whose presence people felt most capable.

I keep coming back to that, especially today.

Because if you think about the mothers who shaped the most capable leaders you know, that’s usually the description:

Not the ones who had all the answers.
The ones who made you feel like your answer mattered.

They asked before they told.
They held the standard high and stayed in the room with you while you worked toward it.
They believed in the version of you that hadn’t arrived yet, and asked questions that helped you get there.

To every mother in the Lab: thank you for showing us what leadership looks like in the most important rooms of life.

And to the leaders reading this who are doing leadership work without the title, without the institutional cover, without the automatic assumption of competence:

This practice is leverage.

The leader who makes everyone around them smarter, who asks the question that unlocks the room, who credits specifically and delegates boldly, does not wait to be recognized.

They build something so undeniable that recognition becomes a formality.

You are not the smartest in the room. That is not the goal.

The goal is to build a room smarter than any one person in it, and to be the kind of leader whose presence makes that possible.

🔁 Share + Engage

What’s your favorite leadership question, the one that changes conversations when you ask it?

Drop it in the comments. I read every one, and the best ones are going into a future Lab resource.

And if you have a mother, grandmother, mentor, or woman in your life who asked the right questions at the right moments: share this with her today. That’s a good use of a Sunday.

Share

See you on Wednesday. Pleasantries.

— Chibundu

This week, you’ll get:

• A midweek reframe for when you’re tempted to shrink or show off

• A 3-step rep called Signal → Invite → Elevate

• One sentence to keep you out of the ego ditches

• Five reads/listens with real links worth your Wednesday attention

🧭 THIS WEEK’S THEME

Humility is Not Shrinking. It’s Stable.

By Wednesday, most leaders drift into one of two bad habits:

• Over-functioning (talking too much, taking up too much, needing to be “the one”)

• Under-showing (going quiet, over-qualifying, letting your best thinking die in your notes app)

Both are ego, just in different outfits.

Humility is the center: clear enough to contribute, secure enough to share the room.
That’s not personality. It’s a rep.

Subscribe now

🔁 YOUR 2% MOVE THIS WEEK

The Signal → Invite → Elevate Rep

Run this once in your next meeting. You’ll feel the difference immediately.

Step 1 — SIGNAL (Clear spine).
Say your point cleanly in one sentence. No disclaimers. No apology tour.

Example: “Here’s what I’m seeing: we’re solving the symptom, not the cause.”

Step 2 — INVITE (Open hands).
Ask one question that proves you’re here for the truth, not the trophy.

Example: “Where could this break?” or “What am I missing?”

Step 3 — ELEVATE (Share the room).
Hand the mic to someone else on purpose.

Example: “I’d love to hear [Name] pressure-test this.”

That’s humble confidence in 20 seconds.
It keeps you out of both traps: erasing and inflating.

🗣️ ONE SENTENCE WORTH KEEPING THIS WEEK

(That’s the line to repeat when you feel yourself performing.)

📚 THIS WEEK’S READS/LISTENS

1. “The Power of Humble Leadership”: Short, practical, and sharp. A quick reset when you’re tempted to make leadership about you.

2. Watch: “What It Takes to Be a Great Leader”: A clean explanation of the “humility + will” leadership paradox, without the fluff.

3. “Being Passionate to Perform: The Joint Effect of Leader Humility and Follower Humility”: This is evidence that humility is not “soft,” it’s functional.

4. Listen: Brené Brown + Michael Bungay Stanier on the “Advice Trap”: If you tend to “help” by taking over, this one will hit. Humility often sounds like better questions.

5. “The Value of Humble Leadership”: Why humility changes trust, tone, and followership.

🧪 GO DEEPER IN THE LAB

Sunday’s Lead goes deeper on the two traps that look like humility but aren’t, plus the “clear spine / open hands” model for showing up accurately in rooms that matter.

Quick check-in (hit reply):

What do you need more of this week?

SPINE (clear contribution) or HANDS (open posture)?

Forward this to the leader who keeps disappearing in rooms they earned a seat in. Or the one who can’t stop auditioning for “smartest person here.” Either way, this rep helps.

See you Sunday. Pleasantries.

— Chibundu

There’s a moment I still replay sometimes.

I was running a meeting. At the end, someone casually said:
“Yeah… all of this was already discussed in another meeting.”

My stomach dropped.

Translation: I wasn’t in the room.

In a territorial environment, being “left out” doesn’t just feel like a calendar mistake. It feels like your authority is being tested.

So my nervous system did what tired leaders do late in a long week.
I drafted a message. Polite. Direct. “Please include me going forward.”

I revised it… a ridiculous number of times.
And even after all that editing, you could still feel the edge underneath it. Because my real goal wasn’t clarity.

My real goal was to prove: I’m running this whole show.

That’s not humility.

That’s ego trying to stay safe.

And on the other side of that same mistake is the version of us that stays quiet even when we’ve done the work, know the issue, and could genuinely help the room. We call it humility. It’s usually fear.

A few years ago, I was in a stakeholder meeting where the loudest voice in the room was also the least informed.
He was confident and wrong, and I could feel my ego warming up like, say something… correct him… prove you belong here.

Instead, I asked one question that redirected the room:
“Can we define what success looks like in one sentence before we debate tactics?”

The temperature dropped. There was less performance.

A junior colleague (who rarely spoke) offered the clearest answer in the room. I handed her the floor, built on her point, and then shut up again. After the meeting, I sent a clean one-page recap: decisions, owners, next steps.

Nobody remembered who “won” the meeting.
They remembered who made it make sense.

That’s when it clicked for me: humility isn’t silence. It’s leadership that doesn’t need applause to be effective.

Most of us swing between both.

• Over-performing to protect our status.

• Under-speaking to protect our image.

Neither one is humility. Both are self-focus.

And if we don’t get this virtue right, we’ll keep mistaking performance for character… and silence for grace.

Share

🧭 The Definition We Were Given is Wrong

A lot of us inherited this definition: humility means making yourself small.

Head down. Don’t brag. Defer. Wait to be called on. Minimize yourself so nobody can accuse you of thinking too highly of yourself.

But C.S. Lewis nailed the correction:

That sounds subtle. It’s not.

• “Think less of yourself” teaches shrinking.

• “Think of yourself less” teaches freedom.

Humility is not self-erasure. It’s accurate self-assessment with the spotlight off your ego and onto the work.

A humble leader isn’t unsure of their worth.
A humble leader just isn’t obsessed with proving it.

🪤 Two Traps that Sound Like Humility, but aren’t

Trap 1: Inflate

This is the leader who fills every silence. Claims every win. Competes for the spotlight. Needs to be seen as the sharpest person in the room.

That’s not confidence. It’s insecurity with a microphone.

Over time, people realize the agenda isn’t the mission. It’s the mirror.
And trust gets expensive.

Trap 2: Erase

This is the leader who over-qualifies every idea. Stays quiet in rooms they earned their way into. Calls it “not wanting to take up space.”

Sometimes what we call humility is just fear.

And the cost is real: the room loses the value you were supposed to bring.

Both traps keep attention stuck on you.

• Inflate says: “Look at me.”

• Erase says: “Please don’t look at me.”

Humility exits that loop.

🧩 The Humility Model that Actually Works

Clear Spine. Open Hands.

This is the simplest model I’ve found that holds in real meetings, real pressure, and real politics.

Clear Spine means you stand in your expertise.
You know what you bring. You’ve done the work. You don’t need permission from the room to be solid.

Open Hands means you hold your ideas loosely.
You listen. You let better ideas win. You give credit without performing it. You don’t need your name attached for the work to move.

Clear spine without open hands becomes arrogance.
Open hands without clear spine becomes shrinking.
Humility is holding both at the same time.

Humility is strength without spotlight.

[IMAGE: Mid-article graphic — “Clear Spine / Open Hands”]

📌 What This Looks Like in Leal “Loud Rooms”

Board meetings. Stakeholder calls. Coalition briefings. Policy rooms. Senior leadership updates.

Those rooms tempt you into two bad strategies:

• Compete for airtime

• Disappear and call it professionalism

Neither one serves the mission.

The leaders who move work in those rooms show up with what I call humble confidence:

• They contribute with clarity.

• They stay curious.

• They don’t need to win the room, just move the work.

That’s not a diminishment. That’s an upgrade.

🗣️ What Humble Confidence Sounds Like

These are not “scripts.” They’re reps.

When you’re tempted to…
Try this instead…

• Over-qualify before you say your point
  → “Here’s what I’m seeing. I’d want to pressure-test it, but it matters.”

• Stay silent while someone else runs with your idea
  → “Building on what you said, the piece I’d add is…”

• Apologize for taking space
  → “I want to put something on the table for the group.”

• Nod along to protect the relationship
  → “I see it differently. Can I share what’s driving that?”

• Perform credentials before your point
  → “From what I’ve seen working on ___, here’s the pattern.”

This is the muscle: accurate contribution without performance.

🔗 From Grace to Humility: the Thread

April was Grace. A month of learning to lead without punishment:

• Grace for yourself

• Grace in feedback

• Grace under fire

• Grace in systems

Now May is Humility, and it’s the deeper question underneath all of it:

Can you see yourself accurately?

Not inflated. Not erased. Accurate.

Grace is honest assessment without cruelty.
Humility is that same discipline applied inward.

You don’t catastrophize your mistakes.
You don’t pretend they didn’t happen.
You don’t inflate your contribution.
You don’t delete yourself either.

And that honesty is why humble leaders get trusted. Not because they’re perfect. Because they’re real.

🧪 THE LAB REPORT

One room. One rep. This week.

🔍 On Your Default

1. Under pressure, I tend to default toward (circle one): inflate / erase
   The behavior that tells me I’ve gone there is: _________________________

2. The room/context where this shows up most reliably is: _________________________

3. The last time I stayed quiet when I had something worth saying, I told myself: _________________________
   What was more likely true: _________________________

🔁 On the Rep

1. One room I’ll be in this week where I usually shrink or over-perform is: _________________________

2. The phrase I’ll practice in that room is: _________________________

3. The expertise I’ve earned that gives me the right to speak is: _________________________

⚡ On the Carryover

1. One way I practiced grace last month that I want to carry into May is: _________________________

Share Everyday Leadership Lab

🎯 The 2% Challenge

Pick one room you’ll be in this week.

A meeting. A briefing. A call. A conversation with a decision-maker.

In that room, contribute once using one of the reps above.

Not to prove you belong.
Not to take space for its own sake.
But because the room needs what you actually know.

Humility is accuracy.
Shrinking is not a virtue.
And the work is too important for your silence.

One rep. That’s the 2%.

🧡 One Last Thing

Humility is not pretending you’re nothing.

It’s refusing to make everything about you.

The leaders who last are rarely the loudest in the room. They’re the ones who are most accurately themselves. No performance. No shrinkage. No ego chase.

Clear spine. Open hands.

That’s the whole thing.

Welcome to May. Welcome to Humility.

Comment one word: When you’re under pressure, do you tend to inflate or erase?
No explanation needed. Both are data.

Pleasantries.

— Chibundu

• The 90-Second Rule that separates blame cultures from recovery cultures

• A 3-step move called The System Scan (ten minutes, tops)

• One sentence to use the next time someone brings you bad news early

• Five fresh reads aligned to this week’s theme

  

THIS WEEK’S THEME

Recovery is grace made operational

Here’s the uncomfortable truth: most “people problems” are actually system problems wearing a person’s name tag.

The handoff that keeps getting dropped.
The deliverable that keeps arriving late.
The same issue you’ve coached three different people on.

If the same failure keeps showing up with different names, you’re not dealing with a character flaw. You’re dealing with a design flaw.

And the culture isn’t built by what you say about mistakes. It’s built by what happens in the first 90 seconds after someone says:

“We have a problem.”

That first response teaches your team whether truth is safe here.

YOUR 2% MOVE THIS WEEK

The System Scan

A quick audit of one recurring failure point, plus one guardrail installed before Friday.

Step 1 — Name the recurring failure.
Pick one place where things reliably break down.
Not the dramatic crisis. The quiet repeat offender.

Step 2 — Run the swap test.
Ask:
“If I replaced every person involved with equally capable people, would this still happen?”
If yes, your system is the problem. Congratulations. That’s fixable.

Step 3 — Install one guardrail.
Choose one:

• Checklist at the friction point (shared memory beats heroic memory)

• Named owner for the output (one throat to choke, one brain to support)

• Stop-the-line permission (explicit escalation before it becomes a fire)

One guardrail. One point of failure. This week.

ONE SENTENCE TO USE THIS WEEK

The next time someone brings you bad news early—while it’s still recoverable—say:

“Thank you for telling me early. What do you need from me to address it?”

That sentence does more for culture than most leadership offsites.

THIS WEEK’S READS

Five different (and aligned) reads for your Wednesday attention:

1. Why Organizations Forget What They Learn from Failures

2. How Complex Systems Fail

3. Blameless PostMortems and a Just Culture

4. 5 Whys Root Cause Analysis

5. The Checklist Manifesto

GO DEEPER IN THE LAB

Sunday’s Lead goes past “be accountable” and into design:
how to build a system where problems surface early, recovery happens fast, and learning becomes normal.

A NOTE ON CLOSING THE GRACE ARC

This is the final Midweek Minute of April’s Grace theme.

Grace for yourself.
Grace in feedback.
Grace under fire.
Grace in systems.

Next week, May begins a new virtue theme. But the foundation stays the same: make it safe to tell the truth, and the work gets better.

Reply with one system on your team that needs a recovery guardrail (five words or less).

Or forward this to a leader who keeps trying to “fix people” when it’s the process that’s broken. Pleasantries.

— Chibundu

At some point in your leadership journey, you will sit across from a team member who let something fall through the cracks.

And you will have a choice that most leaders don’t realize they’re making.

You can ask: How did this happen?
Or you can ask: What did we build that allowed this to happen?

Those two questions sound similar. They produce completely different cultures.

For most of my leadership life, I was asking the first one while telling myself I was practicing the second.

I wasn’t.

I was doing something that felt like accountability, but was actually closer to an audit. I traced the failure back to a person, applied pressure to that person, and called it a “system fix.” The process that produced the failure stayed exactly the same. The next person to run it hit the same wall. And everyone watching quietly updated their internal policy:

Don’t be the one holding it when it drops.

That’s not a culture of grace. That’s a culture of concealment. And I helped build it in more than one organization before I finally understood what I was doing.

This is the last Sunday Lead of April. We’ve spent this month building grace from the inside out: grace with yourself, grace in feedback, grace under fire. This final piece is the one that determines whether any of that work actually changes anything:

Grace in the systems where the work lives.

Because grace that never makes it into your design is not a culture. It’s a speech. And your people deserve more than a speech.

🧱 The Hidden Cost of “Perfect or Punished” Cultures

Let me describe the team you probably already know.

They’re competent. They deliver. Meetings are on time. Reports go out. The external metrics look fine.

But underneath the surface, something is off.

People are careful in a way that reads as “professional” but is actually protective. Nobody volunteers bad news. Problems surface fully formed instead of early and small. Post-mortems focus on what went right. The real conversation about what went wrong happens in the parking lot, not in the room.

This team isn’t dysfunctional in the obvious ways.

They’re dysfunctional in the expensive ways. The ones that don’t show up in the quarterly review until a small, hideable problem has compounded into a large, undeniable one.

The root cause is almost always the same: somewhere along the way, this team learned that mistakes were not information to be processed. They were evidence to be managed.

They learned it not from a memo, but from watching what happened to the person who raised their hand:

• The colleague who flagged a problem early and got assigned the blame for it

• The direct report who admitted they were behind and got treated like they were incompetent

• The team member who pushed back on a flawed plan and got managed out of the conversation instead of engaged

You don’t need to say, “We punish mistakes here,” for a team to know it.

The hidden cost of a perfect-or-punished culture is not the mistakes it produces. It’s the mistakes it conceals.

It’s the project that was recoverable at week two but didn’t surface until week eight because nobody wanted to be the one to say it.

It’s the client relationship that could have been saved with an honest conversation early, but wasn’t, because honesty felt too risky.

It’s the talented team member who stopped bringing their full thinking to the work because full thinking includes risks and gaps. And they learned that naming risks and gaps was a liability.

Blame is a lazy system.

It takes the complexity of a process failure and reduces it to a person-sized problem that feels “resolved” once someone is held responsible.

But the process that allowed the failure hasn’t changed. And the next person to run it will hit the same wall.

Recovery is the harder design. It’s also the only one that actually improves the system.

🔁 The Recovery Loop

The alternative to perfect-or-punished is not “no accountability.” Let me be direct about that, because this is the place where grace gets misread as softness and leaders who care about standards get nervous.

A recovery-oriented system holds people accountable for the quality of their response to a mistake, not only the mistake itself.

It asks:

• When something went wrong, did you surface it early or hide it?

• Did you bring the problem to the people who could help solve it, or manage it alone until it got worse?

• Did you extract the learning and share it, or minimize it and move on?

Those are accountability questions. They’re just aimed at behavior that actually improves the system rather than behavior that assigns blame.

The Recovery Loop has three movements. All three must be present for the system to work.

1) Detect Early

The goal is to shrink the gap between when something starts going wrong and when someone says so.

Early detection is almost entirely cultural. It depends on whether people believe that surfacing a problem early will be treated as useful information or as evidence of their failure.

This means the leader’s response to early bad news is one of the highest-leverage moments in the entire system.

When someone comes to you and says, “I think we have a problem,” before the problem is visible to everyone else, what you do in that moment teaches the whole team what to do next time.

The response that builds the system:
“Thank you for telling me early. What do you need to address it?”

The response that destroys it:
Any version of “How did this happen?” aimed at the person instead of the condition.

2) Correct Fast

Once the problem is visible, the system needs a clear path to resolution without the correction turning into a referendum on everyone’s competence.

Fast correction requires:

• clear ownership of the fix

• access to the resources needed to execute it

• permission to stop other work to address it

That last one matters more than most leaders admit. In many organizations, people are expected to solve the problem and keep doing everything else at full pace. The result is predictable: neither the problem nor the regular work gets proper attention.

3) Learn Publicly

This is the step most teams skip. It’s also the one that determines whether recovery produces a better system or merely a fixed incident.

Learning publicly means what was discovered about the process gap, the unclear ownership, the missing checklist, the communication breakdown gets shared with everyone who runs that part of the process, not just the people directly involved.

It means the post-mortem is a system design conversation, not a performance review.

And it means the leader models intellectual honesty:

“Here is what we built that allowed this to happen, and here is what we’re changing.”

That is more powerful than any speech about psychological safety.

🛠️ Three System Tweaks That Install Recovery at Ground Level

Changing a culture of blame into a culture of recovery is long work. But it starts with specific structural changes, not exhortations to “be more open,” but actual redesigns of the moments where errors get detected, owned, and addressed.

Here are three you can install this week.

1) The Checklist

Not as bureaucracy. As a shared memory system.

Most recurring failures happen at the same points in the same processes:

• the handoff where nobody confirmed receipt

• the approval step where the wrong version got sent forward

• the communication that assumed context the other person didn’t have

A checklist at those friction points isn’t an insult to intelligence. It’s an admission that human memory under load is unreliable.

Reliable systems don’t depend on individual perfection.

Ask: Where does our process most reliably break down, and what would a 3-item checklist at that step look like?

2) Clear Owners

Diffuse ownership is one of the most common structural causes of dropped balls. Not because people don’t care, but because when everyone is responsible, no one feels the weight clearly enough to act.

Clear ownership means: for every output, every handoff, every deliverable, one person is accountable. Not “the team.” One person.

Installing this doesn’t require a reorg. It requires a habit:

At the end of every meeting where work is assigned, confirm who owns what before the room empties.

3) Stop-the-Line Permission

Borrowed from manufacturing: workers have the authority to halt the line when they detect a defect, because catching it early is infinitely cheaper than letting it travel.

The leadership equivalent is explicit permission for any team member to escalate a concern before it becomes a crisis, without fear that escalation will be held against them.

Most teams don’t have this explicitly. They have the implied version (“my door is always open”) which gets undermined by what happens when someone walks through it.

Stop-the-line permission must be:

• stated clearly

• modeled by the leader

• reinforced with genuine gratitude when someone uses it

🧑🏾‍🏫 How Leaders Model Grace in the System

The structural tweaks above won’t hold if the leader’s behavior contradicts them. Systems are downstream of culture, and culture is downstream of what the leader does when it costs them something.

I want to tell you something I’m still in the middle of fixing.

As President of the OSU Black Alumni Society, I spent the better part of my early tenure doing something that felt like holding high standards, but was actually something else.

I was importing expectations. Taking leadership experiences I had accumulated (NBLSA, professional board work, years of learning how organizations function at their best) and projecting them onto a board that hadn’t built those reference points yet.

I expected people to know Roberts Rules instinctively.
I assumed a shared baseline about governance, meeting conduct, decision documentation, and follow-through.

When the outcomes weren’t there, I called it underperformance.

What I hadn’t fully reckoned with was this:

The system I was operating from had never been explained to the people inside it.

I would talk about resetting expectations without naming what the expectations actually were. I would acknowledge that the previous approach wasn’t working without describing clearly what we were moving toward or why.

Leaders on the board were inconsistent, and I was frustrated by the inconsistency, until the lightbulb finally came on:

The systems the OSU Black Alumni Society was using were broken. They didn’t create an environment where the board could thrive.

And I, as President, as the leader by title and presence, had failed them by not building a better one.

That is a hard sentence to write. It is also the most accurate one.

The work I’m doing right now (creating written internal board policies, distributed to every board member at the start of each new term, designed with clarity and grace) is the direct result of finally asking the right question.

Not: “Why aren’t they performing?”
But: “What did I design that made it harder for them to succeed than it needed to be?”

That question changes everything. It changed how I lead. And the system we’re building now is the answer to it.

🧩 The Moments That Teach the Real Rules

Grace in systems is modeled in four specific moments. Every team watches these.

1. When someone brings you bad news early, your instinct is frustration, and you choose curiosity instead.

2. When a post-mortem is heading toward a person-sized explanation for a system-sized problem, and you redirect it toward the process.

3. When you made the decision that created the failure, and you say so clearly instead of letting the ambiguity settle on the implementer.

4. When someone reports a mistake they could have hidden, and you thank them in front of the people who were watching.

Each of these is a system decision. Each one teaches the team what the real rules are, regardless of what the stated values say.

Repeated consistently, they build what no memo about psychological safety ever can:

A team that believes it is actually safe to tell the truth here.

Recovery is grace made operational. It is the design that makes the value real.

🧪 THE LAB REPORT

Work through these before the week is out. Be specific about the system, not just the feeling.

🔍 On the Culture You’ve Built

1. If I watch how my team responds when something goes wrong, the behavior I see most consistently is: _________________________

2. The last time someone brought me bad news early, I responded by: _________________________
   And the message that sent to the people watching was probably: _________________________

3. A process on my team that currently functions on the “perfect or punished” model (whether I intended it or not) is: _________________________

🔁 On the Recovery Loop

1. The point in our work where errors are most consistently detected late rather than early is: _________________________

2. The reason people don’t surface problems earlier is probably: _________________________

3. One place where ownership is unclear (where “everyone” is responsible, which means no one is) is: _________________________

⚡ On the Redesign

1. One small structural change I could make this week (checklist, named owner, stop-the-line permission) is: _________________________

2. The next time someone brings me bad news early, the response I’m committing to (specific words, not just good intentions) is: _________________________

🎯 The 2% Challenge

This week, pick one recurring failure point on your team (the place where things break down in different costumes) and install one recovery guardrail.

Not a culture initiative. Not a meeting about accountability.

One structural change at the friction point where the process consistently fails:

• a checklist

• a named owner

• explicit stop-the-line permission with one team member who has been carrying problems alone

Then watch what happens over the next few weeks:

Do problems surface earlier?
Do people bring things to you they used to manage quietly?
Does the recurring failure finally have a place to be caught?

That is the 2%. One design change that makes recovery possible.

Grace built into the structure.

Share Everyday Leadership Lab

🧡 One Last Thing

We started April with Easter, with the idea that what looks like a final ending can be the beginning of something you didn’t see coming. That failure is not a funeral. That the stone can be rolled away.

We spent the month building grace from the inside out:

• grace for yourself (owning a mistake without being destroyed by it)

• grace in feedback (dignity and direction at the same time)

• grace under fire (staying human when pressure is inhuman)

• and now, grace in systems (designing work that expects imperfection and recovers with speed, honesty, and learning intact)

Here’s what I want to leave you with:

Grace that stays inside you and never makes it into your meetings, handoffs, post-mortems, and approvals has a ceiling. It can make you a more self-aware leader. It will not change the culture.

Culture lives in the design. In what your systems reward, what they punish, what they make easy, and what they make dangerous.

I’m still building the right system at the OSU Black Alumni Society. The written board policies, defined onboarding, clear expectations distributed at the top of each new term, that work is in progress. I want to say that plainly: I haven’t “arrived.” I’m in it.

And I know this:

The inverse is also true: a system designed with grace expects mistakes, surfaces them early, corrects them fast, and learns from them publicly. That system makes your people better because it is honest with them.

It says: you’re human, the work is complex, and what matters is not whether you stumble, but how quickly and honestly we recover together.

Grace is not a speech. It’s a structure your people can actually live inside.

What system on your team needs a recovery guardrail?
Comment in five words or less: “handoffs,” “approvals,” “onboarding,” whatever it is.

Leave a comment

A full month of Grace together. Thank you for building it with me.
Next week, we start May’s virtue theme.

See you then. Pleasantries.
— Chibundu

Subscribe now

One idea. One move. One minute. Back to leading.

This week, you’ll get:

• A simple way to “pressure-proof” your leadership before the heat hits

• A 3-step rep called The Pressure Protocol Card

• One sentence you can use when you don’t have the answer yet

• 4 links worth your Wednesday attention

🧭 THIS WEEK’S THEME

Grace Under Fire Is Designed

Pressure doesn’t make you a different leader. It activates your default leader.

So the question isn’t “Can I stay calm?”
The question is: Have I built guardrails so my worst instincts don’t get the wheel?

Because when pressure spikes, your team doesn’t just need speed. They need stability. And stability is built on purpose, not on vibes.

🧪 YOUR 2% MOVE

The Pressure Protocol Card

Use this before your next high-stakes meeting, tense email, or fast decision.

Step 1 — Name the moment (one sentence).
“I’m walking into ______ and the stakes are ______.”

Step 2 — Name your default (pick one).
Controller / Critic / Ghost / Sprinter

Step 3 — Write 2 guardrails (and commit).
Pick one decision guardrail and one communication guardrail.

Examples:

• Decision guardrail: “No major decisions after 9pm.” / “I will get one second set of eyes before I hit send.”

• Communication guardrail: “I will send an update by ____ even if it’s incomplete.” / “I will say what I know + don’t know instead of performing certainty.”

That’s it. Three lines. One card. A better version of you shows up because you planned for the heat.

🗣️ ONE SENTENCE YOU CAN USE TODAY

“I don’t have the full answer yet, but I’m not disappearing—here’s what I know, what I’m finding out, and when you’ll hear from me next.”

📚 THIS WEEK’S READS

1. To Lead Through Uncertainty, Unlearn Your Assumptions (HBR) — Useful collection for leaders navigating incomplete information and shifting realities.

2. Postmortem Culture: Learning from Failure — How to develop blameless postmortems for high-performing teams to repair systems (and trust) without scapegoating people.

3. Box Breathing (Cleveland Clinic) — A quick nervous-system tool when you feel yourself speeding up.

4. Middle Managers Feel the Least Psychological Safety at Work — How to develop communities of practice and learning specific to middle managers as well as how to support leaders in the early stages of transition following promotion.

🔬 GO DEEPER IN THE LAB

This week’s Sunday Lead breaks down the full “Grace Under Fire” framework: pressure personalities, the 48-hour stabilization play, and clean repair moves when you get it wrong. If you’re in a high-stakes season right now, it’s worth the read.

Read on Substack

Reply with: Default + Guardrail (one line).

Example: “Critic + no feedback when depleted.”

And if you know someone leading under heat right now, forward this.

Sometimes one guardrail saves a week.

Pleasantries.

— Chibundu

The call came at 11:47 PM on a Thursday.

At the time, I was National Chair of the National Black Law Students Association — an organization with chapters at nearly every accredited law school in the country, a national conference drawing hundreds of law students, a legacy stretching back decades, and a board of some of the sharpest, most ambitious, most opinionated people I had ever been in a room with. Leading NBLSA was one of the greatest honors of my life. It was also one of the most unrelenting pressure-cookers I’ve ever sat inside.

That Thursday night call was a crisis I didn’t see coming.

I won’t get into the details. That’s not the point. But here’s what it involved:

• a time-sensitive decision

• a divided board

• external pressure from people with real institutional weight

• a public-facing dimension that could impact the organization

• and a timeline that demanded action fast

After I hung up, I sat in the dark and felt a very specific urge:

Not the urge to think.
Not the urge to collaborate.
The urge to just decide.

To override process. Move fast. Cut through uncertainty. Deal with consequences later.

Not because it was the right call.

Because the pressure was heavy. And the not-knowing was uncomfortable.

That urge is the real leadership test.

🔥 Pressure Doesn’t Just Test Leaders. It Tempts Them.

We say “pressure reveals who you really are” like the crisis version of you is the truest version.

I don’t believe that anymore.

What pressure actually does is activate your defaults.

Pressure doesn’t hand the mic to your best leadership. It hands it to your fastest leadership.

And fast isn’t the same as wise.

Under heat, your nervous system reaches for what it already knows: control, critique, withdrawal, sprinting. Patterns that may have helped you survive hard moments before… even if they don’t help you lead well now.

This is why teams don’t just remember what happened in the crisis. They remember who you became while it was happening.

🧭 Name Your Pressure Personality

Before we talk solutions, we need honesty.

Most leaders have never named their pressure default clearly enough to interrupt it.

Here are four “pressure personalities” I see constantly. Most of us are a blend, but one tends to run the show under fire.

1) The Controller

Default move: consolidate, hover, take decisions back
Team experience: “We can’t move without you.”
Hidden cost: you become the bottleneck and burnout source

2) The Critic

Default move: standards go up, patience goes down
Team experience: “I’m walking on eggshells.”
Hidden cost: people hide problems instead of surfacing them

3) The Ghost

Default move: go quiet, disappear into work, delay communication
Team experience: “We’re alone in this.”
Hidden cost: uncertainty grows in the silence

4) The Sprinter

Default move: move fast, decide early, communicate late
Team experience: “Hard to follow. Hard to trust.”
Hidden cost: momentum replaces alignment

If I’m being fully honest: I’m often a Controller + Critic under pressure.

And I get why. When I see obligations slipping and the work at risk, I consolidate. I absorb. I take it back.

The Critic side comes from a related place: when you’ve already decided you don’t get to make excuses for yourself, it becomes hard to extend patience to the excuses of others.

But here’s what that combination produces if I don’t manage it:

A leader who is harder to be near precisely when the team needs safety most.

I was often right about the gaps.
I was sometimes wrong about the approach.

And the repair took longer than the measured response I wanted to skip.

Name your default honestly. You can’t interrupt what you won’t admit.

🧱 What Grace Under Fire Actually Looks Like

After that 11:47 PM call, I didn’t do what pressure wanted me to do.

I didn’t perform certainty.
I didn’t send a unilateral decision email to prove I was handling it.
I didn’t call an emergency session at midnight just to relieve my anxiety.

I paused.

I wrote down what I knew and what I didn’t know.
I identified the 2–3 people who needed to be in the decision (versus the larger group who needed to be informed).
I slept four hours.
And at 7 AM, I called the right people and told them the truth, plainly.

The decision we made that morning was better than anything I would’ve produced alone at midnight.

It held up. It protected the organization. And the people trusted me more afterward, not less.

That’s why grace matters under fire.

Not because it feels softer.

Because decisions made with your humanity intact are almost always better than decisions made from your worst instincts.

And because people remember how you made them feel in the hard moment long after they forget the decision.

🛠️ The 48‑Hour Stabilization Play

Pause. Prioritize. Protect.

When pressure spikes, I come back to a three-part sequence:

1) Pause

Pause is not hesitation. It’s inserting space between stimulus and response.

Sometimes it’s 60 seconds in a heated meeting.
Sometimes it’s one night of sleep before sending the message that will live forever in someone’s screenshot folder.

Pressure will tell you the pause is dangerous.
Most of the time, the pause is the safest thing you can do.

2) Prioritize

Under pressure, urgency and importance get scrambled.

Use these questions:

• What happens if this isn’t addressed in the next 2 hours?

• The next 24 hours?

• The next week?

If you write down what feels urgent versus what is truly time-sensitive, those lists are rarely the same.

3) Protect

Protect has two objects: people and work.

Under pressure, leaders tend to sacrifice one for the other:

• protect people by lowering the bar

• protect work by crushing people

Grace under fire is holding both.

Protecting people can look like:

• transparency about what you know and don’t know

• checking in on the humans inside the crisis

• refusing to treat people like instruments of the solution

Protecting the work can look like:

• resisting panic decisions

• keeping standards clear

• developing others instead of becoming the only reliable person

That last one is hard. I’m still learning it.

You cannot build an organization by becoming its only dependable system.

🗣️ What to Say When You Don’t Know Yet

Pressure pushes toward false certainty: say something definitive, project confidence, end the discomfort.

That logic is understandable.

The cost is high.

Here’s the alternative. Four sentences. Works anywhere.

Here is what I know right now.
Here is what I don’t know yet.
Here is what I’m doing to close that gap.
Here is when you’ll hear from me next.

This is leadership without performance. It keeps trust intact while reality is still forming.

🩹 Repair Moves When You Got It Wrong

Sometimes you don’t pause. Sometimes pressure wins.

You snap.
You go cold.
You sprint and break trust.
You control the room and shrink everyone else.

It happens.

The measure of leadership under fire isn’t perfection. It’s repair.

1) Own it fast (clean, not dramatic)

Not self-flagellation. That makes them manage your guilt.

Say:
“I handled that wrong. Specifically, I did ___. That wasn’t fair, and it’s not how I want to lead.”

2) Re-center the team

Teams need a signal the leader is back.

A simple acknowledgement works:
“That meeting was harder than it needed to be. I want to own my part.”

3) Move forward with the loop closed

Not pretending it didn’t happen. Not camping in shame. Repair, then lead.

Repair isn’t the end of the story.
It’s the bridge back to trust.

🧪 THE LAB REPORT

Do these before your next high-stakes moment, not after.

🔍 On your pressure personality

1. When I’m under real pressure, my default is: _________________________

2. The behavior I’m least proud of when activated is: _________________________

3. The people who absorb the most of my pressure default are: ___________________

🔁 On stabilization

1. In my next high-stakes situation, the Pause I can build in is: ___________________

2. The thing that will feel most urgent but probably isn’t is: ______________________

3. The people-protection move I need to remember is: _________________________

🏥 On repair

1. A recent moment where my pressure default cost someone something is: _________________________

2. The repair move I still owe, and what it would sound like, is: _________________________

⚡ The 2% Challenge

Before your next high-stakes meeting or pressure moment this week, do one thing:

Name your pressure default in writing before you walk in.

Not as a confession. As a briefing.

Write this:

• “My default under pressure is: ______.”

• “The behavior to watch for is: ______.”

• “My stabilization move today is: ______ (Pause / Prioritize / Protect, specifically).”

Then check it after.

One moment of deliberate self-awareness, before pressure gets to choose for you.

Grace keeps your humanity intact under heat.
But only if you practice before the fire starts.

Share

🧡 One Last Thing

I think about that 11:47 PM call more than I admit.

Not because of the crisis details. Those fade.

I think about it because of what I almost did.

The Controller in me was right: something needed to be done.
The Critic in me was right: standards had slipped.

What neither one could give me, what only the pause could give me, was the judgment to respond instead of react. And the part I didn’t fully realize at the time: the biggest stakes weren’t only operational. They were relational.

The NBLSA board deserved a better version of me, more consistently than I sometimes delivered. The honest reckoning wasn’t just about what my pressure defaults cost the work. It was about what they cost people. Sitting with that is what drove the development.

And that development is what made the friendships possible.

Not the title. Not the wins. Not even the things we built together, as meaningful as they were. The relationships that have lasted more than a decade, the ones that have carried us through career pivots, personal chapters, and the cultural and professional complexity leaders of color navigate in today’s workplaces, exist because some of us kept growing after the pressure subsided.

We chose each other not just as colleagues in a high-stakes season, but as people committed to becoming better over time.

Here’s what I know now:

You can be intense without being cruel.
You can hold a high standard without making people feel like they’re always failing.
You can lead a crisis without leaving broken trust behind you.

And when you get it wrong (because you will), you can repair quickly and cleanly enough that people choose to stay. Not because they have to. Because the growth is real.

That’s grace under fire.

And the people watching who you become when things get hard deserve the version of you that decided, in advance, who it will be.

Leave a comment

What’s your biggest pressure trigger, and what’s one stabilizer you’ll use this week?
Comment: Trigger + Stabilizer (one line). I read every one. And if this landed for a leader in your network who is currently inside a hard season, send it their way. The Lab is better when we build it together.

See you next Sunday.

Pleasantries,
— Chibundu

Subscribe now

This week, you’ll get:

• The reframe that fixes most “bad performance review” problems before they become HR problems

• A 3-step move called Vibe → Behavior → Rep

• One sentence you can use in your next 1:1

• Five reads/watches worth your Wednesday attention (with source links)

THIS WEEK’S THEME

Dignity + Direction

If feedback is “news” at performance review time, it wasn’t high standards.
It was unclear leadership in real time.

Most managers aren’t trying to be shady. They’re trying to be “nice.”
So they give feedback that sounds supportive… and changes nothing.

That’s not kindness. That’s delay.

This week’s rep is about one thing: turning fog into footage.
So people can actually improve.

YOUR 2% MOVE THIS WEEK

Vibe → Behavior → Rep

Use this when you catch yourself saying something like:
“Be more proactive.” “Improve your communication.” “Show more ownership.” “Have more executive presence.”

Those aren’t instructions. They’re vibes.

Step 1 — Name the vibe (the fog phrase).
Write the exact sentence you’ve been using. No edits.

Examples:

• “I need you to be more proactive.”

• “Your communication needs to be stronger.”

Step 2 — Convert it into observable behavior (footage).
Ask: If we recorded you at work, what would I literally see or hear?

Examples of behavior (not traits):

• “Send the client update by 3pm Thursdays.”

• “Flag risks within 24 hours of seeing them.”

• “Summarize decisions + owners in the last 2 minutes of the meeting.”

• “Acknowledge the concern before redirecting back to the plan.”

Step 3 — Schedule the rep (one situation, one deadline).
Behavior without a rep is still fog.

Use this format:
“In [next situation], do [new behavior]. I’ll look for it by [time/date].”

Example you can copy/paste:
“In next Tuesday’s team meeting, when someone raises a concern, acknowledge it before you redirect. I’ll watch for that on Tuesday, and we’ll do a 2-minute debrief right after.”

That’s it.
Not a personality critique. Not a lecture. A rep.

ONE SENTENCE YOU CAN USE TODAY

(That line does two things at once: dignity + direction.)

BONUS REP

The 2-Minute Debrief

If you want feedback to stick, don’t just deliver it. Close the loop.

Right after the next “rep moment,” ask:

1. “What did you notice yourself doing differently?”

2. “What reaction did you get?”

3. “What’s one tweak for next time?”

This turns feedback from a talk into training.

THIS WEEK’S READS

1. “The Feedback Fallacy ” (HBR): Marcus Buckingham and Ashley Goodall

2. SBI Feedback Model (Situation–Behavior–Impact): Center for Creative Leadership

3. Radical Candor (framework + examples): Kim Scott

4. “Clear is kind”: Brené Brown

GO DEEPER IN THE LAB

Sunday’s edition breaks down the full system for honest + humane feedback (including the 4-part frame and the 48-hour aftercare that makes it stick).

Read the Sunday Lead →

Before you go:

What’s the foggiest feedback phrase you’ve ever received (or given)?

Reply with the phrase. I’ll translate a few into clear behaviors + a rep.

— Chibundu

Share

There’s a version of leadership “kindness” that looks like this:

You tell someone they’re doing “great.”
You soften the edges.
You wait until the performance review to name the real issue.
You hope they “pick it up.”

It feels warm in the moment.

It’s also expensive.

I once had a manager who never told me when I was falling short—at least not in real time. In our one-on-ones, the feedback was vague and encouraging. I’d walk out thinking I was on track.

Then the real feedback would arrive months later, usually at midyear or end of year. Wrapped in careful language. More documentation than development. So unclear I couldn’t tell if I was being celebrated or managed out.

He thought he was being kind. He was actually being unclear.

And unclear feedback—no matter how nicely packaged—doesn’t help or protect people. It confuses them. It delays course-correction. It turns fixable gaps into patterns.

I’ve also had the opposite kind of manager. The one who gave feedback like an incident report: direct, specific, airtight. But delivered with a flatness that made the gap feel like a defect in me, not a problem we could solve.

I left those conversations knowing what was wrong.
I did not leave believing he thought I could fix it.

Neither approach is what we’re building here.

This week in the Grace arc, we’re talking about feedback that’s both honest and humane. Feedback that holds the standard clearly while treating the person like someone capable of meeting it.

Because dignity and direction are not opposites.

🧭 Why Most Feedback Fails

Most feedback doesn’t work; not because the observation is wrong, but because the delivery breaks down in predictable ways.

Here are the three failure modes:

1) It’s late.
By the time you bring it up, the moment is abstract, the context is fuzzy, and the person feels blindsided. Late feedback lands like a grievance, not guidance.

2) It’s vague.
“You need to be more proactive.”
“Your communication could be stronger.”
“I need you to show up differently.”
That’s not feedback. That’s fog. People can’t improve what they can’t see.

3) It’s emotional (dysregulated).
Not caring. Caring is good.
I mean activated: frustration running the delivery, tone doing damage before the content has a chance to land.

Late. Vague. Emotional.

Fix even one of these and your feedback improves fast. Fix all three and you become the kind of leader people actually want feedback from.

⚖️ The Grace + Accountability Rule

Here’s the distinction that changes everything:

Grace in feedback is not softening the truth.
Grace is delivering the truth in a way the person can actually receive and act on.

The leader who avoids the hard conversation to preserve comfort isn’t practicing grace. They’re practicing avoidance and calling it kindness.

The leader who drops the truth cold isn’t practicing accountability. They’re offloading frustration and calling it leadership.

Leadership is the harder move:

• Exact about the standard

• Genuinely invested in the person’s ability to reach it

Grace doesn’t lower the bar. It teaches people how to clear it.

🧩 The 4-Part Feedback Frame

This is the structure I come back to because it keeps you out of the two ditches:
avoidance and verdicts.

Context → Observation → Impact → Next Step

Now let’s break down why each part matters:

1) Context

Set the stage. Make the intention clear. Reduce threat.

Sounds like:
“I want to talk about the client update from Tuesday. I’m bringing this up because I think you’re capable of more here, and I want to be useful—not just flag an issue.”

2) Observation

What you saw. Specific. Behavioral. No interpretation.

Sounds like:
“In the last three team meetings, when someone raised a concern about the timeline, you redirected back to the original plan without acknowledging the concern.”

3) Impact

Why it matters—to the team, trust, execution, results.

Sounds like:
“People have started bringing concerns to me afterward instead of raising them in the room. That tells me they don’t feel their input is landing. That’s risky, because we need early problems surfaced, not hidden.”

4) Next Step

This is where grace becomes visible. It turns feedback from verdict into work session.

The change. Specific. Actionable. Forward-facing.

Sounds like:
“Next meeting, I want you to acknowledge the concern before you move to the plan. Even one sentence: ‘That’s a real concern—let’s talk about it.’ Can you try that?”

That’s the whole frame.
Four parts. One conversation. Dignity intact. Direction clear.

Unclear feedback isn’t kindness. It’s a delayed cost.

✅ Use The Script This Week

Context: “I want to talk about ___ from ___. I’m bringing this up because I believe you can grow here, and I want to help.”
Observation: “What I saw/heard was ___.”
Impact: “The impact is ___.”
Next Step: “Next time, I want to see ___. Can you try that by ___?”

🧠 Regulate Before You Speak

This is simple. It’s also the difference between feedback that builds and feedback that bruises.

Your tone is part of the message.
People process tone before content. If your tone communicates disappointment in their identity, your words about behavior won’t land.

So before you give feedback: regulate.

Ask yourself:

• Am I having this conversation because they need it… or because I need relief?

• Can I say the truth and communicate belief in their ability to change?

If you can’t access that belief right now, don’t force it.
Wait 24 hours. Come back when you can be intentional.

Same words. Different nervous system. Completely different outcome.

🩹 Aftercare: The 48 Hours That Decide If It Worked

Most leaders think the conversation is the intervention.

It’s not.

The conversation is the start of the intervention. The next 48 hours decide whether feedback becomes growth or just becomes a hard memory.

Here’s what aftercare looks like:

1. Follow up within 24 hours (brief + warm).
   Text/email example:
   “Appreciate how you engaged with that conversation. I know it wasn’t easy. If anything comes up that we didn’t get to, I’m here.”

2. Watch for the next rep (coach, don’t surveil).
   Catch them getting it right. Name it early. Specific praise after hard feedback builds the new behavior faster than another critique ever will.

3. Close the loop when the pattern changes (Call out the win).
   “In the last two meetings, you acknowledged concerns before redirecting. The room responded differently. That’s the change we were aiming for.”

That is how people learn to trust feedback:
not just because you correct them, but because you notice growth.

🧪 THE LAB REPORT

Work through these before you have the conversation, not after.

🔍 On the Feedback You’ve Been Avoiding

• The person who most needs honest feedback from me right now is: _________________________
  and I’ve been avoiding it because: _________________________

• If I’m honest, my hesitation is mostly about: their readiness / my discomfort (circle one) Why: _________________________

• The last time I gave feedback that landed badly, the part that went wrong was: _________________________

🔁 On the Frame

• Context: _________________________

• Observation: _________________________

• Impact: _________________________

• Next Step: _________________________

⚡ On Regulation

On a scale of 1–10, how regulated am I right now about this situation? ___
(10 = Calm + Invested)

Which means before I have this conversation, I need to: _________________________

🎯 The 2% Challenge

This week, give one piece of feedback early.

Before it becomes late.
Before it becomes a pattern.
Before it becomes a bigger conversation than it needed to be.

Use the frame: Context → Observation → Impact → Next Step.
Write it out first if you need to.

Don’t read it like a robot. Just build it ahead of time so the conversation doesn’t collapse into vagueness or heat.

One conversation. This week.

Not at the next review. Not “sometime soon.”
Now, while it can still land as support instead of a verdict.

🧡 One Last Thing

The people who grow the most aren’t always the most talented.

They’re often the ones who had a leader willing to tell them the truth:

• not eventually

• not vaguely

• not coldly

• not in a way that made them feel like a problem

But directly, specifically, and with belief underneath the hard words.

That kind of feedback is respect.

It says:
“I see you clearly enough to name what isn’t working.”
“And I believe in you enough to say it to your face.”

So this week, practice the standard version of leadership grace:

Dignity and direction. Both present. Every time.

That’s grace in feedback.

Leave a comment

What feedback conversation do you need to have this week—and what would it look like to be both honest and humane?
Drop it in the comments.

If you want a clean copy/paste version of the 4-part frame, comment FRAME and I’ll reply with it.

See you next Sunday. Pleasantries.
— Chibundu

This week, you’ll get:

• The difference between reflection and a shame spiral (and how to tell which one you’re in)

• A 3-step rep called The 24-Hour Repair Sprint

• One sentence you can use today when you miss the mark

• 6 reads (with links) to strengthen your self-grace muscle without losing your standards

THIS WEEK’S THEME

Re-entry is a leadership skill

Self-grace is not “being nice to yourself.” It’s the ability to own the miss, repair the impact, and stay in the arena.

Most leaders don’t get taken out by one mistake.
They get taken out by what they do after the mistake.

Shame makes you hide.
Overthinking makes you stall.
Overworking makes you brittle.

Grace is different: you stay accountable without punishing yourself into avoidance.

Midweek check-in: when you mess up, do you repair… or do you perform suffering?

YOUR 2% MOVE THIS WEEK

The 24‑Hour Repair Sprint

Run this the next time you feel that “I can’t believe I did that” voice start warming up.

Step 1 — Own it in one sentence (Fact + Impact).
No speech. No self-attack. Just clean truth.
Example: “I missed the deadline, and it created churn for the team.”

Step 2 — Repair in one action (within 24 hours).
Pick the smallest real repair that closes the loop:

• apologize directly

• send the clarification note

• redo the work

• reset expectations with the stakeholder

• name what you’ll do differently next time

Step 3 — Upgrade one condition (so it’s less likely to repeat).
This is where grace becomes strategy. Choose one small safeguard:

• a 10-minute pre-brief before high-stakes meetings

• a “no yes until I check my calendar” rule

• a checklist for recurring work

• a buffer block before deadlines

• a decision log so you stop re-litigating

That’s the sprint: Own. Repair. Upgrade.
Not a personality overhaul. A repeatable rep.

ONE SENTENCE YOU CAN USE TODAY

“I’m going to own it, make the repair, and keep leading.”

THIS WEEK’S READS

1. Self-Compassion Will Make You a Better Leader: Practical argument for why self-compassion increases clarity and resilience, not complacency.

2. Self-Compassion Break: A short guided practice you can run in 2–3 minutes when shame starts to spike.

3. Shame vs. Guilt: A clean distinction: guilt targets behavior (“I did”), shame targets identity (“I am”). That shift changes how you repair.

4. Strategies for Learning from Failure: If you want to lead without fear, you need a real learning process after mistakes.

5. A Better Approach to After-Action Reviews: How to turn misses into learning without turning it into a blame session (great for managers).

6. Listening to Shame (TED): A powerful watch if shame is driving perfectionism, hiding, or defensiveness in your leadership.

GO DEEPER IN THE LAB

Sunday’s Sunday Lead is the foundation for this rep: Your Inner Critic Isn’t Your Coach. It lays out the full self‑grace framework and why shame doesn’t just hurt you, it changes how your leadership lands on everyone else.

Two asks:

1. Reply with the one you need most right now: Own / Repair / Upgrade

2. Forward this to the leader who holds everyone else with patience but speaks to themselves like an enemy.

— Chibundu

Whatever today means to you personally, the story at the center of it carries a leadership truth worth naming before we talk tactics.

It’s the idea that what looks final doesn’t have to be the end.
That failure isn’t a funeral.
That a heavy stone can move.

Not as a theological debate. As a leadership reality.

Because I watch some of the best leaders extend grace to everyone but themselves.

They’ll coach a struggling direct report with patience.
They’ll give a peer the benefit of the doubt.
They’ll tell their team, “Mistakes happen. We learn. We move on.”

Then they walk back into their own head after a hard week and say things to themselves that they would never say to anyone they manage.

And that contradiction quietly breaks people.

Not all at once. Over time.

April’s virtue is Grace. Not grace as softness. Not grace as an excuse. Grace as the thing that makes sustained, high-quality leadership possible.

We’re starting with the hardest version.

The grace you owe yourself.

The Quiet Leadership Killer Nobody Names

There’s something living inside a lot of high-performing leaders that doesn’t get talked about directly.

It’s not laziness.
It’s not even imposter syndrome, exactly.

It’s self‑contempt dressed up as high standards.

It sounds like:

• “I can’t believe I let that happen.”

• “I should be better than this by now.”

• “If I were really a leader, I wouldn’t have messed that up.”

It’s efficient. It’s practiced. It knows exactly where to hit.

And here’s the practical problem with that arrangement:

That’s not motivational. It’s structural.

Because self‑contempt doesn’t stay internal. It leaks.

It shows up as:

• the leader who won’t admit a mistake because admission feels like collapse

• the manager who avoids an ambitious idea because being wrong in public feels too expensive

• the executive who white‑knuckles everything alone because asking for help got filed under “evidence of inadequacy”

• the leader whose team feels tension, not because the leader is “mean,” but because the leader is always braced for failure

If your inner voice is a bully, your leadership eventually feels like punishment.

Not just for you. For the people around you who are absorbing your relationship with imperfection.

What Grace Actually Is, and What It Is Not

Let’s address the resistance head-on.

When high-performing people hear “be easier on yourself,” something tightens. Because we’ve seen leaders use self‑compassion as cover for avoidance.

That version is real. And it’s not what we’re building.

Here’s the distinction:

Excuse

Avoids the mess.
Avoids full ownership.
Keeps the lesson unlearned and the damage unrepaired.

Grace

Goes through the mess.

Grace says:

• “I did that.”

• “It had impact.”

• “Here’s what I’m going to do to repair it.”

• “Here’s what I’m changing so it doesn’t repeat.”

• “And I’m not going to spend the next three weeks in a shame spiral that benefits no one.”

Because when the cost of being wrong is shame that attacks your identity, you’ll do almost anything to avoid being wrong.

Including lying to yourself about what happened.

Grace builds recovery capacity.
Recovery capacity is not soft. It’s infrastructure. It’s how leaders stay in the arena long enough for the work to compound.

The Self‑Grace Reset

A repeatable rep for when you miss the mark

Grace without structure usually collapses into one of two things:

• rumination that looks like reflection

• bypass that looks like “moving on”

Neither one actually closes the loop.

Here’s the rep I use when I stumble. It’s simple enough to run on a Tuesday, not just on a retreat.

Step 1: Name it

Say plainly what happened and what you feel.

Not a performance. Not a spiral. Just truth.

• “I missed the deadline, and I feel like I let the team down.”

• “I snapped in that meeting, and I’m embarrassed.”

• “I avoided the conversation, and now it’s bigger than it needed to be.”

Naming matters because it moves the mistake from a vague weight to a specific event.

The inner critic thrives in vagueness. Precise language shrinks it.

Step 2: Learn it

Extract the data point, not the verdict.

Don’t ask: “What does this say about me?”
Ask: “What condition produced this, and what do I change?”

Examples:

• “I overcommitted because I didn’t check my actual capacity before saying yes.”

• “I reacted because I went into that meeting depleted and unprepared.”

• “I avoided the feedback because I didn’t have a clean structure to hold care and clarity at the same time.”

The coach voice is always more interested in the condition than your character.

Fix the condition. Leave your identity intact.

Step 3: Re-enter

Go back into the arena without dragging shame behind you like a chain.

Re-entry might look like:

• a direct apology

• a repair conversation

• a clarification note to your team

• a quiet correction and a changed behavior pattern the next day

Re-enter. Don’t hide.

That’s the move.

Grace is ownership without a shame sentence.

Critic voice vs Coach voice

What to say to yourself when you’re tempted to spiral

Your inner critic has had years to workshop its material. It’s fast and it knows which accusations land hardest.

Replacing it is not one decision. It’s a daily practice of responding like a coach instead of a bully.

Here are a few translations you can borrow:

• Critic: “I can’t believe I’m this incompetent.”
  Coach: “That was a hard moment. I didn’t handle it the way I wanted to. I can own it and repair it.”

• Critic: “Everyone else has this figured out. Why am I still struggling?”
  Coach: “I’m in the middle of learning. The middle is supposed to feel messy.”

• Critic: “I should be better than this by now.”
  Coach: “I have high standards. I’m also human. My job is to learn and re-enter.”

This is not lowering the bar. The standard is still the standard.

This is keeping the bar high without whipping yourself to reach it.

🧪 THE LAB REPORT

Work through these before the week is out. Be specific. Vague answers let the critic run free.

🔍 On the Inner Critic

1. The harshest thing my inner critic says regularly is: _________________________

2. If a trusted mentor heard me say that, they would respond with: _________________________

3. The area where self‑contempt is most active in my leadership right now is: _________________________

🔁 On the Self‑Grace Reset

1. One recent mistake or stumble I haven’t fully named yet is: _________________________

2. The data point (the condition, not the verdict) is: _________________________

3. The re-entry move that would actually close the loop is: _________________________

⚡ On the Standard

1. One standard I’m demanding from myself that I would never demand from someone I love is: _________________________

2. A more gracious and equally rigorous relationship with that area would look like: _________________________

THE 2% CHALLENGE

One self‑grace rep. One week. One re-entry.

Pick one area where shame has been running the agenda.

Where your relationship with imperfection has made you:

• smaller

• more avoidant

• less present

• more defensive

• more alone than you need to be

Then do the one thing you’ve been postponing because it requires admitting you’re human.

Examples:

• send the apology

• ask for help

• repair the relationship

• set the boundary

• revisit the work you avoided because it didn’t go well the first time

• take the rest you keep denying yourself, not as escape, as stewardship

One rep.

Grace practiced once builds the muscle for the next time.

One Last Thing

We spent March in Patience. We practiced the long view: seasons, pace, developing people, active waiting, and the reframe that we are not late, we are in process.

All of that work has a quiet requirement underneath it.

Grace.

Grace is what makes patience sustainable.
Grace is what makes accountability livable.
Grace is what keeps ambitious leaders in the arena long enough for the coaching they are receiving and the work to compound.

The inner critic will tell you you need to be harder on yourself to get better.

But “harder” has a ceiling.

At some point, punishment stops producing performance and starts producing avoidance. Brittleness. Leaders who are more focused on not being wrong than on doing what’s right.

You don’t need a harsher verdict.

You need a better process.

Own it. Learn it. Re-enter.

That’s grace in motion.

And if you needed a symbol for it today, it’s this:

The stone can move.
WALK OUT.

— Chibundu

Where do you need self‑grace right now?
One sentence. No explanation. No performance.

Leave a comment

One idea. One move. One minute. Back to leading.

This week, you’ll get:

• A midweek reset that stops the comparison spiral without pretending it isn’t real

• A 3-step rep called The Thursday Artifact (formation you can see)

• One sentence you can use to protect your priorities without sounding defensive

• Six reads (and one short video) to reinforce the long game

THIS WEEK’S THEME

Make Formation Visible

If you can’t point to what you’re building, comparison will always feel louder than progress.

The Sunday Lead named the trap: the Internal Accounting.

Because the “behind” feeling feeds on vagueness. It thrives when your growth is real but undocumented, private, and easy to dismiss.

So here’s the next level move: stop arguing with the feeling.
Start collecting evidence.

YOUR 2% MOVE THIS WEEK

The Thursday Artifact

A repeatable rep to turn formation into something tangible.

Step 1: Pick the capability you’re forming (not the title you want).
Ask: “What do I need to be able to carry at the next level?”
Examples: clearer strategic thinking, stronger boundaries, better coaching, cleaner decision-making, calmer execution.

Step 2: Build one small artifact in 15 minutes.
Keep it simple and shippable. Options:

• a one-page “Top 3 priorities” plan for next week

• a meeting agenda that forces decisions and owners

• a coaching script for a hard conversation

• a decision log (what we decided, why, what success looks like)

• a checklist you wish your team already followed

Step 3: Put it in the world. Timestamp it.
Use it in a meeting. Send it to one person for feedback. Save it in a folder called Formation.
That’s the point. Formation becomes real when it becomes usable.

By Friday, you’ll have receipts. Not vibes.

ONE SENTENCE YOU CAN USE TODAY

“I’m not trying to look ready. I’m building what readiness requires.”

THIS WEEK’S READS

1. “The Mundanity of Excellence” — A classic study that proves elite results come from ordinary reps done consistently.

2. “If Strategy Is So Important, Why Don’t We Make Time for It?” — A clean push to protect strategic time when the week wants to eat it alive.

3. “How to Master the Art of Continuous Improvement” — The math behind small reps compounding.

4. “Deliberate Practice and Proposed Limits…” — Helpful nuance: practice matters, but quality and structure matter more than grind.

5. “Q&A: The Dip and Knowing When to Quit” — A smart filter for knowing what to stick with and what to drop.

6. Carol Dweck: “The Power of Believing You Can Improve” — A short watch that reinforces formation as a process, not a personality trait.

GO DEEPER IN THE LAB

If The Sunday Lead hit a nerve, go back and name your archetype (Deep Rooted, Long Path, Reflective Veteran). Then run Your 90‑Day Patience Plan with the Thursday Artifact as your weekly execution tool.

If your “behind” feeling is tied to waiting on a decision or timeline, pair it with: Active Waiting: What to Do While the Door Hasn’t Opened Yet.

Reply: What’s your Thursday Artifact this week? One sentence.
Forward: Forward this to a leader who keeps discounting their own progress because it isn’t public yet.

There’s a specific Sunday evening anxiety ambitious leaders know by heart.

It’s not about the inbox.

It’s the Internal Accounting. The moment you compare where you are against the imaginary timeline you drew for yourself at twenty-two.

The math never adds up. The result is always the same:

I should be further by now.

Sometimes it’s that exact sentence. Sometimes it’s a vague restlessness you can’t name. Sometimes it gets triggered by a LinkedIn post from someone you went to school with. Sometimes it shows up mid-conversation you’re supposed to be leading, as a quiet thought you don’t want to admit:

How is it that I still don’t have this figured out?

We treat this feeling like a secret confession of failure. We see a peer’s promotion or a “30 Under 30” list and we immediately cancel out our own progress.

I want to challenge that silence.

Because you aren’t “behind.” You are likely stuck in one of three common leadership traps.

The Feeling Nobody Talks About in Professional Settings

The “I should be further” feeling hits leaders differently than it hits people who aren’t invested in growth.

For ambitious people, growth is not just a goal. It becomes identity.

So slower-than-expected progress does not land as a career observation. It lands as a statement about who you are.

That’s where the real damage lives. Not in the timeline. In the identity.

And this feeling almost always arrives with comparison. Quiet. Constant. Convincing.

Here are three versions of it I see constantly.

QUICK SCAN: The 3 Archetypes

The Deep Rooted Leader
Looks “behind” because their growth is underground: trust, judgment, people skills.

The Long Path Leader
Feels “late” because their development includes pivots, detours, and depth-building seasons.

The Reflective Veteran
Feels “behind” because the finish line keeps moving, so the present always feels like deficit.

The Deep Rooted Leader

“I’m doing the work. Why do I still feel behind?”

She’s young, capable, and already leading.

On paper, she’s ahead of schedule. She got responsibility early. Her results are solid. Her skip-level respects her.

And she still feels behind.

Because someone in her feed just got promoted to Senior Director at thirty. Because a peer has a bigger scope. Because the leaders being praised online seem to have clarity and authority she doesn’t feel yet.

So every piece of evidence that should produce confidence gets cancelled by evidence that someone else is doing it bigger, faster, louder.

What she doesn’t see is the full story behind the highlight reel. She doesn’t see the private burnout. The shaky foundation. The anxiety-driven leadership. The role someone is not actually ready for.

She also doesn’t see her own wins as wins, because they are not flashy.

She is building trust. She is learning how to hold authority without becoming harsh. She is getting better at conflict without detonating the relationship. She is developing pattern recognition about people.

That’s real leadership.

It just doesn’t come with a badge.

The trap: grading your full interior against someone else’s best exterior.
The rep: start counting root growth as real progress.

The Long Path Leader

“The detour cost me.”

He didn’t go straight through.

There was a pivot away from a path that stopped fitting. There was a smaller organization that paid less and taught more. There was a season of figuring it out that took longer than he would have chosen.

Now he’s in a role he’s genuinely good at. He’s leading in a way that feels aligned.

But he looks at colleagues who stayed on the straight path and sees titles, compensation, levels. Things his longer road has not delivered yet.

And the narrative he tells himself late at night is simple:

The detour cost me. I should be further.

What that narrative misses is the inventory of what those years built.

He has a tolerance for ambiguity his straight-path peers are only now developing, because he lived in it. He has values clarity that took discomfort to earn. He has a relationship with failure that does not threaten his identity, because he already moved through the thing that could have broken him and learned it didn’t.

None of that shows up in a title.

All of it shows up when pressure hits.

The trap: counting the detour as lost time instead of formative time.
The rep: count depth-building seasons as leadership capital.

The Reflective Veteran

“I’ve accomplished a lot. Why doesn’t it feel like enough?”

She has been leading for fifteen years.

She has built culture in environments that were not designed for it. She has developed people who now lead their own teams. She has navigated crises. She has a track record most people would trade for.

And she’s still waiting to feel like she’s arrived.

Because every time she reaches what she was working toward, the horizon moves.

The new role becomes baseline. The recognition becomes expectation. The capability becomes the floor. The present starts to feel like deficit.

The trap: an internal measuring system calibrated only against future milestones.
The rep: turn around, get accurate, and count what you’ve built.

The Reframe That Actually Holds

Formation vs. Stagnation

Here is the factual correction:

You are not late. You are learning how your life actually works.

In leadership, we value Information, but we ignore Formation.

Information is fast. You can read a book in a weekend.

Formation is slow. It is the unglamorous process of becoming a person capable of holding the weight of the thing you’re trying to do.

It happens when you learn to hold authority without losing your soul. When you give feedback that actually lands. When you stay calm under pressure instead of reacting. When you stop rescuing and start coaching. When you make decisions with incomplete information and still lead with integrity.

That work is real.

And it has its own schedule.

You aren’t behind. You’re in formation.

Here’s the other part the “behind” narrative gets wrong:

Your timeline is not someone else’s timeline.

Different starting conditions. Different access. Different assignments. The person you’re measuring yourself against is not carrying what you’re carrying.

A Different Kind of Evidence

When the “behind” feeling arrives, it comes with one kind of evidence: what you don’t have yet.

Title. Role. Recognition. Platform. Compensation. Impact.

I’m not telling you to ignore that. Some gaps are real.

I’m telling you to stop acting like that is the only ledger that counts.

Because the “behind” narrative survives by omitting the other column. What you have built. What you have navigated. What you can now carry without breaking.

Here’s the question I want you to sit with:

What have you built in the last twelve months that you didn’t have before?

Some examples that count, even if nobody applauds them:

• You can lead a hard conversation without spiraling afterward

• You built credibility and trust you didn’t have

• You coached someone through a messy season

• You learned how to protect your pace under pressure

• You got clearer about what you refuse to trade for a title

The “behind” narrative keeps your attention locked on what’s absent.

The accurate story includes what’s been built.

Your 90-Day Patience Plan

Comparison loses its power when you move from Aspirational to Operational.

Aspirational is who I want to be in five years.
Operational is what I am doing in the next 90 days.

Stop asking: “Where should I be?”
Start asking: What matters for the next 90 days, given where I actually am?

Use this structure:

In the next 90 days, I’m focused on:

1. One skill to sharpen

2. One relationship to invest in

3. One proof-of-work artifact to create

Small enough to execute. Specific enough to measure. Yours enough to matter.

The 10-Minute Sprint

The long game is won in 10-minute increments.

Not in dramatic pivots. Not in the fantasy of perfect clarity.

In small, consistent reps that serve your 90-day goal.

Try one this week:

• Read one chapter of the book addressing your current gap

• Write one honest paragraph about what you don’t know yet

• Execute one task that serves your 90-day plan, not your 5-year ego

Ten minutes becomes twenty. Twenty becomes a practice. The practice becomes who you are.

Start today.

THE LAB REPORT

On the “Behind” Narrative

1. The “I should be further” thought I carry most often sounds like: _________________________

2. The person or benchmark I’m measuring myself against is: _________________________
   What I actually know about their full story is: _________________________

3. The last time I felt genuinely on pace was: _________________________

On the Evidence

1. Something I built in the last 12 months that I didn’t have before is: _________________________

2. Something I learned that I could not have learned faster than I did is: _________________________

3. Something I navigated that made me more capable is: _________________________

On the Next Season

1. The one thing that matters most in my next 90 days is: _________________________

2. My 10-minute sprint I can start today is: _________________________

3. What a kinder, wiser leader would say to me about where I am right now is: _________________________

The 2% Challenge

This week, name one thing you’ll stop rushing.

Not to give up on it. Not to lower the bar.

To release the timeline pressure you’ve been carrying about it.

Write what a more patient relationship with it would actually look like. Active. Consistent. Without the added weight of it needing to arrive faster than it can.

That release is the 2%.

One Last Thing

We’ve spent this whole month in Patience—looking at it from four angles: the seasons of development, the pace we keep with ourselves, the people we’re trying to develop, and the outcomes we can’t control.

So I want to close the month the way it deserves to close: not with a productivity tip, but with something closer to the truth.

The young manager comparing her interior to someone else’s exterior isn’t behind.
The leader counting the detour as lost time isn’t behind.
The veteran leader moving the finish line isn’t behind.

They’re in process.

And that difference isn’t semantic. It’s the difference between a narrative that shrinks you and a narrative that orients you.

Patience isn’t waiting. It’s the practice of staying faithful to the process.

Your assignment is unique. The person you’re comparing yourself to isn’t even in the same line as you.

Next month, we’re moving into a theme that follows naturally from Patience: Grace. Not grace as softness or avoidance—grace as the practice of extending to yourself and others the same understanding you’d offer someone you genuinely believe in, even when progress is uneven and the results are messy.

I’m looking forward to building that with you.

Comment (be specific)

What’s one thing you’re going to stop rushing, starting today?

Leave a comment

Share

Subscribe now

— Chibundu

This week, you’ll get:

• The reframe that turns a waiting season into a growth season

• A three-step 2% Move called The Controllable Column

• One sentence worth keeping close this week

• Five “reads” worth your Wednesday attention

THIS WEEK’S THEME

The Workshop, Not the Waiting Room

Active waiting keeps you growing while outcomes are out of your hands.

Most of us are waiting on something right now: a decision, a timeline, an approval, a door that hasn’t opened yet.

The question isn’t whether you’re waiting.

The question is whether the waiting is shaping you… or shrinking you.

Passive waiting just watches the calendar and quietly resents the people holding the keys.
Active waiting uses the time to build your own keys: skill, relationships, proof of work.

Midweek check‑in (be honest):
Have you been working the controllable column this week, or staring at the uncontrollable one?

YOUR 2% MOVE THIS WEEK

The Controllable Column

Use this today to redirect “waiting energy” into “building energy.”

Step 1 — Name what you’re waiting on.
Write it plainly. One sentence. No packaging.
Example: “I’m waiting for approval to launch ____.” / “I’m waiting to hear back about ____.”

Step 2 — Draw the line.
Make two lists:

Out of your control: timeline, other people’s decisions, politics, budget cycles, external conditions.
In your control: a skill you can build, a relationship you can invest in, proof of work you can create, the quality of today’s effort.

Don’t pretend the “out of control” list isn’t real.
Just stop carrying it like it’s yours to solve.

Step 3 — Move on one thing today.
Not “this week.” Today. Before you log off.

Pick one action that fits in 15 minutes:

• send the email that builds the relationship

• draft the one‑pager that clarifies your idea

• pilot a small version of the project

• ask for feedback on your proof of work

• schedule the conversation you keep postponing

That’s the 2% Move: one in‑control action completed, not just considered.

ONE SENTENCE WORTH KEEPING THIS WEEK

THIS WEEK’S READS

1. Feeling Stuck or Stymied? (Dorie Clark) - A sharp reminder that “not yet” doesn’t mean “never,” and a practical push to use waiting seasons strategically.

2. If Strategy Is So Important, Why Don’t We Make Time for It? (Dorie Clark) - A clean explanation of why leaders stay reactive and how to reclaim time for real thinking.

3. Build a Network, Even When You Don’t Think You Need One (Dorie Clark) - A playbook for investing in relationships before you need a favor, which is the whole point.

4. Q&A: The Dip and Knowing When to Quit (Seth Godin) - A short, clarifying read about the hard middle: when patience is wisdom and when it’s avoidance.

5. Welcome to The Obstacle Is The Way (Ryan Holiday) - A straight shot of perspective on turning obstacles into fuel instead of excuses.

GO DEEPER IN THE LAB

Sunday’s Sunday Lead laid out the full “Active Waiting” framework: build skill, build relationships, build proof of work (and how to navigate slow systems without burning energy you can’t afford).

If you’re in a waiting season right now, don’t just read it. Run it.
Read The Sunday Lead here →

Before you go: Hit reply and tell me the door you’re waiting on + your next in‑control move (one sentence).

And if someone in your circle is stuck in “not yet,” forward this to them. The right reframe at the right moment is a gift.

Share

See you Sunday,
— Chibundu

The door didn’t open for years. He kept building the keys.

That’s the part of the MrBeast story that matters to me.

Before Jimmy Donaldson became “MrBeast,” he was a 13-year-old kid uploading videos to what felt like an empty room. No traction. No applause. No externally visible progress. No proof that the work would ever matter.

And he kept going anyway.

Just reps. Not because it was fun. Not because it was rewarding. But because he understood something most people don’t:

Waiting seasons are either a waiting room or a workshop.
Same time passing. Different person on the other side.

A lot of us aren’t waiting to be discovered by YouTube. But we are waiting on something:

• a role to open

• a decision to get made

• funding to clear

• permission to move

• the right person to finally say yes

And here’s what I want to name today:

Waiting doesn’t just test your patience. It tests whether you’ll keep building when nobody is clapping.

The frustration nobody names out loud

Most ambitious leaders don’t talk about their waiting seasons.

Not in meetings.
Not in performance reviews.
Not even with mentors, half the time.

But the waiting is happening. And if we’re honest, it does quiet damage:

• you get bitter

• you get loud

• you get small

• you start taking the wait personally

Here are three patterns I see constantly. Different leaders, same trap: treating the waiting season like something to survive instead of something to use.

Three “Lab Cases” that will feel painfully familiar

LAB CASE #1: The high performer who goes quiet after being passed over

She’s delivered for two years. Applies for the role. Doesn’t get it.

The feedback is clear: “Almost there. You need more influence without authority. You need to manage upward.”

She nods… and disengages.

She still performs, but she stops stretching. Stops building relationships outside her team. Stops practicing the very skills the feedback named.

The door told her exactly what key to build.
She treated the feedback like a verdict instead of a blueprint.

LAB CASE #2: The early-career leader who mistakes visibility for readiness

He wants the next level. Gets this feedback:
“You need strategic thinking. You need more comfort with ambiguity.”

So he becomes louder. More visible. More “in the room.”

But he’s performing readiness instead of building it.

Strategic thinking is developed through unglamorous reps:

• sitting with a problem long enough to think past the first answer

• naming tradeoffs

• deciding with incomplete information and learning from results

Visibility can’t substitute for capability. It only makes the gap easier to notice.

LAB CASE #3: The mid-career leader waiting on a system to move

She’s been trying to get a solid initiative approved for months. The idea is good. The process is slow. Priorities shift. Budget gets deferred. Again.

Now she’s waiting… and she’s bitter.

She talks about bureaucracy constantly, which might be understandable. But it’s also draining the very energy she needs.

Meanwhile, she hasn’t:

• piloted a small version within her control

• documented early results

• built stronger relationships with the two people who can actually move the decision

The system is moving slowly. But she isn’t moving inside it.

None of these leaders lack talent. They’re failing at one thing:

Using the season they’re actually in to build what the next season will require.

Two kinds of waiting

There’s passive waiting.

Head down. Holding pattern. “I’ll do the work after the door opens.”
The outcome determines the effort.

And then there’s the version that changes everything:

Active waiting.

Active waiting says: “The outcome isn’t mine to control, but my preparation is.”

It’s not motivational. It’s practical.

It starts with one question:

What is within my control right now?

Not the timeline.
Not the decision-maker’s calendar.
Not the economy.
Not the reorg.
Not the politics above you.

But this is within your control:

• the skills you build

• the relationships you invest in

• the proof you produce

• the quality of your current work

• your ability to navigate reality instead of arguing with it

  ---

ACTIVE WAITING = BUILD THE KEYS

Three moves. Run them in any “not yet” season.

Key #1: Skill — what you’ll need on the other side
Key #2: Relationships — who will matter when it’s time
Key #3: Proof of work — evidence, not optics

The Controllable Column (where your power actually is)

Here’s the fastest way to burn out in a waiting season: pouring your best energy into what you cannot move.

Uncontrollable (real, but not yours):

• when leadership will open the role

• when the budget cycle will approve funding

• who is “in the room” this quarter

• how fast the system moves

• whether someone else changes their mind

Controllable (yours):

• what you learn

• who you build with

• what you ship

• what you document

• how you prepare

• how consistently you show up

Active waiting is simple:

Three Active Waiting Keys to Build

These are not abstract concepts. These are reps you can run this week.

Key #1: Build the skill you’ll need next

Don’t just ask, “How do I get through the door?”
Ask, “What will I need to succeed on the other side?”

Then build that now.

If the feedback is “influence without authority,” build reps:

• lead a cross-team effort without formal power

• write executive-ready updates

• bring solutions, not just problems, to senior stakeholders

If the feedback is “strategic thinking,” build reps:

• draft a one-page strategy memo before proposing a solution

• name the risks and assumptions

• make decisions with imperfect information and review what you learned

Passive waiting stares at the gap.
Active waiting turns the gap into a training plan.

Key #2: Build the relationships that will matter

Not networking. Not card-swapping. Not “let’s grab coffee so I can ask you for something.”

Real relationships. The kind built through curiosity, presence, and usefulness without keeping score.

Two reps that work:

• One message a week: “Saw your work on ___. Curious how you’re thinking about ___.”

• One value add: summarize a useful insight, share a resource, connect two people who should know each other

If you’re waiting on an initiative, identify the two people whose buy-in changes everything and start moving toward them.

Doors don’t open only because you were talented.
They open because the right people trust your work and your judgment.

Key #3: Build proof of work

Proof of work is not self-promotion.
It’s evidence. Output. Receipts.

If you’re waiting to do something at a bigger scale, do the smallest version now:

• run a 2-week pilot inside your scope

• document results (before/after)

• create a repeatable process

• share the proof with the right stakeholder

Visibility without substance is noise.
Proof of work is quiet confidence with documentation.

Patience with systems: navigate, don’t rage

Let’s talk about a specific kind of waiting that hits leaders hard:

Waiting on a system.

Bureaucracy. Procurement. Approvals. The four signatures from people who don’t talk to each other. The process built for a world that no longer exists.

Here’s the hard truth:

Rage at the system is usually wasted energy.
Not because the frustration isn’t legitimate. It often is.
But because the system doesn’t receive your frustration.

You do.

So the posture that helps is navigation:

• How do decisions actually get made here?

• Who has informal influence?

• What evidence makes “no” harder to justify?

• What can I pilot inside my control while the system catches up?

MrBeast couldn’t make YouTube move faster. He studied how it worked, positioned himself, and kept producing while he waited.

That’s not passivity.

That’s strategic patience with a system that runs on its own timeline.

THE LAB REPORT

Six questions. Fifteen minutes. Honest answers only.

On the waiting

1. The outcome I’m waiting on (and can’t fully control) is: ____________________

2. If I’m being honest, this waiting season has been doing this to my energy: ____________________

3. The way I’ve mostly been waiting so far looks like: ____________________

On the keys

1. The key I need to build right now is (circle one): Skill / Relationships / Proof of work

2. One specific “key-building” action I can complete or start this week is: ____________________

3. The uncontrollable thing I need to loosen my grip on (or the system I need to navigate differently) is: ____________________

The 2% Challenge

Pick one in-control move. Schedule it. Ship it.

This week, identify one active waiting move and actually do it.

Not a plan. Not an intention. The actual thing.

Use this template:

By (day/time): ____________________
I will do: ____________________
Proof I did it (deliverable): ____________________

• A message sent.

• A pilot launched.

• A one-pager written.

• A relationship built.

• A skill rep completed.

The door may not open faster. That’s not the point.

Active waiting keeps you growing. And growth doesn’t wait for permission.

Jimmy made “the next video” for years before the numbers moved.

What’s your version of the next video?

One Last Thing

A waiting room is where you sit until something happens to you.

A workshop is where you get better while you wait.

Same time passing.
Completely different person on the other side of it.

You can’t control when the door opens.

But you can control what kind of leader you become while you’re standing in front of it.

Build the keys. Start this week.

Leave a comment

In this format:

• I’m waiting on: ____

• I’m building: Skill / Relationships / Proof

• My next 2% move: ____

If this landed, send it to someone who’s been stuck in “not yet” longer than they’d like to admit.

See you in the Lab.

— Chibundu

This week, you’ll get:

• The reframe that turns a frustrating team member into a development opportunity

• A three-step move called The Ownership Transfer

• One sentence you can use in a hard conversation today

• Five reads worth your Wednesday attention, plus a Vault resource

THIS WEEK’S THEME

The Long View on People

Patience with people isn’t patience instead of standards. It’s patience in service of standards that actually stick.

There’s a version of “patience” that’s really avoidance.
Where you tell yourself you’re being kind by not pushing, when really you’re dodging the discomfort of the conversation that could actually help someone grow.

That’s not the rep.

The rep is this: “You’re not there yet, and I’m not going anywhere.”
Clear-eyed. Steady. Not soft.

Midweek check-in (be honest): Who are you currently managing, but not really developing?
Name them privately. That’s step one.

YOUR 2% MOVE THIS WEEK

The Ownership Transfer

Use this in any coaching conversation where you’ve been carrying the problem more than the person who owns it.

Step 1 — Catch yourself before you solve it.
When you feel yourself about to give the answer, fix the situation, or soften the expectation, pause. Ask:
“What do you think the issue is here?”
Give them the first move.

Step 2 — Reflect back what you heard.
Say: “So what I’m hearing is…” (then mirror their words).
No correction yet. No lecture. This slows things down enough for real thinking to happen.

Step 3 — Close with their next step, not yours.
End with: “What’s your next step?”
Then follow up on that next step. That follow-up is where accountability lives.

Ten minutes today. Compounding impact over the next few weeks.

ONE SENTENCE YOU CAN USE TODAY

Before feedback or a redirect with a struggling team member, say:

THIS WEEK’S READS

1. “The Feedback Fallacy” — A sharp argument for why most feedback doesn’t create growth, and what leaders should do instead.

2. “The Power of belief: mindset and success” — A clean, research-backed reminder that what leaders believe about people shapes how they lead them.

3. Multipliers — A practical lens on leaders who shrink people versus leaders who expand them. Read it with your coaching habits in mind.

4. “Stop Trying to Motivate Your Employees” — A useful tension: you can’t “install” motivation, but you can build conditions that unlock it.

5. The Coaching Habit — If you want to stay curious longer (and stop rescuing), this is the playbook.

Vault Resource (for your back pocket):

The Patience Rep Script Card (Care + Clarity + Curiosity) — reply with “PATIENCE REP” and I’ll send you the one-page version you can keep open during 1:1s.

GO DEEPER IN THE LAB

Sunday’s Lead breaks down the real leadership mistake: quietly stepping back from someone before you’ve actually done the work of development. It also includes the full Patience Rep boxed callout and the Lab Report questions to help you spot who you’ve “written off” prematurely.

If you reply to this email, tell me one thing: Where do you most need patience with people right now: standards, support, or staying curious?

And if someone in your world is ready to give up on a team member too early, forward this. Sometimes the most helpful thing we can do is hand someone a better rep.

Subscribe now

There was a team member once who I was absolutely certain wasn’t going to make it.

She was talented. Sharp instincts. Great with people. The kind of person who could read a room in real time. But she was chronically late on deliverables. Not occasionally. Predictably. Consistently.

And when I’d bring it up, she’d nod, apologize… and then two weeks later, late again.

So I did what a lot of leaders do when they’re frustrated and trying to be “fair”:

• I had the direct conversation.

• I increased check-ins.

• I set clearer deadlines.

• I explained the impact.

• I tightened the expectations.

And if I’m honest, I probably added a little extra edge in my tone over time because I felt like I was being played.

At some point, I quietly made a decision I’m not proud of: I stopped investing in her.
I still managed her. I still assigned work. But the real coaching, the real belief, the “I’m going to fight for you to grow” energy?

I pulled it back.

I told myself it was pragmatic.

Really, it was impatience wearing professional clothes.

Then something happened that forced me to confront my own leadership. It wasn’t another missed deadline. It wasn’t a performance review. It was a moment of curiosity I didn’t plan, but needed.

In a conversation that had nothing to do with deliverables, she mentioned her last manager.

She said it casually, like it was normal:
“In my old role, the first deadline wasn’t the real deadline. Things always shifted.”

That line hit me harder than I expected.

Because it meant she wasn’t choosing not to change.
She was struggling to.

She had been trained (by a previous system) to believe deadlines were suggestions until proven otherwise. She wasn’t testing me. She was operating on the only environment she’d known.

When I finally got curious instead of frustrated, things started to shift.

Not overnight.
Not on my timeline.
But they shifted.

She’s still leading today, by the way. Runs her own team now. Tight operation.

I think about her whenever I’m tempted to write someone off too early.

People don’t experience your values through your intentions. They experience them through your consistency.

The Speed of Human Change

Here’s the thing nobody tells you when you get your first direct report:

People change slowly.
Meaningfully, profoundly slowly.

And almost never on the schedule you’ve already set for them in your head.

That isn’t because people are lazy. Or resistant. Or ungrateful for your investment.

It’s because real change has stages you can’t skip.

Think about what you’re asking of someone when you want them to change:

1. They have to recognize the pattern exists.

2. They have to accept it’s a problem (for them, not just for you).

3. They have to believe change is possible.

4. They have to practice a new behavior while feeling awkward and unskilled.

5. They have to repeat it under pressure, where their old pattern used to “protect” them.

6. They have to do all of that while still doing their job.

Most of that work happens beneath the surface, in the weeks where you’re watching behavior and thinking: Nothing is happening.

You can’t rush that process.

But you can build better conditions for it.

And that’s where a lot of leaders get tripped up. We confuse patience with passivity.

Patience isn’t “we’ll see.”
Patience is “we’ll work.”
But with the right rep.

The Patience Rep

Most leaders default to one of two modes:

Mode 1: Care without Clarity
You soften expectations when someone struggles. You avoid accountability because you don’t want to pile on. People feel supported… and confused. The bar gets fuzzy.

Mode 2: Clarity without Care
You hold the standard, but the message lands cold. People know what’s expected… and feel alone. The bar is clear, but the relationship becomes brittle.

Neither produces the kind of change that sticks.

What works is Care + Clarity, and the bridge that makes it practical is Curiosity.

Because curiosity is what keeps you from turning feedback into judgment.
Curiosity is what turns “you’re failing” into “let’s solve the real problem.”

📦 CARE + CLARITY + CURIOSITY (The Patience Rep)

Care: “I’m invested in you.”
Clarity: “The standard isn’t moving.”
Curiosity: “What’s the real barrier, and what’s your plan?”

Here’s what it sounds like in a real conversation:

“I want to be direct with you because I’m invested in you. The report was late again, and that’s the third time in six weeks. The standard isn’t moving. Help me understand what’s actually driving this, and what your plan is for next time.”

That’s the rep.

Care keeps the person from shutting down.
Clarity keeps the team from paying the price.
Curiosity finds the real issue instead of debating symptoms.

Patience isn’t “letting it slide.” Patience is staying in it long enough to get to the truth.

Coaching, Not Rescuing

There’s a distinction I come back to constantly:

Coaching is development. Rescuing is relief.

Rescuing looks like:

• rewriting their work so it’s “done right”

• taking on the hard conversation so they don’t have to

• lowering the standard quietly to keep things moving

• accepting “almost” because you’re tired

Rescuing protects the relationship short-term and stunts growth long-term.

It also communicates something you probably don’t intend:

Coaching looks like:

• asking questions instead of delivering verdicts

• letting them sit in the discomfort long enough to learn

• refusing to fix fast when fast-fixing is just impatience in a helpful disguise

• transferring ownership back to them every time

Here are a few coaching questions I keep on repeat:

• “What do you think the real issue is here?”

• “What have you already tried?”

• “What would help most from me right now: a sounding board, a resource, or space to figure it out?”

• “What’s your next step?” (This one closes the loop.)

These questions don’t guarantee fast change.

But they build the one thing all lasting change depends on:
their ownership of their own growth.

Accountability Without Shame

This is where a lot of leaders quietly struggle.

Accountability and shame are not the same thing, but they can feel similar in the moment.

• Shame attacks identity: “You are the problem.”

• Accountability addresses behavior: “This behavior had this impact, and it needs to change.”

Shame produces defensiveness, withdrawal, and sometimes a kind of freeze response.

Accountability produces discomfort too, but it’s the useful kind. The kind that has somewhere to go.

One of the most effective ways I’ve found to practice accountability without shame is a tight feedback loop:

• Specific: name the behavior, not the person

• Timely: address it close to when it happened

• Forward-facing: spend more time on what needs to happen next than what went wrong

• Repeated without escalation: hold the standard consistently without adding emotional heat every time

This is where patience becomes real.

Because the fourth conversation can feel like failure if you think growth should be instant.

It isn’t failure.

It’s how humans develop.

THE LAB REPORT

Set aside fifteen minutes before Friday. Don’t skip the uncomfortable questions.

On Your Frustration

1. The person I’m most frustrated with on my team right now is: _________________________.

2. When I’m honest about what they’re struggling with, the root of the issue is probably: _________________________.

3. Have I actually made the expectation explicit and clear, or have I been expecting them to intuit it? _________________________.

On Your Default

1. When someone is struggling, I tend to default toward (circle one):
   softening the standard / holding the standard coldly / avoiding the issue / using the Patience Rep

2. The last time I gave feedback, what I said was: _________________________.
   What I probably should have also asked was: _________________________.

On Your Next Step

1. One curiosity question I can bring to a conversation this week is: _________________________.

2. The person I’ve been managing but not really developing is: _________________________.
   The first thing I could do differently is: _________________________.

THE 2% CHALLENGE

Have one real coaching conversation this week.

Not a status update. Not a drive-by check-in. A real coaching conversation with someone who is on a growth edge.

Use The Patience Rep.

Do (within 24 hours):
Schedule 20 minutes. Name one behavior. Ask one curiosity question. Close with ownership.

Say:
“I’m invested in you. The standard isn’t moving. Help me understand what’s driving this, and what your plan is for next time.”

Measure:
By the end of the conversation, you should be able to answer:

• What’s the real barrier?

• What’s their plan?

• What is the next step and by when?

That’s it. One rep. Done clean.

One Last Thing

Leading people is the most patient work there is.

Harder than strategy. Harder than systems. Harder than most of the stuff that gets celebrated in leadership culture.

Because it requires you to hold belief in someone’s growth longer than it’s comfortable to hold it, and to keep showing up with support and standards even when it feels like nothing is changing.

The leaders who changed me weren’t easy on me.

They were the ones who refused to lower the bar while also refusing to leave me alone with it.

And that staying, that stubborn, clear-eyed staying, is what eventually moved me.

You can’t rush someone into maturity.
But you can be the kind of leader who’s still there when it arrives.

Closing + Comment

What’s one change you’re trying to lead in someone right now, and what’s your next step?
If you want a simple format:

Comment: Care / Clarity / Curiosity + the behavior you’re tempted to label “stubborn” + your next step. I read every single one.

If this landed, forward it to a leader you know is in the middle of a hard development conversation and who needs a reminder: Patience isn’t soft. It’s skilled.

See you in the Lab.

— Chibundu

Welcome to The Midweek Minute (MWM). Every Wednesday, you’ll get a short read with one idea and one move before you are back to leading.

This week, you’ll get:
∙ The reframe that makes pacing feel like strategy, not retreat
∙ A 3-step reset called The Energy Audit
∙ One sentence you can use with yourself (or your team) today
∙ Four reads worth your Wednesday attention

THIS WEEK’S THEME
The Pace That Lasts
Sustainable leadership is doing the right things in a way you can repeat.

If your week feels like constant sprinting, hear me: that’s not always a workload problem. A lot of the time it’s an energy allocation problem.

Because leadership isn’t just what you do. It’s how you show up while you do it.

When your pace is off, everything starts to drift:

• your patience gets thin

• your feedback gets vague

• your decisions get reactive

• your presence gets transactional

The leaders who last aren’t the ones who “power through” the most. They’re the ones who protect enough capacity to keep leading well.

YOUR 2% MOVE THIS WEEK
The Energy Audit
Use this today to reclaim your peak capacity before the week slips further away.

Step 1: Name your drain.
Look at yesterday and identify the one activity, interaction, or habit that cost you the most energy relative to its actual importance.
Not the hardest thing. The thing that drained you disproportionately.

Step 2: Name your restore.
Find the one moment (even five minutes) where you felt clear, steady, or present.
What was happening? What made it different?

Step 3: Make one adjustment today.
Protect one more moment like the restore.
Reduce, limit, or restructure one thing like the drain.
No reinvention. One move.

That’s your 2% Move. Your Energy Audit in three questions, completed in under ten minutes.

ONE SENTENCE YOU CAN USE TODAY
When someone asks why you’re protecting your schedule or your energy:

THIS WEEK’S READS

1. “Manage Your Energy, Not Your Time” — The piece that reframed how an entire generation of leaders thought about productivity. Still the clearest argument for the energy-first approach. Essential reading if you haven’t read it.

2. “The Research Is Clear: Long Hours Backfire for People and for Companies” — A data-backed dismantling of the overwork myth. This article is short, well-sourced, and useful to share with a leader who still believes hours in = output out.

3. “Burnout Is About Your Workplace, Not Your People” — Not all pacing challenges are personal choices. Sometimes the environment is the problem. This will help you identify which situation you’re actually in.

4. “The Art of Rest” — This book explores what restores human beings (the research will surprise you). Even reading a summary will shift how you think about recovery.

GO DEEPER IN THE LAB
Sunday’s piece goes deeper on three tools I keep finding myself recommending to leaders: planning by energy, designing your Minimum Viable Day, and building a Recovery Ladder you can actually maintain. If your pace has been unsustainable lately, the Lab Report questions at the end will tell you the truth fast.

Two asks (and I mean them):

1. What’s one thing you’re doing this week to protect your pace? Hit reply and tell me — seriously, I read every one, and this is the kind of conversation that’s worth having in public. What are you actually doing to sustain yourself?

2. Forward this to one leader you know who’s running too hot. Sometimes the most loving thing you can do is help somebody slow down before they break.

Leave a comment

See you Sunday.
— Chibundu

There’s a version of my story that sounds impressive on paper.

National Chair of the National Black Law Students Association.
Student liaison to the American Bar Association.
Leadership roles across SMU’s Student Bar Association, the Cox Graduate Real Estate Club, the Entrepreneurship Club, and the JD/MBA Society.

And at the same time?
I was still a student.

So my “real” priorities were basic:
Go to class. Get good grades. Perform well at my extern and fellowships. Lead NBLSA well. Find a job after graduation. Make sure my family had the details for graduation. Coordinate the details that nobody else thinks about until they’re suddenly urgent.

I wanted NBLSA to run well.
I wanted to leave it financially strong.
I wanted our convention to be the best convention EVER.
And I wanted the leadership transition to be smooth.

In my head, that meant one thing: I just have to keep pushing.

And I did. For months.

Then my term wrapped… and my body collected its debt.

I didn’t “take a break.”
I didn’t “rest up.”

I passed out.

I slept for three days.

Not the cute “I slept in” kind of sleep. I mean the kind of sleep where you miss classes, miss calls, miss friends, miss obligations, miss transition work… and you wake up disoriented because your body finally got what it had been begging you for the whole time.

That’s the part people don’t see when they praise your ambition.

They see the leadership titles.
They don’t see the cost.

And when I finally came back to myself, I promised my body something, out loud:

“I will never do that to you again.”

Share Everyday Leadership Lab

That moment became a leadership lesson I still use today:

Your gift can’t help anybody if your pace destroys the person carrying it.

Burnout Isn’t a Failure of Commitment. It’s a Failure of Pace.

Most ambitious leaders don’t burn out because they don’t care.
They burn out because they care… without a system.

We celebrate the wrong things:

• the late-night emails

• the back-to-back calendar

• the leader who never says no

• the person who “always comes through”

But leadership isn’t proven by how much you can survive.
It’s proven by what you can sustain.

Burnout is not a character flaw.
It’s not laziness.
It’s not “you just need to be more disciplined.”

Burnout is an arithmetic problem:
you’ve been withdrawing more than you’ve been depositing for so long that your account hit zero.

And here’s the sneaky part: most leaders don’t notice burnout when it shows up.

It rarely arrives as one dramatic collapse.
It arrives like this:

• You start snapping in meetings, and you don’t recognize your own tone.

• You avoid conversations you used to handle with clarity because you don’t have the bandwidth.

• You start doing “good enough” work in places you normally take pride in.

• You get home and scroll because your brain can’t do one more thing.

• You stop enjoying what you once loved, and you tell yourself it’s just “a season.”

Some seasons are real.
But some seasons are self-inflicted.

And if you’re leading people while living in that state, your team pays for it too.

Because they don’t just experience your intentions.
They experience your pace.

What Sustainable Pace Actually Means

Let me clear up a misunderstanding right now:

Sustainable pace is not soft.
It’s not coasting.
It’s not “doing the minimum.”

Sustainable pace is strategic output over time.
It’s the difference between:

• a leader who spikes intensity, then crashes

• and a leader who can show up consistently, even under pressure

Think athlete training, not athlete highlights.

A sprinter can produce elite speed for a short distance.
A marathon runner builds capacity to cover real ground.

Neither is better. But if you’re trying to build something that lasts (a team, a culture, a career, a legacy), you can’t run every week like it’s the championship.

And yes, sometimes there are crunch seasons. Sometimes you have to push.

But here’s the rule I wish I understood earlier:

You can borrow energy for a moment. You can’t borrow energy for a life.

Signs You’re Outpacing Your Capacity

Quick check. No shame. Just honesty.

You might be outpacing your capacity if:

1. Your irritability shows up before your thinking does.
   Small friction is producing big reactions. You’re reacting before you’ve processed.

2. You’re cutting corners on what you used to do with care.
   Your feedback gets generic. Your prep disappears. You call it “efficiency” but you know it’s depletion.

3. Avoidance becomes your coping strategy.
   Not because you don’t know what to do. Because you don’t have the energy to do it well.

4. Recovery takes too long.
   Sleep doesn’t reset you the way it used to. Weekends feel like rehab.

5. You stopped enjoying the work you once loved.
   That’s not “adulthood.” That’s a pace problem.

If you recognized yourself in two or more, listen:
I’m not judging you. I’m telling you the truth.

Your body keeps receipts.

Three Pace Tools Worth Building Into Your Week

Tool 1: Plan by energy, not just time

Most calendars are built around time blocks. But time isn’t your real bottleneck. Energy is.

Most people have 2–3 hours a day where they’re sharp, focused, and emotionally steady. That window is where you should put:

• strategic work

• hard conversations

• deep thinking

• planning

If you spend your best window on email and reactive meetings, everything else will feel harder than it has to.

2% Move: Identify your sharpest 90 minutes this week and protect it like it matters (because it does).

Tool 2: Build a “Minimum Viable Day”

Your Minimum Viable Day is the floor.

It’s the handful of actions that, if done, mean the day wasn’t wasted even if everything else gets loud.

For a leader, it might be:

• one real check-in with a direct report

• one concrete decision captured and communicated

• 10 minutes of planning for tomorrow

That’s not lowering standards.
That’s keeping you from living in reaction all day and calling it leadership.

2% Move: Write your Minimum Viable Day on a sticky note. Put it where you’ll see it.

Tool 3: Use a simple “Pace Script” when people ask for more

A lot of burnout isn’t workload. It’s boundaries.

Here’s a line that saves leaders:

“I can do that. I just need you to tell me what moves down.”

Or if you want it even cleaner:

“I have capacity for one: A or B. Which one matters most?”

This isn’t avoidance. It’s stewardship.
It’s you refusing to pretend you’re infinite.

THE LAB REPORT

Work through these before the week is out. One sentence each. Honest is the point.

On Your Pace

1. If my body could review my schedule this week, it would say: ____________________

2. The sign I’m outpacing my capacity that I’ve been ignoring is: ____________________

3. The last time I felt genuinely restored after a workday was: ____________________

On Your Energy Architecture

1. My sharpest window (when I’m most present) is typically: ____________________

2. What I usually spend that window doing is: ____________________

3. My Minimum Viable Day includes: ____________________

On Your Boundaries

1. The request I need to renegotiate instead of absorbing is: ____________________

2. The sentence I need to practice saying is: ____________________

The 2% Challenge

This week, set one boundary to protect your pace.

Not a new personality.
Not a 17-step routine.
One boundary you can defend.

Examples:

• “No email after 8 PM this week.”

• “I’m blocking 9:00–10:30 AM for deep work.”

• “I’m taking a 10-minute walk after lunch.”

• “I’m not scheduling over my recovery night.”

Write it down. Tell someone.
And when it gets tested (because it will), remember:

One Last Thing

Ambition is a gift.

But gifts can be burned out, not just by bad people, but by good people who never learned pace.

I learned it the hard way, after months of leadership and pressure and responsibility, when my term ended and my body took what I refused to give it.

Your team doesn’t need you to be a hero.
They need you to be here.
Clear. Steady. Consistent.

That takes discipline.
That takes maturity.
That takes sustainable pace.

Comment (be specific):

What’s one boundary you’ll set this week to protect your pace?
Drop it in the comments in this format: “My boundary: ____.”

And if you know an ambitious leader who’s quietly burning out, forward this to them.
If you’re not subscribed yet, Sundays in the Everyday Leadership Lab are free, practical, and built for real life.

See you in the Lab.
— Chibundu