What we cover:

• Why the person who gets promoted was already operating at the next level before the title changed — and what that means for how you think about your own contribution right now

• Charles Hamilton Houston and the idea that changed everything Marshall ever did: a lawyer is either a social engineer or a parasite on society — and what Rung 4 thinking looks like from a first year law school classroom

• The traveling years: what Marshall’s life actually looked like driving county roads in the South arguing cases in hostile courtrooms — and why he was thinking at a constitutional altitude from a car with barely enough money to cover his expenses

• The Sam Walton connection: what a variety store manager in Arkansas driving hours to study competitor layouts has to do with a civil rights lawyer choosing cases for their precedent value

• The legal architecture of Brown v. Board: why Marshall didn’t go straight at Plessy v. Ferguson — and what twenty years of deliberately chosen cases reveals about what operating at organizational altitude actually looks like in practice

• Kenji’s story: two years of strong work at the wrong altitude — and what the colleague who got the role was doing differently the entire time

• Three specific practices for climbing the ladder without a new project, a new title, or anyone’s permission

The question to take into this week:

Think about your last three significant contributions. What rung were you actually operating at? And if the answer is mostly Rung 1 or 2 — what would it look like to reframe just one of them at Rung 3?

For the full Altitude Ladder framework — including the four rungs, the three practices, and the complete Kenji story — check out the article at thereadyset.substack.com

Signal Forward runs alongside The Ready Set — built for individual contributors, specialists, and practitioners whose behavioral patterns determine whether their contribution gets seen, valued, and rewarded.

Subscribe: thereadyset.substack.com

Paid membership for The Ready Set is open. KLIR gives you a personalized behavioral picture of where you actually stand across the ten behaviors we’ve covered. The AI Ready Set Coach helps you build a real development plan around your specific results. It’s not a content upgrade — it’s a genuine development experience.

Learn more: https://ready-set-membership.c2advising.com/

New here? Start with the first article. In People or HR? Pass this along to your team.

Every promotion decision answers a question. Most people assume it’s this one: has this person mastered their current role?

It’s not. The real question is whether this person has already demonstrated the behaviors of the next role.

Sit with that for a second, because it reframes a lot of career frustration that otherwise has no good explanation. Talented people master their current role. Get strong reviews. Put in the time. Watch someone who looked less accomplished on paper get the role they wanted. Assume it’s politics, or timing, or some invisible favoritism they can’t see.

Sometimes that’s true. More often it’s altitude.

The person who got promoted was already operating at the next level before the title changed. Thinking at a higher level. Communicating at a higher level. Taking ownership of problems that weren’t technically theirs yet. The promotion didn’t change what they were doing. It just made it official.

The Four Rungs

The Altitude Ladder is not about doing someone else’s job or performing ambition for an audience. It’s about expanding how you think about your work while you keep doing your work well. Four rungs. Each one is a shift in orientation, not a shift in job description.

Rung 1: Task. The work directly in front of you. Your assignment, your deliverable. You have to execute here. The problem is when it’s the only place you ever operate.

Rung 2: Team. How your work connects to what your teammates need. Where the handoffs are. What breaks down when you don’t do your part well. Solid contributors live here, and it matters. But it doesn’t differentiate you.

Rung 3: Function. How your team’s output connects to what the broader department or function is trying to accomplish. What the priorities are at that level. Whether your contribution is actually serving those priorities or just completing tasks. Most promotions require you to demonstrate this rung consistently before anyone will seriously consider you for a role that operates here.

Rung 4: Organization. How the function connects to strategy, competitive position, direction. Individual contributors who operate here regularly tend to end up in conversations and meetings nobody expected them to be in. Because they’ve made themselves useful at an altitude the organization didn’t know was available to them.

Most people stay at Rung 1 or 2 indefinitely. Not because they lack capability. Because nobody told them the game was being played at a different level.

Why Alicia’s Story Fits Here

In the last article, Alicia’s manager had made a cryptic comment about “strategic thinking” that she couldn’t decode for seven months. When she finally asked directly in a CPP conversation, the translation was plain: she was solving tactical problems without connecting her solutions to business context. Rung 2 thinking in a role that needed Rung 3.

Her solutions were good. Her altitude was wrong. And no one said so clearly until she created the conditions for an honest conversation.

That’s how altitude gaps usually surface. Not as performance problems, but as vague feedback that feels personal but is actually structural. You’re operating well at the level you’re at. However, the organization needs someone operating at the level above it. And nobody has figured out how to say that without it sounding like criticism.

The Version Nobody Talks About

Kenji was a data analyst at a healthcare organization. Technically strong, reliable, well-liked on his team. He’d been watching a senior analyst role for two years. When it opened, he applied. He didn’t get it.

The feedback was vague. It usually is.

What actually happened was simpler than the feedback suggested. In two years of working alongside Kenji, the people making the decision had never seen him operate above Rung 2. He talked about his projects. He delivered clean work. He helped his immediate teammates. But he never demonstrated any awareness of what the department was trying to accomplish, how the data his team produced connected to decisions being made further up, or what problems were keeping the function leadership awake at night.

The person who got the role had been doing all of that. Not loudly. Not in a way that felt like she was campaigning for anything. She just consistently framed her work at a higher altitude. Asked questions in cross-functional meetings that showed she understood the bigger picture. Flagged trends relevant to adjacent teams because she was paying attention to what mattered beyond her own deliverables.

Same technical skill. Different altitude. Different outcome.

Kenji’s problem wasn’t performance. It was that the behavioral evidence he’d been generating for two years answered the wrong question.

How to Actually Move Up the Ladder

None of this requires a new project or anyone’s permission. It requires asking different questions about work you’re already doing.

Before a meeting, add one question to your prep: what does the person two levels above me need to be true coming out of this conversation? Not what do I need to present. What does the organization need from this room. That question alone changes how you show up before you’ve said a word.

When you deliver work, connect it to something above the task level. One sentence. “Here’s the analysis, and based on the Q3 pattern, this will probably affect how we think about capacity planning going into next year.” Ten seconds. Rung 3 signal.

When problems come up, frame them at one level higher than where they started. “We’re seeing this pattern in our team, and based on what I’m hearing in cross-functional conversations, I think it’s showing up elsewhere too” is a different contribution than “here’s my problem and here’s how I fixed it.” Same information. Different altitude.

The ladder doesn’t require more time. It requires a different orientation to the time you’re already spending.

One More Thing Worth Saying

Poor leadership doesn’t make this harder. It actually makes it more available.

When leaders are unclear, checked out, or just overwhelmed, gaps open up. The function still needs to run. Priorities still need to be communicated. Work still needs to connect upward to something that matters. The person who steps into that space, not as a power grab, but to be useful at a higher altitude than their role requires, becomes someone the organization leans on.

And an organization leaning on you is one of the strongest career signals there is. You don’t need a great manager to climb the ladder. All you need is the discipline to keep asking what the view looks like from one rung higher than where you’re standing.

Honest question for this week: Think about your last three significant contributions. What rung were you actually operating at? And if the answer is mostly Rung 1 or 2, what would it look like to reframe just one of them at Rung 3?

Start there. I’d love to hear what comes up in the comments.

One more thing before you go.

Everything in this series (the signal, the three I’s, the disciplines, the traits) is being built into something larger.

Later this year, we’re releasing a significant update to The Ready Set experience. What’s coming is an extension of the AI Ready Set Coach that will meet you exactly where you are, whether you’re two years into your first real role or two levels from the executive suite, and grow with you as you move.

For individual contributors, that means the full Signal Forward framework: the behaviors, the disciplines, the trait development, and guided content built specifically for people who are doing excellent work and trying to make sure it doesn’t stay invisible.

For emerging leaders and managers, it bridges the gap, the moment when your contribution shifts from personal performance to collective performance, and the skills that got you here stop being sufficient for where you’re going.

For experienced leaders, it’s the full Ready Set framework: the ten behaviors, the diagnostic, the coaching, and the development architecture that drives what leadership actually looks like at scale.

One experience. Every level. Built to progress with you.

We’ll have more details as we get closer. If you’re already a paid member, you’ll be among the first to know, and the first to access it.

More Signal Forward coming soon. Stay with us.

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership and talent content and resources to everyone. Subscribe free and get new behavioral-based leader and talent insights every week.

Plus two Ready Set resources to put to work immediately.

Leave a comment

Share The Ready Set

Subscribe now

What we cover:

• Edison’s mother pulling him out of school at seven and deciding his development was her responsibility — and what that decision seeded in him for the rest of his life

• The baggage car laboratory: what a twelve-year-old convincing a railroad to let him run chemistry experiments on a moving train reveals about who owns your development

• The five million pages: why Edison’s notebooks weren’t a record of his development but the engine of it — and how every failure became a data point rather than a setback

• The Charlie Munger connection: what building a latticework of mental models across disciplines has to do with an inventor running continuous feedback loops in a laboratory

• Menlo Park 1876: the first industrial research laboratory in American history — and why scheduling breakthroughs instead of hoping for them changes everything

• The phonograph: how ten days of work produced one of the most significant inventions in history — and why that moment was the output of years of compounding development, not a lucky break

• Why the breakthrough is the evidence and the system is the point

The question to take into this week:

What does your version of the notebook look like? And when did you last add to it?

For the full Continual Performance Pursuit framework — including the three questions, the thirty-minute structure, and the math that makes it worth doing — check out the article at thereadyset.substack.com

Signal Forward runs alongside The Ready Set — built for individual contributors, specialists, and practitioners whose behavioral patterns determine whether their contribution gets seen, valued, and rewarded.

Subscribe: thereadyset.substack.com

Paid membership for The Ready Set is open. KLIR gives you a personalized behavioral picture of where you actually stand across the ten behaviors we’ve covered. The AI Ready Set Coach helps you build a real development plan around your specific results. It’s not a content upgrade — it’s a genuine development experience.

Learn more: https://ready-set-membership.c2advising.com/

New here? Start with the first article. In People or HR? Pass this along to your team.

Alicia’s annual review was in March. It was October.

In the seven months between those two dates, she had received exactly two pieces of meaningful feedback. A “nice job” in a team meeting. And a cryptic comment from her manager about “continuing to develop her strategic thinking” that she couldn’t decode no matter how many times she turned it over.

She didn’t know if she was on track. She didn’t know what her manager actually thought of her trajectory. She didn’t know what “strategic thinking” meant in practical terms, or how she was supposed to develop something that nobody had defined. Seven months of career-shaping time was passing and she was flying without instruments, waiting for March.

Here’s the thing about Alicia’s situation that’s worth naming clearly: she wasn’t being neglected. Her manager wasn’t indifferent or incompetent. He was managing twelve direct reports through a budget cycle and a reorganization, which meant performance conversations for people who were performing adequately had migrated to the bottom of a list that never got short enough. Alicia wasn’t a priority problem. She was a scheduling casualty.

And scheduling casualties are everywhere. The annual review system wasn’t designed to develop you. It was designed to document you. To create a defensible paper trail of performance ratings for HR purposes. The feedback it generates is often too vague to act on, too infrequent to be timely, and too high-stakes to be fully honest. Everyone knows this. Almost nobody does anything about it.

Alicia decided to do something about it.

The Inversion

Most people approach their own development as a passive exercise. You do the work. Your manager evaluates the work. You receive the feedback. You adjust. The power dynamic is fixed: evaluator and evaluated. And within that dynamic, your development moves at the pace of someone else’s availability, someone else’s priorities, someone else’s comfort with difficult feedback.

Continual Performance Pursuit flips that entirely.

It’s a simple practice: a focused thirty-minute conversation with your leader every four to six weeks, structured around three specific questions that you own, you prepare for, and you lead. Not asking for feedback in the traditional sense, which puts your manager in the evaluator seat and keeps you in the receiver seat, but something more assertive than that. You’re not being reviewed. You’re pursuing your own growth and inviting your leader to participate.

When Alicia proposed it, she didn’t frame it as a request for more face time or a bid for attention. She was direct: I want to take more deliberate ownership of my own development. I’d like to schedule a short conversation with you every five weeks, focused on three questions. I’ll prepare and lead. I just need your honest input.

Her manager said yes without hesitating. Because what she was offering him was easy, a structured agenda, a defined time box, and a clear role. All he had to do was show up and be honest for thirty minutes. She’d done everything else.

That’s the design insight behind CPP: even a mediocre manager can answer three specific questions in thirty minutes. Even a disengaged leader will participate in a meeting you scheduled, prepared for, and are running. The discipline doesn’t require a great manager. It requires a structured invitation that makes honest contribution easy.

What Twenty-Eight Minutes Surfaced

In Alicia’s first CPP conversation, she learned three things that seven months of silence had never produced.

First: her communication in cross-functional settings was creating friction she didn’t know existed. She led with detail when the audience needed the headline. She was optimizing for thoroughness when the room was measuring her by clarity. A Suitability gap (invisible to her, visible to everyone watching) that had been shaping perceptions for months without a single person saying it directly.

Second: the “strategic thinking” comment finally got translated into something she could act on. She was bringing solutions to tactical problems without connecting them to business context. She was operating at what the book calls Team altitude, solving the problem in front of her, when the organization needed her thinking at Function altitude, understanding how the problem connected to broader priorities and framing her solutions accordingly. Not a capability gap. An orientation gap. Completely fixable, once named.

Third, and most valuable: her manager paused before saying something he probably wouldn’t have offered in any other format. When things go sideways, you go quiet. I don’t know if you’re frustrated, recalibrating, or checking out. The silence is ambiguous, and ambiguous signals get interpreted negatively here.

That one observation, too nuanced for an annual review, too specific for a “nice job” in a team meeting, was the most useful career intelligence Alicia had received in two years. She hadn’t known she was going quiet. She’d experienced it as composure. Her manager experienced it as disappearance. The gap between those two interpretations had been quietly shaping his read on her readiness without either of them knowing it.

She left the conversation with a specific focus, a clear signal correction, and something harder to quantify: her manager now experienced her as someone who owned her growth. That shift in his perception, from “solid performer waiting to be developed” to “professional actively managing her own trajectory”, changed the prediction he made about her. And changed predictions lead to different decisions.

The Three Questions

The CPP framework runs on three questions, asked in sequence every four to six weeks. They’re not complicated. Their power is in the consistency and the fact that you’re the one asking them.

What’s working that I should double down on?

Not fishing for compliments. Asking your manager to articulate specifically what behaviors, contributions, and patterns are creating genuine value, so you can do more of them intentionally rather than accidentally. Most people don’t know what their manager actually values most about their work. This question produces that answer directly.

Where is there a gap between how I think I’m showing up and how I’m actually landing?

This is the question that surfaces what nobody will say in normal conversation. The communication style that creates friction. The habit that reads differently than intended. The pattern that’s visible to everyone except you. Asking it explicitly, with enough specificity that your manager can answer honestly, is what makes CPP worth the calendar space. Vague feedback is useless. This question creates conditions for specific feedback.

What’s one thing I could focus on in the next four to six weeks that would most change your read on my readiness?

This is the trajectory question. It connects the conversation to the future instead of just the present. It also tells you something important: what your manager is actually using to evaluate readiness. The answer reveals the criteria that will shape the next opportunity decision, criteria you might not have known existed, or might have been underweighting relative to the things you were focusing on.

Three questions. Thirty minutes. Every four to six weeks. That’s the whole system.

Eight Conversations vs. One Review

Here’s the math that makes CPP worth understanding structurally, not just tactically.

If your organization does annual reviews, you get one formal performance conversation per year. If you’re in a progressive organization, maybe two. Even if those conversations are excellent, which, as we’ve established, they usually aren’t, you’re operating on a development cadence of once or twice a year.

CPP, practiced consistently, gives you eight to ten substantive conversations per year. Eight to ten opportunities to course-correct before the correction becomes expensive. Eight to ten chances to close the gap between how you think you’re landing and how you’re actually landing. Eight to ten moments where your manager is directly engaging with your trajectory instead of just your task list.

The compounding effect of that is significant. A signal correction made in week six is six weeks of better behavioral evidence before the next review. A gap identified in month three gets nine months of remediation before March. An insight about what your manager is actually measuring for readiness changes what you focus on for the entire rest of the year.

The person who waits for the annual review is operating on one data point per year. The person running CPP is operating on ten. Over three years, that’s the difference between three development conversations and thirty. The trajectory implications of that math are not subtle.

The Fear That Stops Most People

The most common reason people don’t do this is a version of the same fear: What if my manager thinks I’m being demanding? What if it reads as needy, or ambitious in the wrong way, or high-maintenance?

It’s worth examining that fear directly, because it’s revealing something specific about the compliance mindset we covered earlier in this series. The fear of being seen as demanding for asking to own your own development is the fear of stepping outside the role the system assigned you: wait, perform, be evaluated.

The reality of how it lands in practice is almost universally the opposite of the fear. Managers are not sitting around hoping their reports will stay quiet and wait for March. They are, in almost every case, managing more than they can adequately attend to and quietly hoping someone will make their job easier. The CPP request (structured, self-led, low-maintenance) makes their job easier. It takes development conversations off their plate and puts them on yours. It gives them a format instead of ambiguity. It produces a thirty-minute meeting that requires almost nothing from them except honesty.

Alicia’s manager said yes without hesitating. So did Marcus D.’s supervisor, when he asked a version of the same question. So did Dani’s. The resistance that most people anticipate almost never materializes, because the request itself signals exactly what every manager wants to see: someone who owns their growth instead of waiting for it to be handed to them.

That signal, before a single CPP conversation has even happened, is already changing the prediction.

Starting This Week

One message. It can go in an email, a Slack, a text, or the last two minutes of your next one-on-one:

I’d like to schedule a focused thirty-minute conversation about my development. I’ll prepare and lead, I just need your honest input on three questions.

Schedule it four to six weeks out. Prepare your three questions. Lead the conversation. Schedule the next one before you leave the room.

The first conversation will feel slightly awkward because it’s unfamiliar. By the third, it will be the most useful thirty minutes in your professional calendar. By the fifth, your manager will expect it, rely on it, and have a fundamentally different read on your readiness than they had before you started.

Not because you’ve performed differently. Because you’ve governed your own development differently. And in a world where most people are waiting for the system to develop them, the one who builds their own system doesn’t just outpace the curve.

They change the prediction entirely.

A question before you go: Think about the last time your manager gave you feedback specific enough to actually act on. How long ago was it? How much career-shaping time has passed since then and what would it mean to stop waiting for the next one?

The answer to that question is probably the best argument for sending the message this week. I’d love to hear what comes up when you sit with it in the comments.

One more thing before you go.

Everything in this series (the signal, the three I’s, the disciplines, the traits) is being built into something larger.

Later this year, we’re releasing a significant update to The Ready Set experience. What’s coming is an extension of the AI Ready Set Coach that will meet you exactly where you are, whether you’re two years into your first real role or two levels from the executive suite, and grow with you as you move.

For individual contributors, that means the full Signal Forward framework: the behaviors, the disciplines, the trait development, and guided content built specifically for people who are doing excellent work and trying to make sure it doesn’t stay invisible.

For emerging leaders and managers, it bridges the gap, the moment when your contribution shifts from personal performance to collective performance, and the skills that got you here stop being sufficient for where you’re going.

For experienced leaders, it’s the full Ready Set framework: the ten behaviors, the diagnostic, the coaching, and the development architecture that drives what leadership actually looks like at scale.

One experience. Every level. Built to progress with you.

We’ll have more details as we get closer. If you’re already a paid member, you’ll be among the first to know, and the first to access it.

More Signal Forward coming soon. Stay with us.

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership and talent content and resources to everyone. Subscribe free and get new behavioral-based leader and talent insights every week.

Plus two Ready Set resources to put to work immediately.

Leave a comment

Share The Ready Set

Subscribe now

What we cover:

• Why the 3 is more dangerous than the 1 — and how adequate accumulates silently into a career that stays exactly where it is

• What 2,632 consecutive games actually required — and why the Tuesday afternoon games in September when nobody was watching are the most instructive part of the whole story

• The Warren Buffett connection: what looking for one foot bars to step over has to do with a shortstop who showed up every single day for sixteen years

• Priya, Dev, and Camille: three strong performers, three different signal problems, and why only one of them got the role

• The 1990 season: how Ripken’s worst year got absorbed by his pattern rather than defining it — and what that means for the unrepaired moments you might be carrying

• Why the record-breaking night in 1995 didn’t create the reputation — it revealed it

• Four specific practices for raising your average — and why eliminating the forgettable matters more than adding the exceptional

The question worth asking honestly:

Think about the last week of professional interactions. Not the best one, not the worst — the average one. What was the actual quality of your contribution across those moments? And where, specifically, are the 3’s clustering?

For the full 4.8 framework — including the complete Priya, Dev, and Camille stories and the four practices — check out the article at thereadyset.substack.com

Signal Forward runs alongside The Ready Set — built for individual contributors, specialists, and practitioners whose behavioral patterns determine whether their contribution gets seen, valued, and rewarded.

Subscribe: thereadyset.substack.com

Paid membership for The Ready Set is open. KLIR gives you a personalized behavioral picture of where you actually stand across the ten behaviors we’ve covered. The AI Ready Set Coach helps you build a real development plan around your specific results. It’s not a content upgrade — it’s a genuine development experience.

Learn more: https://ready-set-membership.c2advising.com/

New here? Start with the first article. In People or HR? Pass this along to your team.

Think about the last rideshare you took. Chances are you didn’t think much about it at all. The driver showed up, you got where you were going, nothing went wrong. You probably gave it four stars without really deciding to, it just felt like the right number for a ride that was fine.

Now think about the last rideshare that stuck with you. Maybe the driver knew a shortcut you didn’t. Maybe they handed you a phone charger before you thought to ask. Maybe there was a brief conversation that was actually interesting. You gave that one five stars and felt good about it.

Now think about the 3. The driver who was late. Who took a weird route. Who was just a little off in a way you couldn’t fully articulate but felt the entire ride. You gave it three stars because you didn’t want to be harsh, but you also never requested that driver again. And somewhere in the algorithm, that 3 quietly accumulated with the other 3’s and started pulling the average down.

Here’s what’s interesting about that system: the driver didn’t get fired for the 3. Nobody called them. Nobody gave feedback. The 3 just quietly did its work, interacting with every other score, shaping a pattern that determined which rides they got offered, which routes, which opportunities.

Your career runs on the same math.

The Number Nobody Talks About

Most career advice is organized around two poles: don’t have catastrophic failures, and try to do excellent work. Avoid the 1’s. Chase the 5’s. What almost nobody talks about is the 3, the adequate interaction, the forgettable meeting, the conversation that was perfectly fine and completely without value.

The 3 is the real threat. Not because it’s bad. Because it’s invisible.

A 1 (a genuine failure, a serious mistake, a significant lapse in judgment) is at least visible. It creates feedback. It creates accountability. It creates an opportunity to repair, which, as we covered in the last article, can itself become a positive data point when handled well. The 1 is painful but recoverable.

The 3 accumulates silently. Nobody mentions it. Nobody flags it. You leave the meeting and assume it went fine because nothing went wrong. But fine is not memorable. Fine doesn’t build anything. Fine, stacked on top of fine, on top of fine, produces the kind of career that stays in place. Technically solid, entirely stalled.

Here’s the math that makes this concrete: if you’re operating at a 4.8 average across your significant professional interactions, you have almost no room for 3’s. A 3 doesn’t feel like a failure. It is one. Not a dramatic failure, a quiet one. The missed opportunity to create value when value was available. The meeting where you showed up but didn’t contribute. The conversation where you were competent but not present. The interaction that nobody will remember, including you.

The enemy of a 4.8 career isn’t the catastrophic mistake. It’s the ordinary accumulation of moments that didn’t matter.

What 4.8 Actually Means

Let’s be precise about this, because 4.8 sounds like a specific number someone invented to make a point, and it is, but the logic behind it is worth understanding.

A 4.0 average is what most people who are trying would land. It means the majority of your interactions are strong and some are merely adequate. Nobody has a reason to complain about you. Nobody has a particularly compelling reason to advocate for you either. A 4.0 keeps you in good standing and out of trouble. It also keeps you right where you are.

A 4.8 means something fundamentally different. It means the vast majority of your professional touchpoints (the meetings, the conversations, the deliverables, the moments when someone needed something from you) created genuine value, built trust, or left the other person more capable than before. It means that when you fall short, which you will, you repair so quickly and genuinely that the repair itself becomes a positive data point rather than a negative one.

The rideshare analogy holds: a 4.8-rated driver isn’t someone who never has a difficult ride. They’re someone who handles difficulty so well that it barely registers as a negative. Their baseline is so consistently excellent that the rare miss gets absorbed by the pattern rather than defining it.

That’s the standard. And it’s achievable, not because it requires perfection, but because it requires discipline, repair, and the deliberate governance of your own signal. Those are learnable. Perfection isn’t.

The Prediction Engine

Here’s what makes 4.8 more than a performance target: it’s a prediction engine.

Your behavior is predictive. That’s the foundational premise of everything in this series. When you sustain a 4.8 standard across your significant interactions, you’re building a behavioral data set in the minds of everyone who works with you, a data set that predicts, with high accuracy, how you’ll perform in any future context.

That prediction is what opens doors.

A VP considering you for a stretch assignment isn’t reviewing your resume when she makes the decision. She’s reviewing the accumulated evidence of how you show up. The meeting where you came prepared when nobody else did. The conversation where you stayed steady when the news was bad. The project where you delivered cleanly and made the people around you better in the process. All of it has been accumulating into a pattern. That pattern predicts an experience. And the question she’s answering, without consciously framing it this way, is: does the behavioral evidence I’ve accumulated on this person predict a 4.8 experience if I give them more?

If the answer is yes, the opportunity moves toward you. If the answer is no, or even maybe, it goes to someone whose pattern is cleaner.

You don’t have to be in the room for this conversation to happen. The evidence you’ve been creating is already there, working for you or against you, in the minds of everyone who has worked alongside you.

Three People, Three Patterns

Priya was a product analyst who worked hard and consistently met her commitments. She also had a specific habit that she wasn’t aware of: in meetings where she didn’t have strong opinions, she went quiet. Not visibly disengaged, just absent. Nodding. Taking notes. Present in body, absent in contribution.

For any individual meeting, this was unremarkable. Across eighteen months, it created a pattern: Priya is reliable but you won’t get much from her in a room. When a cross-functional working group was being assembled for a high-visibility initiative, her manager thought of three other people before her. Not because Priya was inadequate — because her signal in those moments had been 3’s, and 3’s don’t surface names when opportunities are being allocated.

Dev was a logistics coordinator with the opposite problem. His individual contributions were strong. He was sharp, prepared, and frequently the most useful person in any given conversation. But he had a 1 that he’d never repaired. Six months prior, he’d clashed publicly with a peer in a cross-functional meeting, gotten visibly frustrated, and said something he probably didn’t mean in the way it landed. He’d assumed it had blown over. It hadn’t. That single unrepaired moment was sitting in the pattern alongside his strong work, pulling the read on him toward unpredictable.

Two strong performers. Two different signal problems. Same result: careers not moving.

Then there was Camille. A project coordinator at a healthcare system who wasn’t the most technically skilled person on her team and knew it. What Camille had was consistency. She showed up prepared. She followed through without being reminded. When something went wrong, she addressed it quickly and didn’t make it dramatic. She asked questions in meetings that moved things forward. She left every interaction slightly cleaner than she found it.

Nobody would have called Camille the star of the team. But when a project management role opened with significant cross-functional responsibility, her manager didn’t hesitate. Because the accumulated evidence on Camille predicted one thing with high reliability: working with her is a 4.8 experience. Every time.

Camille got the role. Priya and Dev got feedback they couldn’t fully interpret because nobody told them about the pattern.

Raising Your Average

If you’re reading this and recognizing some version of Priya’s quiet 3’s or Dev’s unrepaired 1, the path forward isn’t complicated. It’s just deliberate.

Find your 3 patterns. The 3’s you’re producing aren’t random, they’re probably clustered around specific situations. Meetings where the agenda isn’t yours. Conversations with people you find difficult. Interactions at the end of the day when your energy is low. Find the pattern and you’ve found the intervention point.

Raise the floor before chasing the ceiling. Most people try to add more 5’s, more standout moments, more visible wins. That’s not wrong, but it’s the wrong priority if you have consistent 3’s pulling your average down. Eliminating the forgettable matters more than adding the exceptional.

Repair the 1’s you’re carrying. If there’s an unrepaired moment sitting in your pattern (a conflict that got weird and was never addressed, a commitment you missed and moved past without acknowledgment), it’s still there. The 24-hour rule applies to the spirit of the repair even if the moment was months ago. A genuine, specific acknowledgment still does more than continued silence.

Treat every interaction as a data point. Not in a paranoid way, in an intentional one. Before a meeting, ask: what would a 4.8 contribution look like here? After a meeting, ask: what did I actually produce in that room? That thirty seconds of reflection, practiced consistently, changes patterns faster than almost any other single discipline.

The Quiet Compounding

Here’s what makes the 4.8 standard worth the effort: it compounds.

The individual interactions don’t feel consequential in the moment. One prepared meeting doesn’t make a career. One steady response under pressure doesn’t open a door. One clean delivery doesn’t change a trajectory.

But the pattern does. The accumulation does. Thirty days of 4.8 interactions builds something noticeable. Ninety days builds something that travels. A year builds a reputation that precedes you into rooms you’ve never entered, answers questions about you that nobody asks you directly, and predicts opportunities toward you before you know they exist.

The math isn’t glamorous. It doesn’t produce the kind of career highlight reel that gets written about. It produces something more valuable: a signal so consistent that the people in a position to change your trajectory already know the answer before they ask the question.

That’s what 4.8 actually is. Not a score. Not a rating system. A prediction about what it’s like to work with you and what it would be like to give you more.

A question worth sitting with: Think about the last week of professional interactions. Not the best one, not the worst, the average one. What was the actual quality of your contribution across those moments? And where, specifically, are the 3’s clustering?

The answer to that second question is probably the most actionable thing in this entire article. I’d love to hear what you find in the comments.

One more thing before you go.

Everything in this series (the signal, the three I’s, the disciplines, the traits) is being built into something larger.

Later this year, we’re releasing a significant update to The Ready Set experience. What’s coming is an extension of the AI Ready Set Coach that will meet you exactly where you are, whether you’re two years into your first real role or two levels from the executive suite, and grow with you as you move.

For individual contributors, that means the full Signal Forward framework: the behaviors, the disciplines, the trait development, and guided content built specifically for people who are doing excellent work and trying to make sure it doesn’t stay invisible.

For emerging leaders and managers, it bridges the gap, the moment when your contribution shifts from personal performance to collective performance, and the skills that got you here stop being sufficient for where you’re going.

For experienced leaders, it’s the full Ready Set framework: the ten behaviors, the diagnostic, the coaching, and the development architecture that drives what leadership actually looks like at scale.

One experience. Every level. Built to progress with you.

We’ll have more details as we get closer. If you’re already a paid member, you’ll be among the first to know, and the first to access it.

More Signal Forward coming soon. Stay with us.

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership and talent content and resources to everyone. Subscribe free and get new behavioral-based leader and talent insights every week.

Plus two Ready Set resources to put to work immediately.

Leave a comment

Share The Ready Set

Subscribe now

What we cover:

• The Silence Dogood letters: how a sixteen year old apprentice who was told he couldn’t write for the paper found a way to contribute at the level he believed he was capable of — without permission, without credit, and without anyone knowing it was him

• The Sam Walton connection: what a future Walmart founder driving hours to visit competitor stores and keeping obsessive notebooks has in common with Franklin rewriting essays from memory in a print shop

• The Junto: why the small Friday night club Franklin organized at twenty-one — built around sharing what you know with people who need it — ran for thirty-eight years and produced ideas that shaped a nation

• Franklin’s Moral Perfection Project: the daily notebook, the thirteen virtues, the grid — and why stopping every day to ask whether your effort actually moved something forward is the hardest and most important of the three disciplines

• The Library Company of Philadelphia: what happens when Influence scales beyond its original radius — and why the mechanism is identical whether you’re building the first subscription library in America or spending thirty minutes with a dispatch team

• Why trajectory is built in the ordinary moments — not the dramatic ones — and what Franklin’s career looks like when you trace it all the way back to where it actually started

Three questions worth asking every single day:

For Initiative: What would I do today if nobody told me what to do?

For Influence: Who outside my immediate team would genuinely benefit from knowing what I know?

For Impact: What did my effort today actually produce?

For the full Three I’s framework — including the complete Dani and Marcus D. stories and the practical ninety-day breakdown — check out the article that dropped this week at thereadyset.substack.com

Signal Forward runs alongside The Ready Set — built for individual contributors, specialists, and practitioners whose behavioral patterns determine whether their contribution gets seen, valued, and rewarded.

Subscribe: thereadyset.substack.com

Paid membership for The Ready Set is open. KLIR gives you a personalized behavioral picture of where you actually stand across the ten behaviors we’ve covered. The AI Ready Set Coach helps you build a real development plan around your specific results. It’s not a content upgrade — it’s a genuine development experience.

Learn more: ready-set-membership.c2advising.com/

Signal Forward is a series inside The Ready Set, same publication, different altitude. The Ready Set is for leaders. Signal Forward is for everyone else: the individual contributors, specialists, and practitioners whose behavioral patterns determine whether their contribution gets seen, valued, and rewarded, regardless of title or tenure.

New here? Start with the first article. In People or HR? Pass this along to your team.

Dani had been a supply chain coordinator for two years. Solid performer. No complaints. Reliable enough that her manager stopped thinking about her, which is either a compliment or a quiet catastrophe depending on how you look at it.

Marcus D. was a field service technician at a utilities company. Three years of excellent service records. The kind of technician dispatchers were relieved to see on a job because they knew it would get done right. Also invisible. Also going nowhere.

Neither of them was failing. That was almost the problem. Failing would have at least produced feedback. What they were experiencing was quieter and harder to fix: the specific invisibility of someone who meets expectations so consistently that they stop generating any signal at all.

Both decided to run an experiment. Same ninety days. Same roles. No promotion, no title change, no organizational reshuffling. Just a deliberate shift in how they oriented their contribution.

By the end of it, Dani’s manager was calling her strategic. Marcus D.’s supervisor was assigning him the complex jobs, the ones that required coordinating multiple crews, and the rest of the crew had started coming to him for guidance before going to their supervisor. Neither outcome was announced. Neither was orchestrated. Both were earned through a pattern that compounded quietly over three months.

The pattern has three parts.

Part One: Initiative (Days 1–30)

The first question Dani asked her manager was not about her performance review, her development plan, or her career path. It was simpler and more disarming than any of those: What does exceptional look like in this role? Not good, what would have to be true for you to consider me indispensable?

Her manager paused. Then said something that reoriented two years of effort in a single sentence: If you could anticipate problems before they reached me instead of reporting them after they happened, that would change everything.

Dani had been measuring herself by how well she responded to problems. Her manager had been measuring by whether she prevented them. Two years, same job, completely different scorecards, and nobody had ever said so out loud.

Marcus D. asked his crew supervisor a version of the same question before a Monday shift: If I wanted to be considered for the senior tech role, what would you need to see from me that you’re not seeing now?

His supervisor paused too. Then said: Honestly? I need you to stop being the guy who fixes the problem and start being the guy who makes sure the next crew doesn’t run into it. You’re the best technician I’ve got. But the senior role is about making the whole team better, not just being the best individual.

Both of them got the same message, translated for their world: the next level is not a bigger version of your current job. It’s a different kind of contribution entirely.

So both of them made the same three changes. They stopped letting the task list define their day and started asking what the most important thing was that nobody had told them to do. They defined personal goals that reached beyond their job descriptions. And they started arriving at every meeting or shift huddle with one prepared contribution nobody had requested.

Dani’s initiative showed up as providing updates before they were asked for, surfacing a supplier risk on Tuesday instead of waiting for someone to notice it on Friday. Marcus D.’s showed up as a one-page troubleshooting guide he posted in the break room for the next shift, documenting the three recurring issues that sent crews on unnecessary calls.

Different environments. Same reflex: begin without being told.

Initiative is not about working harder. Most people who are invisible are already working hard. It’s about changing your starting point, from what has been assigned to me to what actually needs to happen. That shift, practiced consistently, is the first thing people notice. Not because it’s dramatic, but because it’s rare.

Part Two: Influence (Days 30–60)

By the end of the first month, both of them had changed their starting point. The second month was about expanding their radius.

Dani noticed that her logistics partner was routinely blindsided by priority changes, the kind she could see coming from her position in the supply chain. She started sending a five-minute weekly update. Entirely outside her job description. It made the system work better, so she did it.

Then she did something less obvious: she reached out to a peer in finance and asked how her supply chain metrics translated into the VP’s monthly cost report. For the first time in two years, she understood what her numbers actually meant to the people above her. Not in a political sense, in a practical one. She could now see the downstream effect of her work in a language the organization measured itself by.

Marcus D. noticed that the customer service team was routinely dispatching technicians for problems that a better diagnostic question could have resolved over the phone. He asked his supervisor if he could spend thirty minutes with the dispatch team walking them through the three most common false alarms. His supervisor said yes without hesitating.

That thirty-minute session reduced unnecessary dispatches by fifteen percent in the first month. Marcus D. hadn’t done anything outside his technical expertise. He’d simply shared what he knew with people who needed it. The dispatch supervisor mentioned him by name in the monthly operations meeting. The operations manager made a mental note: this technician thinks beyond his truck.

Influence, at the individual contributor level, isn’t about persuasion or politics or learning how to work a room. It’s simpler than that. It’s expanding your contribution beyond the boundaries of your defined scope by connecting what you know to people who need it. Most people know things that would genuinely help someone else on a different team, in a different function, further up or down the chain. They just don’t share it, because sharing it wasn’t explicitly part of the job.

The people who share it anyway, without being asked, without expectation, without making a production of it, are the ones who start generating signal in rooms they’ve never been in.

Part Three: Impact (Days 60–90)

The third month was about measurement. Not the organization’s measurement — their own.

Dani started a daily three-minute practice: did what I spent time on today actually move something forward, or did it just fill the day? The question was uncomfortable at first. She found that roughly forty percent of her activity was reactive busywork, necessary, maybe, but not the kind of work her manager had described as the difference between good and indispensable. She started reclaiming that time. Not dramatically. Just incrementally, day by day, redirecting effort toward the anticipatory work that actually created value.

By day ninety, something had compounded. Her manager called her strategic. Her logistics partner told a VP that coordination quality had improved. Her finance peer mentioned her name for a cost initiative. None of it was orchestrated. All of it was earned through consistency, through the accumulated weight of a hundred small contributions that pointed in the same direction.

Marcus D. started tracking a single question for every job he completed: did I leave the next technician in a better position than I found it? That meant cleaner documentation. Clearer notes in the work order system. Occasionally a quick text to the next shift — Unit 4 on Elm Street, the access panel is behind the water heater, not where the diagram shows. Save you twenty minutes. Small things. Consistently done.

By day ninety, his supervisor had started assigning him the complex jobs, the ones requiring coordination across multiple crews. The team had started coming to him before going to the supervisor. Nobody had announced this shift. The behavioral evidence had produced it on its own.

Why This Works

Initiative changes your starting point, you stop waiting and start beginning. Influence expands your radius, you connect what you know to people who need it. Impact changes your measurement, you stop counting tasks and start evaluating value created.

Three questions, asked daily, drive all of it:

For Initiative: What would I do today if nobody told me what to do?

For Influence: Who outside my immediate team would benefit from knowing what I know?

For Impact: What did my effort today actually produce?

Those three questions change your contribution patterns within thirty days. They change how people talk about you within sixty. They open trajectory conversations within ninety.

Here’s what’s important to understand about why it works: none of it requires permission. None of it depends on the quality of leadership above you. None of it requires a program, a platform, or a sponsor. Dani proved it from a desk in a supply chain office. Marcus D. proved it from a truck on a service route. The principle doesn’t care where you work.

What it does require is consistency. Not intensity, consistency. The difference between a signal and noise is repetition. A single instance of initiative is interesting. Thirty days of it is a pattern. Ninety days is a reputation.

And reputation, once formed from behavioral evidence, is extraordinarily difficult to undo, in either direction. The question is which direction you’re building in.

Here’s the question worth sitting with this week: Of the three (Initiative, Influence, Impact) which one are you strongest in? And which one, if you’re honest, are you almost entirely skipping?

Most people are strong in one, decent in another, and quietly avoiding the third. The one you’re avoiding is almost always the one that would move things fastest. I’d love to hear which one it is in the comments.

One more thing before you go.

Everything in this series (the signal, the three I’s, the disciplines, the traits) is being built into something larger.

Later this year, we’re releasing a significant update to The Ready Set experience. What’s coming is an extension of the AI Ready Set Coach that will meet you exactly where you are, whether you’re two years into your first real role or two levels from the executive suite, and grow with you as you move.

For individual contributors, that means the full Signal Forward framework: the behaviors, the disciplines, the trait development, and guided content built specifically for people who are doing excellent work and trying to make sure it doesn’t stay invisible.

For emerging leaders and managers, it bridges the gap, the moment when your contribution shifts from personal performance to collective performance, and the skills that got you here stop being sufficient for where you’re going.

For experienced leaders, it’s the full Ready Set framework: the ten behaviors, the diagnostic, the coaching, and the development architecture that drives what leadership actually looks like at scale.

One experience. Every level. Built to progress with you.

We’ll have more details as we get closer. If you’re already a paid member, you’ll be among the first to know, and the first to access it.

More Signal Forward coming soon. Stay with us.

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership and talent content and resources to everyone. Subscribe free and get new behavioral-based leader and talent insights every week.

Plus two Ready Set resources to put to work immediately.

Subscribe now

Leave a comment

Share The Ready Set

What we cover:

• Why the stakes of reaction are actually higher for individual contributors than for executives — and what the authority cushion you don’t have means for every pressure moment you’re in

• Ashe’s early career: the deliberate decision he made navigating a sport that actively didn’t want him — and why he concluded that reaction was a trap before anyone was writing about his tennis

• The Marcus Aurelius connection: what the most powerful person in the Western world and a Black tennis player in 1950s Virginia figured out about governing the gap between stimulus and response — from completely opposite directions

• The 1969 South Africa visa denial: how Ashe turned a public insult into a four-year strategic campaign — and why the difference between a reaction and a response is often the difference between a moment and a movement

• Alec’s story: seven seconds in a cross-functional meeting, fourteen months of silence, and the role that went to someone with a thinner resume and a steadier signal

• The R-R-R sequence — Recognize, Regulate, Restore — and what each move actually looks like in a real pressure moment

• The neuroscience of the labeling effect: why naming what you’re feeling internally in the moment actually decreases the physiological response — and buys you the two or three seconds that change everything

• The HIV press conference: the R-R-R sequence executed under the most extreme personal pressure imaginable — and what Ashe did with less than a year

The question worth sitting with:

Think about the last time you reacted when you meant to respond. What triggered it. What came out. And — if you’re honest — what signal did the people in the room take away?

For the full framework — the complete R-R-R breakdown, the 24-hour repair rule, and the practical guidance — check out the article that dropped this week at thereadyset.substack.com

Signal Forward runs alongside The Ready Set — built for individual contributors, specialists, and practitioners whose behavioral patterns determine whether their contribution gets seen, valued, and rewarded.

Subscribe: thereadyset.substack.com

Paid membership for The Ready Set is open. KLIR gives you a personalized behavioral picture of where you actually stand across the ten behaviors we’ve covered. The AI Ready Set Coach helps you build a real development plan around your specific results. It’s not a content upgrade — it’s a genuine development experience.

Learn more: The Ready Set Experience

What we cover:

• Why Jordan’s eligibility was never the question — and what six years of playoff exits with the best player in the league reveals about the layer underneath raw talent

• The Ed Catmull and Pixar connection: the difference between a brilliant jerk and a brilliant collaborator — and why the single most talented person in a room can actually decrease collective output

• What Phil Jackson actually did when he installed the triangle offense — and why it was a behavioral requirement delivered through a tactical system, not a basketball instruction

• What changed and what didn’t: why Jordan’s standards never lowered — and why redirecting them toward his teammates instead of at them changed everything

• The research on how the highest performer in any group sets the ceiling for what everyone else believes is possible

• Ty and Carmen: two high performers asking the same question in completely different industries — and the answer nobody is telling them directly

• The most accurate picture you have of your own suitability — and where to find it

The question worth actually sitting with:

Think about the last time you received genuine criticism. Not the formal review version. The real version. What happened in your body when you heard it? What did you want to say? What did you actually say? That response is the most accurate picture you have of where your suitability actually stands.

For the full framework — the three layers, the Ty and Carmen story, and where to start if you recognize yourself in any of this — check out the article at thereadyset.substack.com

Signal Forward runs alongside The Ready Set — built for individual contributors, specialists, and practitioners whose behavioral patterns determine whether their contribution gets seen, valued, and rewarded.

Subscribe: thereadyset.substack.com

Paid membership for The Ready Set is open. KLIR gives you a personalized behavioral picture of where you actually stand across the ten behaviors we’ve covered. The AI Ready Set Coach helps you build a real development plan around your specific results. It’s not a content upgrade — it’s a genuine development experience.

Learn more: The Ready Set Experience

New here? Start with the first article. In People or HR? Pass this along to your team.

Alec was having a good career.

Project manager. Strong track record. Stakeholders trusted his timelines. Well-liked, competent, the kind of person who gets described in performance reviews as a “consistent contributor”, which sounds underwhelming but is actually harder to achieve than most people realize.

On a Thursday afternoon, in a cross-functional status meeting, a senior stakeholder publicly challenged the timeline Alec had committed to. The challenge was legitimate and based on new information Alec hadn’t yet received. But it didn’t feel legitimate. It felt like an ambush in front of fifteen people who were all now watching to see what he’d do.

Alec felt the heat rise. His jaw tightened.

What happened next took seven seconds and cost him fourteen months.

He fired back. His tone sharp and words defensive. Body language broadcasting exactly what his nervous system was feeling: threat. He challenged the stakeholder’s data. Questioned the timing of the critique. Made it personal when the situation was entirely professional. The room went quiet. And not the productive kind, where people are absorbing something important, but the uncomfortable kind, where people are watching someone damage themselves in real time.

The meeting moved on. Alec recovered his composure within minutes. He probably assumed it had blown over.

It hadn’t.

The following week, his name came up in a leadership conversation about a senior program manager role. The feedback was brief and fatal: Strong executor, but I’m not sure he can handle the pressure at the next level. Did you see the status meeting? The role went to someone with a thinner resume and a steadier signal.

Alec didn’t learn any of this until fourteen months later, when a colleague mentioned it in passing. Fourteen months of wondering why the call never came. Fourteen months of attributing the silence to politics, timing, etc. You know, the usual explanations people reach for when the real explanation is too uncomfortable to see clearly.

The cause was seven seconds of ungoverned reaction in a room full of people who were paying closer attention than he realized.

The Biology You Are Fighting

Before we get into the fix, it’s worth understanding what you’re actually up against. Because the problem isn’t Alec’s character. It isn’t a flaw in his professionalism. It’s his hardware, and it’s yours too.

When pressure arrives (a public critique, a missed deadline, a sudden priority change, a conflict with a peer, a question that feels like an accusation) your nervous system does what it has been doing for thousands of years. It prepares for threat. Stress hormones release. Cognitive bandwidth narrows. The prefrontal cortex, the part of your brain responsible for nuanced judgment, perspective-taking, and thinking through consequences, goes partially offline. Your emotional system moves into the driver’s seat. And it is a terrible driver, interpreting ambiguous signals as threatening, defaulting to defense, prioritizing speed over accuracy.

None of this is a character flaw. It’s the architecture. And the question isn’t whether it activates, it will. The question is whether you have a system for governing what happens in the gap between activation and response.

Here’s where it gets specific to individual contributors: executives who react poorly have something you don’t, authority. An executive who snaps in a meeting may damage trust, but they still hold power. The room adjusts around them and recovery is assumed.

When you react, there’s no cushion. There’s only the moment and the observation. A sharp response to a peer becomes a reputation. A defensive answer to a leader becomes a judgment about your maturity. Visible frustration during a priority change becomes evidence about your adaptability. The stakes of reaction at the individual contributor level aren’t organizational, they’re personal, directly and immediately linked to how people experience you and what opportunities follow.

This is why the ability to respond instead of react is arguably more important for you than for the executives above you. Less room for recovery. Fewer formal channels for repair. A reputation forming in real time with every observed interaction.

The R-R-R Sequence

There’s a three-move discipline for governing these moments. Not eliminating pressure, that’s not available. Not suppressing the reaction, that’s not sustainable. Just governing what happens next.

Recognize. Regulate. Restore.

Recognize: Name the moment before it names you.

Before you respond to anything that creates heat, name it internally. This is a moment that will shape how people experience me. That’s it. Not a lengthy internal monologue. One sentence, directed inward, before anything comes out.

The recognition itself changes the response. It reactivates the prefrontal cortex that pressure partially took offline. It shifts you from automatic to intentional. Three seconds, maybe less.

The specific skill here is learning to distinguish between what is happening and what it feels like is happening. Your leader publicly redirects your approach in a meeting. What is happening: feedback on a work product. What it feels like: a personal attack in front of peers. The gap between those two interpretations is where reaction lives. Recognition closes the gap before reaction can fill it.

A useful practice is in any moment of pressure, ask one question internally before speaking externally: What is actually happening here, and what signal do I want to send? That pause is the difference between a response that builds your reputation and a reaction that quietly dismantles it.

Regulate: Lower the intensity, raise the clarity.

Not just “by about ten percent”. By exactly ten percent. Slightly slower pace. Slightly more deliberate word choice. Slightly more space before responding. That specific, small adjustment changes how the room reads you. Not less engaged, more governable. Not less passionate, more trustworthy.

The discipline here is separating emotional processing from professional communication. You can feel frustrated and respond professionally. You can feel blindsided and ask a clarifying question. You can feel genuinely disrespected and still maintain your standard. The feelings are real. The discipline isn’t suppressing them, it’s sequencing them. Feel now. Process later. Respond well in the moment.

One physical interruption helps more than most people expect: a single deliberate breath, a shift in posture, picking up a pen. The physical break interrupts the neurobiological cascade. It buys two or three seconds. Two or three seconds, used well, is enough.

Restore: Redirect to what actually matters.

Frame what is true. Name what matters most. Clarify what you will do next. In that order, every time: truth first, then priority, then action.

Under pressure, the most common failure for individual contributors is defending position instead of advancing the work. Alec did this. He defended his timeline instead of addressing the new information that had changed the situation. He protected his ego when the moment needed him to solve a problem.

Restoration sounds like this: I hear the concern. Here’s what I understand the priority to be. Here’s what I’ll do next. That sequence, delivered calmly under genuine pressure, sends a signal worth more than any technical contribution in the same meeting. It says: this person can absorb difficulty, maintain clarity, and move forward. Repeated across dozens of pressure moments, it becomes the behavioral evidence that opens every door that matters.

The 24-Hour Repair Rule

Nobody responds perfectly every time. Some reactions will happen, the heat arrives faster than the recognition, the moment passes before the regulation kicks in, and something comes out that shouldn’t have.

The discipline isn’t avoiding all reactions. It’s repairing the ones that get through within 24 hours, before the signal they created has time to harden into a reputation.

Unrepaired reactions don’t stay isolated. They become data points. A sharp response to a colleague that goes unaddressed teaches two things to everyone who witnessed it: the sharpness is your default, and the colleague’s experience in that moment wasn’t important enough to acknowledge. Neither lesson was intended. Both will be acted on.

Repair within 24 hours teaches the opposite. That you hold yourself accountable to your impact, not just your intent. That mistakes get acknowledged rather than rationalized. That the experience of working with you actually matters to you.

Repair sounds like this: I want to go back to yesterday’s conversation. I was sharper than the situation warranted, and that was about my frustration, not about you or the work. I value this, and I want to make sure my reaction didn’t cost us trust. That statement takes ninety seconds to deliver and is worth more than months of strong execution in rebuilding what a single reaction can erode.

What This Actually Produces

Here’s what’s counterintuitive about this discipline: the people who benefit most from it rarely look like they’re doing anything remarkable in the moment.

They just don’t react when everyone expects them to. They stay level when the room gets tense. They ask a clarifying question when the instinct is to defend. They absorb a public redirect without matching the energy. And in a room full of people who are watching , always watching, even when they look like they’re staring at a laptop, that steadiness becomes the most reliable signal of readiness for more.

Alec got his next opportunity eventually. But the fourteen months he lost to one ungoverned Thursday afternoon are gone. The role went to someone steadier. Not more talented. Not more experienced. Steadier.

That’s what’s available when you build this discipline. Not perfection under pressure, nobody has that. Just a system that governs the moments that define you before they define you in ways you didn’t intend.

Think about the last time you reacted when you meant to respond. What triggered it, what came out, and, if you’re honest, what signal did the people in the room take away? I’d love to hear what you’re working on in the comments.

One more thing before you go.

Everything in this series, the signal, the three I’s, the disciplines, the traits, is being built into something larger.

Later this year, we’re releasing a significant update to The Ready Set experience. What’s coming is an extension of the AI Ready Set Coach that will meet you exactly where you are, whether you’re two years into your first real role or two levels from the executive suite, and grow with you as you move.

For individual contributors, that means the full Signal Forward framework: the behaviors, the disciplines, the trait development, and guided content built specifically for people who are doing excellent work and trying to make sure it doesn’t stay invisible.

For emerging leaders and managers, it bridges the gap. The moment when your contribution shifts from personal performance to collective performance, and the skills that got you here stop being sufficient for where you’re going.

For experienced leaders, it’s the full Ready Set framework: the ten behaviors, the diagnostic, the coaching, and the development architecture that drives what leadership actually looks like at scale.

One experience. Every level. Built to progress with you.

We’ll have more details as we get closer. If you’re already a paid member, you’ll be among the first to know, and the first to access it.

More Signal Forward coming soon. Stay with us.

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership and talent content and resources to everyone. Subscribe free and get new behavioral-based leader and talent insights every week.

Plus two Ready Set resources to put to work immediately.

Subscribe now

Leave a comment

Share The Ready Set

What we cover:

• The early speeches: why Douglass’s raw, first-person abolitionist delivery worked in converted rooms and actively closed doors in the rooms he actually needed to move

• The split with William Lloyd Garrison — and why reading the political system differently than his mentor cost him his most important relationship and ultimately proved correct

• The 4th of July speech of 1852: how Douglass used the room’s own occasion, language, and mythology to deliver an indictment the room couldn’t dismiss or deflect — and what that reveals about reading organizational systems at the highest level

• Tomás and Elena: two people in completely different industries hitting the exact same invisible wall — and what the colleague translations they both received reveal about the gap between official systems and real ones

• The C.A.R.E. framework — Clarity, Alignment, Resources, Enablement — four questions that change how you see any organization you operate in

• Why the gap between how you’re delivering your contribution and what the system is built to receive is almost always the ceiling — not the organization itself

The question worth sitting with this week:

Think about the last good idea you had that went nowhere. Was it a bad idea — or was a good idea that arrived in a language the system wasn’t built to hear? Those are completely different problems with completely different solutions.

For the full framework — including the C.A.R.E. breakdown, the complete Tomás and Elena stories, and the practical questions — check out the article that dropped this week at thereadyset.substack.com

Signal Forward runs alongside The Ready Set — built for individual contributors, specialists, and practitioners whose behavioral patterns determine whether their contribution gets seen, valued, and rewarded.

Subscribe: thereadyset.substack.com

Paid membership for The Ready Set is open. KLIR gives you a personalized behavioral picture of where you actually stand across the ten behaviors we’ve covered. The AI Ready Set Coach helps you build a real development plan around your specific results. It’s not a content upgrade — it’s a genuine development experience.

Learn more: ready-set-membership.c2advising.com

New here? Start with the first article. In People or HR? Pass this along to your team.

Tomás and Elena started their new jobs the same week. Different industries, different cities, different job descriptions. But somewhere around week three, they both walked into the same invisible wall.

The place they worked was not the place they’d been told about.

The Wall

Tomás was a new warehouse team lead at a distribution center. Safety posters on every surface. A handbook with a full section on reporting hazards without fear of retaliation. A safety briefing at the top of every shift. The message was consistent and loud: this organization takes safety seriously.

So when Tomás noticed the loading dock team stacking pallets in a way that would eventually put a forklift operator in a bad situation, he did what any reasonable person would do. He raised it at the shift meeting.

His supervisor nodded. Good catch, we’ll look at it.

Nothing happened.

He raised it again the following week. Same nod. Same nothing.

Third week, a senior team member pulled him aside after the meeting. Quietly. The way people do when they’re about to say something the room won’t say out loud. Look, they do care about safety. But that dock layout was set up by the ops director. It’s not moving based on a new lead’s suggestion. You want to fix it? Put numbers to it. Show them what it costs in throughput. That’s the language that actually moves things here.

Tomás had been operating in the official system, the one on the posters. The real system ran on a completely different currency.

Elena’s wall looked different but was made of the same material.

She was a project coordinator at a healthcare company with a stated culture of open communication. Town halls, accessible leaders, feedback actively encouraged. Our door is always open. In her second month, she spotted something genuinely worth fixing: patient intake data being entered inconsistently across three clinics, creating downstream chaos for the billing team. She had the data. She had the solution. She brought it to her manager.

Her manager loved it. Told her to take it to the cross-clinic meeting.

She did. The coordinators from the other clinics listened politely, then explained, each in turn, why the solution wouldn’t quite work for their site. Different workflow here. Different constraint there. The meeting ended with a collective nod toward “continuing the conversation”, which is organizational language for this is going nowhere.

Elena was baffled. The problem was obvious. The fix was straightforward. What was happening?

A colleague who’d been there five years gave her the translation: The open door is real. People do listen. But this organization decides by consensus, not directive. You walked in with your solution. What they needed was to feel like they helped build it. Go to each of them individually first. Learn their workflow. Come back with something that has their fingerprints on it. The meeting would have gone completely differently.

Elena’s idea wasn’t wrong. Her read of the environment was.

The Invisible Operating System

Every organization has one. Not a secret one, nobody designed it deliberately and locked it in a drawer somewhere. It’s emergent. It grows over time from accumulated decisions, unwritten norms, and behavioral patterns until it becomes the actual logic the place runs on. The official version lives in the handbook. The real version lives in how things actually get done.

Most individual contributors never clearly see it. They operate in it, get frustrated by it, occasionally get flattened by it, but rarely stop to study it the way you’d study anything else you needed to navigate well.

And that’s expensive. Not in any dramatic way, your career doesn’t crater overnight because you misread the system. It just quietly limits you. Good ideas go nowhere. Concerns get acknowledged and ignored. You start to wonder if the organization is broken, or leadership is checked out, or your work simply isn’t valued.

Sometimes that’s accurate. But more often, the idea was fine and the delivery was wrong for the environment. Those are completely different problems with completely different solutions.

Four Questions That Change How You See the Place You Work

There’s a simple framework for reading any organizational system, regardless of what industry you’re in or what kind of work you do. Four questions. We call it C.A.R.E.: Clarity, Alignment, Resources, Enablement.

The name matters. The professionals who ask these questions consistently are the ones who signal they care about more than their own corner of the work. That’s not a small thing. It’s visible. And visible caring, demonstrated through behavior rather than announced, is a signal all by itself.

Clarity: Does everyone actually know what matters most?

Not what the stated values say. Not what leadership emphasized in the last all-hands. What actually wins when priorities compete for the same resources, the same attention, the same decision.

Tomás ran a quick test early on. He asked three people on his team what the facility’s top priority was. Safety. Throughput. Customer satisfaction. All three answers were correct. None of them told him which one would win in a fight. That gap, between stated priorities and operational ones, is where confusion lives and where effort gets wasted.

It’s also where the individual contributor who can read it becomes genuinely valuable. Not by exposing the gap, but by navigating it intelligently. By knowing which language moves things.

Alignment: Are people actually working toward the same outcome?

Elena’s three clinics operated under the same organizational umbrella with different workflows, different norms, and different working definitions of what good looked like. Nobody had declared a misalignment. It had simply grown, quietly, over time. Alignment was assumed because it was never tested.

Understanding that gap told Elena something specific: she needed to build cross-clinic relationships before proposing cross-clinic solutions. Go in with a solution first, and you’re asking people to accept someone else’s answer to a problem they haven’t finished defining. Go in with curiosity first, learn their world, earn their trust, incorporate their input, and the solution that comes out the other side doesn’t feel like yours anymore. It feels like everyone’s. That’s not manipulation. That’s how adoption actually works.

Resources: Is growth something the organization invests in, or something you’re expected to pursue yourself?

The honest answer in most environments is somewhere in the middle, and leaning toward the latter. Training exists for compliance and certification. Development for career growth is mostly self-directed, whether the organization will admit that or not.

Tomás learned this by watching the people who had advanced. Without exception, they were the ones who hadn’t waited for a program to develop them. They’d sought out skills, taken on experiences, and built capability on their own initiative. The organization rewarded that. It just didn’t create the conditions for it.

Knowing this changes your posture. If you’re waiting for the system to grow you, you’ll wait longer than you should. The individual contributor who owns their own development, who doesn’t sit around hoping someone will notice what they need, is sending a fundamentally different signal than the one who waits.

Enablement: Does the culture make your best work easier, or does it quietly work against it?

Carmen’s manufacturing plant valued speed of repair above everything else. That cultural priority was so deeply embedded it actually discouraged the preventive maintenance conversations that would have reduced breakdowns in the first place. The culture enabled fast reaction. It quietly penalized proactive prevention, not through policy, but through what got celebrated and what got ignored.

Once Carmen understood that, she stopped framing her recommendations around prevention. She started framing them around speed. If we replace this bearing during Saturday’s scheduled downtime, we avoid four hours of unplanned downtime next week. Same recommendation. Different framing. The culture could receive it.

The idea didn’t change. The delivery did.

The Gap Is the Canvas

Here’s the reframe that changes everything.

Most people experience organizational dysfunction as a ceiling, evidence that the place doesn’t value good ideas, that leadership is too rigid, that contribution doesn’t matter unless you have a title. And sometimes that’s true. Genuinely broken organizations exist and no amount of reading saves you from one.

But in most cases, the ceiling isn’t the organization. It’s the distance between how you’re delivering your contribution and what the system is actually built to receive.

The gaps, the confusions, the misalignments, they’re not just obstacles. They’re opportunity. Every gap in the system is a space where the person who reads it accurately can contribute in ways others can’t. Because most people are too frustrated by the gap to study it.

Tomás reframed his safety concern as a throughput issue. The dock layout changed within two weeks. More importantly, he earned a reputation as someone who understood how the facility actually worked, not just how the handbook said it did. That reputation traveled further than the fix.

Elena went back to each clinic coordinator individually. She learned their workflows, incorporated their input, and brought a revised proposal to the next cross-clinic meeting, not as her solution, but as a shared one. It passed unanimously. She became known as someone who could move things across organizational lines. That’s exactly the signal that opens larger doors.

Carmen started translating every maintenance recommendation into production time saved. Six months later, the production manager started including her in planning meetings. A technician. In planning meetings. Because she’d stopped speaking technician and started speaking the language the room understood.

None of them changed what they were trying to contribute. They changed how they delivered it into the environment that had to receive it.

That’s not compromise. That’s sophistication. And it’s a signal almost nothing else replicates.

Think about the last good idea you had that went nowhere. Was it a bad idea, or was it a good idea that arrived in a language the system wasn’t built to hear?

That’s usually the more interesting question. I’d love to hear what you think in the comments.

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership and talent content and resources to everyone. Subscribe free and get new behavioral-based leader and talent insights every week.

Plus two Ready Set resources to put to work immediately.

Subscribe now

Leave a comment

Share The Ready Set

A Signal Forward Article

Signal Forward is a series inside The Ready Set: same publication, different altitude. The Ready Set is for leaders. Signal Forward is for everyone else: the individual contributors, specialists, and practitioners whose behavioral patterns determine whether their contribution gets seen, valued, and rewarded, regardless of title or tenure.

New here? Start with the first article. In People or HR? Pass this along to your team.

Ty was the strongest analyst in his department. Everyone knew it. His models were precise, his insights respected, and when a complex analysis was needed, his name came first. Four years in the role. Four years watching less technically skilled peers move into senior positions while he stayed put.

Six hundred miles away, in a manufacturing plant outside Memphis, a maintenance technician named Carmen was having the same experience in a completely different world. Carmen was the best troubleshooter on her shift. When a production line went down, she could diagnose the problem faster than anyone. She’d been passed over twice for the lead technician role, both times for people who, in her view, didn’t know the equipment as well as she did.

Ty worked in a glass office. Carmen worked on a concrete floor. But the force holding both of them in place was identical: they were both exceptional at the technical part of their jobs and completely unaware of the behavioral patterns that were quietly limiting everything else.

This is the story most high performers never get told. And it’s the story this article is about.

What Ty Couldn’t See

When Ty asked his director about advancement, the feedback was vague. Keep doing what you’re doing. You’re valued. What nobody told him directly was that his skill had never been the question.

The question was whether people wanted to work with him when the pressure was on.

The answer, formed over four years of accumulated behavioral evidence, was: Ty is brilliant but brittle. He pushes back on feedback. He gets visibly frustrated when timelines compress. He solves problems but creates tension doing it. People respected his output, but they did not enjoy his process.

What Carmen Couldn’t See

Carmen’s supervisor gave similar non-answers when she asked about the lead role. You’re one of our best. Just keep at it. What nobody told her directly was that the lead role wasn’t just about technical diagnosis. It was about coordinating a crew during a crisis, staying calm when a line was down and the production manager was calling every ten minutes, and communicating with operators who didn’t understand the mechanical side.

Carmen was fast and brilliant under pressure. She was also sharp-tongued when stressed. When a line went down and an operator gave her incomplete information, her instinct was to let them know it. If you’d told me the bearing was making noise yesterday instead of waiting until it seized, we wouldn’t be standing here right now.

She was usually right. And it didn’t matter. Because the operators started working around her instead of with her. They’d call another technician first, even one who was slower, because the experience of working with Carmen during a crisis was unpredictable.

Both Ty and Carmen were stuck. Both for the same reason. And neither one knew it.

Two Forces, One Engine

Every career, whether it plays out in a conference room or on a production floor, runs on two forces.

Capability: Can you do it?

Can you perform the work? Do you have the skills, knowledge, and experience to deliver what the role requires?

But here’s where most people stop thinking about capability too early. Capability isn’t just the technical part. An analyst who builds a brilliant model but can’t present it to a skeptical audience without getting defensive has a capability gap. A technician who can diagnose any failure but can’t communicate what happened without alienating the crew has a capability gap. The technical skill is strong. The professional capability, the full range of what the role actually requires, is incomplete.

And capability doesn’t stand still. Ty’s skills were built for a world where the analysis was the deliverable. Carmen’s were built for a world where fixing the machine was the whole job. Both worlds were shifting. The capability that got them here wouldn’t get them where they wanted to go.

Capacity: Can you do enough of it?

Picture Ty with one project: brilliant. With three simultaneous projects, two with shifting timelines and a difficult stakeholder: unknown, because he’d never been tested there, and his behavioral signal suggested the pressure would crack him.

Picture Carmen on a normal Tuesday, troubleshooting one issue: flawless. Now picture a Friday night when two lines go down at once, the parts supplier is closed, the shift supervisor is new, and the production manager wants an ETA every ten minutes. Carmen’s technical skill is the same. Her capacity to deliver that skill under multiplied pressure, while coordinating others, while communicating clearly, while managing her own frustration, that’s the question the lead role was designed to answer.

Capability without capacity produces potential that never scales. The senior role requires both.

The Three Layers That Actually Determine Your Trajectory

Here’s where it gets specific. Because most people think about career advancement as a single question: Am I good enough? But the organizations you work in are actually asking three distinct questions, in sequence, whether they know it or not.

Layer One: Performance Impact

Your knowledge, skills, experience, and credentials. The resume version of you. Ty’s impact was never the issue. Carmen’s troubleshooting record was the best on her team. If performance impact were the only thing that mattered, both would have been promoted years ago.

Performance Impact gets you in the room. On the floor, it gets you the call when something breaks. But rooms and shop floors are full of highly eligible people whose careers have stalled. Your impact is the entry requirement, not the advancement requirement. And most high performers already have it. Which means performance impact is rarely the actual problem.

Layer Two: Suitability

This is how you get work done. Your patterns under pressure. Your tendencies when challenged. How you treat people when things go wrong. Whether the experience of working with you during difficulty is something people want to repeat.

Here’s a quick test. Think of two people you’ve worked with who had similar skills. One was someone you wanted on every project or every crew. The other was capable but exhausting. Both were had impact. Only one was suitable for the high-trust work that accelerates careers.

Ty’s suitability blind spot was defensiveness disguised as intellectual rigor. Carmen’s was sharpness disguised as straight talk. In both cases, the person experienced their own behavior as a strength. The people around them experienced it as a cost.

That gap, between how you experience your own behavior and how others experience it, is where careers stall.

Layer Three: Trajectory

The combination of what you do and how you do it, observed over time. Not something you declare. Something others conclude. It answers the question that determines where you go and how fast you get there: Given everything I’ve seen from this person, is investing in them worth the risk?

Ty believed his trajectory was high because his output was strong. Carmen believed hers was high because nobody could match her on the equipment. Both were right about the performance impact part and blind to the suitability part. And trajectory impact, the thing that actually opens doors, requires both.

Performance Impact gets you in the room. Suitability determines whether people enjoy working with you, relate to you, and how you influence them. Trajectory determines whether the next opportunity is bigger than the last one. Whether you work in an office or on a floor, that sequence is identical.

The Blind Spot Nobody Warns You About

There’s a specific trap that catches talented people more than anyone else: the belief that doing your job exceptionally well is sufficient.

It isn’t. And this isn’t cynical, it’s structural.

The next level of almost any role isn’t a bigger version of what you’re currently doing. It’s a different kind of contribution entirely. Ty’s next level wasn’t better analysis. It was the ability to navigate organizational dynamics, communicate under pressure, and bring people along when they pushed back. Carmen’s next level wasn’t faster diagnosis. It was coordinating a crew through a crisis without leaving people feeling diminished in the process.

Nobody told either of them this directly. And that’s the problem. The feedback systems in most organizations are terrible at surfacing suitability gaps. Managers say keep doing what you’re doing when what they mean is your technical work is fine but working with you is hard and I don’t know how to say that. So talented people keep doing what they’re doing, keep getting passed over, and keep assuming the system is broken.

Sometimes the system is broken. But more often, the signal is the problem…and the signal is fixable.

Three Places to Look

If you recognize any version of Ty or Carmen in yourself, here’s where to start.

Look at the organization. How connected are you to why the organization exists and how your work fits? Dani, a supply chain coordinator, spent two years managing metrics without understanding what they meant to the people above her. When she learned how her numbers translated into the VP’s cost report, everything changed. Not her skills, but her understanding of where her contribution actually landed. Carmen had a parallel moment. She’d always thought of her job as keeping machines running. When she sat in on a production planning meeting for the first time, she realized that every hour of downtime she prevented was worth roughly twelve thousand dollars in output. She wasn’t a mechanic. She was a frontline contributor to the plant’s profitability. That realization changed how she prioritized, communicated, and framed her own value.

Look at the situation. Each of us responds differently when things go well versus when they go badly. Ty read a stakeholder’s challenge as a personal attack and matched the energy. Carmen read an operator’s incomplete information as negligence and let them know it. Both were reacting to what the situation felt like rather than reading what the situation actually needed. Situational awareness is asking, in real time: what does this moment require from me? Not what does my instinct want to do, what does the moment need?

Look at yourself. Think of the last time you received genuine criticism. What happened in your body? What did you want to say? What did you actually say? Ty’s self-awareness stopped at his technical strengths. Carmen’s stopped at her diagnostic speed. In both cases, the behavioral patterns they couldn’t see were the ones holding them back.

The blind spot isn’t that you don’t know your strengths. Most high performers know their strengths well. The blind spot is that the thing you experience as a strength, the directness, the rigor, the high standards, is sometimes the exact thing creating friction in the people around you.

What This Means for You

Your performance engine runs on capability and capacity. But what actually determines your trajectory is whether you’re eligible, suitable, and impactful. In that order, and all three together.

Most individual contributors spend the majority of their development energy on performance impact: more skills, more certifications, more technical excellence. And that energy is never wasted. But if you’re already technically strong and your career still isn’t moving, the impact is probably not the gap.

The gap is almost always suitability. How people experience working with you. How you show up under pressure. Whether the behavioral evidence you’re creating every day predicts that investing in you is worth the risk.

Ty and Carmen both figured this out eventually. Ty stopped treating feedback as an attack and started treating it as information. Carmen started asking what the situation needed from her before reacting to what the situation felt like. Neither change was dramatic. Both were consequential. The behavioral evidence they started creating was different, and the signal it sent was different.

The career didn’t change. The performance engine did.

What about you? If you’re honest about where you might have a gap, performance impact, suitability, or trajectory, which layer is it? You don’t have to answer that publicly. But it’s worth sitting with. I’d love to hear what comes up in the comments.

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership and talent content and resources to everyone. Subscribe free and get new behavioral-based leader and talent insights every week.

Plus two Ready Set resources to put to work immediately.

Subscribe now

Leave a comment

Share The Ready Set

We start with Katherine Johnson. Because there is no better opening story for what this series is about.

What we cover:

• Why talent alone doesn’t explain trajectory — and what actually separates the individual contributors whose careers build momentum from the ones who stay stuck

• The briefing room: what Johnson walking in and staying — without permission, without explanation — reveals about the difference between showing up to perform and showing up to contribute

• Maya and Jared: two people, same organization, same level, comparable skills — and why eighteen months later their careers are in completely different places

• Why you are being evaluated constantly and almost never through formal systems — and what that means for how you show up in ordinary interactions

• The John Glenn moment: what it means that the most celebrated astronaut in America wouldn’t get in the capsule until Johnson personally verified the numbers

• The signal you’re already sending — and why the people around you already know whether you’re there to perform or to contribute

One question to sit with honestly this week:

Think about the last week of work. Were you showing up to perform — or to contribute? There’s a real difference. And the people around you already know which one you’re doing.

For the full Signal Forward launch piece — including the complete framework and where the series is headed — check out thereadyset.substack.com. Worth reading alongside this episode.

Signal Forward runs alongside The Ready Set on Substack. New content drops weekly.

Subscribe: thereadyset.substack.com

Introducing Signal Forward

A quick note before we start.

Most of what gets published here, and most of what gets published anywhere, is written for leaders. People with teams, titles, and positional authority. The Ready Set is built around that. The ten behaviors, the framework, the research, it’s aimed at the people responsible for leading others.

But a lot of you aren’t there yet. And some of you never want to be. You’re individual contributors. Specialists. Early-career professionals figuring out why solid work isn’t creating the momentum you expected. Mid-career practitioners who are excellent at what they do and quietly frustrated that it doesn’t seem to be enough. Experienced people who’ve watched less capable colleagues get pulled into opportunities they should have had.

This series, which will be ongoing, is for you.

Signal Forward runs alongside The Ready Set content. Same publication, different altitude. Where The Ready Set focuses on the behaviors that make leaders effective, Signal Forward focuses on the behavioral patterns that determine whether your contribution gets seen, valued, and rewarded, regardless of whether you manage anyone.

After this initial Signal Forward launch series, we’ll publish to this series on a rotating basis. You don’t need to read them in order, but if you do, they build on each other.

Now. Let’s get into it.

Two Careers, Same Organization

This is a story about two people. Same company. Same function. Same level. Comparable skills, similar tenure, overlapping responsibilities. Neither manages anyone. Both are described as strong performers.

In eighteen months, their careers will be in fundamentally different positions.

Maya will have been pulled into a cross-functional initiative she never applied for. Given exposure to senior leadership. Mentioned in a succession conversation she knows nothing about.

Jared will have received another solid performance review, a standard merit increase, and the quiet, corrosive sense that his contribution is invisible.

Nothing dramatic will separate them. No single defining moment. No lucky break. No political maneuver.

What will separate them is something far more consequential and far less discussed: the signal each of them has been sending, every day, in every interaction, without knowing it.

What Maya Does That Jared Doesn’t

Maya arrives at a routine status meeting. She’s prepared, not because the meeting requires it, but because that’s how she operates. When a peer raises a concern about a process handoff, Maya doesn’t wait for someone to assign ownership. She says she’s seen the pattern too and offers two options she’s already thought through. The meeting moves forward.

She doesn’t know that the director observing the meeting made a mental note. Not about the solution, about the behavior.

Maya operates with initiative in low-stakes environments. That predicts how she’ll operate in high-stakes ones.

The director doesn’t articulate this consciously. But the note is made and the signal has been received.

Jared arrives at the same meeting. He’s competent, prepared enough, contributes when called on directly. When the process concern is raised, he waits to see who will take it. Nobody assigns it to him, so it’s not his problem. He offers a thoughtful comment when the group discusses next steps.

His contribution is fine and, well, forgettable.

Jared isn’t a poor performer. He’s just an invisible one. Not because his work lacks quality, but because his signal lacks intentionality. He shows up to perform. Maya shows up to contribute. That difference, performed consistently across hundreds of small interactions, is the difference between a career that builds momentum and one that maintains position.

The Evaluation That Never Stops

Here’s what most individual contributors never learn: you are being evaluated constantly, and almost never through formal systems.

The performance review captures a fraction of what the organization knows about you. The real evaluation happens in the observations people make every day: how you respond when a deadline moves, how you handle ambiguity, whether you take initiative or wait for instruction, how you treat people who can’t help your career, what you do with feedback, how you behave in meetings where no one senior is watching.

These observations accumulate into a reputation. That reputation travels. It enters conversations you’re not part of. It shapes decisions about opportunities you don’t know exist. It answers questions about you that no one ever asks you directly:

Can this person handle more? Will they step up under pressure? Do they see beyond their own role? Would I want them on my team?

Your signal is the answer to those questions. And you’re providing the answer right now, whether you’ve designed it or not.

The Chain That Runs Your Career

Predictive Performance operates through a chain: Traits drive Behavior. Behavior creates your Signal. Signal shapes what Activity follows. Activity determines your Trajectory.

At the individual contributor level, that chain is your career’s operating system. And the critical piece most people miss: you may not control how leadership intent reaches you. But you absolutely control the signal you send outward.

You cannot control the shadow cast on you. You can absolutely control the signal you cast forward.

Why This Works Even With Poor Leadership

The most common objection to owning your own trajectory is also the most understandable: What if my leader is the problem? What if I’m doing excellent work and no one above me sees it, values it, or creates conditions where it can thrive?

This is a real condition. Poor leadership suppresses initiative, distorts feedback, and makes good work invisible. Plenty of people reading this are working in exactly that environment right now.

But here’s what the leadership industry never tells you: even in the most dysfunctional environment, signal travels. Your peers observe you. Adjacent leaders observe you. People who leave your organization carry your reputation with them. The person two levels above your leader, who you’ve never met, is forming an impression of you based on the behavioral evidence that reaches them through the system.

Bad leadership can slow the recognition of your signal. It cannot prevent your signal from forming.

The Maya-and-Jared divergence happens under good leadership and bad leadership alike. The difference isn’t whether the signal is received. It’s whether you designed one worth receiving.

What This Series Covers

Over the next several months, Signal Forward will go deep on the specific behaviors, disciplines, and frameworks that govern individual contributor performance and trajectory. Not productivity hacks. Not how to manage your boss. Not how to survive a bad team. The behavioral architecture of a career that builds momentum on its own terms.

We’ll cover how to read the system you operate in. How to govern your response under pressure instead of reacting to it. How to expand your contribution beyond your defined scope. How to own your own development without waiting for your organization to do it for you. How to build a signal that compounds over time into a reputation that opens doors you didn’t know existed.

And we’ll go deep on the ten specific traits that predict whether an individual contributor thrives, stalls, or derails, regardless of industry, function, or the quality of leadership above them.

The shelf of books written specifically for you has always been nearly empty.

This series exists to change that.

A question to start: Think about the last week of work. Were you showing up to perform, or to contribute? There’s a difference, and the people around you already know which one you’re doing. I’d love to hear your honest answer in the comments.

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership and talent content and resources to everyone. Subscribe free and get new behavioral-based leader and talent insights every week.

Plus two Ready Set resources to put to work immediately.

Subscribe now

Leave a comment

Share The Ready Set

What we cover:

• The difference between compliance and engagement — and why they look similar from the outside and are completely different on the inside

• Why you can’t build both at the same time — and how the behaviors that create compliance actively undermine engagement

• How Brooks selected his roster before the final tryout ended — and what that reveals about choosing engagement potential over raw talent

• Why Brooks made himself difficult to like deliberately — and the sophisticated understanding of team investment that decision reveals

• The August practice: what happened in a darkened arena after a disappointing exhibition tie — and why what formed that night couldn’t have been built any other way

• The question every leader needs to sit with honestly: where are you building compliance when the work actually requires engagement?

Three things to try this week:

1. Look at where people are doing what they’re told because that’s what’s expected — and ask whether the work actually requires something more than that

2. Think about how you respond when someone challenges an idea or flags a concern — does that response encourage more of it or less?

3. Ask yourself what you’re actually rewarding — execution and compliance, or initiative and investment? The answer reveals what you’re really building

For the full framework on engagement versus compliance — including the complete reflection questions and practical guidance — check out the article that dropped this Tuesday at thereadyset.substack.com

This episode closes out the five-part New Leadership Model series:

• From Planning to Inspiring

• From Directing to Enabling

• From Controlling to Facilitating

• From Managing to Developing

• Engagement vs. Compliance

Paid membership for The Ready Set is open. KLIR gives you a personalized behavioral picture of where you actually stand across the ten behaviors we’ve covered. The AI Ready Set Coach helps you build a real development plan around your specific results. It’s not a content upgrade — it’s a genuine development experience.

Learn more: ready-set-membership.c2advising.com

The Ready Set is a behavioral leadership model built on 15+ years of observational data. New content drops weekly on Substack.

Subscribe: thereadyset.substack.com

Compliance looks good on paper. Tasks are completed. Deadlines are met. Rules are followed. Boxes are checked. Metrics are hit. From a distance, a compliant team can look like a high-performing team. Everything is getting done, people are showing up, and the work is moving forward.

But engagement? Engagement is what actually moves organizations forward.

And here’s what most leaders miss: You can’t build both at the same time. The behaviors that create compliance actively undermine engagement. The leadership that generates engagement doesn’t rely on compliance. At some point, often without realizing it, every leader makes a choice between the two.

The question is: which are you choosing?

The Difference Most Leaders Miss

• Compliance is external motivation, minimum effort, and risk avoidance. People do what they’re told because they’re supposed to. They follow the process because that’s the expectation. They hit the standard because that’s what keeps them out of trouble. It’s transactional. You tell me what to do, I do it, and we both move on.

• Engagement is ownership, initiative, and commitment. People care about the outcome, not just the task. They look for ways to improve things, not just complete them. They bring discretionary effort, the energy and creativity they’re not required to give but choose to anyway because they’re invested in the work.

You can command compliance. You earn engagement.

That’s the fundamental difference. Compliance can be mandated. “Here’s the policy. Follow it.” Engagement can’t. You can’t force someone to care. You can’t require them to bring their best thinking. You can’t demand initiative. Those things only show up when people feel connected to the work, trusted by their leaders, and valued for more than just executing tasks.

Why Compliance Is a Leadership Ceiling

Compliant teams do what’s asked. They rarely challenge assumptions and they avoid risk. They follow the script, stick to the plan, and don’t color outside the lines.

And in stable, predictable environments where the script works and the plan is sound, that might be fine. But in fast-changing environments where assumptions break, where innovation matters, where adaptability is survival, compliance is dangerous.

Compliant teams don’t innovate, they don’t experiment, and they don’t stretch. They don’t flag problems early because raising concerns feels risky. They don’t offer ideas because offering ideas means sticking your neck out, and compliant cultures punish that.

I worked with a team at an oil and gas company where compliance was the unspoken standard. People showed up on time, completed their assignments, followed every process to the letter. Turnover was low and performance reviews were fine. On the surface, everything looked functional.

But when the market shifted and the company needed to move faster, to try new approaches, to adapt quickly, guess what happened? That’s right, the team froze. They waited for permission. They asked for detailed instructions. They wanted to know the exact process for the new situation before they’d act. They’d been trained so thoroughly to comply that they’d lost the ability to think independently.

And the leader, frustrated, kept asking, “Why won’t they take initiative?” But initiative had been conditioned out of them. Every time someone had tried something new and it didn’t work perfectly, they’d been corrected. Every time someone questioned a process, they’d been reminded to follow it. And every time someone took a risk, they’d been asked to justify it.

The team had learned: compliance is safe. Initiative is risky. So they chose compliance. And the organization paid the price in missed opportunities, slow adaptation, and declining competitiveness.

As author and business thinker Peter Drucker observed, “Management is doing things right; leadership is doing the right things.”

Compliance cultures optimize for doing things right according to the existing playbook. Engaged cultures empower people to figure out what the right things are, even when the playbook doesn’t have an answer yet.

How Leaders Accidentally Create Compliance Cultures

Most leaders don’t set out to build compliance cultures. It happens by accident, through small decisions that add up over time.

• It happens through over-control. When leaders monitor everything, approve everything, and stay involved in every detail, people learn that their job is to execute, not to think. Initiative fades because it’s not needed, or rewarded.

• It happens through punishing mistakes. When failure is treated as unacceptable rather than as part of learning, people stop taking risks. They play it safe. They do only what they’re certain will work. Innovation dies.

• It happens through rewarding silence over candor. When leaders respond defensively to feedback, when dissenting voices are dismissed, when challenging ideas is seen as disloyalty, people learn to keep their mouths shut. The best ideas never surface because it’s not safe to offer them.

• It happens through valuing obedience more than contribution. When promotions, recognition, and rewards go to people who follow instructions well rather than people who think critically and add value, the message is clear: compliance is what we actually want, even if we say we want innovation.

None of it is intentional. But all of it is common. And the cumulative effect is a culture where people show up, do what they’re told, and save their best thinking for somewhere else.

What Engaging Leaders Do Differently

Engaging leaders create conditions where people want to contribute, not just comply. They do this through specific, consistent behaviors:

• They invite ideas early. Before decisions are finalized, before the plan is locked, they ask: “What are we missing?” “What concerns do you have?” “What would you do differently?” They make it clear that input matters and will actually shape the outcome.

• They encourage ownership. They give people real authority over their work. Not just responsibility to execute someone else’s plan, but ownership to shape how the work gets done, to make calls, to improve processes. Ownership creates investment. Investment creates engagement.

• They respond well to challenge. When someone pushes back on an idea, questions a decision, or surfaces a risk, engaging leaders don’t get defensive. They lean in. They ask clarifying questions. They explore the concern. They model that challenge makes thinking better, not that it’s a personal attack.

• They connect work to purpose. They consistently help people see how their work connects to something meaningful, to customers, to the mission, to impact. Purpose fuels engagement. Tasks fuel compliance.

They don’t just set expectations. They create meaning. And meaning is what transforms compliance into commitment.

A Telling Leadership Moment

Here’s a scenario that reveals which culture you’re building:

A team member spots a risk in an upcoming project. It’s not a catastrophic risk, but it’s real. It could cause delays, or quality issues, or customer frustration if not addressed.

In a compliance culture, they stay quiet. Because raising the issue might make them look negative. It might slow things down. It might create friction. And in compliance cultures, friction is punished. So they keep their head down, do their part, and hope someone else notices.

In an engagement culture, they speak up. Because they know it’s safe to flag concerns. They know the leader will listen. They know raising the issue won’t be held against them, it will be valued as contribution. So they bring it up early, when it’s still manageable.

That difference, whether people feel safe to speak up or feel safer staying quiet, determines whether organizations learn from problems or repeat them. It determines whether you catch issues early or discover them late when they’ve become crises.

And it all comes down to how leaders respond to candor.

Why Engagement Drives Performance

Engaged people solve problems proactively. They don’t wait to be told something’s broken, they notice it and fix it. They see inefficiencies and improve them, and they anticipate customer needs and address them before they become complaints.

Engaged people care about outcomes, not just tasks. They’re not just checking boxes, they’re thinking about whether the work is actually achieving what it’s supposed to achieve. And when it’s not, they adjust.

Engaged people go beyond role boundaries. They help colleagues without being asked. They share knowledge freely. They step in where they see gaps because they’re invested in the team’s success, not just their own individual performance.

They don’t need to be pushed. They pull themselves forward. And that difference, between push and pull, is everything.

Research from Gallup’s State of the Global Workplace report shows that highly engaged teams are 23% more profitable, have 10% higher customer ratings, and experience 81% lower absenteeism than disengaged teams. But engagement isn’t created through perks or policies. It’s created through leadership behavior, day after day, interaction after interaction.

Engagement Is Built Through Behavior

Engagement grows when leaders listen deeply. Not listening to respond or to defend, but listening to understand. When people feel genuinely heard, they lean in.

Engagement grows when leaders respond thoughtfully. When someone brings an idea or concern, engaging leaders don’t dismiss it reflexively. They consider it. They ask questions. They take it seriously, even if they ultimately decide differently. That respect builds trust.

Engagement grows when leaders act consistently. When values aren’t just posters on the wall but actual guides for how decisions get made. When the leader does what they said they’d do. When there’s alignment between words and actions. Consistency builds credibility, and credibility builds engagement.

Engagement grows when leaders show trust. When they give people autonomy, when they let them make decisions, when they don’t micromanage every detail. Trust begets trust. When you trust people with real responsibility, they rise to it.

It’s not created through perks or slogans. You can’t engage people with ping-pong tables and free snacks. You engage them by making them feel that their thinking matters, their contribution counts, and their growth is supported.

The Leadership Choice That Matters Most

Every leader chooses, often unconsciously, between control or trust, safety or silence, compliance or commitment.

Control or trust. Do you maintain tight oversight because you’re afraid of what might happen if you don’t? Or do you trust people to use good judgment and step in only when needed?

Safety or silence. Do you create environments where people can speak honestly, even when it’s uncomfortable? Or do you inadvertently punish candor and reward people who tell you what you want to hear?

Compliance or commitment. Do you optimize for people following instructions? Or do you optimize for people caring about the outcome and bringing their full capability to achieving it?

Only one scales. Only one lasts. Only one unlocks the discretionary effort, the creative problem-solving, the adaptive thinking that organizations need to thrive in complexity.

You can build a compliant organization. People will show up, do what they’re told, and meet the minimum standard. But when the market shifts, when competitors innovate, when challenges arise that the playbook doesn’t cover, compliance won’t save you.

Engagement will. Because engaged people don’t just execute. They think. They adapt. They own. They care. And that’s what actually moves organizations forward.

Reflection Questions

To ground this in your own leadership:

1. Does your team comply, or commit? When you look at how people show up, are they doing what’s required, or are they bringing discretionary effort and genuine investment?

2. How safe is it to challenge ideas around you? When someone pushes back on a plan or questions a decision, how do you typically respond? Does that response encourage more candor or discourage it?

3. What behaviors do you reward most? When you recognize people, celebrate wins, or make promotion decisions, what actually gets rewarded? Execution? Initiative? Risk-taking? Candor? The answer reveals what you’re really optimizing for.

4. Where might control be limiting engagement? Are there places where your need to maintain oversight is preventing people from taking ownership and bringing their best thinking?

5. What would shift if trust became the default? If you started from a place of trusting people to make good calls instead of requiring them to prove themselves first, what would change about how you lead?

Compliance gets you the minimum. People will show up, follow the rules, and do what’s asked. That’s not nothing. But it’s not enough. Not in environments where adaptability, innovation, and sustained performance matter.

Engagement gets you people’s best. Their creativity, their initiative, their commitment, their resilience. The things that can’t be commanded or required. The things that only show up when people feel trusted, valued, and connected to something meaningful.

You can’t build both. The leadership that creates compliance undermines engagement. The leadership that builds engagement doesn’t rely on compliance.

So you have to choose. And the organizations that thrive in uncertainty, that innovate under pressure, that build cultures people want to be part of—they’re the ones whose leaders chose engagement.

What about you? Where do you see the difference between compliance and engagement playing out in your organization? What helps you build one versus the other? I’d love to hear your thoughts in the comments.

That completes the five-article series on the New Leadership Model! We’ve covered:

1. From Planning to Inspiring - Why vision beats control

2. From Directing to Enabling - Why letting go creates more control

3. From Controlling to Facilitating - How leaders unlock collective intelligence

4. From Managing to Developing - Why leaders must stop being the system

5. Engagement vs. Compliance - Why leaders must choose one

   ---

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership content and resources to everyone. Subscribe free and get new behavioral-based leader insights every week.

Plus two Ready Set resources to put to work immediately.

Subscribe now

Leave a comment

Share The Ready Set

What we cover:

• The first practice: why Wooden spent the opening session of every season teaching players how to put on their socks — and what he was actually teaching them

• Why Wooden never talked about winning — and how his definition of success as capability fully expressed produced a scoreboard that nobody has matched since

• How Wooden ran practice: real-time feedback, deliberate challenge, and the difference between correcting a task and developing a person

• The pattern that turns competent leaders into bottlenecks — and why it almost always starts with being good at the job

• Why Wooden’s players kept coming back for thirty years after they left UCLA — and what that reveals about the difference between managing output and developing people

• What developing leadership actually produces that managing never can: people who keep growing long after they’ve left the room

Three things to try this week:

1. The next time someone brings you a problem, ask what options they’ve considered before you offer your answer — every time you fix instead of coach, you solve today’s problem and create tomorrow’s dependency

2. After your next meeting or project milestone, ask one reflective question: how do you think that went, and what would you do differently? That’s where experience becomes expertise

3. Look at your team honestly — who depends on you more than they should, and what would it take to start developing their capability to handle it themselves?

For the full framework on developing leadership — including the complete reflection questions and practical guidance — check out the article that dropped this Tuesday at thereadyset.substack.com

Paid membership for The Ready Set is open. KLIR gives you a personalized behavioral picture of where you actually stand across the ten behaviors we’ve covered. The AI Ready Set Coach helps you build a real development plan around your specific results. It’s not a content upgrade — it’s a genuine development experience.

Learn more: ready-set-membership.c2advising.com

The Ready Set is a behavioral leadership model built on 15+ years of observational data. New content drops weekly on Substack.

Subscribe: thereadyset.substack.com

Most leaders were trained to manage. Manage tasks. Manage timelines. Manage performance. Manage problems. Get things done on time, on budget, and according to spec. Keep the machine running smoothly. Make sure nothing falls through the cracks.

And for a long time, that worked. When success was mostly about execution, managing made sense. You needed people who could organize work, track progress, hold others accountable, and keep things moving. Management was the job.

But here’s the hard truth of modern leadership: If you are the system, the system will always be limited by you.

Your capacity becomes the ceiling. Your availability becomes the constraint. Your knowledge becomes the boundary of what’s possible. And when the complexity increases or the pace accelerates or you’re not available, everything grinds to a halt because the team hasn’t learned to function without you.

Why Managing Is No Longer Enough

Managing focuses on tasks over people, efficiency over growth, and compliance over capability.

Managers ask:

• “Is this done?”

• “Did you follow the process?”

• “Are you meeting expectations?”

Those aren’t bad questions. They matter, but they’re insufficient. Because they focus entirely on output and ignore the capacity being built, or not built, along the way.

Developing leaders ask different questions:

• “What are you learning?”

• “Where are you growing?”

• “What capability are we building next?”

The difference is subtle but profound. Managing keeps the system running today. Developing builds the system that can run tomorrow without you.

When I work with leaders who are stuck in management mode, they usually have a few things in common: they’re working long hours, they’re involved in everything, and they’re frustrated that their team doesn’t take more initiative. And when we dig into it, the pattern is always the same: the team has learned that their job is to execute, not to think, because the leader manages everything instead of developing anyone.

The Hidden Cost of Over-Managing

When leaders stay in management mode, teams wait for direction. They don’t step up with ideas because they’ve learned the leader already has the answer. They don’t make decisions because they know the leader will just override them anyway. They execute tasks efficiently but don’t evolve as professionals.

Growth stalls. And not just individual growth, but organizational growth as well because when everyone is focused on getting today’s tasks done, no one is building the capability needed for tomorrow’s challenges.

And leaders become overloaded. They’re the ones triaging every issue, making every call, and answering every question. They become the bottleneck not because they’re incompetent, but because they’ve built a system where everything depends on them.

I saw this with a leader named “Marcus” who ran a finance/risk team at a port company. Marcus was exceptional at execution. He could manage a projects from inception to completion flawlessly. He knew every detail, tracked every metric, and caught every mistake before it became a problem.

But as the company scaled and the team grew, Marcus couldn’t keep up. He was working 70-hour weeks, reviewing every piece of information, attending every client meeting, approving every asset. His team was capable, but they’d learned to wait for Marcus. They’d bring him problems instead of solutions. They’d ask permission instead of making calls. and ultimately they’d execute his vision instead of developing their own.

And when Marcus took a vacation, things fell apart. Not because the team was incompetent, but because they’d never been developed to lead without him. They could manage tasks when given direction, but they couldn’t think strategically, make tough calls, or navigate ambiguity on their own.

Marcus had managed them well. But he hadn’t developed them at all. And the cost of that showed up the moment he stepped away.

As leadership author Simon Sinek has noted, “Leadership is not about being in charge. It’s about taking care of those in your charge.”

Managing takes care of the work. Developing takes care of the people. And only one of those creates sustainable performance.

What Developing Leadership Actually Means

Developing leadership doesn’t mean lowering standards, slowing execution, or avoiding accountability. It’s not about being soft or letting people off the hook.

It means investing in people while delivering results. It means coaching in the flow of work instead of treating development as something that happens in a training room once a year. It means helping others think, not just do.

Development isn’t separate from performance. It’s how performance becomes sustainable.

Developing leaders do a few things differently:

• They invest time in capability, not just capacity. Capacity is about getting more work done. Capability is about expanding what people can do. When you develop someone’s capability, their capacity grows naturally. But when you just push for more capacity without building capability, people burn out doing the same level of work faster.

• They coach after action, not just during crisis. After a project wraps, after a meeting ends, after a decision gets made, developing leaders ask: “What did you learn from that?” “What would you do differently next time?” “What surprised you?” Those reflective questions turn experience into expertise.

• They give feedback early and often. Not just during annual reviews or when something goes wrong, but continuously. Real-time feedback that helps people adjust while the work is still happening. “Here’s what I noticed. Here’s what worked. Here’s what to try differently.”

• They create stretch opportunities. They give people assignments slightly beyond their current capability because that’s where growth happens. Not so far beyond that they’re set up to fail, but far enough that they have to stretch, learn, and develop new muscles.

• They normalize learning, not perfection. Developing leaders make it safe to make mistakes, ask questions, and admit when you don’t know something. They model that behavior themselves. They don’t punish people for learning curves, they expect them.

A Familiar Leadership Trap

Here’s the trap most leaders fall into: A team member makes a mistake or struggles with something, and the leader thinks, “It’s faster if I just fix it.”

Short-term? That’s true. You probably can do it faster. You’ve done it before. You know the shortcuts. You can knock it out in 20 minutes while it might take them an hour.

Long-term? That decision is costly. Because every time you fix instead of coach, you solve today’s problem but create tomorrow’s dependency. You reinforce that when things get hard, they should come to you. You rob them of the chance to develop the capability to solve it themselves next time.

Development requires patience. But it pays compound interest. The 20 minutes you invest in coaching someone through a problem today saves you hours down the road when they can solve it, and problems like it, without you.

Research from Gallup shows that employees who strongly agree their manager helps them develop their strengths are 30% more engaged and teams with managers who focus on strengths have 12.5% higher productivity on average. But that doesn’t happen by accident. It happens when leaders prioritize development over just getting the task done.

Why This Shift Changes Everything

When leaders develop instead of manage, teams become more resilient. They don’t fall apart when conditions change or when the leader isn’t available. They’ve learned to adapt, to think, to lead from wherever they sit.

Leaders regain time and energy. They’re not in the middle of everything anymore because their team can handle more independently which means they can focus on the strategic work that actually requires their level of experience instead of being stuck in tactical firefighting.

Organizations build bench strength. You have a pipeline of people ready to step into bigger roles because they’ve been developed along the way. Succession becomes safer. Promotions become easier. Growth becomes possible.

Succession planning is no longer a spreadsheet exercise of hoping the right names are in the right boxes. It’s a lived practice of developing people continuously so when opportunities open up, you have capable leaders ready to step in.

And performance becomes scalable. You’re not limited by your own capacity anymore because you’ve built capacity across the team. That’s how organizations grow without breaking.

Developing Leadership as a Daily Practice

This shift happens when leaders treat every interaction as a development moment. Not in a heavy-handed way, but in a mindset that asks: “Is this just about getting the task done, or is this also a chance to help someone grow?”

• Coach before correcting. When someone brings you a problem, resist the urge to solve it immediately. Ask: “What options have you considered?” “What do you think we should do?” Help them think it through before you offer your answer.

• Let others struggle productively. Watching someone work through a difficult problem can be uncomfortable. You want to jump in and make it easier. But that struggle is where capability develops. As long as they’re not heading toward catastrophe, let them work through it. Be available to support, but don’t rescue prematurely.

• Celebrate growth, not just results. When someone handles a situation better than they did last time, name it. “I noticed you stayed calm in that meeting when things got tense. That’s real growth.” Recognition of development reinforces that growth matters, not just outcomes.

• Model continuous learning yourself. Talk about what you’re learning. Share when you made a mistake and what you took from it. Ask for feedback from your team. When leaders model being learners, it creates permission for everyone else to learn too.

Development isn’t a program you run once a year. It’s a posture you take every day.

Why This Matters for the Future

The future of work demands people who can think independently, navigate ambiguity, make sound decisions, and lead without a title. You can’t build those capabilities by managing tasks. You have to develop people.

And if you want to lead at scale, if you want to build something that grows beyond your own capacity, you have to stop being the system. You have to build systems made of capable people who can think, decide, and lead themselves.

As author and educator Stephen Covey once said, “Always treat your employees exactly as you want them to treat your best customers.”

If you want your team to develop others, coach others, and invest in others, you have to model that with them first.

Reflection Questions

To ground this in your own leadership:

1. Where might you be managing instead of developing? Are there places where you’re focused entirely on task completion and ignoring the capability being built (or not built)?

2. Who depends on you more than they should? Which team members still come to you for decisions they could make themselves if they had more development and context?

3. What capability does your team need next, not just output? If you look six months ahead, what skills, mindsets, or behaviors does your team need to develop to be ready for what’s coming?

4. How often do you coach in real time? Are you giving feedback and asking reflective questions in the flow of work, or only during formal reviews?

5. What would change if development became part of daily work? Not a separate program, but woven into how you show up in meetings, conversations, and decisions every day.

Managing keeps things running. Developing builds the people who can run things without you. Both matter, but only one creates sustainable performance.

The shift from managing to developing isn’t about doing less. It’s about investing differently. It’s about recognizing that your job isn’t just to deliver results today—it’s to build the people who can deliver results tomorrow, next quarter, and long after you’ve moved on to something else.

When you develop your team, you’re not just making them better at their jobs. You’re building future leaders. You’re creating organizational resilience. You’re making it possible to scale without breaking. And you’re giving yourself the capacity to actually lead instead of just managing an endless stream of tasks.

What about you? Where have you seen the difference between managing and developing play out? What helps you shift from one to the other? I’d love to hear your experience in the comments.

Subscribe to The Ready Set

By Ryan Carnes | A data-backed development experience

Providing executive caliber leadership content and resources to everyone. Subscribe free and get new behavioral-based leader insights every week.

Plus two Ready Set resources to put to work immediately.

Subscribe now

Leave a comment

Share The Ready Set