Reason the role-to-person assignment for the engagement
Reasons a concrete named assignment — who fills which role, with capacity and fit justification — from the engagement's role slots and the candidate producers' current commitments.
In / outRole slot definitions + candidate roster with commitments + skill/domain fit requirements → Named assignment per slot with justification and second-choice fallbacks
You might say…
“I've got five roles and eight potential people, but three of them are at capacity, two don't have the domain depth, and the remaining three overlap on the slot I care most about — I need a reasoned call, not a spreadsheet.”
What it does
Given the engagement's defined role slots, the candidate internal producers with their current commitments, and the skill/domain fit each role demands, reasons to a concrete named assignment per slot — who fills what, with the justification (capacity headroom, level match, domain fit) and any second-choice fallback. Used at the core staffing decision when matching named internal people to the defined roles on this specific engagement.
Trigger: Use when you have defined role slots and a pool of internal producers and need a defensible staffing decision before the project kicks off.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation