Position Management vs Jobs: Choosing Your Foundation Deliberately
Position management or job-based? This foundational choice shapes your whole HCM. Pick for how your organisation actually runs, not fashion.
One of the earliest and most consequential decisions in a Core HR build: position management or a simpler job-based model. Get this wrong and you're fighting the foundation for years. It's not about which is 'better', it's which fits how your organisation actually runs.
Position management suits structured, budgeted orgs
If you have defined positions with headcount budgets, public-sector style establishment control, and roles that persist regardless of who fills them, position management gives you that control. It's heavier to maintain but gives real establishment discipline.
Job-based suits fluid, fast-moving orgs
If your organisation is more fluid, roles created and changed quickly, less rigid headcount control, a job-based model is lighter and less administrative overhead. Forcing position management onto a fast-moving company creates bureaucracy people route around.
Decide before you build, not after
This is genuinely hard to change once you're live and transacting against it. Model both against your real operating style up front and commit deliberately.
Real scenario: a fast-growing client was sold full position management because it sounded rigorous. Within a year they were drowning, every new role needed a position created and budgeted before they could even recruit, and they were moving too fast for it. We'd have saved them a painful migration by choosing job-based from the start. Match the foundation to the organisation, not to what sounds impressive.