It's a Friday afternoon. A new brief lands from a client; a project starting in three weeks, requiring a specific combination of skills, running for six weeks. You need to staff it.
What happens next in your business?
For most agency leaders and consultancy directors, the honest answer involves some combination of: running through a mental list of who seems to be less busy, thinking of the two or three people you know have done this type of work before, and sending a message to a couple of team leads asking what capacity looks like.
It works. Sort of. But it's not resourcing. It's resourcefulness. And those are very different things.
When resourcing decisions are made from memory, a few things reliably happen:
None of these are failures of leadership. They're the predictable output of a system that stores skills data in people's heads rather than in a place the whole organisation can see.
'Skills mapping' is one of those phrases that can sound like an HR exercise; something that sits in a document that no one reads, updated once a year during a performance review. That's not what we're talking about.
Operational skills visibility means knowing, in real time, what your people can do, and having that information directly connected to the decisions you're making about who works on what.
When skills data lives in the same system as project data and availability data, the staffing question changes fundamentally. Instead of 'who do I think could do this?', you're asking 'who does the data say is best placed for this, and are they available?'
That shift sounds incremental. In practice, it opens up decisions you couldn't have made before:
A lot of project-based businesses think about resourcing primarily as a capacity problem: do we have enough people to do the work? That's a real question. But it's the easier one.
The harder, and more commercially significant, question is whether you have the right people doing the right work. Margin on a project isn't just about how much time it takes. It's about whether the people doing it are appropriately skilled for the task, not overqualified and therefore expensive for the work required.
A project staffed with a senior consultant doing work that a mid-level person could handle is a margin problem masquerading as a resourcing decision. You only see that if you're looking at skills, not just availability.
The shift from memory-based resourcing to data-driven resourcing doesn't require a management consultancy or a six-month implementation. It requires one thing: putting your people data and your project data in the same place.
When skills are mapped and visible, when availability is real-time rather than estimated, and when project assignments are connected to individual capacity; the staffing decision changes from a conversation to a query. You ask the question. The system shows you the answer. You make a better decision, faster.
And sometimes the answer surprises you. The best person for the project was someone you wouldn't have thought of. That's not a failure of instinct, it's what data is for.
When a new project brief arrives at your business, how do you decide who works on it? And how confident are you that the person you choose is actually the best fit; not just the most available, or the most familiar?
Workup connects your people, projects, and time in one intelligent platform.