Performance feedback: an evidence-based conversation template

“You need to be more proactive” is not clear enough feedback

In a hypothetical situation, a founder tells an employee to be proactive while still requiring approval for every exception. The employee does not know what they can handle independently. Broad feedback can convey dissatisfaction without providing an action they can take immediately.

Feedback should identify a specific gap between results and agreed standards. If standards are unclear or have just changed, clarify expectations first. Do not assess someone against a rule that exists only in the manager’s head.

This article focuses on discussing a particular deliverable. One-to-one meetings have a broader scope, including support, development and work challenges. Feedback can be included when appropriate, but every meeting should not be devoted solely to pointing out mistakes.

Prepare three things: the situation, standard and impact

Record when the issue occurred and the deliverable to discuss. For example: Tuesday morning’s report omitted pending orders, although the agreed template includes them. The observable impact is that meeting participants had to request more information and could not decide on a course of action. Avoid writing “you don’t care,” which is an assumption about motives.

Check whether the data is complete and the employee knows the standard. If there are several examples, choose clearly related situations; do not bundle every frustration into one conversation. Agree on a suitable time, speak privately and protect the information of those involved.

A five-step conversation framework

The template below takes the conversation from facts to actions. Managers should adapt the wording so it sounds natural, remain specific and give the recipient time to respond.

Listen to the context to choose the right solution

A skill gap calls for guidance and practice. Late input data calls for better coordination. A lack of authority calls for clear decision boundaries. A workload exceeding available resources calls for reprioritization. Calling every cause “a lack of responsibility” can lead the solution away from the real problem.

Listening does not mean abandoning standards. The manager still needs to confirm what the employee is responsible for and what support the system must provide. If there are two different interpretations, return to the specific situation and output template, then record the agreement before moving to broader conclusions.

When information is insufficient, set a date to gather more rather than force a conclusion during the meeting. A useful conversation may end with a question that needs clarification, provided someone owns it and there is a completion deadline.

Example: the same error, two different responses

Suppose a report lacks a data field. In the first case, the data is available and the template is clear, but the preparer skips the checking step. Both parties can agree to use a checklist before sending, test it in the next report and observe the results.

In the second case, another department supplies the data after the reporting deadline. A checklist cannot address the cause. The data handoff deadline or the way incomplete information is marked must change. Both cases produce an incomplete output, but require different changes.

After corrections, also give feedback on what improved: describe the situation and its positive impact. Specific recognition helps the team understand which practices to continue, rather than receiving feedback only when something goes wrong.

Track an observable change

A brief record should include the output to improve, the employee’s action, the manager’s support and the review date. If the action is “try harder,” rewrite it as a specific check, discussion or practice. Choose a manageable number of actions the recipient can carry out.

At the review, check whether the agreed conditions were provided before assessing results. If the error continues, examine whether the cause and support were correctly identified, whether the standard is appropriate and how execution has changed. Do not treat a single feedback conversation as automatic evidence about an entire period of performance.

If the conversation reveals an exception missing from shared guidance, update the team’s knowledge instead of requiring each person to remember a separate instruction. This is how feedback becomes system improvement.

Suggested actions