Most mid-sized companies do not lack ambition. The budget is approved, the priorities are on a slide, and the leadership team agrees on direction. Then three months in, work slows. Backlogs grow, nobody is sure who owns the last step, and the people on the project are not quite the people the project needs.
This is a staffing problem as often as a strategy problem. Here is where it shows up and what to do about it.
A plan is not a set of choices
A budget, a software rollout and a list of annual goals are all useful. None of them tells a supervisor on a Tuesday afternoon what to do when two priorities collide.
Test your own plan with a simple exercise. Ask five people at different levels to name the three things the company must get right this year. If you get five different answers, the issue is not effort. The priorities have not been turned into something people can use to decide.
For hiring, this matters because you cannot write a good job description for a priority nobody can state. Fuzzy goals produce fuzzy roles, and fuzzy roles produce hires who spend six months working out what they were hired to do.
What the plan could not show you
Once work starts, the same things tend to surface:
- Data you counted on is incomplete, scattered or not trusted.
- The skills needed differ from the skills you budgeted for.
- The timeline was either too optimistic or padded beyond use.
- Someone good is in the wrong seat.
None of this means the strategy was wrong. It means the work is real now. The mistake is treating these findings as failures and waiting for the next planning cycle to deal with them. The companies that keep moving adjust their teams while the work is under way.
Where ownership leaks
As more departments touch a project, accountability gets split into pieces. Finance owns the numbers, operations owns the process, IT owns the system, and nobody owns the outcome from start to finish.
We see this most in three places:
- Operations and finance: invoice exceptions, month-end close and vendor disputes that bounce between teams.
- AI and data projects: a pilot that works in a demo but has no named owner for data quality or day-to-day use.
- Plant and supply chain work: a new line or scheduling system where the trades, production and quality each assume another group is handling the handoff.
The fix is not another meeting. Name one person who is accountable until the work is finished, not until the milestone is reached. Write that into the role.
When the team model has to change
A structure that suited the first 90 days often fails at higher volume. Work becomes more specialized, more people need visibility, and a generalist who coped early on is now buried.
Before adding more people to the same setup, look at how work moves. A few questions help:
- Where does work wait the longest, and who is waiting on whom?
- Is there a clear intake point, or does work arrive from five directions?
- Who handles exceptions, and is that a defined job or an interruption?
- Can you see workload and capacity without asking around?
Often the answer is a small dedicated team with a clear scope rather than a larger pool of stretched people. Sometimes it is a specialist who fills a skill gap the plan never mentioned. Sometimes it is a contract resource to clear a backlog while the permanent structure is redesigned.
Using contract and temporary talent in the middle
The stretch between plan and steady state is where contract hiring earns its place. You need skills quickly, you do not yet know the permanent shape of the role, and a wrong full-time hire is expensive.
A contract analyst, project accountant, data engineer or production planner can carry the work while you learn what the permanent team looks like. Then you convert the person, hire someone different, or wind down. The key is to be honest about which one you are doing at the start, so the contractor and your team both know.
We worked with a food manufacturer in the GTA on a similar pattern. Over 20 hires in 18 months across production, skilled trades and office roles, the needs changed as the operation grew. What kept it manageable was reviewing the roles as the work changed rather than filling against a plan written a year earlier.
A practical rhythm
You do not need a new framework. You need a habit:
- Every 30 days, review each major initiative and ask what has been learned that the plan did not predict.
- Check ownership. Can you name one person accountable for each result?
- Check capacity. Is the team sized and skilled for the work as it is now?
- Decide on roles early. If a skill is missing, start the search before the deadline is at risk, since good people take time to find.
- Keep priorities few. Three that everyone can state beat ten that nobody remembers.
What to do next
Pick your most important initiative this quarter and write down who owns it end to end, what skills the work now requires, and which of those you do not have. That list is your hiring brief, whether the answer is a permanent hire, a contractor or a reshaped team. A Traverse recruiter can help you work through it and find the people to fill it.