Downward feedback template
Eight questions a manager answers about someone in their team, across four areas: contribution, strengths, growth and risk. Short enough to finish.
8 questions · Performance reviews
The template
Contribution
What this person actually did. Ask for specifics — a manager who cannot name one thing has a different problem to solve first.
- What has this person contributed over the period that mattered most?
- Where did they have an impact beyond their own work?
Strengths
The thing to build on. Most people underuse their best quality because nobody has ever named it to them.
- What is this person distinctly good at?
- Are they being given enough work that uses it?
Growth
One area, not a list. A manager who names four development areas has given none of them.
- What is the one thing that would most improve their effectiveness?
- What is your part in making that happen?
Rated
Two statements. The first is shared with the person; the second is for the organisation and should never be shown to them.
- This person is clear on what is expected of them12345
- I would be concerned if this person resigned in the next six months12345
What this one assumes
There is more than one way to run this. Here is what we assumed, so you can tell quickly whether it fits — and what to change if it does not.
- The manager completes it once per person, per cycle, and it takes under ten minutes
- The person sees everything written about them — nothing here is a private manager note
- It is the input to a conversation, not a substitute for one
- The retention question is read at an organisation level, never shown to the individual
What this is for
Most downward review forms fail because they are long. A manager with eight reports facing a twelve-question form writes eight versions of the same paragraph, and the organisation gets a filing cabinet of text that nobody acts on.
This one is eight short questions across four areas, because a form a manager can finish in ten minutes actually gets finished. The constraint is the design — a manager who has to pick one growth area picks the real one.
How the template is built
Contribution asks what the person did, not how they rate. The second question — impact beyond their own work — catches the people who make everyone around them better, which is invisible in any output-based measure.
Strengths has a second part that is really a question about the manager. Naming what someone is good at is easy; answering whether they are actually getting work that uses it is where the useful conversation starts.
Growth is singular on purpose. A list of four development areas is a manager avoiding a choice, and the person receiving it will act on none of them. The follow-up — what is your part in making that happen — stops development being something the employee is told to go and do alone.
The two rated statements do different jobs. Clarity of expectations is about the manager's own performance as much as the employee's, and it is shared. The retention statement is an organisational signal: aggregated it tells you where you are exposed, and shown to an individual it is corrosive. Keep that boundary.
How to run it
Have the manager write it before the conversation and share it before the conversation. Reading feedback aloud for the first time while the person reacts in real time is the worst format for both of them.
Read the growth answers across a team together. If six people have the same development area, that is not six individual gaps — it is a training need, or a manager, or a process.
If you also run peer feedback, run it first. A manager who writes their view after seeing peer input writes a more accurate one, and the overlap between the two is the most reliable signal in a review cycle.
What we would change, and when
If this is feeding a pay or promotion decision, add one more rated statement about performance against expectations and say plainly on the form that it carries that weight. What this template must not do is pretend to be developmental while quietly determining someone's pay.
For managers with very large teams — twenty or more reports — cut to the growth question and the two ratings. Twenty thoughtful short answers beat twenty rushed long ones.
If you are introducing reviews for the first time, drop the retention statement for the first cycle. It is the question most likely to make managers suspicious of what the form is really for, and you can add it once the process has credibility.
Run this one, then change it
Load it into Crewmojo as a starting point and reshape the questions, the timing and who is involved around how your organisation actually works.