Hiring strategy
Plan headcount from the work, not the org chart
Build a headcount plan by tracing each proposed role to work the business has committed to deliver. Estimate the capacity already available, remove work that should stop, and compare hiring with reassignment, automation, or temporary support. Give every request an owner, a decision date, and a clear consequence if the role is delayed.
On this page
Start with committed work
Ask each team to list the outcomes it must deliver during the planning period, who owns them now, and what effort is missing. Keep aspirations separate from approved commitments. A role should solve a visible ownership or capacity problem, not merely make an existing team feel more complete. This makes the hiring discussion about work that must happen rather than titles managers would like to add.
Subtract before you add
Review recurring meetings, low-value reports, duplicated approvals, and projects that no longer support a priority. Some pressure disappears when work is stopped or simplified. Other work may move to a team with the right capability. Hiring becomes credible only after leaders can explain what they chose not to do. The tradeoff is explicit: protecting every task usually creates a larger, slower plan.
Describe each gap precisely
For every remaining gap, record the outcome at risk, the capability needed, when it is needed, and how long the need is likely to last. A six-week launch bottleneck is different from permanent ownership of a customer workflow. Include manager onboarding capacity because a new hire consumes time before adding capacity. Treat notice-period discussions and hiring approvals as schedule inputs, not candidate quality signals.
- What stops or slips without this role?
- Which current person is carrying the gap?
- Is the need recurring or time-bound?
- Who can onboard the new joiner?
Compare credible options
Place hiring beside at least two alternatives. Reassignment may start quickly but leave another priority uncovered. Temporary support may suit a defined project but create hand-off work. Process improvement may reduce volume but cannot replace missing judgment. A permanent hire can create durable ownership while adding recruitment and onboarding time. Record why the selected option fits the duration and consequence of the gap.
Use a decision-ready plan
Illustrative example: a Bengaluru product team requests two analysts because weekly reporting is late. Its workload review finds one report can stop, one can be generated from an existing dashboard, and stakeholder questions still need an owner. The revised request is one analyst tied to decision support, with the manager accountable for onboarding and a review after the first planning cycle.
Review the plan for hidden duplication
Before approval, compare role requests across teams. Similar titles may hide overlapping work, while different titles may compete for the same ownership. Ask whether two managers have assigned the same outcome or assumed the other team will supply support. Also check whether the plan creates more coordination roles than delivery ownership. Resolve overlaps in the plan itself instead of expecting new joiners to negotiate them after arrival.
Next step
Choose one proposed role this week and rewrite its request around the committed work, the gap, the alternatives considered, and the cost of waiting.