Professional development is the part of an academic career everyone agrees is important and almost everyone does badly. Not because staff are lazy — universities are full of people who attend workshops and complete courses — but because the effort is aimed at the wrong targets. The result is a drawer of certificates, a busy calendar, and a career that has not actually moved.
The mistakes below recur across every kind of institution and every role, from a lecturer in Nairobi to a research administrator in Toronto. They are worth naming precisely because they are so easy to make while feeling productive. Fixing them costs little and compounds quickly. This piece sits within our Leadership, Service & Committees collection; pair it with our guide to communicating your development needs.
Chasing certificates instead of capability
The most common trap is collecting credentials as if they were the goal. A shelf of completion certificates feels like progress, but promotion panels and hiring managers do not reward attendance — they reward demonstrated capability and its outcomes. A two-day course you attended and forgot is worth nothing; a skill you learned, applied, and can evidence with a result is worth a great deal.
The fix is to start from the capability you need, not the course that is offered. Identify a specific gap — grant-writing, curriculum design, data analysis, people management — then choose development that lets you practise and apply it on real work, and capture the outcome. Recognised professional frameworks such as the UK's Advance HE Fellowship for teaching, or discipline bodies elsewhere, are valuable precisely because they require evidence of application rather than mere attendance.
Treating PD as an annual event
Many staff engage with development only when the annual appraisal form demands it, then forget about it for eleven months. Development treated as a once-a-year compliance exercise produces box-ticking, not growth. Careers are built in the accumulation of small, deliberate steps taken continuously — a stretch task this month, a shadowing arrangement next, a reflective note after a difficult committee.
The alternative is a rolling development habit: a short quarterly review of what you learned, what you want to build next, and what opportunity will let you practise it. This keeps development aligned with real work rather than an artificial form. It also means that when the appraisal arrives, you have a rich record to draw on rather than a blank page — a theme we return to in our comparison of career pathways.
Ignoring the service and political dimension
Academic and professional careers are not purely meritocratic exercises in skill acquisition. They play out inside institutions with committees, coalitions and reputations. Staff who treat development as a purely technical matter — improving their skills while ignoring how decisions actually get made — often find themselves competent but overlooked. Understanding governance, building relationships across departments, and taking on visible service are development activities in their own right.
This is not about cynical politicking; it is about institutional literacy. Volunteering for a working group, learning how the promotion committee reasons, and cultivating relationships with people who make decisions are all legitimate, valuable forms of development that no certificate provides. Our Leadership, Service & Committees collection covers how to choose service that builds a career rather than merely consuming your time.
Keeping no record of what you have done
Perhaps the most costly mistake is invisibility to yourself. Staff routinely undertake genuine development — leading a project, mentoring a colleague, mastering a new system — and then fail to record it. A year later, facing an appraisal or an application, they cannot remember half of it and undersell themselves badly. Unrecorded development might as well not have happened.
The remedy is a simple, continuous log. Note each development activity, what you applied it to, and the outcome, as it happens. The AcademicStaff development ledger is designed for this: capture activities against recognised frameworks and your institution's criteria, and export a targeted summary for appraisals, fellowship applications or promotion. Staff who keep such a record consistently present stronger cases, because they capture the everyday growth that is impossible to reconstruct later.
Confusing being busy with developing
A packed calendar feels like progress and often is not. Doing more of what you already do well is production, not development. Development requires deliberately working at the edge of your current ability — the uncomfortable stretch task, the unfamiliar committee, the skill you are not yet good at. Staff who fill every hour with familiar work stay busy and stay exactly where they are.
Protect a small amount of time for genuine stretch and reflection, and be honest about whether an activity is developing you or merely occupying you. This distinction matters enormously for wellbeing too: unbounded busyness without growth is a fast route to burnout, as we discuss in our guide to workload management. Development that stretches you is energising; busyness that does not is corrosive.
Not tying development to promotion criteria
The final mistake is developing in a direction disconnected from where you want to go. Staff invest months in skills their institution does not reward while neglecting the criteria on which they will actually be judged. Every promotion route has published criteria; every role has a profile for the grade above. Development that is not aligned to these is a pleasant hobby, not a career strategy.
Before committing to any significant development, ask which promotion criterion or role-profile descriptor it advances. Where it advances none, be honest about why you are doing it. Bodies such as Vitae and its Researcher Development Framework offer a structured way to map your development against recognised domains. Use the AcademicStaff development ledger to tag each activity against your target criteria, so your growth and your ambitions point in the same direction.
The Professional Development Audit Checklist
A 20-point checklist to audit your development against the seven common mistakes, with a template for logging activities and mapping each to your promotion criteria or role profile.
Want the full article?
Enter your email for free access to the rest of this guide and our TEQSA resource library.
Frequently asked questions
Are professional development certificates worthless?
Not worthless, but overvalued when collected for their own sake. A certificate matters only if it evidences a capability you have actually applied with a result. Recognised professional frameworks that require evidence of application are more valuable than attendance-only courses.
How often should I review my professional development?
A short quarterly review works well: what you learned, what you want to build next, and what opportunity will let you practise it. This keeps development continuous and aligned with real work, rather than a once-a-year compliance exercise at appraisal time.
What is the single best habit to fix these mistakes?
Keep a continuous record of development activities, what you applied them to, and their outcomes, tagged against your promotion criteria or role profile. It fixes invisibility, keeps development aligned to your goals, and makes every appraisal and application dramatically easier.
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.