More The EntreLeadership Podcast episodes

I Cant Promote My Best Employee thumbnail

I Cant Promote My Best Employee

Published 16 Nov 2026

Duration: 00:16:21

Leaders should retain top performers without promotion opportunities by honestly addressing business constraints and reinforcing the team's connection to the organization's core mission and values.

Episode Description

Your best employees won't stick around forever if they don't see a future. In this episode, head coach John Felkins takes a call from a business owner...

Overview

A director of a 20-person clinics revenue cycle team in Texas asks how to keep a five-year star performer motivated when no positional advancement exists within the department. The performer has expressed wanting both more pay and more responsibility, and the director has proposed an internal ladder but hasn't received approval yet.

The discussion centers on the tension between growth expectations set during hiring and the reality that advancement requires both the person's readiness and an actual opportunity. The host emphasizes that a for-profit business cannot promote everyone if it isn't growing, and that paying people more without earning more "doesn't math." The department itself needs to grow to create advancement paths.

A key retention strategy proposed is tying the performer to the company's mission - transforming lives through patient care and mission trips to Kenya. The host stresses that leaders must act as "chief reminding officers," regularly sharing stories and reminders of why the work matters, because "vision leaks" and people forget. The performer in question hadn't submitted his name for a mission trip, suggesting he may be more invested in his own career advancement than in the broader purpose.

What If

  • What if you, as a solo developer, treat your product's mission the way the host treats the Kenya stories - by sharing one specific user-impact narrative with your team or community every month rather than leaving it on a website?

    • Move: Record a two-minute video or write a short post featuring one real customer story (analogous to the host reading a customer email to the entire company) and share it in your next team sync or newsletter. Propose doing this on a fixed monthly cadence.
    • Why Now?: The source warns that "people forget, vision leaks, there's new people," and that the Kenya stories were only reaching management, not the full team. As a solo operator scaling a small team, the same gap likely exists between your stated mission and what contributors actually hear.
    • Expected Upside: This could reduce the sense of "jumping jacks in the dark" that the host describes, making it easier to retain contributors who feel their work lacks meaning even when a promotion isn't on the table.
  • What if you, as a solo operator, build a responsibility ladder inside your current team structure before you have the headcount to create new roles?

    • Move: Draft three to four levels of increasing scope (e.g., "handles on-call," "leads a feature end-to-end," "mentors a junior contributor") and present them to your team as a proposed framework, mirroring the director who "came up with a ladder within the current structure of the team." Propose a 30-day trial before formalizing.
    • Why Now?: The source makes clear that "we can't promote everybody if the business isn't growing," but it also shows that a structured path - even without a title change - gives a performer something concrete to aim for while the business scales.
    • Expected Upside: This could keep a high performer engaged by giving them a visible progression path, reducing the risk of them leaving for a competitor who offers a title bump.
  • What if you, as a solo developer, directly ask your top contributor whether they've engaged with your product's purpose beyond the day-to-day code or tickets?

    • Move: In your next one-on-one, ask a question modeled on the host's: "Have you had a chance to [participate in a community event / talk to a customer / contribute to an open-source side project] yet?" If the answer is no, invite them specifically rather than leaving it to self-nomination, since the source performer "hasn't submitted his name when we ask."
    • Why Now?: The host uses the mission-trip question as a diagnostic for whether someone is "bought in to the mission versus how much has he bought in to his career and his own advancement." As a solo operator, you may not know where your key contributor stands on this spectrum.
    • Expected Upside: This conversation could reveal whether the person's frustration is about scope and pay (addressable via the ladder) or about disengagement from the product's purpose (addressable via the mission-sharing cadence), letting you target the right retention lever.

Takeaway

  • Audit the growth language in your hiring materials and prepare an honest follow-up conversation for any team member whose advancement expectation you can't yet fulfill, acknowledging that "the expectation during the hiring process has been set that they can advance and now they can't."

  • Draft a three-to-four level responsibility ladder within your existing team structure and present it as a proposed framework, giving performers a concrete progression path even when no new title or role is available.

  • Pick one specific customer-impact story and share it with your full team in a meeting or written update on a fixed monthly cadence, rather than leaving it on a website where, as the source notes, "I'm not sure that everyone's opening our internet to read the stories."

  • In your next one-on-one with your top contributor, ask directly whether they've engaged with your product's purpose beyond daily work (community events, customer conversations, open-source contributions), and if not, extend a specific invitation rather than relying on self-nomination.

  • Schedule a recurring mission or values reminder for your team and accept the repetition: the source's tell is that "when we start to get sick of how often we're telling people this, we are telling them almost enough, almost enough."

Recent Episodes of The EntreLeadership Podcast

11 Nov 2026 3 Products That Made Absolutely No Sense

ESPN, Ford, and Harley-Davidson failed by ignoring customer needs and market shifts, illustrating the need to kill unprofitable or distracting products.

6 Nov 2026 How I Built a 7-Figure Business From My Garage

John Youngblood built JJ George from a side hustle into a million-dollar business by solving grill accessory problems, eventually manufacturing the Smarter Scrubber domestically in the US.

More The EntreLeadership Podcast episodes