Position hierarchies

Build a hierarchy using parent positions, look at the graphical view, create and edit the hierarchy there, and see where the hierarchy drives manager derivation and approvals. Demonstrate parent-position defaulting — and where it does not default. Then compare the position hierarchy against the supervisor hierarchy for manager derivation. Position hierarchy versus supervisor hierarchy is a real design choice, not a preference. The position hierarchy is structural and survives people leaving; the supervisor hierarchy is per-assignment and more flexible. Where positions are used seriously, the position hierarchy is usually right — because otherwise the client is paying the position maintenance cost and not taking the benefit. And orphan positions break the hierarchy silently. Report on them regularly: it is a query somebody should own, not a thing to notice.

In this module: Module 6 · Jobs and Positions

1. 1The decision that shapes everythingFree preview
2. 2Jobs and job catalogue design
3. 3Job and position structures
4. 4Creating jobs
5. 5Positions: what they add
6. 6Creating positions
7. 7FTE, work hours and workday defaults
8. 8Position synchronization
9. 9Configuring position synchronization
10. 10Position hierarchies
11. 11Evaluation criteria and valid grades
12. 12Position approvals
13. 13Loading workforce structures by spreadsheet
14. 14What breaks
15. 15Lab briefing: one model, or two?