How a 500-person company should structure leadership development.
One owner, rooms sized to manager count and promotion volume, a bench you can name. Not an enterprise catalog.
A 500-person company should run leadership development as a short owned system: one operator, rooms sized to manager count and promotion volume, and a bench that is small enough to name. It is not an enterprise catalog. At this size you can still know who the managers are. Design for that, not for a Fortune 500 org chart.
"500" is a band, not a cliff. The same structure holds from a few hundred to the first thousand if you still have one People team and no dedicated CoE staff. When you need a RACI between HRBPs and a center, use HRBP vs Center of Excellence.
If you cannot name the managers, you built the wrong system.
What ~500 actually means.
You probably have a thin director layer and a CEO who still hears about a bad 1:1. L&D is a person or a fraction of a person. A steering committee of eight is how the year disappears. We are not publishing a standard manager count, bench size, or senior-coaching headcount for this band. Those numbers are yours to write down.
You do not need a competency encyclopedia. You need a short list of behaviors you will actually watch: feedback, 1:1s, and who you are willing to put on the bench. The longer design sequence lives in how to build a leadership development program. Cut it down until one operator can run it.
Plan from three inputs.
People-manager count
Write the number of people who have direct reports. That is the 1:1 and manager-cohort denominator. Do not guess a "few dozen" from headcount. Span of control varies by function.
Promotion volume this year
How many people will get a team, or move from IC to lead, in the next two cycles. That is the first-time manager and emerging-bench demand. A year with three promotions is not a year that needs a standing university.
People-team hours that can operate launch
Who will run matching, comms, and the two-week clock. One operator with a day a week can launch one room. The same person cannot also run a 14-vendor RFP. Capacity is the constraint, not ambition.
| If this is true | Size the first year like this |
|---|---|
| Manager count is small and promotions are few | One 1:1 room. Skip a standing cohort until a wave exists. |
| A promotion wave is already on the calendar | 1:1 plus one new-manager cohort. Do not mix them with a HiPo bench. |
| People-team capacity is a fraction of an FTE | One operator, one launch clock, one vendor. No RFP theater. |
| The senior layer already has a separate boutique coach | Keep them on the same system so promoted managers do not start over. |
That table is a planning model, not Boon data. We do not have a published distribution of manager counts at 500-person customers. Use your roster.
One operator, not a university.
Give one person the launch clock and the vendor relationship. That person wears the CoE hat in the HRBP vs CoE RACI. The CHRO or CEO sponsors. Managers repeat a three-sentence script. Launch ops are how to launch a coaching program people actually book.
Rooms follow the inputs.
On-demand 1:1 for people who carry teams. One cohort when a wave hits. Senior coaching on the same system so a promoted director does not walk into a blank page. You can add a team session when a function is stuck. You do not need a fifth vendor for it.
SCALE, GROW, and EXEC are Boon rooms that map to those jobs. They are not a prescription that every 500-person year needs all three. Open ADAPT only if AI adoption is a real program. Size the bench with how to design an emerging leaders program: a named list, each with a reason. Keep the top of the house on the same path as scaling coaching beyond executives.
What not to copy from enterprise.
Do not run a 14-vendor RFP. Do not publish a 40-competency model nobody uses. Do not buy per-seat access for every employee because a slide said "coaching for everyone" and then skip the launch. Coaching for everyone is a system. At 500 it still starts with the people who manage people.
Put the manager list in a spreadsheet. If you can name the people before lunch, you are the right size for this page. If you cannot, you need layers, not a bigger catalog.
Sketch the 500-person system on one page.
Owner, rooms, first cohort. Thirty minutes. No university blueprint.
Book a strategy callFrequently asked questions
How should a 500-person company structure leadership development?
Name one operator, count the people managers and the promotions you will make this year, then pick only the rooms that operator can launch. Keep the exec layer on the same system. Do not stand up a full university and do not copy an enterprise RFP.
Does a 500-person company need a leadership development function?
It needs an owner. That owner might be an HRBP with a day a week, or a People lead who also runs recruiting. A Center of Excellence with no operators is theater at this size. See HRBP vs Center of Excellence.
Who should get coaching first at 500 people?
Start where the week breaks: new managers, a thin director layer, or specialists you are about to make into managers. Size the first cohort from those lists, not from a generic bench recipe.
Should we buy an enterprise coaching platform at 500 employees?
Buy the architecture you will actually run. A hybrid with usage-based 1:1 can fit. A per-seat enterprise bundle sized for 5,000 people will sit unused. Structure first, contract second.
How is this different from an enterprise leadership program?
At 500 you can still name the people. At 5,000 you need layers and a CoE. Copying the enterprise org chart is how mid-market programs drown in steering committees.