Give feedback on an observable problem and a next step
Kritik konkret und lösungsorientiert formulieren
Distinguish observation, impact and request, and respond to correction without blaming motives.
Constructive feedback describes a specific observation, its effect on the task and a feasible next step. “Two entries lack dates” is more useful than “You are careless.” The first can be checked; the second attributes a personal quality. Avoid treating an inferred motive as a fact. Use mir ist aufgefallen, dass … to introduce an observation and dadurch … to explain a supported consequence. A polite request can still name a concrete correction and deadline. When receiving feedback, acknowledge what is correct, clarify any mistaken assumption and agree on an action you can actually deliver. A repair statement should not promise that an error can never recur. The aim is reliable improvement, not a forced admission of intentions.
Mir ist aufgefallen, dass zwei Datumsangaben fehlen.
I noticed that two dates are missing.
Dadurch lässt sich die Lieferplanung noch nicht abschließen.
As a result, delivery planning cannot yet be finalized.
Könnten Sie die fehlenden Angaben bis Mittag ergänzen?
Could you add the missing information by noon?
Vielen Dank für den Hinweis; einen Termin kann ich bereits bestätigen.
Thank you for pointing that out; I can already confirm one date.
Der zweite Termin muss noch mit dem Lieferanten abgestimmt werden.
The second date still needs to be coordinated with the supplier.
Ich melde mich bis Mittag mit dem aktuellen Stand, auch wenn die Bestätigung noch aussteht.
I will report the current status by noon, even if confirmation is still outstanding.
Constructive feedback describes a specific observation, its effect on the task and a feasible next step. “Two entries lack dates” is more useful than “You are careless.” The first can be checked; the second attributes a personal quality. Avoid treating an inferred motive as a fact. Use mir ist aufgefallen, dass … to introduce an observation and dadurch … to explain a supported consequence. A polite request can still name a concrete correction and deadline. When receiving feedback, acknowledge what is correct, clarify any mistaken assumption and agree on an action you can actually deliver. A repair statement should not promise that an error can never recur. The aim is reliable improvement, not a forced admission of intentions.
Distinguish observation, impact and request, and respond to correction without blaming motives.
Do not turn „Zwei Datumsangaben fehlen“ into „Sie wollten die Arbeit absichtlich behindern“. Missing data do not prove a motive.
Observable issue → concrete effect → feasible request. In the response: acknowledge facts, clarify limits, agree on action and timing.
Write a 180–220-word exchange between colleagues: two dates are missing from a handover list, so delivery planning cannot be finalized. Give factual feedback, ask for correction by noon and write a response that confirms one date but explains that the other still needs supplier confirmation. Agree on a follow-up without inventing the missing date.