Study the ADSPM by practising integrated decision-making, not topic-by-topic recall. For each syllabus area, write a short decision memo that names a framework, applies it to a specific organisational context, connects it to at least one other people-policy area, and flags one ethical or evidence limitation. Administrative details for the credential sit with the CIPD; this guide focuses on how to think and write at the strategic level the subject demands.
Choosing between best-practice and best-fit people strategies
Strong answers distinguish universalist 'best-practice' claims from contingent 'best-fit' reasoning, then argue which lens suits the scenario. A recommendation that ignores the organisation's strategy, lifecycle and sector reads as generic rather than strategic.
Best-practice thinking holds that certain commitments, such as investment in learning, voice and involvement, or selective hiring, benefit organisations broadly, and that policies work as bundles rather than in isolation. Best-fit (contingency) thinking counters that the right people strategy depends on the competitive strategy, maturity and environment of the organisation: a scale-up chasing rapid market entry and a public service facing budget constraint need different choices even with identical goals.
In writing, apply the distinction by naming your lens and showing its cost. If you argue for a high-commitment bundle in a cost-driven turnaround scenario, acknowledge the affordability tension and mitigate it. If you argue best-fit, state explicitly which strategic condition drives the fit, so the marker can see reasoning rather than assertion. This habit turns every policy question into a strategy question, which is the level of argument this subject expects.
Workforce planning: supply, demand and gap analysis in scenario decisions
Workforce planning means estimating future demand for people and skills, auditing current supply, and closing the gap through build, buy or borrow options. Treating it as a recruitment task is the most common conceptual shortcut in scenario work.
Demand analysis asks what roles, capabilities and numbers the strategy requires, ideally under two or three scenarios rather than one forecast. Supply analysis audits the current workforce and its likely movement: internal capability, attrition risk, retirement patterns and skills nearing obsolescence. The gap between the two is then closed through building capability (development and redeployment), buying it (hiring), or borrowing it (contractors, partners, automation choices), each with different cost, risk and time profiles.
Worked scenario: a healthcare group opens two regional clinics in twelve months and must staff them. A plausible mistake is to answer 'run a recruitment campaign and offer signing bonuses', which treats planning as hiring. The better decision runs the sequence: model demand for each clinic's skill mix under slow and fast ramp-up scenarios; audit supply in adjacent existing sites for redeployable senior staff; then choose build for routine roles through an academy pipeline and buy for scarce specialists, with borrow as a bridge. It matters because the recruitment-only answer ignores attrition risk and internal capability, so it cannot explain whether the plan is affordable or sustainable.
Telling organisation design apart from organisation development
Organisation design changes structure, roles, and reporting lines; organisation development changes culture, capability and how people work together. Scenarios often demand both, and answers that name only one usually address half the problem.
Design is the deliberate configuration of structure: spans of control, layers, matrix relationships, centralisation, and where decisions sit. Development is the planned, participative change of behaviours, culture and capability, often through leadership work, team interventions and dialogue. They differ in pace, in typical methods, and in who is involved: design can be announced, development generally cannot. Confusing them produces answers that draw a new chart for a culture problem, or run workshops for a span-of-control problem.
Use the table below as a self-test whenever a scenario describes an organisational change. Then link the two deliberately: for example, moving to a flatter, more customer-aligned structure (design) will only deliver if manager capability and decision norms change alongside it (development). Stating that dependency explicitly is the kind of horizontal connection that lifts a section from descriptive to strategic, because it shows you understand interventions as a system rather than a menu.
| Dimension | Organisation design | Organisation development |
|---|---|---|
| Object of change | Structure, roles, decision rights | Culture, behaviours, capability |
| Typical levers | Layer and span changes, reconfiguration, role clarity | Leadership development, team interventions, dialogue and feedback |
| Speed and mode | Can be decided and announced centrally | Gradual, participative, negotiated |
| Common mismatch | Drawing a new chart for a culture problem | Running culture workshops for a structural problem |
Reward and performance decisions where incentives fight the strategy
Strategic reward means aligning pay, benefits, recognition and development with the behaviours the strategy needs. A worked scenario shows how an individually competitive performance system can quietly undermine a collaboration-based strategy.
Concepts to keep distinct: total reward (the whole package of pay, benefits, learning and meaningful work), extrinsic versus intrinsic motivation, and performance management as a continuous cycle of expectation-setting, feedback and development rather than an annual rating event. Horizontal fit is the test that matters here: does the reward system pay for the behaviours the organisation says it values, or for something else?
Worked scenario: a technology firm states that cross-team knowledge sharing drives its product strategy, yet ranks employees on a forced curve with individual bonuses. A plausible mistake is to recommend only market benchmarking and pay-ratio adjustment, which treats reward as a compensation exercise. The better decision diagnoses the fit problem first: the curve rewards individual relative ranking, directly conflicting with the sharing strategy. Recommend shifting to team-based and organisation-wide elements in the mix, retraining managers for developmental feedback, and piloting in one function before scaling. It matters because benchmarking a misaligned system just makes the wrong incentives more competitive.
Reading HR analytics without over-claiming: leading versus lagging evidence
Analytical answers should classify measures as leading or lagging indicators, question whether data supports cause, and acknowledge data quality limits. Presenting a dashboard as proof of impact is a reasoning error, not a technicality.
Lagging indicators, such as turnover, absence or engagement survey results, describe what has happened. Leading indicators, such as offer-acceptance rates, internal-mobility rates or manager-communication measures, give earlier signals you can act on. Distinguish human capital metrics from proxy measures: an engagement score is a proxy for a complex state, so treat changes as signals for investigation. Watch for correlation presented as causation: teams with training hours showing higher productivity may differ in other ways, such as better managers who both train more and perform better.
In scenario answers, use analytics to size and evidence the case, then state its limits. For example, attrition modelling supports a retention business case, but note what the data excludes, such as reasons for leaving or the quality of leavers. Pair quantitative signals with qualitative evidence, such as exit-interview themes or focus-group findings, and specify what you would monitor to test whether an intervention works. That pattern, evidence plus stated limitation plus a feedback loop, demonstrates the evidence-based reasoning the subject is built on.
Applying an ethics and compliance lens to people decisions
Every strategic recommendation carries ethical duties: fairness and non-discrimination, transparency, privacy, and respect for consultation and employee voice. Compliance obligations vary by jurisdiction, so scenarios are best reasoned through principles you name explicitly.
Build a short ethics check you can apply to any recommendation: Does the decision treat affected groups equitably? Would affected employees consider its basis transparent and its process fair? What personal data does it use, and is that use proportionate and lawful in context? Does it preserve employee voice and meaningful consultation where change affects people? Employment-rights requirements differ across countries and change over time, so in scenario work the disciplined move is to flag 'subject to local employment law and current guidance' and identify what you would verify, rather than asserting rules you cannot confirm.
Worked scenario: a global firm plans to use productivity analytics drawn from workplace systems to identify low performers. A plausible mistake is to accept the tool's efficiency case and design the rollout. The better decision pauses at the ethics check: the data may function as covert monitoring, the proxy measures may be biased against roles or working patterns, and the use case may conflict with privacy expectations and local data-protection duties. Recommend narrowing the purpose to aggregate, team-level improvement, informing employees, involving representatives, and taking legal advice per jurisdiction before any individual use. It matters because the same dataset can support capability building or become a trust-destroying surveillance programme, and the distinction is a design choice you are being asked to make.
A preparation sequence and self-check rubric for integrated answers
Prepare by cycling through the six topic areas against one ongoing case organisation, writing a decision memo per topic, then combining topics in timed practice. Use the rubric below as a learning milestone, not a score prediction.
Work through a repeatable loop. First, choose a case organisation with public information, such as a company expanding, restructuring or digitising, so every topic has the same context. Second, for each topic area, write a one-page memo: the decision, the named framework and its trade-off, the horizontal link to one other policy area, one piece of evidence, and one ethical flag. Third, compare frameworks across topics using a two-column exercise, such as best-fit versus best-practice for the same memo. Fourth, finish with timed combined tasks that force workforce planning, reward and analytics into a single recommendation.
Self-check rubric (suggested milestones for your own review, not exam predictions): a memo at 'developing' names a framework correctly; at 'secure' it also states the trade-off and a horizontal link; at 'exam-ready' it adds an evidence source, an ethical flag, and a monitoring step, all within a tight word budget. Expected observations as you improve: your recommendations start citing the case's strategy instead of generic HR practice; you catch yourself writing activity lists where decisions are needed; and your ethics notes shift from vague fairness appeals to specific questions about data, process and voice.
- Sessions 1–2: map the six topic areas onto your case organisation and draft the workforce-planning memo with demand, supply and gap analysis.
- Sessions 3–4: design versus development memo, then the reward and performance memo, each with an explicit horizontal link to workforce plans.
- Session 5: analytics memo; add one leading indicator and one stated data limitation to a previous memo.
- Session 6: rewrite one memo through the ethics check, including jurisdiction-verification flags.
- Sessions 7–8: timed combined practice with the rubric, then targeted review using practice questions and the wider study guides.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.