Ask a plant manager, a controller and a sales leader why their last big project ran late. You will hear different details and the same root cause: nobody was sure who decided.
The ERP cutover, the new production line, the CRM rollout, the move to a new shared-services model. Each one touches several departments. Each one stalls at the same point, when a call needs to be made and three people assume it belongs to someone else.
This post is about fixing that before you hire more people to push the work along.
Why mid-sized employers feel this more than they admit
Large companies have project offices and layers of governance. Mid-sized employers usually have neither. The same 12 people run the business and the project, and the project gets whatever time is left.
That creates a predictable pattern:
- The sponsor approves the budget and then disappears into the day job.
- The project lead has the work but not the authority to settle a dispute between operations and finance.
- Department heads agree in the meeting and then change course in the hallway.
- Problems are visible to the team weeks before they reach the owner.
That last point matters most. The people doing the work usually see the tool problems, the unclear priorities and the queue of unmade decisions first. Owners and senior leaders tend to see outside pressure: customers, markets, deadlines. Both views are correct. They just rarely meet.
Three questions every project should answer on day one
You do not need a framework with a logo. You need written answers to three questions, agreed by the people named in them.
- Who is accountable for the outcome? One name. Not a committee.
- Who decides each type of question? Scope changes, spend over a set amount, vendor choice, hiring, go-live timing. List them.
- Who do people escalate to, and by when? A blocker with no deadline is just a delay with a nicer name.
Put it on one page. Review it at the first meeting and again at each major phase. If two people think they own the same decision, you have found the problem early and cheaply.
Habits that hold up under pressure
Teams that deliver complex work tend to do a few plain things consistently.
- Agree on success before work starts. The sponsors define what done looks like, in measurable terms, while the project is still cheap to change.
- Schedule stakeholder time around decisions. A weekly status call where everyone reports and nobody decides wastes the hour. Book short sessions at the points where choices are actually due.
- Clear blockers within days. Leaders own visibility. If a team lead raises a problem and nothing happens for two weeks, people stop raising problems.
- Make it safe to say it is late. Accountability built on blame produces good-looking reports and bad outcomes. Reward early warnings.
Where hiring fits
Sometimes the gap is not clarity. It is capacity, or a skill you do not have in the building. Be honest about which one you have.
| Symptom | Likely cause | Fix |
|---|---|---|
| Decisions drift, same issues return | Unclear ownership | Decision map, named sponsor |
| Work is clear but never finishes | Not enough hours or skill | Contract or permanent hire |
| Good work, wrong priorities | Sponsors not aligned | Reset success criteria |
Hiring into an ownership problem makes it worse. A new project manager with no authority will absorb the confusion and burn out. Define the role's decision rights first, then recruit against them.
When capacity really is short, contract talent is often the right first step for a defined project: a project or operations lead, a data or AI implementation specialist, a finance analyst for a system conversion. The key is scoping the engagement the same way you would scope the project, with a named owner, a clear end date and a handover plan so knowledge stays in the building.
On the permanent side, a GTA food manufacturer we worked with hired more than 20 people in 18 months across production, skilled trades and office roles. Growth at that pace only works when each role has a clear owner and a clear scope from the first day. The same principle applies to a project team of five.
What to look for in a project owner
When you hire or appoint someone to carry complex work, test for these:
- Has run work that crossed departments, not just their own area.
- Can describe a time they escalated early and what happened.
- Writes things down: decisions, owners, dates.
- Is comfortable telling a senior person a date is at risk.
Technical skill matters, but these four habits predict whether the project finishes.
What to do next
Pick one active project and write the one-page decision map this week. Name the accountable owner, list the five decisions that most often stall, and set an escalation deadline. If the map shows you are short on people or skills, decide whether you need a contract specialist for the project or a permanent hire to own it afterward.
A Traverse recruiter can help you scope the role and find the right person, whether for a defined project or a long-term seat.