Most academic development happens backwards. A generic workshop appears in the staff calendar, you attend because attendance is expected, and six months later nothing about your research practice has changed. The problem is not the workshop — it is that development was pushed at you rather than pulled from a genuine assessment of what your research actually needs next.
A needs-oriented approach reverses that logic. You start from the specific gap between where your research is now and where it must be to reach the next grant, publication, or promotion threshold — then you buy, borrow, or build only the development that closes that gap. This article shows you how to run that assessment rigorously, whether you sit in Lagos, Leeds, Nairobi, or Manila, and whatever your national funding system.
Why generic training wastes your development budget
Every academic has a finite budget of the scarcest currency in the sector: uninterrupted attention. A day spent on a course that duplicates something you already do competently is a day stolen from writing, analysis, or supervision. Generic development is optimised for the institution's reporting needs — headcount through a room — not for the marginal improvement of any individual researcher. That mismatch is why so much training feels simultaneously mandatory and pointless.
A needs-first plan treats development as an investment with an expected return. Before committing time, you ask three questions: what specific research outcome is blocked, which missing capability is blocking it, and what is the cheapest reliable way to acquire that capability? Sometimes the answer is a formal course. Just as often it is an afternoon with a colleague who runs the statistical model you need, a methods paper, or structured practice. Framing development this way also gives you a defensible case when you request funds or protected time — you are not asking for enrichment, you are removing a named bottleneck. For a broader view of how development connects to output, see our Research, Publishing & Impact guides.
Running an honest research skills audit
An honest audit separates three layers: technical skills (methods, software, statistics, instrumentation), scholarly skills (framing questions, structuring arguments, writing for target journals), and enabling skills (grant writing, project management, collaboration, data management). Rate yourself against each not in the abstract but against a concrete near-term target — the specific journal you want to publish in, the specific call you intend to answer. A skill you rate as "good" for a regional journal may be "inadequate" for a top-quartile one.
The most reliable audits use external reference points rather than self-perception alone. Register and populate your ORCID record and study the profiles of researchers one stage ahead of you: what methods do they command, what collaborations, what outputs per year? The gap between their capability set and yours is your development map. Ask a trusted senior colleague to review your last two outputs and name the single skill that, if improved, would most raise their quality. That one answer is worth more than a generic training-needs questionnaire. Our piece on raising your research output pairs well with this audit.
Mapping your gaps to funder expectations
Funders publish their expectations more transparently than most academics use. Whether you work under the US systems (NSF, NIH, and departmental tenure and promotion criteria), the UK (UKRI councils and the Research Excellence Framework), the EU (the European Research Council and Horizon Europe), or a national council in Nigeria, India, Kenya, or the Philippines, each publishes assessment criteria that map directly onto capabilities you can develop. Read the assessment rubric, not just the call. When a scheme rewards "demonstrated data management planning" or "evidence of interdisciplinary collaboration," those are named skills you either have on paper or you do not.
Build a two-column table: on the left, the explicit criteria of the two or three schemes you realistically intend to target in the next 24 months; on the right, your audited capability against each. The empty right-hand cells are your priority development list, now anchored to money and time rather than vague improvement. The cOAlition S / Plan S open-access requirements, for example, now shape what many funders expect around publishing and data sharing — a criterion easy to miss until a proposal is rejected on compliance grounds.
Building a realistic 12-month roadmap
A roadmap that lists twelve skills is a wish, not a plan. Sequence ruthlessly: pick the two or three capabilities whose absence blocks the most valuable near-term outcome, and schedule those first. Attach each to a real deliverable — not "improve statistics" but "complete the mixed-effects analysis for Paper 2 by March, using a two-day course plus three supervised practice sessions." Development tied to a live output sticks; development pursued for its own sake evaporates.
Protect the time formally. Block recurring development sessions in your calendar the way you block teaching, and treat them as immovable. Track your progress in one place so the plan does not live only in your head — AcademicStaff's publication ledger lets you log each output alongside the skills and methods it required, so over a year you can see exactly which development investments produced results and which did not. For structuring the writing that follows a skill upgrade, our guide to building a research impact portfolio is a useful companion.
Matching development to your career stage
The right development changes sharply by stage. Early-career researchers should weight technical and scholarly skills — method mastery, writing for target journals, and building a publication rhythm — because these compound. Mid-career academics typically hit a different wall: the bottleneck shifts from doing research to winning resources and leading people, so grant craft, team leadership, and mentoring move up the list. Senior staff often need development least discussed in formal programmes: strategic influence, editorial and review leadership, and translating research into policy or practice impact.
Diagnosing your stage honestly prevents a common waste — the mid-career researcher who keeps attending method refreshers because they are comfortable, while the real barrier to promotion is that they have never led a funded team. If you are still establishing your footing, our early-career pathway guide maps the specific capabilities each stage rewards.
Measuring whether development moved your research
Development without measurement is faith. Set a leading and a lagging indicator for every item on your plan. A leading indicator is behavioural and immediate — you now run the analysis unaided, you submitted the proposal on time. A lagging indicator is the outcome that matters — the paper accepted, the grant awarded, the invitation to collaborate. Review both quarterly and be willing to abandon development that is not producing movement.
Keep the review lightweight but honest. Once a quarter, spend thirty minutes comparing your plan against what actually changed in your practice and output. Most academics discover that two or three high-leverage investments produced almost all the value, and the rest was noise — which is precisely the insight a needs-first approach exists to surface, so next year's plan is sharper still. Over several cycles this becomes the most valuable professional habit you own: development that reliably converts your scarce attention into research that lands.
The Research Skills Audit Worksheet
A one-page template that maps your current capabilities against your next target grant or journal, ranks the gaps by leverage, and turns them into a sequenced 12-month development roadmap.
Want the full article?
Enter your email for free access to the rest of this guide and our TEQSA resource library.
Frequently asked questions
How is a needs-oriented development plan different from a training-needs analysis?
A conventional training-needs analysis usually surveys skills in the abstract and feeds institutional reporting. A needs-oriented plan starts from a specific blocked outcome — a target journal, grant, or promotion threshold — and identifies only the capabilities required to unblock it, then measures whether development actually produced that outcome.
I have almost no development budget. Where do I start?
Most high-leverage development costs time, not money: a methods paper, a supervised practice session with a colleague who already commands the skill, or studying the profiles of researchers one stage ahead via ORCID. Audit your two most important near-term targets, find the single blocking skill, and buy or borrow the cheapest reliable way to acquire it.
How often should I revisit the plan?
Do a full audit annually, but review progress quarterly with a thirty-minute check against leading and lagging indicators. Be willing to drop any development item that is not measurably moving your practice or output.
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.