# Developmental Feedback: How to Give It and Actually Use It Canonical URL: https://headwayskills.com/knowledge/self-awareness/developmental-feedback/ Markdown URL: https://headwayskills.com/knowledge/self-awareness/developmental-feedback.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving building self-awareness at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Developmental feedback is future-focused advice aimed at growth, not a rating. Here's how it differs from evaluation, and how the conversation works. ## Key facts - Title: Developmental Feedback: How to Give It and Actually Use It - Category: Self-Awareness - Primary skill: Building Self-Awareness - Related skills: Working with Your Manager, Communication - Primary keyword: developmental feedback - Source page: https://headwayskills.com/knowledge/self-awareness/developmental-feedback/ ## What this page covers - Developmental feedback is future-focused advice aimed at growth, not a rating. Here's how it differs from evaluation, and how the conversation works. - Practical guidance for developmental feedback - How this topic connects to Building Self-Awareness ## Detailed explanation Developmental feedback is information about someone's behavior given to help them learn and improve going forward, rather than to rate how they have performed. It is future-focused, usually informal and ongoing, and delivered while there is still time to act on it — which is what separates it from the evaluative feedback of a [performance review](/knowledge/working-with-your-manager/performance-reviews/). Most of us have sat on both sides of a conversation that was meant to be developmental and landed as a verdict instead. The difference is rarely intent. It is almost always sequence. ## What makes feedback developmental rather than evaluative Both kinds are useful, and most workplaces run on a mix of them. Evaluative feedback tells someone where they stand — how the work measured up against expectations, often attached to a rating. Developmental feedback does something else: it concentrates on the process of learning rather than the product of it, and it points forward. Research on the subject describes it as helpful, valuable information a supervisor provides to help someone learn, develop and make improvements on the job — raising their awareness of their work and their environment through future-oriented suggestions rather than through an assessment of what has already happened. Two practical consequences follow. The first is that developmental feedback carries an implicit vote of confidence: it tells someone how they could improve while signaling that improving is available to them. Strip that out and the same words become criticism. The second is that timing is part of the definition, not a nicety. Feedback only functions developmentally if it arrives with enough runway to be used — in time to strengthen a skill or course-correct before the review, rather than learning at the review that you should have. That is also why blending the two registers in one conversation tends to fail. Once someone hears a judgment about their standing, they stop processing the advice and start defending the record. Growth and promotion conversations want the developmental register; formal assessment wants the evaluative one. Working out which one you are in is the first step of the process, not a preliminary to it. ## How to give developmental feedback, step by step The structure most workplace guidance is built around is the Situation–Behavior–Impact model from the Center for Creative Leadership, with preparation wrapped around the front of it and follow-up around the back. The sequence below runs that full arc. Each step depends on the one before it, and skipping ahead is usually what turns a growth conversation into a vague or defensive one. ### 1. Decide which conversation you are having Before you book anything, settle whether you are helping someone develop or telling them how they rate. You cannot do both well in the same twenty minutes. If a formal evaluation is due soon, deliberately hold the developmental conversation separately and earlier, so the advice has somewhere to go. This single decision shapes everything downstream: the register you open in, whether you cite one example or summarize a quarter, and whether the other person spends the conversation listening or bracing. ### 2. Gather specific observations before you speak Developmental feedback dies on vagueness. The standard advice is to observe first and take notes on specific behaviors, then write your feedback down before [the one-on-one](/knowledge/working-with-your-manager/one-on-one-meetings/) rather than improvising it in the room. Aim for one or two real instances you could describe to someone who was not there — what was said, what was produced, what happened next. Preparing this way also exposes when you do not actually have an example, which is a useful thing to discover before the meeting rather than during it. ### 3. Set the stage Open by naming what the conversation is for. A sentence is enough: you want to talk about how something went, with a view to what comes next. This does two jobs at once — it removes the ambiguity that makes people assume the worst, and it commits you publicly to the developmental register you chose in step one. It depends on step two, because setting the stage for a conversation you have not prepared for simply raises expectations you are about to disappoint. ### 4. Describe the situation Anchor the feedback to a specific time and place. "In Tuesday's client call" does more work than it looks like: it tells the other person which version of themselves you are talking about, and it stops the feedback from generalizing into a comment on who they are. Without the anchor, "you interrupt people" is a character assessment. With it, it is an observation about one meeting that can be discussed, disputed or acted on. ### 5. Describe the behavior, not the person Behavior is anything you could see or hear — the words used, the action taken, the thing that was or was not done. Keep the description at that level and resist the interpretation underneath it. "You cut in three times while the client was explaining the problem" is a behavior. "You do not listen" is a conclusion you have drawn about them, and it invites an argument about their character instead of a conversation about Tuesday. This is the step people skip fastest under pressure, and skipping it undoes steps three and four. ### 6. Name the concrete impact Impact is what makes feedback land, and it has to be specific to do that. Name the time, the trust or the decision that was affected — rather than reaching for a general verdict like "it was unhelpful." Impact is also the part only you can supply: the other person can see their own behavior, but they cannot see what it cost from where you were sitting. Include your own reaction where it is honest, and keep the causal claim modest; you are reporting an effect, not proving one. ### 7. Hand the conversation over Stop talking and make room for a response. Invite questions, ask how they saw it, and [listen properly](/knowledge/communication/active-listening-workplace/) to what comes back — the guidance is consistent that this stage is a two-way exchange rather than a delivery. You may learn a constraint you did not know about, in which case the feedback changes shape. This is also where the confidence half of developmental feedback becomes audible: you are telling someone you think this is within their reach, which is hard to convey while you are still the only one speaking. ### 8. Agree one next step, then come back to it Close by converting the conversation into something actionable — a specific behavior to try, a resource, an opportunity to practice, whatever support you can genuinely offer. Keep it to one thing; a list of five reads as a verdict again. Then follow up. Feedback that is acknowledged once and never revisited quietly teaches both people not to bother next time, and it is the step most often dropped once the calendar fills up. A short check-in a few weeks later is what makes the whole sequence ongoing rather than an event. If you are the one [receiving developmental feedback](/knowledge/self-awareness/how-to-receive-feedback/) rather than giving it, the same sequence tells you what to do with it: understand the situation and the behavior first, add your own view before you evaluate the verdict, and reflect afterward on what holds up. It also tells you what to ask for when nobody offers — a specific instance, its impact, and one forward-looking suggestion. Going into your next one-on-one with a clear sense of [what to ask for](https://assessment.headwayskills.com/) beats waiting to see what arrives. ## What these conversations actually ask of you Read back over the eight steps and very little of the difficulty sits in the words themselves. It sits in noticing your own reaction, in the state of the relationship the conversation runs through, and in being clear without being blunt. **Building Self-Awareness** is what makes feedback worth anything to you. The useful move on the receiving end is to understand the point first, then add your own perspective, then reflect on what is actually true — in that order, rather than collapsing all three into an instant judgment. And because the whole premise of developmental feedback is that it shows you something you could not see from the inside, the payoff is not in agreeing with it but in staying open long enough to check. Asking for specific, future-focused advice is part of the same skill; the feedback you request tends to be more usable than the feedback you wait for. **Working with Your Manager** is where most of this actually happens. Developmental feedback is meant to be informal and ongoing, and for most people that channel runs through one recurring one-on-one — which only stays open if you meet regularly, prepare for it, ask rather than wait, and treat the relationship as a partnership. Keeping the conversation future-focused, even in a formal review, is the difference between an evaluation you receive and a conversation you shape. **Communication** governs the delivery on both sides. Being clear and direct, leading with the main point, keeping the framing positive, and choosing a real conversation over a written message for anything sensitive are what stop a well-intentioned message from arriving as something else. On the receiving side it is mostly listening — the genuine desire to understand before you respond, which is harder than it sounds when you already have a rebuttal loaded. Those three sit inside a set of twelve work skills that keep resurfacing whatever the job, and none of them is a fixed trait — people pick them up late and pick them up anyway. Seeing [where these skills stand](https://assessment.headwayskills.com/) for you right now is a more reliable starting point than guessing which one is holding a conversation back. You may recognize parts of this already — perhaps you are the one who writes something down before a difficult conversation, or who asks for an example instead of accepting a vague comment. The pieces that are not yet habit are learnable, and building them does not require becoming a different kind of person at work; it mostly requires knowing which piece to practice. That matters more as you go, not less: the further into a career you get, the more your development depends on conversations that people are increasingly reluctant to start with you, and the more the initiative has to be yours. Reading this far rather than assuming you already handle feedback well is exactly that initiative in miniature. ## See which of these skills to work on first The remaining question is a small one: which part of this is yours to practice. The **free** Job Skills Test is a short self-assessment that shows you where you stand across all twelve work skills — including the self-awareness, manager-relationship and communication habits that decide how a developmental conversation goes — and points you to the ones worth starting with. Take it once, and you have something specific to bring to your next one-on-one instead of a general intention to improve. **[Take the skills test](https://assessment.headwayskills.com/)** *It's free and takes 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? Developmental feedback is future-focused advice aimed at growth, not a rating. Here's how it differs from evaluation, and how the conversation works. ### Which Headway skill does this connect to? This guide connects primarily to Building Self-Awareness. It also relates to Working with Your Manager, Communication. ### 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/self-awareness.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/self-awareness/developmental-feedback/ Preferred summary: "Developmental feedback is future-focused advice aimed at growth, not a rating. Here's how it differs from evaluation, and how the conversation works." ## Change log - 2026-07-07: Content collection version published.