How HR Leaders Make Stronger Workforce Planning Decisions

The first question I ask is how soon the new function has to be working. If we need it this quarter, we hire someone from outside who has already done the job, because it's rare that someone can be developed into a new function in a few weeks, however good they are. If we have six months or more and someone on the team is already doing part of that work, we develop them, because they already know how we operate and have business context.

I decide by testing whether the organization can define, teach, and assess the capability. I also compare the disruption of each route, looking at the complete workforce effect rather than just comparing an internal person to an outside candidate. My core principle favors durable organizational capacity over quick fills, avoiding concentrating an important capability in one person and reducing dependence on any single departure or promotion.

When a role opens, the right person might already be on your payroll. Of course it takes time to help someone develop in a new job, and it might seem easier to hire an expert from the outside to do a job. However, the organization can make a smart decision based on demonstrated skills and experience relevant to the role. And, it is essential to evaluate actual skills, for example through situational exercises or assessment tools, using consistent, job-related criteria to reduce bias.

A successful internal promotion is often prepared in advance through an appropriate development plan. And, having a lot of experts in your business is most valuable when they are able to share their knowledge. After all, it doesn't take an expert to know that when knowledge is shared, the entire organization benefits.

Who on your team is already doing the new work on the side, badly and without being asked? If a name comes up, I develop that person. When nobody comes to mind after a day of asking around, we hire from outside.

Qubit is a Dubai headquartered firm of about 60 people, where every outside hire changes the room more than you would expect. When we needed someone to own SEO reporting, a writer on the content team had already built a rough dashboard nobody requested. We gave her the role and 3 months of a course. It worked, mostly. Where it went wrong was the time we moved someone into a role he had never shown any interest in, because he happened to be free. He was polite about it for 6 months. He asked to go back to his old work in month 7.

I decide between developing and hiring by looking at time horizon, transferability, and business risk. If the capability will matter across multiple future priorities, I prefer to build it internally when possible because that investment compounds very visibly over time. If the need is immediate and failure would materially affect delivery, external hiring may be the more responsible choice. Take one specific planning cycle, for example, when we chose to train several existing employees on a new customer research approach because the skill would benefit multiple teams over time. If the need had been for something like a more specialized system with a near-term deadline, we would have hired externally instead. That combination works because we are very careful to not confuse urgency with strategic importance. My decision principle is simple: build internally when the organization benefits from owning the capability long term; hire when speed, scarcity, or risk makes waiting too costly.

We regularly help our clients at Equilliem to address these kinds of emerging skill gaps in their teams. When we're working with someone in this situation, our first advice is to start by considering the time horizon of the gap. If you need specialized expertise immediately, the best choice is usually to hire external talent. When the organization lacks the internal foundation to develop that expertise, then a permanent hire is usually the best choice. In other cases, hiring on a freelance or contract basis can be a good middle ground solution to give you the capability you need quickly while you work on developing skills within your existing team. For skills that aren't currently critical but will become so in the near future, developing current employees is often the best choice because it allows you to build institutional knowledge and strengthen retention along with reducing your recruiting costs.

We apply this same decision-making principle whenever we need to add skills to our team internally at Equiliem. Client needs are always evolving, particularly in the essential infrastructure industries that we represent. It's important for us to balance bringing in new professionals who have specialized market knowledge, against developing the capabilities of existing team members who already understand our business and clients. When the market shifts significant, or a new client need calls for deeper expertise in a specialized area, we evaluate whether our current recruiters can build that knowledge through targeted training or if we should hire an experienced recruiter who can establish that capability immediately. Across situations, we aim to hire for expertise we cannot develop fast enough while still investing in the potential we cannot afford to lose. Taking this approach ensures our workforce planning stays tied to business outcomes instead of being dictated by short-term pressure.

Capability gaps tempt leaders to hire first, because a new hire feels faster than development. Often it is not. External hires need time to learn the business, while internal people already carry the context that makes skills useful.

The decision principle I use weighs context against urgency. When the gap requires deep knowledge of the company's customers and processes, develop from within and support the learning with structure. When the gap requires a skill nobody internal has touched and the need is immediate, hire externally.

That principle holds up because it forces an honest look at what the gap actually is. Many apparent skill gaps turn out to be process gaps that no hire would fix. Name the decision the new capability must support, then choose the path that builds it most reliably.

1. I analyze for how long the gap will matter and what kind of gap it really is. As the priorities at CheapForexVPS shifted towards more consultative selling, I had the instinct to hire some closers. However, it turned out that the biggest gap in the team was in product knowledge and in the relationships with the traders that my team already had established. Although I could have hired someone and sent them off for 6 months of training, I would have lost in that time the value that my team was already delivering. Instead, I sent them for 6 weeks of coaching on the sales techniques that I had been unable to teach in the quarter. If the gap is technical, then I can always buy that in. However, the gaps around how people treat customers are much harder to fix, and so I grow the team to fill those gaps.

2. I am sticking to one main principle: Hire for things that cannot be learned in a quarter, and then grow in the things that your customers already trust you to do. In my many years of real estate, it was well known that agents with good knowledge of local neighborhoods and their families living in them generally outperformed their 'star' recruits to the area. Similarly, within a company, it is generally best to move trusted clients of yours into a 'stretch' role with suitable support. If, on the other hand, you only ever hire from CVs, hoping to save time and get people up to speed quickly, you will almost certainly incur costs and setbacks in terms of onboarding and, subsequently, losses through turnover down the line.

When business priorities shift, how do you decide whether a capability gap should be addressed through developing current people or hiring externally?

As a leader of a global recruitment agency for virtual assistants called VA Masters, I start by asking what kind of gap it is. If it's a tool or a defined procedure, develop. If it's judgment in messy, ambiguous work, hire for it.

Tools are teachable and they change fast. Across 322 virtual assistant or VA roles opened between February and August 2026, 26.4% named AI in their requirements. Zapier and n8n together appeared in more roles than ChatGPT alone. Hiring a person for one tool's current version is a bet that ages quickly. Someone who learns well can pick up the next tool. Judgment is different. In our experience the tipping point isn't task volume, it's task ambiguity. The messier the decision, the more you need a human who can catch what the process misses, and that is much harder to train in a few weeks.

We see this in how people grow. A person who started in a small role often becomes more technical, then starts suggesting automations themselves. Someone doing customer service today who learns to manage the tools that cut down simple repeat inquiries is a good example. The people who move up are the ones who learn the tools.

What is one decision principle that helped your workforce planning hold up over time?

Hire for judgment and the ability to learn, and teach the tools. Our skill tests measure whether a person can catch where AI output falls short, not which software they already know. That standard doesn't expire when the tools do.

In retail lending I develop current people when a new priority sits next to skills they already use, like client work, basic underwriting, and branch execution. We hire externally when the shift needs specialized product or market expertise the team lacks and can't ramp without hurting production. Loan officers and branch staff receive training in related programs, while specialists handle new investors or alternative documentation lines. Production stays intact only when the ramp uses nearby skills. One principle from owning lending P&L over time has held our workforce planning steady. I choose the path that keeps borrower knowledge, credit culture, and pipeline ownership inside the company unless the skill will stay core to profitability for years.

When priorities shifted at 717HomeBuyers, I leaned on the 70% adjacency rule. If someone already had most of the skills, we'd train them on the rest instead of hiring. That's how we got into off-market deals without adding headcount. Works well, but when we needed skills way outside our wheelhouse and had to move fast, we had to bring someone new in.

I start with one question: does this gap depend on knowing our customers, or on knowing something nobody here has done before? Customer knowledge takes years to build, so I develop people for that. New technical skills are faster to hire.

When we expanded our printed backdrop lines, we needed stronger color management. We hired one experienced print technician from outside, but we moved someone from our customer support team into the production role. She'd spent years reading complaints about colors that looked different in the studio than on screen, so she already knew what "wrong" looked like. The new hire's main job was teaching her the technical side.

Hire people who can teach the skill. Grow people who already know why it matters.

When priorities shift, I sort the gap by what's missing. If it's a skill, like a new process or a piece of equipment, I train someone already on the team. If it's judgment, like running a crew alone or handling an upset host at 6 a.m., I hire for it, because judgment takes years to teach and a skill takes weeks.

The principle that's held up for me is to match the fix to the time the gap will last. A need that's going to stick around is worth growing someone into, since a person you train already knows how the work runs and how the people around them work. A need that might disappear in a quarter doesn't justify a permanent seat at all, so I cover it with overtime or short-term help first.

The cleaners on our teams work alone inside homes, so hiring is where I'm strictest. Only 1 in 60 applicants make it through our process, and I'd rather run short for a few weeks than lower that bar to fill a gap. Anyone who gets through that screen is someone I'll invest in, because retraining a trusted person beats starting over with a stranger.

The principle I'd use is to grow inside the team the skills where you need to see every stage yourself, and to bring in outside people for expertise that lives at its source or that you only need now and then. There's no workforce plan on record I can quote, and I've stepped back from daily operations, but you can see that split in what our company publishes. A member of our team has made island hydrosols for us on the island, and the post on the turmeric one explains that small-batch distillation on the Big Island lets us watch every stage of the process. We buy our Mountain Juniper oil straight from a small family distiller in Arizona, and our blog points customers to an independent essential oil consultant. When priorities shift, I'd first ask which side of that line a gap falls on, and only then decide between training someone and hiring.

The question I ask first is whether we should be carrying the capability at all. A surprising number of gaps are better closed by removing the work.

We are a broker, and connecting insurers to our platform is the work. Every carrier integrates differently, with its own API quirks and its own maintenance, so each one you add is a permanent claim on engineering time. The instinct is to connect as many as possible and then hire to keep it all running. We went the other way and cut the carriers we display from eight to between four and five. That took a lot of engineering overhead out, and it helped customers decide faster, because fewer options means a quicker choice. It also made us more of a recommender than an aggregator, which is what we want to be. The capability gap closed because the work shrank.

When the capability is genuinely core, I hire. When our chatbot needed access to our own database through APIs so it could answer account questions, that was not something to develop in somebody's spare hours. We put a programmer on it.

The principle that has held up is to look at the overhead a capability creates after you acquire it. Developing someone internally is cheaper up front and only sensible if the work will keep existing. Hiring externally is right when the work is permanent and specialised. When neither is clearly true, the honest answer is usually that the work is not worth having.

Headcount decisions get easier once you are willing to delete the requirement.

My principle is to hire for the capability the business needs in the next 12 months, and develop for the one it needs in 3 years, as long as the person already shows curiosity in that direction.

Practically, I ask two questions. How fast do we need it? If the gap is hurting us now, learning on the job is too slow and risky, so I hire or bring in a specialist. And does someone on the team already show a spark? If a person has been tinkering on their own with something related, I would bet on developing them. They usually have the context, trust and motivation that an outsider takes months to build.

At Simply Noted we have 11 employees and build robots that write handwritten notes, so a bad external hire is felt immediately. Developing someone from inside protects culture, and it also tells everyone else that growth here is real.

The part that makes this decision hold up over time is being honest with the person. If I develop someone, I set a check date. If the skill is not coming along, we talk early instead of letting it drag. The principle is to decide by urgency plus evidence of interest, and to put a deadline on it.

My decision principle is to identify the constraint before choosing development or hiring. A capability gap can mean missing expertise, but it can also mean capable people lack the tools, context or ownership needed to contribute. Adding headcount before making that distinction can preserve the original bottleneck.

At Market Brew, serial QA was tying up our shared testing systems. We used Codex to create parallel mini testing environments and monday.com to give team members ownership of individual change requests. That made more of the existing team potential QA testers, with responsibility for seeing a change through testing.

The first rollout exposed another constraint: automatically generated test plans were too long and difficult to understand. We changed the writing guidance to short instructions, with the action and expected result separated. The team understood the tests better and closed QA items more quickly. The improvement depended on making the work understandable, as well as providing the technology.

That experience reinforces how I would approach a staffing decision. Develop internally when people can acquire the required judgment through bounded, real work with clear review standards. Hire when the required expertise or coaching capacity is genuinely missing, or when the business cannot wait for a responsible learning period. In either case, define the work and evidence of readiness first. The useful unit of workforce planning is a capability someone can demonstrate and own, rather than a job title alone.

A build-versus-hire decision has to include the team's capacity to teach and the expected life of the gap. When priorities change, I'd first ask how soon the new work needs experienced ownership. If someone has adjacent skills and the need will recur, developing them can strengthen the team beyond the immediate assignment. If the work needs an experienced owner sooner than the team can train one, hiring is the safer route.

At Ronas IT, we plan and track mentoring, onboarding and recruiting as internal projects alongside client delivery. Making that work visible changes the staffing conversation. A development plan needs an experienced colleague with room to coach, while a new hire needs time and support before working independently. Both paths consume capacity before they add it. Without that view, a team can promise to grow a capability while quietly taking the mentor away from delivery, or hire for an urgent gap and overlook the ramp-up.

The principle that holds up is to compare the full path to useful, independent work with how long the business will need the skill. For a short-lived requirement, I'd question whether a permanent role makes sense. For a capability we expect to use repeatedly, I'd look for an internal growth path before assuming every new priority calls for a hire. If the people who would teach are already committed, the development option isn't ready yet.

The decision principle I keep coming back to: develop when the gap is about exposure, hire when the gap is about wiring.

Some capability gaps exist because a person has never been given the chance to do the work. A strong individual contributor who has never led a project does not lack leadership ability. They lack leadership experience. That is a development opportunity, and it is almost always cheaper and more effective than hiring because the person already understands your product, your team, and your culture.

Other gaps are about operating style. If your business needs someone who thrives in ambiguous, fast-moving situations and nobody on your current team operates that way, training will not close the gap. You are asking people to work against their natural wiring, and that creates frustration on both sides. That is when you hire.

At Pigment, this distinction saved us from a costly mistake. We considered hiring a head of partnerships when our growth team was mature enough to develop the skill internally. The gap was not that our team could not do partnership work. It was that nobody had been asked to try. We gave one person ownership of three pilot partnerships and she outperformed what an external hire would have delivered in the first six months because she already understood the product deeply.

The workforce planning choices that hold up over time are the ones where you match the nature of the gap to the right intervention.

I'm a venture builder and the founder of APMZEE rather than an HR leader, but deciding whether to build a capability in-house or bring it in from outside is the decision I make most often when launching something new, and the principle carries across.

My rule is to bring in outside expertise for anything where being wrong would damage the customer's trust, and to develop internally the things that make the brand ours. At APMZEE the clearest example was formulation. We are active people in our 30s, 40s and 50s, and none of us was going to become a sports nutritionist in a year, so the formulas were developed with elite sports nutritionists and gold medal athletes, and the products are third-party tested. What we kept and grew in-house was the brand, the community and the four pillars of Action, Performance, Movement and Sleep that the whole range is organised around. More than 50,000 servings later, I would make the same split again.

In corporate ventures I see the opposite mistake a lot. A large organisation spots a gap, usually in digital product or go-to-market, and asks an existing team to retrain into it because that feels safer and cheaper. By the time the team is competent, the window for the venture has often closed. Start-up agility with corporate rigour, in practice, means being honest that some gaps should be hired for on day one, and keeping your own people for the work that carries your identity.

I build and run a SaaS company with a small team, fewer than 50 people and mostly remote, so every capability gap is a real decision for us. The principle I keep coming back to is to hire for knowledge of the customer's world and to develop everything that's about our own product and process.

Over 1,700 real estate companies use Paperless Pipeline, mostly brokerages and transaction coordinators. When we need someone to onboard new customers, we look for people who've done transaction coordination or run a brokerage back office. We could take a sharp software support person and teach them real estate, but it would be years before they hear a broker describe a stuck file and know which document is missing. Our software they can learn in weeks, because we built it to be simple on purpose.

The same rule runs the other way when the product shifts. Paperless Pipeline now uses AI to cut out data entry, and the people best placed to explain that to a broker are the ones who already know the workflow it removes. So we treat that as a training job and keep the hiring budget for gaps in customer knowledge. Bringing in an outside expert there would get us someone who understands the technology and not the customer, which is the wrong half.

We've served brokerages since 2009, and that rule has held because the customer's world changes slowly while our product changes all the time.

The clearest test case I have is from the third year of Visionary Marketing, when we expanded into Google Shopping. We could have trained our search people into it, and they were good, but Shopping feed work and product-level bidding is its own discipline, and the clients spending money on it would have been paying for us to learn on their accounts. So we brought in Shopping specialists. That was also the year we started managing more than £50k a month in ad spend.

The principle that has held up since is fairly simple. If the gap is a whole discipline that a client pays for directly and judges us on within a quarter, we hire someone who already does it. If the gap sits next to something a person already does well, say a PPC specialist picking up conversion tracking, or an SEO taking on the technical side of AI search, we develop them, because the core judgement is already there and the new skill builds on it.

What I'd flag is the cost people forget when they choose to develop. Training looks cheap on paper, but the learning happens on live work, and in a client business the mistakes land on the client. I would rather pay more for an experienced hire than ask a client to fund our learning curve.

I ask whether the gap can be closed in one quarter with training and mentorship. If it can, I develop someone internally. If the gap is a core skill that takes years to build, I hire externally. People lose months trying to promote someone into a role they were never going to grow into, and a quarter is a short enough window to tell me early which situation I'm in.

So I always look at the top three things the role actually does and ignore the full job description. If an internal candidate can already do two of them and the third is teachable, I promote. If they can only do one, I hire outside. We promoted a warehouse lead into operations because he already understood our inventory flow, and the reporting side was learnable.

When we needed someone to build our logistics tech stack, nobody on staff had that depth, so we went external. Clear roles, honest timelines, and no forced promotions are what keep the plan from falling apart.

My decision principle is to measure the gap before choosing to develop or hire, because most owners decide on a feeling and end up hiring for a problem they never defined. When I coach business owners through this, I have the person who currently carries the work track their week minute by minute, then we review it, often with AI, to see where the hours actually go. Sometimes the gap is a skill an existing employee can learn; sometimes it is a specialist skill nobody inside has; and sometimes it is repetitive admin that an AI agent can take off people entirely. Each answer leads to a different choice, and seeing it written down stops you hiring a full salary to cover what is really five hours of data entry.

When the gap is skill and the person already has the right character, I develop. That is how I learned myself: after the Army I knew radios, not telecom, and a mentor who had run a large engineering firm in the UK taught me cable jointing until I became one of the most relied upon jointing contractors on the NBN rollout. When the gap is character or commitment to quality, training will not fix it, and that is when I hire. In my telecom company, priorities shifted toward quality, and the contractors I had only cared about money, so I moved to employees on a legal minimum base plus uncapped performance pay and hired hungry, quality focused people. That principle held up for years: teach skills to the right people, and hire when what is missing is the right person.

I decide by asking where the learning curve would land: if someone already on my team can grow into the new skill behind the scenes, I develop them, and if the work will face customers from day one, I hire from outside someone who has done it before. The people already with us carry what is hardest to recruit, a feel for our customers and for a label where resort wear meets chic street style, as our About page frames it, so giving them room to add a skill is often a better trade than teaching a newcomer all of that. But when a shift in priorities puts the gap right where customers meet us, in an order, an email reply or a product page, the mistakes made while learning land on a shopper, and that is where outside experience is worth paying for. The decision principle I rely on is simple: the business can absorb a learning curve, but a customer should never have to sit through one. It holds up through changing priorities because it never depends on the priority itself, only on who would pay for the learning.

When priorities change, I first determine the type of gap we face. In behavioral health, some gaps are credential-based, such as when a new service line requires a licensed clinician we do not have. Since internal training cannot address this quickly enough for those seeking care, we hire externally. However, most gaps are related to context, such as navigating insurance, building referral relationships, or leading a team through a new program. In these cases, team members who already understand our patients, community, and processes typically acquire new skills more quickly than an external hire can adapt. Context is the most challenging quality to recruit.

I rely on is to diagnose the gap before creating a job posting. Many hiring mistakes occur when a context issue is mistaken for a credential issue, resulting in hiring an impressive outsider when the real need is someone who understands our operations. Promoting from within has a compounding effect: it demonstrates to the team that growth is possible here. In a field where burnout often leads to turnover, this may be a leader's most effective retention tool.