Most hiring plans start with a list of titles. A backfill here, two analysts there, a project coordinator because the last project ran late. The list gets approved, the roles get filled, and six months later the work is still slow.
The problem is rarely the people. It is usually that the team around them was never designed for the work in front of it.
Start with the work
Before you write a job description, answer three questions:
- What outcome is this team responsible for?
- Which skills does it need to deliver that outcome without asking another department for permission?
- Is the work continuous, or does it come in defined batches?
The answers point toward a structure, and the structure tells you what to hire.
Two common structures
Most mid-sized employers end up choosing between two models, or running both.
The standing cross-functional group. A small team owns a product, a customer segment, a production line or a business process from start to finish. It holds every skill it needs. Think of a data engineer, an analyst, an operations lead and a business owner working as one unit on a reporting and forecasting function.
The time-boxed delivery team. Work is planned in short fixed cycles, usually 1 to 4 weeks, then reviewed before the next cycle starts. The cadence gives leaders predictability and a regular point to change direction.
They are not rivals. A standing group often runs its work in short cycles. The question is whether ownership sits with the team permanently or only for the length of a task.
| Question | Standing group | Time-boxed team |
|---|---|---|
| Who owns the result? | The team, ongoing | The team, per cycle |
| Best for | Continuous work | Work that splits into increments |
| Main risk | Gaps if one skill is missing | Dependence on other teams |
What this means for hiring
Structure changes the profile you recruit for.
A standing group needs breadth. Each person carries more of the outcome. You want people who are comfortable making decisions without a hand-off, and who can cover for a colleague on a bad week. One missing skill stalls the whole unit, so a single vacancy hurts more than it would in a departmental model.
A time-boxed team needs reliability and communication. People must estimate honestly, say what is blocked and finish what they committed to. Strong planners and clear communicators matter as much as technical depth.
Both need someone who keeps the work moving. Whether that is a project manager, a scrum master or a capable operations lead depends on size and complexity. A team of 5 usually does not need a dedicated person. A group of 4 teams working on connected deliverables usually does.
Where this shows up outside software
This is not only an IT conversation. The same thinking applies across the areas we recruit in.
- Operations: a process improvement group with an analyst, a supervisor and a finance partner will move faster than three departments passing a request along.
- AI and data: a model is only useful when the people who build it sit close to the people who use it. Pairing a data scientist with a domain expert beats a central team that takes requests.
- Manufacturing: a line team with production, maintenance and quality in the same daily huddle finds problems sooner than one that escalates through a chain.
- Finance: a month-end close team with clear ownership of each step closes faster than one that relies on e-mail chasing.
- Sales: pairing an account lead, a sales engineer and an operations contact on key accounts reduces the delay between a promise and its delivery.
Contract talent fits some structures better than others
Time-boxed work is where contract hiring earns its keep. If a deliverable has a clear scope and an end date, a contractor with the right skills can join a cycle quickly and leave when it is done. Standing groups are different. Ownership is the point, so the core should be permanent, with contractors filling a specific gap such as a short migration or a peak period.
Warning signs your structure is wrong
- Simple tasks need approval from three people.
- Nobody can say who owns a result when it goes badly.
- The same hand-offs cause the same delays every month.
- You keep hiring for coordination roles to patch over the gaps.
If you recognize two or more, adding headcount will not fix it. Redraw the team first.
What to do next
Pick one piece of work that is slower than it should be. Map who touches it, where it waits and who answers for the result. Then decide which skills need to sit together and which can stay shared. Write the requisition after that, not before.
If you want a second opinion on the roles a team design calls for, or help filling them on a permanent or contract basis, a Traverse recruiter can help.