Implementing Global HR: From Enterprise Model to Live Workforce · Module 6 · Jobs and Positions
Positions: what they add
Lesson 62 of 175 · 3 min
A position is a specific seat, carrying job, department, location, grade, FTE, headcount, manager and more. Four of those do not exist on a job at all, and they are the reason the object exists: headcount and FTE limits, budgeted status, incumbent tracking, and a parent position. Vacancy as an object. An unfilled position is visible, reportable and budgetable. This is the single feature that sells positions to clients, and understanding that one sentence is understanding why anybody accepts the maintenance cost. Design the position naming scheme before creating any. Retrofitting a convention across three thousand positions is a project, and nobody funds it — so what actually happens is you live with two conventions forever. Shared positions — one position, several incumbents — are appropriate for genuinely interchangeable seats: three identical call centre roles in one team, budgeted as three. And they defeat the purpose when they become the…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Global HR: From Enterprise Model to Live Workforce, with a certificate on completion and a fourteen-day refund window.
In this module: Module 6 · Jobs and Positions
- 1The decision that shapes everythingFree preview
- 2Jobs and job catalogue design
- 3Job and position structures
- 4Creating jobs
- 5Positions: what they add
- 6Creating positions
- 7FTE, work hours and workday defaults
- 8Position synchronization
- 9Configuring position synchronization
- 10Position hierarchies
- 11Evaluation criteria and valid grades
- 12Position approvals
- 13Loading workforce structures by spreadsheet
- 14What breaks
- 15Lab briefing: one model, or two?