Continual Performance Pursuit: Stop Waiting for Your Annual Review
Why the performance management system was never designed to develop you and the thirty-minute discipline that changes everything
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.
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.