For Leaders
From Feedback to Development
Turning an assessment result or a mentor's comment into a Development Plan people actually follow — and the three translations that break most often.
Feedback arrives as a judgement. Development happens as a behavior. Between the two sits a translation that most organizations skip, which is why so much feedback changes nothing.
This guide is that translation, in three steps.
The problem with good feedback
“You need to delegate more” is accurate, specific enough to act on, and delivered by someone the person respects. It still usually fails, because it describes a destination and the person is standing at a Tuesday.
The gap is not motivation and it is not comprehension. It is that nobody converted the judgement into something that fits in a calendar.
Step 1: From judgement to observable behavior
Take the feedback and ask: what would I see, if this were fixed?
| Feedback | What you would see |
|---|---|
| “Delegate more” | Work that used to sit with them appears on someone else’s list, and they do not review it. |
| “Be more strategic” | In planning meetings they raise the next two quarters before the next two weeks. |
| “Give better feedback” | Their reports can say, unprompted, what they should do differently. |
Notice that the right-hand column is checkable by a third party. That is the test. If you cannot describe what you would observe, you do not yet have something to develop — you have an impression.
This is also where evidence level matters. A mentor’s assessment of how well-evidenced a behavior is stays between the mentor and the system; it is deliberately not shown to the participant, because the point is to describe the behavior honestly, not to give someone a grade to argue with.
Step 2: From behavior to a Development Goal
Now narrow it to this person, this period.
A Development Goal is the outcome — the right-hand column above, scoped and dated. Two rules:
One behavior per goal. “Delegate more and communicate the reasoning” is two goals wearing one coat, and it will half-happen.
State the outcome, not the activity. “Complete the delegation module” is an activity; you can do it and change nothing. “Three recurring pieces of work have moved and stayed moved” is an outcome.
Step 3: From goal to Development Tasks and MDAs
This is where it becomes doable.
A Development Task is a piece of real work that moves the goal. An MDA is one specific thing to do, on one day, that takes minutes.
Continuing the delegation example:
- Goal: three recurring pieces of work have moved to the team and stayed moved.
- Task: identify and hand over one recurring responsibility per fortnight.
- MDAs: list everything you did last week that someone else could have done · pick one and name who takes it · hand it over in Thursday’s one-to-one and say you will not review the draft · when it comes back imperfect, respond without fixing it yourself.
The last one is the whole point. Most delegation advice fails at the moment the work comes back imperfect, and a plan that does not anticipate that moment is not a plan.
The three translations that break
Judgement kept as judgement. “Be more strategic” goes into the plan verbatim. Nobody can act on it, so nothing happens, and at review time it is still there.
Goal that is really a task. “Have a delegation conversation with Marta” is a single event. It will happen, it will be ticked, and the behavior will not change. A goal survives more than one occurrence.
MDAs that are reflections. “Think about what holds you back from delegating” feels like development and produces nothing observable. An MDA should have a verb someone else could watch you perform.
When feedback and plan disagree
Sometimes a person reads their feedback and does not recognise themselves in it. That is worth taking seriously rather than overriding.
Two honest possibilities: the feedback is about a context the person does not see themselves in (they delegate fine to their senior people and not at all to their juniors), or the raters are describing an effect and guessing at the cause.
Both are resolved the same way — by getting more specific about when the behavior is missing. “Delegate more” becomes “delegate to the people you have not delegated to before”, which is narrower, more accurate and considerably more actionable.
Next
- How to Build Better Habits as a Leader
- Creating and Managing Development Programs — the program-manager view of the same translation.