Intraday Management: Hierarchy and skills
Objective. Understand how the org hierarchy and skill definitions scope every IDM view and action, and why a wrong or stale skill map quietly corrupts staffing, what-if and every downstream figure.
Hierarchy and skills is the structural backbone: who belongs to which team, and which skills each person can work. It is not a daily driving screen but it defines the scope and the available-skill picture that every other screen depends on.
See it in the demo
What this screen answers
'What is the shape of the operation IDM is managing, and who can actually do which work?' This is the setup layer a CSM validates rather than a floor manager drives daily. It determines how teams roll up, how views are scoped, and - critically - which skills are counted as available when staffing computes a gap or the what-if proposes a skill move.
The task
For a CSM, the task is validation: confirm the hierarchy reflects the real reporting and operational structure, and that skill definitions and assignments match who can genuinely work which queue. This is a foundational onboarding and periodic-review check. For sales, it is awareness - enough to explain that IDM's accuracy rests on this structure being right, without over-promising on setup detail.
How to read it
Treat this as the foundation that silently governs everything else. The classic failure is not a misread of this screen but trusting staffing and what-if figures while the skill map behind them is stale - someone marked skilled who is not, or a team structure that no longer matches reality. If the hierarchy or skills are wrong, 'available' is wrong, the staffing gap is wrong, and every what-if built on it is wrong, with no visible symptom on the day-of screens.
Honest limits
This screen defines structure; it does not verify that definitions are current - that is a human validation task. How skills are modelled, who maintains them and how changes propagate are production-dependent - confirm with product and keep the customer's own org and skill source as the reference. Exact hierarchy and skill fields and the demo content are SME-validation-pending.
Interpretation check
A stale or wrong skill map has no visible symptom on the day-of screens but silently corrupts 'available', the staffing gap and every what-if - validating hierarchy and skills is the foundation that makes those figures trustworthy.
In the field
KnackGlobal (RCM, ~6,000 seats): at that scale an out-of-date payer-skill map makes every staffing gap and skill-move simulation unreliable - which is why validating the skill structure is the first CSM job, not an afterthought.
Practical task
On the demo, inspect one team's skill assignments and write a one-line validation question you would put to the customer to confirm the skill map is current before trusting any staffing or what-if figure.
Self-check
Staffing shows a skill as adequately covered. What upstream condition must hold for that to be true?
The skill map must be current and correct - the right people marked as able to work that queue. If the map is stale, 'covered' is wrong even though the staffing screen shows no symptom.
Why is this screen a CSM validation task rather than a daily driving screen?
It defines structure that changes infrequently but governs everything downstream. It is validated at onboarding and periodically, not driven minute to minute like the tower or forecast.
A what-if proposes a skill move that looks ideal. What could make it a bad call despite a clean projection?
An inaccurate skill assignment - the person moved may not truly be able to work the target queue. The projection trusts the skill map; if that is wrong, the move fails in reality.
Why is a skill-map error more dangerous than a visible day-of error?
It is silent - the day-of screens show no symptom, so figures look trustworthy while being wrong at the root. Visible errors get investigated; silent structural ones get believed.
Verified vs demo. Screen is live in the demo at /#/org; exact hierarchy and skill fields, maintenance ownership and propagation are SME-validation-pending.