<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.docmoates.com/index.php?action=history&amp;feed=atom&amp;title=Blog%3ADocmoates%2Fwhat-good-feedback-actually-looks-like</id>
	<title>Blog:Docmoates/what-good-feedback-actually-looks-like - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.docmoates.com/index.php?action=history&amp;feed=atom&amp;title=Blog%3ADocmoates%2Fwhat-good-feedback-actually-looks-like"/>
	<link rel="alternate" type="text/html" href="https://wiki.docmoates.com/index.php?title=Blog:Docmoates/what-good-feedback-actually-looks-like&amp;action=history"/>
	<updated>2026-06-18T13:27:15Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.4</generator>
	<entry>
		<id>https://wiki.docmoates.com/index.php?title=Blog:Docmoates/what-good-feedback-actually-looks-like&amp;diff=5404&amp;oldid=prev</id>
		<title>Docmoates: Imported from docmoates.com blog</title>
		<link rel="alternate" type="text/html" href="https://wiki.docmoates.com/index.php?title=Blog:Docmoates/what-good-feedback-actually-looks-like&amp;diff=5404&amp;oldid=prev"/>
		<updated>2026-06-18T05:41:30Z</updated>

		<summary type="html">&lt;p&gt;Imported from docmoates.com blog&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;The organizational feedback literature has settled on a set of consistent findings: feedback is valuable in principle, most feedback in practice is poorly delivered, and the gap between the two produces significant costs, in employee development, in performance management, and in the trust relationships that make organizations function.&lt;br /&gt;
&lt;br /&gt;
The specific failures are welldocumented. Feedback is too infrequent (the annual review model concentrates what should be continuous information into a single highstakes event). It is too vague (&amp;amp;quot;you need to communicate better&amp;amp;quot; tells the recipient nothing actionable). It is too focused on person rather than behavior (&amp;amp;quot;you&amp;#039;re disorganized&amp;amp;quot; versus &amp;amp;quot;the last three project plans were missing the timeline and resource sections&amp;amp;quot;). And it is frequently contaminated by bias, the same behavior described differently depending on the demographics of the person exhibiting it.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span id=&amp;quot;what-works-instead&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
== What works instead ==&lt;br /&gt;
&lt;br /&gt;
Specific, behavioral, timely feedback is the consistent recommendation of the research. Specific: it names exactly what was observed. Behavioral: it describes observable actions, not inferred characteristics. Timely: it comes close enough to the event that both parties remember it clearly and can connect the feedback to specific choices.&lt;br /&gt;
&lt;br /&gt;
Separating developmental feedback from evaluative feedback is also supported. When the recipient knows they&amp;#039;re being evaluated, they&amp;#039;re less able to engage with developmental feedback as information. Formal evaluation processes and informal coaching conversations serve different functions and are more useful when not conflated.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;#039;&amp;#039;Originally published August 16, 2017 on [https://docmoates.com/blog/what-good-feedback-actually-looks-like/ docmoates.com].&amp;#039;&amp;#039;&lt;/div&gt;</summary>
		<author><name>Docmoates</name></author>
	</entry>
</feed>