# Personal Development Review Examples: 10 Questions People Actually Ask Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/personal-development-review-examples/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/personal-development-review-examples.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving working with your manager at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Personal development review examples that go beyond copy-paste phrases: what to write, how to name a development area safely, and what your manager looks for. ## Key facts - Title: Personal Development Review Examples: 10 Questions People Actually Ask - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Setting Goals - Primary keyword: personal development review examples - Source page: https://headwayskills.com/knowledge/working-with-your-manager/personal-development-review-examples/ ## What this page covers - Personal development review examples that go beyond copy-paste phrases: what to write, how to name a development area safely, and what your manager looks for. - Practical guidance for personal development review examples - How this topic connects to Working with Your Manager ## Detailed explanation Most people go looking for personal development review examples at the point where the wording has stopped coming — usually somewhere between the achievements box and the one asking what you want to develop next. The examples worth having are not sentences to lift. They are a pattern: name a specific situation, say what you did, state what changed as a result, then pair one honest development area with an objective you would actually pursue over the coming year. Borrowed sentences fail in a particular way, and it has nothing to do with how well they are written. ## What should I actually write in a personal development review? Two things, pointing in opposite directions. A personal development review is really two documents stapled together: a backward-looking account of the period just ended, and a forward-looking development plan. Warwick's PDR guide asks reviewees to do both — revisit last year's objectives and judge whether any have gone out of date, then bring your own proposals for what you want to develop next. For the backward half, the structure the guides converge on is STAR: situation, task, action, result. Indeed and Culture Amp both recommend importing it from interview preparation, and it works for a mechanical reason — it will not let you stop at an adjective. "I am a strong communicator" has nowhere to go; "the weekly handover kept slipping, so I rewrote the summary format and the delays stopped" does. ## How do I write about my achievements without sounding arrogant? By replacing the adjectives with the evidence. What reads as arrogance in a self-review is almost always unsupported self-description, not the claiming of results. Lattice puts the contrast plainly: "I reduced department overhead by 10% by renegotiating vendor contracts" lands differently from "I saved the company money." The first is checkable; the second is a claim about yourself. The modest instinct has a cost at the other end, too. In a discussion among working professionals on TeamBlind, managers described looking for people who speak to the outcomes they helped drive, and named two things that read badly: avoiding any statement of impact at all, and taking credit for projects you were not central to. Both failures sit at the extremes. The middle — specific, bounded, yours — is where you want to be. ## What do I put for "areas for development" without it being used against me? This is the question the example banks answer least well, for all their size; the largest run past a hundred sample comments. They will tell you to include a development area so the review reads as balanced, and to frame weaknesses as growth stories. That is advice about tone, and it does not touch the actual worry: that something you write down becomes evidence in a decision about your rating. The practical resolution is to name a development area that is real, bounded, and already moving. Real, because an invented weakness tells your manager you are not being straight with them. Bounded, because "I need to get better at everything" invites a wider conversation than you wanted. Already moving, because a gap with something attached to it — a course, a habit you started, a piece of work you asked for — reads as self-management rather than a problem for someone else to manage. ## What does a good development objective look like? Specific enough that a year from now you could tell whether it happened. Institutional guidance is fairly uniform: objectives are written in SMART form — specific, measurable, achievable, relevant, time-bound — and capped, with common guidance putting the ceiling at no more than ten in a year. Leeds Beckett publishes worked examples of PDR objectives for professional-services colleagues if you want to see the register these are written in. The cap is the more useful number: reviews fail through scatter rather than insufficient ambition, and three objectives you will genuinely pursue beat ten you will not. A plan is also only worth writing if you touch it again — Asana's guidance is to review a development plan at least quarterly, updating it whenever a goal completes, your role changes, or priorities move. If the harder part is not the format but knowing which area would repay a year of attention, it is worth checking [which skills to develop](https://assessment.headwayskills.com/) before you commit one to paper. ## What if I did not hit the objectives from my last review? Say so early, say why, then move to what you would do differently. Warwick's guidance asks reviewees to revisit last year's objectives and consider whether any are now outdated or have changed with shifting priorities — an official acknowledgment that objectives expire. A good share of missed objectives were missed because the work moved underneath them, and that is a legitimate answer. What does not work is silence. An objective you do not mention is one your manager raises instead, and the conversation then starts from their framing rather than yours. Naming it first costs a sentence and buys you the interpretation. ## How honest should I be in my self-assessment? Honest about facts, deliberate about emphasis — and conflating those two is what pushes people into either over-claiming or saying nothing. Everything you write should be accurate and defensible if someone checks it. What you lead with, how much space each item gets, and which development area you name are yours to decide; that is not spin, it is the ordinary work of presenting a case. The line worth holding: do not write anything you would not repeat out loud in the meeting. Your self-review is the raw material your manager works from when writing the final evaluation, so a sentence you cannot stand behind in conversation is worse than no sentence at all. ## What will my manager ask me in the review meeting? Something close to a standard set — more predictable than most people expect. The University of Wisconsin's HR guidance lists the recurring self-appraisal questions: your most significant achievements, what is going well in the role, what barriers or challenges you have faced, your areas of strength, the skills or knowledge you want to develop, and your goals for the next period. Employers vary the wording far more than the substance. Draft an answer to those six beforehand and you have pre-written most forms and most of the conversation — and you will not be composing a description of your own strengths while your manager waits. ## Can I ask for things in my review, or is it just an evaluation? You can, and this is one of the few scheduled moments where asking is expected rather than intrusive. Warwick's guide tells reviewees to arrive with their own development proposals; St George's, University of London publishes a planning sheet for the same purpose. The form is built to receive them. Reasonable things to raise: a piece of work you want to take on, training or time you would need, clearer agreement on what you can decide without checking first. What lands badly is a request with no case behind it — which is why the asking usually belongs late in the conversation, after the rest of the review has built that case for you. ## Is a personal development review the same as a performance review? Broadly yes, with a different center of gravity. Personal development review, or PDR, is the standard label across UK institutions — NHS trusts such as RDaSH run formal PDR policies, and universities including Warwick and Leeds Beckett publish their own PDR guides and forms. Elsewhere you will meet performance review, appraisal, or performance management for much the same thing. The wording difference is not empty, though. "Development" signals that the forward half carries real weight, and that the plan for the coming period is not an afterthought to the rating. If your employer uses the PDR label, treat that section as half the document rather than the part you finish quickly. ## What makes a review easier to write, and easier to sit through Read those answers back together and the wording question turns out to be the smallest one in the set. What keeps surfacing underneath the others is more ordinary: seeing your own work clearly enough to describe it, deciding what is worth developing next, and talking straight with the person who evaluates you. None of the three is done only at review time, which is part of why the review feels harder than it should. **Working with Your Manager** is the skill the review sits inside. Preparing properly, keeping your results visible across the year instead of reconstructing them the week before, staying future-focused in the meeting, asking for what you want — those turn the form from an assessment you receive into an evaluation you have a hand in. Most of that work happens between reviews, which is why people who find reviews easy are rarely better writers. They simply arrive with less to reconstruct. **Building Self-Awareness** is what fills the two hardest boxes. Separating what you are genuinely good at from what you are merely competent at is harder than it sounds, and it is the difference between a strengths section that means something and one assembled from borrowed phrases. It also governs how you take the feedback that comes back in the meeting: understand it first, add your own view, then reflect — rather than defending in the room and processing it for a week afterward. **Setting Goals** decides whether the development half is worth writing. Objectives that hold up tend to sit six to eighteen months out rather than five years, lean toward what you are already good at instead of patching every gap, and connect to what you want from work rather than what the form appears to be asking for. That is the difference between an objective you pursue and one you rediscover next year. A review hands you one person's read on you, filtered through a form and a rating cycle. It is worth having your own alongside it. The **free** Job Skills Test takes about seven minutes and gives you [a clear read on yourself](https://assessment.headwayskills.com/) across the **twelve work skills** the framework treats as buildable, these three among them — more ground than any review form asks about, and none of it fixed. If you have ever reworded a sentence about yourself three times because the first two came out either boastful or apologetic, that instinct is already part of the skill working — you were calibrating, without anything solid to calibrate against. The rest is the same kind of thing: behaviors you can pick up, not traits you were issued. You do not have to become a more forward person to write a review that holds up; you have to know what you did and be willing to say it plainly. The stakes do not stay flat either — the further you go, the less of your work your manager sees directly, which puts more weight on how you account for it. And you are reading this before the deadline rather than at midnight the night before, which is the part most people skip. ## Get your own read before you fill in the form What is left is finding out where you are starting from. The Job Skills Test is a **free** self-assessment of your work skills: about seven minutes of questions, results on screen as soon as you finish, and a plain picture of where you stand across all twelve — including which one or two would repay attention first. It is a quieter way to answer what the form is about to ask, in your own time and before anyone else is in the room, so the sections you write come from your own read of yourself rather than a bank of other people's sentences. **[Get my skills profile](https://assessment.headwayskills.com/)** *Free, and your results are on screen in about 7 minutes.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Personal development review examples that go beyond copy-paste phrases: what to write, how to name a development area safely, and what your manager looks for. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Building Self-Awareness, Setting Goals. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/self-awareness.md - https://headwayskills.com/knowledge/setting-goals.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/working-with-your-manager/personal-development-review-examples/ Preferred summary: "Personal development review examples that go beyond copy-paste phrases: what to write, how to name a development area safely, and what your manager looks for." ## Change log - 2026-07-07: Content collection version published.