A good article by G2G3. I think this is one good example of a time where automation is a bad thing. Its just too easy to set something up that creates a huge report and sends it off automatically, making it look as if something useful has been done. Reports should only be by exception. What went wrong, why and whats being done to stop it ever happening again. This is also a good use for Knowledge Management - a wiki, in fact; with a wiki you can see exactly who read something, and when. If nobody ever reads a section, delete it. The ideal would probably be a nice graphical front-end to the wiki showing the highlights for the services relevant to the person reading it (being a wiki you know who is reading it so you can tailor your message properly, just like in a real service portfolio)... in a non-intrusive way, so everybody can get on with using the wiki as theyd like, but know that, if things get a bit slow, or something goes wrong, they just have to click on the graphic to see if theres a problem with a service thats causing it. americas.g2g3/blog/bid/103541/it-measurement-why-nobody-reads-your-reports?source=Blog_Email_[IT%20Measurement%3A%20%20%20Wh]
Posted on: Tue, 09 Dec 2014 06:57:53 +0000
Trending Topics
Recently Viewed Topics
© 2015