---
title: "The way it ought to be - Microsoft and feedback"
url: "https://osherove.com/blog/2004/11/1/the-way-it-ought-to-be-microsoft-and-feedback.md"
canonical: "https://osherove.com/blog/2004/11/1/the-way-it-ought-to-be-microsoft-and-feedback.html"
published: "2004-11-01T18:02:00"
updated: "2004-11-01T18:02:00"
tags: ["Blogging"]
author: "Roy Osherove"
description: "This is exactly how it should work: You post feedback on an event you have been to, your blog is read by one of the presenters in that event which then posts on his own weblog on the power of feedback and tells his…"
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# The way it ought to be - Microsoft and feedback

By Roy Osherove November 1, 2004 In [Blogging](https://osherove.com/blog/category/blogging)

**Historical article** · Originally published November 1, 2004; technical details may be outdated.

This is **exactly** how it should work:

You post feedback on an event you have been to, your blog is read by one of the presenters in that event which then posts on his own weblog on the power of feedback and tells his manager. Later, the presenter's boss reads the original blog post and posts a details answer on the how's and whys of each point made, making sure to learn important lessons from this feedback and even suggesting ideas for the community for future improvement.

Sounds like fiction? Check out [this post from Dave Donaldson](http://loudcarrot.com/Blogs/dave/archive/0001/01/01/667.aspx) giving event feedback, make sure you read all the comments on that post (notice responses from [Rory](http://neopoleon.com/blog/) and [his boss](http://weblogs.asp.net/MikeoMSDN/)). Then read [Rory's response](http://neopoleon.com/blog/posts/9035.aspx) on his blog. then read Dave's "[I'm happy with the end result](http://loudcarrot.com/Blogs/dave/archive/2004/10/26/671.aspx)" post about the whole thing and realize that blogging and feedback makes for happy clients, even if you screw up.

Yep. This is the way it should work.

Even in Israel.

## More in Blogging

[All posts in Blogging](https://osherove.com/blog/category/blogging)

- Nov 7, 2004

    ### [What blogs are other people reading?](https://osherove.com/blog/2004/11/7/what-blogs-are-other-people-reading.html)

- Nov 5, 2004

    ### [Israeli .Net bloggers worth a read](https://osherove.com/blog/2004/11/5/israeli-net-bloggers-worth-a-read.html)

- Oct 15, 2004

    ### [Best Independent Tech Blog Readers Choice Awards](https://osherove.com/blog/2004/10/15/best-independent-tech-blog-readers-choice-awards.html)

- Oct 6, 2004

    ### [Twilight-Zone problems](https://osherove.com/blog/2004/10/6/twilight-zone-problems.html)


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/