# Performance Development Review: What It Is and What to Bring Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/performance-development-review/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/performance-development-review.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 A performance development review is a scheduled meeting where your manager assesses your work and you agree a development plan. Here's what to expect and prepare. ## Key facts - Title: Performance Development Review: What It Is and What to Bring - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Influence - Primary keyword: performance development review - Source page: https://headwayskills.com/knowledge/working-with-your-manager/performance-development-review/ ## What this page covers - A performance development review is a scheduled meeting where your manager assesses your work and you agree a development plan. Here's what to expect and prepare. - Practical guidance for performance development review - How this topic connects to Working with Your Manager ## Detailed explanation A performance development review is a scheduled meeting — usually annual or twice yearly — in which your manager assesses the work you have done over the period just ended and the two of you agree what you will develop next. It has an evaluative half and a forward-looking half, and both are on the agenda. Most people meet the term the same way: a date appears in the calendar, a form arrives with questions on it, and nobody quite explains what belongs in the boxes. The label shifts between employers — PDR, appraisal, review cycle — but the meeting underneath is standard enough that you can prepare for it properly. What varies is where the input comes from, and that is the part that decides how you prepare. ## Why the meeting has two jobs, not one The word "development" is doing real work in the name. A plain performance review looks backward and produces a judgment. A performance development review is supposed to do that and then convert the judgment into a plan — training, a stretch project, a mentor, a set of goals for the next cycle. Lattice, which builds review software, argues that developmental and performance conversations serve genuinely different purposes and that organizations need both. When they are fused into one meeting, as the name here signals, there is a predictable risk: the evaluative half consumes the airtime and the development half becomes a box ticked in the last five minutes. Knowing that in advance is most of the defense. If you want a training budget, a change in your responsibilities, or a specific piece of experience, the meeting will not hand it to you by default — you have to bring it. Who sits in the room is fairly consistent. You and your direct manager are standard; HR representatives attend in some organizations. What is less obvious is that feedback from peers or the people you support may be collected beforehand and fed into the review as an input, even when none of those people are present. Some of what gets said about you was gathered weeks earlier, which is worth knowing before you hear it. Frequency is the other variable. HiBob's HR glossary and university HR programs such as the University of Maryland's describe anything from monthly to annual, with twice yearly treated as a sensible default and interim reviews used to course-correct between formal cycles. That number matters more than it looks: an annual cycle asks you to recall and evidence twelve months of work, and that is exactly where under-prepared people lose ground. ## Where the input in a performance development review comes from Employers assemble the review from a handful of recognizable sources. Four of the five below describe who contributes; the fifth describes how often. Most organizations combine two or three of them, and identifying which combination yours uses tells you where to put your preparation. ### The manager-led review This is the core of almost every PDR. Your direct manager assesses your performance against predefined criteria and objectives, gives feedback, and discusses goals and development for the period ahead. Its defining feature is that a single evaluator also holds decision authority — over the rating, over the goals you leave with, and often over pay. That concentration is not bad news. It means there is one person whose view you can genuinely shape, and the way to shape it is to find out the criteria before the meeting and arrive with a concrete example ready for each one. ### Your self-assessment Many employers ask you to evaluate your own performance in writing first, and that document then feeds your manager's assessment. It is the only input you fully control, and the only one written before anyone else's view has hardened. Advice from Indeed, Culture Amp, Lattice and Leapsome converges on a single instruction: replace adjectives with evidence. Indeed's worked contrast is the clearest version of it — "I reduced department overhead by 10% by renegotiating vendor contracts" does work that "I saved the company money" cannot. The mechanism behind the advice is memory. Your manager writes from what they can recall and justify to their own boss, so work that was never recorded is effectively invisible on the day. ### Peer review Some organizations collect assessments from the colleagues you work alongside, usually through a structured questionnaire rather than a conversation. What it captures is different in kind from what your manager sees: reliability, knowledge sharing, how you behave when a project gets difficult — the everyday collaborative behavior a manager rarely observes directly. If your employer uses peer input, your preparation extends beyond your own record to the working relationships that produced it. ### The 360-degree review The most comprehensive format pulls feedback from several directions at once — your manager, your peers, the people you support, and in some organizations customers or clients — then aggregates it into one picture. Its distinguishing feature is that the result is usually anonymized and composite, so you cannot trace a comment back or answer it point by point. That changes what preparation means. There is no case to argue on the day; what a 360 measures is consistency across a whole period, and the useful move is to ask a couple of trusted colleagues for [candid input](/knowledge/self-awareness/how-to-ask-for-feedback/) beforehand rather than meeting the composite cold. ### Continuous and interim check-ins The clearest shift in current practice is away from the standalone annual verdict and toward shorter conversations — monthly or quarterly check-ins framed as coaching, running alongside or instead of the formal cycle. Vendors including Rippling and Quantum Workplace describe this as the direction of travel rather than a measured trend, so treat it as a change in how organizations work rather than a statistic. What it changes for you is the evidence horizon: nothing has to be reconstructed from a year ago, and the formal review summarizes conversations you have already had instead of springing news on you. If your workplace runs [one-on-ones](/knowledge/working-with-your-manager/one-on-one-meeting-with-manager/), they are part of your review preparation whether or not anyone calls them that. ## Turning the evaluation into a plan you actually asked for Two frameworks recur across the guidance, and between them they cover both halves of the meeting. STAR — situation, task, action, result — structures the evidence you bring for work already done. [SMART](/knowledge/setting-goals/smart-objectives-sample/) — specific, measurable, achievable, relevant, time-bound — structures the development goals you leave with. Neither is employer-specific, and a reader who walks in with STAR-shaped evidence and out with SMART-shaped goals has done what the process was designed for. The harder part is the gap you name yourself. The instinct is to present an unbroken record, but Business News Daily and StaffCircle both make the same case: [a self-assessment](/knowledge/working-with-your-manager/self-assessment-performance-review/) that includes development areas alongside achievements reads as self-awareness, not as an admission of weakness. There is a practical reason beyond how it reads. Naming a specific gap, and the support you want for it, is the mechanism by which anything actually gets allocated — HSI's guidance on development plans lists on-the-job training, mentorship and formal classes as the usual currency, and none of it arrives unrequested. Which gap to name is the genuinely difficult question, because the areas that would move you most are rarely the ones you notice on your own. An outside read helps here, and [seeing which skills to work on](https://assessment.headwayskills.com/) gives you something concrete to write in the development half of the form rather than a placeholder you invent the night before. ## The skills that decide how the conversation goes Strip away the format and the paperwork, and the difference between a review that moves you forward and one that simply happens comes down to a few things you can practice — how you prepare, how you take an assessment of your work, and whether you ask for anything. **Working with Your Manager** is the most direct of them. This is the skill that treats the review as a partnership rather than a verdict: making your results visible before you are asked for them, agreeing goals that are challenging but achievable, staying future-focused when the conversation drifts into post-mortem, and asking plainly for what you want next. Your manager arrives with an incomplete picture of your year, and the parts you never made visible do not exist in the room. You are one half of the conversation, and the evaluation is not fixed until it happens. **Building Self-Awareness** carries the other half — receiving your manager's read of your work, including the uncomfortable parts, without either swallowing it silently or arguing it down. The sequence that makes this work is understanding the feedback fully first, then adding your own view, then reflecting on it afterward. It is also what makes a self-assessment ring true: naming what you are genuinely good at, not merely competent at, is what turns the development half of the review into something you authored. **Influence** is what stands between a year of solid work and a review that reflects it. Done honestly, it means building a record worth pointing to, understanding what your manager needs the meeting to accomplish, planning the conversation instead of improvising it, and going for a smaller win — one project, one course — when the full ask is unlikely to land. It is not spin. It is the recognition that a manager can only rate what they can recall. If you are unsure which of those three would change your next review most, the free Job Skills Test gives you a read on all of them — they are three of twelve such skills it measures, and every one of them is built rather than inherited. Working out [which one to build first](https://assessment.headwayskills.com/) is a shorter job than it sounds. ## Where that leaves you before the meeting Parts of this may already describe how you work — the habit of noting what went well while you still remember it, or the preference for hearing a hard assessment straight rather than missing it. None of it is fixed, and none of it asks you to become a different person at work; these are behaviors you build at whatever pace the year allows. They also tend to matter more as your responsibilities grow, because each review starts carrying more of what happens next. And the timing here is worth noticing: you are reading about how a performance development review works while you still have time to prepare for one, which is not what most people do. The next step is small — find out where you actually stand. ## Start with an honest read of where you stand What is left is to get a baseline you can bring to the conversation. The Job Skills Test is a **free** self-assessment of the workplace skills this article has been circling — the ones that decide how prepared you feel walking in and how much you leave with. It shows you where you stand across all twelve, and which one or two would make the biggest difference to your next review, so your preparation and your development goals point at the same thing. **[Get my skills profile](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, and you can do it before your next one-on-one.* ## 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? A performance development review is a scheduled meeting where your manager assesses your work and you agree a development plan. Here's what to expect and prepare. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Building Self-Awareness, Influence. ### 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/influence.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/performance-development-review/ Preferred summary: "A performance development review is a scheduled meeting where your manager assesses your work and you agree a development plan. Here's what to expect and prepare." ## Change log - 2026-07-07: Content collection version published.