{"id":13,"date":"2005-06-07T05:56:47","date_gmt":"2005-06-07T05:56:47","guid":{"rendered":"http:\/\/quinert.com\/stblog\/?p=13"},"modified":"2005-06-07T05:56:47","modified_gmt":"2005-06-07T05:56:47","slug":"valuing-early-feedback-why-wait-until-the-end","status":"publish","type":"post","link":"http:\/\/www.software-testing.com.au\/blog\/2005\/06\/07\/valuing-early-feedback-why-wait-until-the-end\/","title":{"rendered":"Valuing early feedback – Why wait until the end?"},"content":{"rendered":"
I suspect that my boss has helped focus this thought for me.\u00ef\u00bf\u00bd I began wondering about why people wait until finishing something before seeking feedback.\u00ef\u00bf\u00bd Underlying assumptions behind checking something at the end might be –<\/div>\n

– that you’re going to get it right first time.
\n– that nobody knows better than you do.
\n– that it is going to be faster if you do it all at once (tightly coupled to the first point).<\/p>\n

Another possibility might be that you’re afraid of negative feedback, which, in the context of working on a software team, is delaying the inevitable.<\/p>\n

I’m sure there are more possibilities.<\/p>\n

Problems with our assumptions<\/strong><\/p>\n

That you’re going to get it right first time
\n<\/em>
\nHow might we behave if we assume that we are not going to get it right?<\/p>\n

That nobody knows better than you do<\/em><\/p>\n

How might we behave if we assume that everyone might know something we don’t?<\/p>\n

That it is going to be faster if you do it all at once
\n<\/em>
\nHow do we know that ‘faster for me’ is necessarily faster for the project overall?<\/p>\n","protected":false},"excerpt":{"rendered":"

I suspect that my boss has helped focus this thought for me.\u00ef\u00bf\u00bd I began wondering about why people wait until finishing something before seeking feedback.\u00ef\u00bf\u00bd Underlying assumptions behind checking something at the end might be – – that you’re going to get it right first time. – that nobody knows better than you do. – […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29,32,33],"tags":[132,134,135],"class_list":["post-13","post","type-post","status-publish","format-standard","hentry","category-software-development","category-systems-thinking","category-teamwork","tag-software-development","tag-systems-thinking","tag-teamwork"],"_links":{"self":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/posts\/13","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/comments?post=13"}],"version-history":[{"count":0,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/posts\/13\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/media?parent=13"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/categories?post=13"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/tags?post=13"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}