Most institutional professional development strategies are written to be filed, not used. They read well in a committee paper, list an impressive catalogue of workshops, and quietly fail to change anything, because they were designed around what is easy to deliver rather than what staff actually need. For any leader — head of department, dean, HR director, or educational-development lead — the challenge is not producing a document but producing a strategy academics engage with and that demonstrably improves capability.
This is a policy and governance problem as much as an educational one, and the principles hold whether you lead a research-intensive university in the UK, a teaching college in the Philippines, or a rapidly growing institution in Nigeria or India. This guide walks through designing a staff development strategy from needs analysis to embedded evaluation — one that earns engagement instead of demanding it.
Why most PD strategies fail
The common failure pattern is recognisable. A strategy is written top-down, launched with a catalogue of generic workshops scheduled at inconvenient times, made nominally mandatory, and then measured only by attendance numbers. Academics comply minimally, learn little, and quietly resent the time. Within a year the strategy is a document no one references and a set of half-empty sessions.
The root causes are consistent: no genuine needs analysis, so the offer misses real gaps; no respect for academic workload and autonomy, so participation feels imposed; and no evaluation beyond headcount, so no one can tell whether anything improved. A strategy that ignores these is destined to be performative. Designing against them — need-led, workload-aware, and impact-evaluated — is the whole task. For the sector context, see our Sector & Policy hub.
Grounding the strategy in a real needs analysis
A credible strategy begins by finding out what staff actually need, from multiple angles rather than assumption. Triangulate several sources: institutional priorities and any regulatory or quality-assurance expectations; aggregated data such as student feedback, promotion outcomes, and where staff struggle; and — critically — direct input from staff themselves through surveys, focus groups, and conversations with early-career, teaching-focused, and research-intensive colleagues alike. Different groups have genuinely different needs, and a one-size strategy serves none of them well.
Distinguish felt needs (what staff say they want), normative needs (what standards require), and comparative needs (gaps relative to peer institutions). The strongest strategies address all three and are explicit about the evidence behind each priority, which also makes them far easier to defend in governance. Where external standards apply, anchor to recognised frameworks such as those from Advance HE, and align individual development with the CPD compliance obligations staff already carry so the strategy reduces their burden rather than adding to it.
Building a framework, not a catalogue
A catalogue of workshops is not a strategy; a framework is. The difference is that a framework organises development around capabilities and career stages rather than around whatever sessions happen to be available. Structure it by the domains that matter — teaching and learning, research and impact, leadership and management, digital capability, and wellbeing — and by career stage, so an early-career researcher and a senior academic find distinct, relevant pathways rather than the same generic menu.
Crucially, a framework should map to things staff already care about: promotion criteria, teaching recognition, and professional-body requirements. When development visibly advances a promotion case or satisfies a mandatory CPD cycle, engagement follows without coercion. Tie the framework explicitly to the academic career ladder so staff see development as investment in their progression, not a compliance tax. AcademicStaff's staff development planner lets institutions build such a framework and let individuals map their own pathway through it against their goals and obligations.
Delivery models that fit academic reality
Even a perfect framework fails on delivery if it ignores how academics actually work. Rigid, all-day, fixed-time workshops collide with teaching, fieldwork and research deadlines, guaranteeing low attendance and resentment. Effective delivery is flexible and blended: short asynchronous modules, communities of practice, mentoring and peer observation, action-learning sets, and just-in-time resources staff can reach when a need arises rather than when a session is scheduled.
Respect autonomy in the design. Adults, and academics especially, learn best when they have agency over what and how they learn. Offer pathways and choice rather than a single mandated route, embed development into real work — a course redesign, a grant application, a leadership project — so it produces something useful, and make expert help available at the point of need. Delivery that fits the rhythm of academic life is the difference between a strategy that is used and one that is endured. This connects to the workload and wellbeing agenda directly.
Evaluating impact beyond attendance
Attendance counts nothing about whether capability improved, yet it is the only metric most strategies collect. Serious evaluation works at several levels: did participants react well, did they learn, did their practice change, and did that change show up in outcomes such as student experience, research success, or retention. The higher levels are harder to measure but are the only ones that justify the investment.
Build evaluation in from the start rather than bolting it on. Define what success looks like for each priority before you deliver anything, choose a small number of meaningful indicators, and collect follow-up evidence months later — because behaviour change appears well after a session ends, not on the exit survey. Feed the findings back into the next cycle of needs analysis so the strategy keeps improving. National regulators increasingly expect this kind of evidence of staff-capability assurance; frameworks published at ukri.org and equivalent bodies assume institutions can demonstrate it.
Embedding the strategy so it survives
A strategy that depends on one champion dies when that person moves on. Embedding means building it into the institution's routines: into induction and probation, into appraisal and promotion criteria, into departmental planning and budgets, and into leadership accountability. When development is part of how the institution normally runs, it survives leadership changes and budget cycles.
Secure genuine ownership at multiple levels — senior sponsorship for resources and legitimacy, departmental leadership for local relevance, and staff voice for continued buy-in. Review the whole strategy on a defined cycle against its evaluation evidence, and be willing to retire what does not work. AcademicStaff's staff development planner supports this by giving leaders visibility of participation and progress across the framework, and by letting the strategy evolve from evidence rather than assumption. For the individual counterpart to this institutional view, see our guide to reskilling and micro-credentials.
The Staff Development Strategy Blueprint
A step-by-step blueprint with needs-analysis templates, a capability-and-career-stage framework, delivery-model options and a multi-level evaluation plan to build a PD strategy staff actually use.
Want the full article?
Enter your email for free access to the rest of this guide and our TEQSA resource library.
Frequently asked questions
Why do most staff development strategies get ignored?
Because they're written top-down without a real needs analysis, delivered as generic workshops at inconvenient times, made nominally mandatory, and measured only by attendance. Design against all four — need-led, workload-aware, choice-based, and impact-evaluated — and engagement follows without coercion.
How do we get busy academics to actually engage with development?
Map it to what they already care about — promotion criteria, teaching recognition, professional-body CPD — and deliver it flexibly through short modules, communities of practice and just-in-time resources. When development visibly advances a career or satisfies a mandatory cycle, participation stops being a chore.
How should we measure whether a PD strategy works?
Go beyond attendance. Define success before delivery, then measure reaction, learning, changed practice and downstream outcomes like student experience or research success. Collect follow-up evidence months later, because behaviour change appears well after a session ends, and feed it into the next cycle.
The AcademicStaff editorial team writes practical, evidence-based guidance for university staff — drawing on sector reporting, funder guidelines and the lived administrative reality of academic work. Every guide is reviewed for accuracy against current Australian higher-education practice.