As I have said on other occasions, internal blogs can be an excellent opportunity to test project testing the beta versions, sharing the progress of a project with the recipients, receiving feedback. Some time ago I also posted that in my ward was an excellent case study about it.
Today I see that this idea of using internal blogs found other supporters, particularly Patric Walsh, who wrote another case study reported a similar experience. His idea is clear: research on average users cover the first phase is the design, while usability tests cover the phase that comes after the design. The internal blog can easily cover everything that happens during the project (and this use of social media to cover steps that are "in flow" of people I work particularly fond). In this way, through the triad:
1) User Research
2) Blog project
3) usability testing
we can achieve a full involvement of everyone in all phases of the project.
I also say that, since in general these projects have a working life of persons, coinvogimento and participation within the blog does not need to be "pumped" artificially: people participate because they know that their contribution is also a contribution to improve their working lives.
