On 22 Aug 2009, at 22:44, Mashhoor Aldubayan wrote:
I'm wondering: how many of you think that writing a big report on
the findings/recommendations for a project is inefficient?
From my experience, it seems that I end up discussing (and often
justifying) almost every single thing I write on the report, no
matter how logical it is.
Isn't a better way to just sit with the client's development team
and/or management, and get things done together?
Yes. I've always found this the most effective technique to actually
get changes made.
However - some clients won't let you do this without there being a big
thick wad of paper with twenty seven eight-by-ten colour glossy
photographs with circles
and arrows and a paragraph on the back of each one.
I try and get some idea of client expectations before I write the
report. I also charge for writing the report separately - so they can
what time/money they are wasting before they waste it. Beyond that -
if they still ask for it I write it.
Adrian
--
http://quietstars.com - twitter.com/adrianh - delicious.com/adrianh
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
