When an organization grows from one team into several, hiring changes with it.
A common situation looks simple at first. A team has been struggling to deliver for several months, and its manager asks to hire another senior leader. That sounds reasonable: there are too few people, the work is not getting done, so add someone.
But the next questions are harder. What will this person actually own? Which responsibilities will the current manager hand over? Who will resolve conflicts between the teams? If the budget supports only one role, why this one? If the market cannot produce someone who meets every requirement, what is the organization prepared to give up?
Sometimes a hiring request does not start with a clearly defined role. It starts with management pressure that has not been resolved. The team is tired, the manager has too little authority, and several goals are fighting for attention. All of that gets compressed into one sentence: “We need someone stronger.”
That is why a manager of managers needs to participate in hiring. They do not need to interview every candidate, but they do need to own what the organization actually needs, what it is willing to promise, and whether the person will be able to carry the responsibility after joining.
In this article, “leadership supply” does not mean treating people as resources to be dispatched. It means continuously finding, developing, and arranging for people to carry important responsibilities, while giving them clear roles, authority, opportunities to grow, and a fair way to transfer responsibility. It includes hiring, but also role design, leveling, development, temporary authorization, and succession. The phrase is useful only if it points to a sustained organizational ability to carry responsibility, not to the number of people added.
Define the gap before deciding whether to hire
Hiring plans often begin with a number: “We need ten people in the second half of the year.” The number is not wrong, but it does not say what those people are meant to solve.
I would start with the work itself:
- Which problems in the next period could directly affect business results, system stability, or collaboration?
- Do they require more execution capacity, deeper professional judgment, or someone who can lead several teams?
- What does the current organization already have, and what is actually missing?
- If we do not hire yet, will the gap show up as delay, quality risk, concentrated knowledge, or sustained pressure on the team?
- Does the problem have to be solved through hiring? Would development, transfer, temporary authorization, a smaller goal, or a different division of responsibility be more appropriate?
If these questions are not answered, a hiring plan becomes a sum of requests. Every team submits a role, and the organization ranks them by volume or influence without explaining why the role is urgent, what it will own, or what will be abandoned if resources are insufficient.
Hiring should start with “what problem must someone carry?” rather than “what kind of person do we want?” The profile follows the problem. Otherwise, the more senior the role, the easier it is to fill the requirements with attractive words while leaving the actual responsibility unclear.
Four roles work together without replacing one another
HRBPs, TAs, technical leaders, and hiring managers often appear in the same hiring process, but they are not the same role. Here I use four roles: manager of managers, frontline hiring manager, HRBP, and TA. A technical leader may also be the manager of managers or the frontline hiring manager. If it is a separate role, it usually owns the professional direction and capability bar, while the manager of managers owns multi-team priorities, organizational boundaries, and trade-offs.
| Role | Main judgment | What it should not decide for others |
|---|---|---|
| Manager of managers | Multi-team goals, organizational boundaries, role priority, and long-term leadership capability | The full professional detail of a candidate |
| Frontline hiring manager | The real work of the role, daily management, professional judgment, and post-hire feedback | Hand an unclear request wholesale to HRBP or TA |
| HRBP | People strategy, organization design, manager support, employee relations, employee experience, and risk judgment within its mandate | Define the business problem alone or make a finding about a person without authority |
| TA | Hiring strategy, talent market, channel mix, process quality, candidate communication, and candidate experience | Decide whether a candidate can carry the professional responsibility |
The table is not meant to divide responsibility into four sealed boxes. Hiring quality depends on whether the judgments connect: the manager of managers explains the organizational problem and priority; the HRBP helps make the people and organizational conditions visible; TA brings the role into the real talent market; and the hiring manager uses evidence to judge whether the candidate fits the work.
Disagreements usually appear here. The business wants to hire quickly while the role is still unclear. The team wants a higher level while the organization has approved a lower one. TA sees that the market cannot produce the full profile, while the manager refuses to change the requirements. The HRBP sees a problem with span of management and authority, while the business says, “Hire first and solve the rest later.” These disagreements should not disappear into the phrase “we will collaborate.”
Working together does not mean sharing one undifferentiated decision right. The manager of managers owns the business responsibility for multi-team outcomes, role trade-offs, and leadership capability. The frontline hiring manager owns the role content and professional match. HRBP and TA contribute their domain judgment. Approval for the role, headcount, level, compensation, and final hire still follows the organization’s authorization chain, which may include a senior leader, finance, compensation, or a recruiting committee.
HRBP sees more than a role
An HRBP’s value is not just entering a hiring request into a system. In a more strategic HRBP model, the role connects business goals to people and organizational conditions. It helps managers see where a responsibility should sit, whether the team can carry it, whether the management span is already too wide, and who will absorb the extra work.
HRBP mandates differ. Some focus on strategy and organization design; others also handle day-to-day employee relations, policy interpretation, and case support. In more mature organizations, employee relations, compensation, learning, talent management, recruiting, and legal work may be shared with specialist teams, shared services, or COEs. The participation described here is therefore not a universal HRBP job description.
For example, if a team repeatedly asks to hire the same kind of senior role, an HRBP can ask with the manager of managers: is this a real capability gap, or has the role been designed to concentrate too much responsibility in one person? If headcount keeps growing without improving delivery, the problem may not be hiring speed. It may be too many goals, unclear boundaries, or insufficient authority.
When attrition rises, feedback worsens, absences increase, conflicts accumulate, or candidates describe the hiring process poorly, the organization should not immediately call it an “attitude problem.” These are clues. They may point to management behavior, work design, development opportunities, or communication, but they may also reflect a business cycle or personal circumstances. Internal work experience and external employer reputation should be observed separately. Neither rumors nor one satisfaction score is enough to label a team.
An HRBP can participate in discussions about team boundaries, management span, leadership levels, role mix, capability structure, onboarding, and the pace of change. It can also connect business planning with organizational capability and people plans. When a management problem appears, it can help distinguish individual performance, work design, conflicting goals, insufficient resources, and management behavior instead of making the conclusion for one side. The authorized business leader still owns the final business goal, team structure, and role trade-offs.
Psychological safety belongs in this discussion too. It does not mean avoiding criticism or lowering the bar for results. It means that people can raise problems, admit mistakes, and disagree without assuming that they will be shamed, punished, or harmed professionally. A manager of managers should watch how frontline managers respond to bad news, and whether disagreement actually changes decisions, rather than relying on a single engagement survey.
When a team has a complaint, sustained attrition, or a dispute about management behavior, first separate confirmed facts, people’s experiences, and conclusions that still need verification. Managers can handle ordinary goals, feedback, and collaboration issues. Allegations involving harassment, discrimination, retaliation, serious misconduct, or possible policy violations should move through the organization’s employee-relations, compliance, legal, or independent-investigation channels. HRBP can help identify the issue, prepare communication, improve management behavior, and route the case, but should not make a finding about either side without authority and facts.
TA sees what happens after the role enters the market
TA is not only there to speed up the process or collect resumes. It sees how candidates understand the role, which requirements cannot realistically be combined, where candidates begin to leave, and whether the job description matches the work.
TA can participate in the hiring kickoff, candidate profile, assessment design, channel mix, candidate communication, offer negotiation, and post-hire quality review. More channels are not automatically better. The mix should reflect the level, target population, location, skill scarcity, time window, and candidate behavior. Useful measures include the proportion of qualified candidates, interview conversion, offer acceptance, candidate experience, and post-hire performance—not just the number of resumes.
“Hard to hire” does not automatically mean lowering the bar or increasing the budget without limit. TA can bring facts back to the discussion: how many people meet the conditions, which requirements exclude candidates, what compensation and location change, and whether the hiring timeline still fits the business window.
Managers then need to choose: narrow the problem, change the level, develop an internal candidate, change the location or working arrangement, or admit that the goal is not worth the investment right now. TA provides market judgment and can recommend pausing the search, redesigning the role, or changing the plan. It does not carry the organization’s final trade-off.
Candidates are judging the organization too. A job description should not promise responsibility the team cannot provide, and an interview should not make candidates repeatedly answer questions unrelated to the role. Within reasonable limits, candidates should know the real responsibilities, assessment focus, process stages, and expected timing. Rejection should be truthful, respectful, and consistent. Whether individualized feedback is offered depends on policy, applicable requirements, and what the organization can actually support.
This is more than a matter of politeness. If a candidate is repeatedly asked to prove themselves without ever learning what the role is meant to solve, they cannot judge whether they want to join. The organization may also be imposing a large interview cost on someone before it has finished defining the job.
A hiring plan is a set of trade-offs, not a wish list
A useful hiring plan should answer at least these questions:
| What to clarify | The question |
|---|---|
| Organizational problem | What result should change, or what risk should decrease, after the role joins? |
| Responsibility | What does the role own, and what does it not own? |
| Timing | Why hire now rather than later, through a smaller role, or through development first? |
| Evidence | How will we judge whether a candidate has handled similar complexity? |
| Conditions | Are compensation, headcount, location, support, and authority real? |
| Market and process | Does the target talent exist, and can the hiring team make a reliable assessment? |
| Candidate promise | What real responsibilities, assessment focus, timing, and joining conditions will the candidate hear? |
| Failure plan | If the search fails, will the organization narrow the goal, redesign the role, or change the plan? |
The plan does not need to expose every personnel detail to everyone. But the people carrying the hiring responsibility need to understand the decision basis, priority, review date, and what cannot be shared. The hiring manager must also have time to participate. Interviewers should know what each of them is judging and provide evidence-based feedback on time. Otherwise, adding channels only sends an unresolved organizational problem to more candidates.
A manager of managers should also avoid ranking every role as the highest priority. Real priority means that some roles come first, some wait, and some problems are not solved through hiring. A plan that cannot say what will be given up is usually not a plan yet.
Leveling is not labeling a candidate
A candidate’s level should not be decided mainly by previous titles, company names, or confidence in an interview. More useful questions are: under what complexity did they carry responsibility, can they explain their trade-offs, how were the results verified, and which costs did they notice and handle?
For a leadership role, listen to what the candidate did not do. What did they give up when resources were limited? When teams disagreed, who paid the cost? When the result missed expectations, did they first change the goal, the organization, or the person? These details say more about fit for the responsibility than “I have strong drive.”
Being a strong individual executor does not mean someone can manage several teams. Having many relationships does not mean someone can hold the goal steady in a complex situation. The role requires connecting judgment, authority, resources, and relationships into an outcome.
Leveling should separate facts, inferences, and preferences. The fact is what the candidate did. The inference is whether those experiences suggest they can handle the new responsibility. The preference is the interviewer’s favored style. Turning preference into a capability standard makes the same responsibility subject to different rulers.
HRBP can provide an organizational and fairness perspective; job-architecture or compensation specialists provide the rules; the business leader explains the responsibility; and the authorized mechanism approves level and compensation. TA can explain market conditions. Technical and hiring managers still own professional judgment and role fit. When views differ, write down the specific disagreement instead of ending with “not a culture fit” or “not mature enough.”
After hiring, the organization is tested too
Hiring is not the end of the judgment. After the candidate joins, the organization needs to test three things: whether the role promise was real, whether the boundaries are clear, and whether the team actually gave the person the conditions needed to make decisions.
If a new leader finds that goals keep changing, promised resources never arrive, and decisions remain concentrated above them, the problem is not necessarily that the person failed to meet expectations. The organization also needs to ask whether it delivered the work it promised during hiring.
In the first months, look for signals: can the person explain the current goal and responsibility boundary? Do collaborators know what to bring to them? Can they make a choice in a real conflict? Does the manager provide support without taking daily judgment back? Is the team beginning to work in a way that does not depend on one person’s memory?
These are not another hidden scorecard. They help the organization notice early whether role design, authority, or support needs to change. A new leader joining or taking over is not only a test of the individual. Team members need to know what will change, what will not change yet, how to raise concerns, and who will handle the extra work during the transition. The organization cannot treat the team as an environment where a new leader may experiment without explanation.
Leadership supply also includes succession
If an organization starts hiring only when a role becomes empty, it will always be chasing change. A manager of managers should look ahead: which responsibilities can only one person carry? Which context exists only in one person’s head? Who could carry the goal in the short term? Which capabilities are worth developing through real work?
Succession is not naming a backup person in advance, and it is not a promise of promotion to everyone. It creates a real opportunity, clear authorization, and a review for the next transfer of responsibility. Development and succession opportunities should be allocated using standards that are as open and explainable as possible. People who temporarily carry leadership responsibility need support and appropriate recognition for the extra work. People who are not selected should not automatically be labeled unsuitable; they should know how to get feedback and find the next opportunity.
External hiring and internal development are not competing moral positions. External hiring may bring capabilities the organization does not have; internal development may preserve business context and working relationships. The manager of managers should combine them according to the problem and the time window rather than treating “stronger from outside” or “more loyal from inside” as a fixed answer.
The final question is not how many people were hired
When managers of managers work with HRBP, TA, and hiring managers, the goal is not a prettier process or more people for every team. The questions are:
- What problems does the organization truly need to solve next?
- Which problems should be solved through hiring, and which through development, transfer, authorization, or a smaller goal?
- Who owns the role problem, organizational conditions, market facts, and professional judgment?
- If the result misses expectations, how will the organization distinguish individual capability from role design and support conditions?
- When the next leadership change comes, which goals and capabilities can remain in the organization?
If an organization opens a role every time pressure rises, it may gain not more capability but more expectations that nobody has made clear. After joining, a person may discover that the role has no boundary, the manager has no authority, and the team is not ready to hand anything over.
What hiring should leave behind is not only a person. It should leave clearer responsibility, a more credible promise, and an organization better able to make a decision the next time conditions change.
This article describes a framework for organizational judgment around hiring, leveling, development, and succession. It does not replace an organization’s HR policies, authorization processes, or applicable legal and compliance requirements. Decisions involving specific candidates, employees, or employment relationships should be made by authorized professional roles based on the facts of the case.