The Team You Need Is Not the Team You Have

01 The Constraint

The hiring problem that isn’t a hiring problem.

Recruitment is often the visible response to a problem that is not about recruitment at all.

Reactive hiring has a recognizable shape. Someone is overloaded, so a role is opened. A customer commitment slips, so a role is opened. A leader cannot get through the week, so a role is opened. Each decision is reasonable on its own. Together they produce an organization shaped by whatever hurt most recently.

The first difficulty is that the role gets written against the symptom. A job description drafted in a hurry describes the pain of the people already there, not the capability the business needs. Over time, roles accumulate unrelated responsibilities: a coordinator who also owns reporting, vendor relationships, and part of customer onboarding, simply because they were the person who could. Nobody decided that bundle. It formed.

The second is the leadership bottleneck. When decision rights are unclear, decisions travel upward by default. Leaders become the routing layer for questions their teams could resolve if they knew they were allowed to. Hiring another manager beneath an overloaded leader rarely fixes that. It often adds another handoff.

The third is subtler. Additional headcount can create more coordination than capacity. Every person added to an unclear process is one more person to brief, align, and check. Output rises more slowly than cost, and the natural conclusion is that the answer must be another hire.

I want to be careful here, because hiring is often necessary. Some constraints are real capability gaps, and no amount of redesign substitutes for the right professional. The mistake is not hiring. It is treating recruitment as the automatic answer to every capacity problem.

The distinction worth holding is between filling a vacancy and solving a constraint. A vacancy is a gap on the org chart. A constraint is the specific thing stopping the business from achieving an outcome it needs.

A vacancy is a gap in the org chart.
A constraint is a gap in the business.

The executive question

What business outcome is currently constrained, and why?

Answer that before a role is opened. If the first answer is “we need more hands,” keep asking why until it becomes specific. The specific answer is usually the real brief.

02 The Work

Design the work before you design the role.

Work backwards from the outcome. The role is the last thing you decide, not the first.

The more reliable way to plan is to reverse the usual order. Instead of starting with a person and asking what they will do, start with the outcome and ask what work it requires. It takes six steps, in sequence.

1. Define the outcome. What does the business need to be true in the next two or three quarters? Make it specific enough to measure.
2. Identify the capabilities and activities. What must the organization be able to do, and what work produces that result?
3. Separate judgment from repetition. Some work depends on judgment, context, and consequence. Some is repeatable operational work. They are designed differently.
4. Clarify ownership. Who owns the outcome, who decides, and who is accountable when it falls short?
5. Decide how each piece is best served. Automate it, redesign it, develop it internally, hire for it, or access it through a partner.
6. Then design the role and the workflow. Only now write the job description, around the work that is genuinely left.

Step three deserves particular attention, because it is where AI changes the arithmetic. As I argued in Issue 001, AI is increasingly capable of absorbing repeatable cognitive work: drafting, summarizing, sorting, reconciling, first-pass analysis. That does not remove the need for qualified professionals. It changes what they spend their time on. Judgment, contextual understanding, relationship management, and accountability remain with people, and a well-designed role is built around them.

It does not follow that everything should be automated, or that everything can be. Two cautions apply. The first is quality and oversight: automated work still needs someone who understands what good looks like and checks for it. The second is that automating a poorly designed process simply makes it fail faster. If the work is unclear, redesign it before handing it to software or to a person.

A role built around well-designed work is easy to hire for, easy to manage, and easy to measure. A role built around leftover tasks is none of those.

03 The Capability

Build capability, not just headcount.

A title describes a position. Capability describes what the position can reliably produce.

Talent decisions made on title and price alone tend to disappoint. A title says little about what someone can own, and the lowest available cost says even less about the value they will create. The more useful lens is capability, ownership, and business impact.

Consider the difference between a person who completes tasks and a professional who owns outcomes. The first needs work assigned, sequenced, and checked, so capacity grows while the management burden grows with it. The second takes responsibility for a result, raises problems before they surface, and improves how the work is done. Both have a place. They are not interchangeable, and a role should be matched to clearly defined responsibilities rather than to a general need for help.

That leaves the question of route. Three honest answers cover most cases.

Develop when the capability sits next to what an existing employee already does well, the gap is learnable, and their knowledge of your business is part of the value. Hire a specialist when the capability is deep, scarce internally, and central enough to the outcome that learning on the job is a real risk. Look globally when the skills you need are hard to source locally, or when building the team locally would take longer than the business can wait.

This is where exceptional Filipino professionals belong in the conversation, and not as a cheaper pair of hands. Having worked across Canada and the Philippines for many years, my view is that the case rests on capability: communication, critical thinking, adaptability, professional discipline, and comfort with remote work. Those are the qualities we look for, and they are the reason to treat the Philippines as a strategic source of talent rather than a line item.

Access, though, is only access. A wider talent pool does not replace rigorous selection, clear expectations, good management, or accountability. A strong professional placed in an unclear role will struggle in any city. Global talent works when the work has been designed first.

05 The Framework

A practical framework for the next hiring decision.

Five possible interventions. Usually, more than one applies.

Before approving the next role, test it against five interventions.

These are complementary decisions, not mutually exclusive categories. One constraint might call for a redesign first, automation of what remains repeatable, a development path for one team member, a recruited specialist for the genuine gap, and a partner for the infrastructure around it. The right mix depends on the constraint and the outcome, not on habit.

Five questions for your next leadership meeting

1. Which business outcome is currently constrained?
2. What capability is missing, and what evidence confirms the gap?
3. What work can be redesigned or automated before additional headcount is approved?
4. What level of ownership and expertise does the role genuinely require?
5. What infrastructure is needed to make the solution reliable and scalable?

If these cannot be answered, the role is not ready to be opened. If they can, the answer is often a different role than the one first imagined, or no new role at all.

Make the operating decision first.
Then make the hiring decision.