There Is Nowhere to Promote Me. How Do I Keep Developing?
Listener Question
I work in a smaller organization with only a few supervisory positions. People can remain in those positions for years, so promotion usually depends on somebody leaving or retiring. I want to keep developing toward greater responsibility without waiting for a vacancy, but I also do not want to confuse getting a title with becoming a better leader. How do I keep developing, and when does the organization itself become part of the problem?
The visible problem is limited promotion opportunity.
That is real. A thirty-person organization cannot manufacture ten additional supervisory positions simply because ten capable people want to grow.
But the harder problem appears when the organization allows its promotion structure to become its development structure. If people only begin preparing for leadership when a position opens, development is already late.
This Mailbag addressed both sides of that problem: what the individual can control and what senior leaders should build before the vacancy appears.
The Direct Answer
Do not attach leadership development to somebody else's retirement date.
Separate promotion from development. Define what the next responsibility actually requires, build those capabilities before the title is available, create legitimate repetitions inside the person's current authority, provide useful feedback, and review readiness before the organization urgently needs a replacement.
Senior leaders should also stop treating a vacancy as the starting point for development. They need a small, usable leadership pipeline that shows who could carry greater responsibility now, who is getting close, what capability is still missing, and what experience would develop it.
The goal is not to create artificial ranks or promise everybody a promotion.
The goal is to have more people becoming capable of carrying greater responsibility before greater responsibility becomes vacant.
A vacancy determines when a position becomes available. It should not determine when preparation begins.
What Limited Promotion Paths Expose
Large organizations often have one advantage that small organizations do not: scale.
The Army, for example, can combine professional education, operational assignments, broadening experiences, progressive responsibility, and continued development across a long career. The system is imperfect, but the underlying principle is useful: greater responsibility should not be the first exposure to the capabilities that responsibility requires.
A small police department, manufacturer, nonprofit, healthcare office, or twenty-person business cannot reproduce that personnel machinery.
It should not try.
The useful lesson is simpler: take the developmental discipline without copying the bureaucracy.
Small organizations also face a difficult pressure. Immediate staffing requirements can consume developmental capacity. Patrol still needs coverage. Production still has to move. Customers still need answers. When capacity gets tight, training, specialty assignments, cross-functional exposure, shadowing, and other developmental work are easy to sacrifice.
That may be reasonable temporarily.
It becomes dangerous when temporary pressure becomes the permanent development model.
Then a retirement or resignation occurs and leadership discovers that the organization protected today's workload by consuming tomorrow's bench.
The Visible Problem Was Not the Whole Problem
Visible issue:
There are not enough supervisory positions.
Incomplete interpretation:
People cannot develop because there is nowhere to promote them.
Deeper operating issue:
The organization may have allowed promotion, selection, development, succession, and leadership readiness to collapse into one event.
That is where another weak assumption often appears:
“We have always promoted people first and trained them afterward. It worked for us.”
Survival is not proof that the development model was good.
People develop capability at different rates and through different combinations of instruction, observation, coaching, responsibility, feedback, and repetition. If somebody does not develop well under one narrow method, that does not automatically prove they lack leadership potential.
It may expose the limits of the development method.
And promoting first does not eliminate development. It postpones development until the consequences are higher.
Now the new supervisor is learning performance correction while somebody's career is on the other side of the conversation. They are learning delegation while real work is being assigned. They are learning accountability while the team is already carrying the consequence.
You moved the classroom into the live operation and acted like that somehow reduced the training requirement.
“This is how I came up” is not evidence that the system should remain unchanged.
That is survivorship bias with rank on it.
1. Separate Development From Promotion
The Point
Promotion is movement into a position. Development is increased capability.
They should support each other, but they are not interchangeable.
Key Line
Do not wait for promotion to begin becoming capable of the responsibility.
What the Leader Should Do
Make the distinction visible inside the organization.
Clarify that an employee can develop judgment, communication, planning, technical breadth, accountability, coaching ability, and organizational awareness before a formal vacancy exists.
Do not promise a title that is unavailable.
Do promise an honest standard for what readiness requires.
Practical Output
A short leadership-development statement that separates:
- Promotion eligibility
- Leadership readiness
- Development opportunities
- Formal authority
- Technical growth
2. Define the Capability Before Naming Candidates
The Point
Do not begin succession planning with names.
Begin with the responsibility.
Key Line
The position may be unavailable. The capability is not.
What the Leader Should Do
Identify the observable capabilities required in each critical first-line leadership role.
That may include:
- Setting expectations
- Assigning work
- Correcting performance
- Making decisions under uncertainty
- Developing people
- Managing competing priorities
- Coordinating resources
- Communicating upward and downward
- Escalating appropriately
- Accepting accountability for team results
Avoid vague requirements such as “needs more seasoning” or “needs leadership presence.”
Describe what successful performance actually looks like.
Practical Output
A one-page capability profile for each critical leadership position.
3. Read the Bench Before the Vacancy
The Point
Leadership should know who is developing before a position becomes empty.
Key Line
The vacancy should activate the succession process, not create it.
What the Leader Should Do
Use three practical readiness conditions:
Ready Now: capable of assuming the responsibility with normal transition support.
Ready Next: meaningful capability is present, but one or more specific gaps still require development.
Developing: potential or interest exists, but foundational capability still needs to grow.
Every assessment needs a reason.
“Ready Next because performance correction still needs work” is useful.
“Not ready yet” is not.
Practical Output
A simple leadership bench showing:
- Current readiness
- Evidence
- Development gap
- Next repetition
4. Create Real Repetitions Before Promotion
The Point
Leadership judgment cannot be built through classroom exposure alone.
People need controlled responsibility.
Key Line
Education creates understanding. Repetition develops capability.
What the Leader Should Do
Create legitimate assignments inside the person's existing authority.
Depending on the environment, that might include:
- Training responsibility
- A contained improvement project
- Event planning
- Cross-functional coordination
- An after-action review
- A team briefing
- Customer recovery ownership
- Process improvement
- Job shadowing
- Acting responsibility where policy permits
Before assigning anything, answer one question:
What capability is this supposed to develop?
If there is no clear answer, the organization may simply be giving a competent person more work.
Practical Output
A developmental assignment tied to one specific capability.
Decision Boundary: Development does not authorize someone to act outside policy, qualification, authority, or an established risk limit.
5. Evaluate the Repetition and Adapt the Development Method
The Point
Experience does not automatically become judgment.
It has to be examined.
Key Line
Repetition without reflection can make a weak habit very well practiced.
What the Leader Should Do
After a developmental assignment, inspect what actually happened.
Did the person:
- Plan effectively?
- Communicate clearly?
- Delegate appropriately?
- Avoid a necessary conflict?
- Take too much work back?
- Adjust when conditions changed?
- Protect the standard?
- Close the loop?
Then give another repetition that addresses what was learned.
Do not assume that everyone develops through the same combination of explanation, observation, practice, coaching, or feedback.
And be careful with the phrase “not a good fit.”
Not a good fit for leadership?
Or not a good fit for the one development method the current leader knows how to use?
Practical Output
A short development review documenting:
- What was attempted
- What worked
- What did not
- What capability needs another repetition
6. Use Lateral Assignments and Technical Paths Deliberately
The Point
Vertical promotion is not the only form of growth.
But a different assignment is developmental only when it builds something new.
Key Line
Movement is not automatically development. Capability change is development.
What the Leader Should Do
Use lateral assignments to create exposure to new:
- Decisions
- Stakeholders
- Technical problems
- Planning requirements
- Coordination demands
- Resource tradeoffs
- Training responsibilities
- Quality or accountability standards
Also stop forcing management to become the only respectable destination.
Some people should continue developing toward leadership.
Others should deepen technical or professional capability.
A strong investigator does not automatically need to become a lieutenant. A strong technician does not automatically need six employees.
Leadership is not a trophy for technical excellence.
Practical Output
Two visible development paths:
- Leadership growth
- Technical or professional growth
7. Keep Development Fair
The Point
Do not punish capable people for being capable.
Key Line
Development should increase capability, not quietly convert one employee into free organizational infrastructure.
What the Leader Should Do
Watch for the pattern where a “high-potential” employee begins:
- Training everyone
- Covering the supervisor
- Coordinating projects
- Handling difficult problems
- Carrying additional accountability
- Maintaining the original workload
Developmental assignments should be bounded, supported, and recognized.
Where permitted, recognition may include acting pay, specialty designation, training, credentials, greater autonomy, formal project ownership, or another appropriate mechanism.
The exact option depends on the organization.
The principle does not.
Sustained higher-level responsibility should not be hidden behind the word development.
Practical Output
A written boundary covering:
- Assignment duration
- Authority
- Support
- Recognition
- End condition
8. Protect Development Capacity and Review the Bench Quarterly
The Point
Current workload will always compete with future capability.
Senior leaders have to manage that tradeoff deliberately.
Key Line
If succession only becomes visible at the retirement party, you do not have succession planning. You have catering.
What the Leader Should Do
Once each quarter, ask:
- Which positions would hurt us if vacant tomorrow?
- Who could carry them now?
- Who could carry them within six to twelve months?
- What capability keeps the next person from being ready?
- What assignment could develop it?
- Where is important knowledge concentrated?
- Which capable employees have stopped developing?
- Where are we repeatedly using the same expert instead of building somebody behind them?
This does not need to become a multi-day HR event.
For a small organization, an hour of disciplined review can be enough to keep succession visible.
Practical Output
A quarterly bench review with:
- Critical roles
- Readiness
- Development needs
- Knowledge-concentration risks
- Next assignments
Where the Limits Must Stay Clear
Development does not mean inventing authority.
A person should not be asked to perform high-consequence supervisory decisions they are not authorized, prepared, qualified, or supported to make.
Senior leaders should also distinguish between a developmental opportunity and sustained higher-level work. Temporary stretch assignments can be useful. Permanent responsibility without the appropriate authority, support, and recognition is a different condition.
The employee has obligations too.
One successful assignment does not create an automatic right to promotion. Wanting the position is not evidence of readiness. Time in service is not evidence of readiness. Confidence is not evidence of readiness.
Capability has to be demonstrated.
Responsibility without authority creates hesitation. Authority without preparation creates risk.
What to Do in the First 30 Days
- Identify the leadership and continuity roles that would materially hurt the operation if they became vacant.
- Define the few observable capabilities required for each role.
- Assess who is Ready Now, Ready Next, or Developing.
- Name the specific capability keeping each Ready Next person from full readiness.
- Assign one or two controlled repetitions tied directly to those gaps.
- Observe the work and provide specific developmental feedback.
- Document where critical knowledge still depends on one person.
- Schedule the first quarterly bench review before another vacancy forces the conversation.
Do not turn this into a committee project.
Build the first usable version, apply it, inspect the result, and improve it.
How to Know Whether the Plan Is Working
Track measures that help leadership make a decision.
Bench depth: Do critical positions have a credible Ready Now or Ready Next option?
Readiness gaps: Can leadership clearly identify what still prevents someone from carrying the next responsibility?
Developmental repetitions: Are people actually practicing capability, or only attending training?
Internal fill capability: When a vacancy opens, does the organization have credible internal candidates?
Knowledge concentration: Which important functions still depend on one person?
Unplanned rescue: How often does senior leadership have to take over work a developing leader was expected to carry?
Retention of developing employees: Are capable people leaving because development, recognition, or opportunity has stopped?
The objective is not a perfect metric dashboard.
The objective is enough evidence to tell whether the bench is becoming stronger.
The Broader Operating Lesson
When the most experienced people become the permanent answer to every difficult situation, the organization can look strong while becoming increasingly fragile.
That applies to a police department, a small manufacturer, a restaurant, a nonprofit, a healthcare office, or a twenty-person business.
The organization may not be able to create another management position.
It can still create stronger people.
That requires senior leaders to stop waiting for fully formed leadership talent to appear. Potential has to be challenged, coached, observed, corrected, exposed to responsibility, and given progressively harder repetitions.
“This is how I came up” is not a development system.
Senior leaders influence whether capability is developed, ignored, or wasted.
How This Fits the Direct Action System
C S A, particularly Long-Range Observation, improves the read by forcing leaders to look beyond today's vacancy list and inspect what capability the organization will need later.
T M C matters when developmental responsibility is assigned. The person needs clear ownership, appropriate authority, the right level of supervision, and a defined communication path.
pro helps leaders inspect the consequences on both sides: promoting too early, failing to develop capable people, concentrating knowledge, or sacrificing tomorrow's bench to protect today's workload.
The system connection is not about predicting every vacancy.
It is about preparing before pressure removes the luxury of preparation.
Final Takeaway
A flat organization does not have to create a flat career.
The title may remain unchanged while capability continues expanding. But that only happens when development is managed separately from promotion.
Do not wait for a vacancy to define what leadership requires.
Define the capability first. Build the bench. Create legitimate repetitions. Give direct feedback. Use lateral assignments deliberately. Protect technical growth as well as supervisory growth. Keep developmental responsibility fair. Transfer knowledge. Review readiness before somebody gives notice.
The goal is not to promise everyone a chair.
The goal is to have more people capable of carrying greater responsibility than the number of empty chairs available today.
Build the bench before the vacancy.
Get the Direct Action Starter Sheet
Do not leave the read in your head.
Use the Starter Sheet before the next decision, correction, handoff, escalation, obstacle, or recovery move.
It gives you six prompts to assess what is happening, identify the pressure, locate the obstacle, and choose the next controlled move.
After submitting, you will go directly to the download page.
