On Tuesday 04 March 2008 15:24:03 Rob Nero wrote: > In this way, we hand off a high-fidelity mockup with a detailed document > explaining how everything works on the screen.
Do you create a separate client deliverable or give the same thing to you project contact (or are you part of an integrated or in-house team so "plop" factor doesn't matter as much). On Tuesday 04 March 2008 15:46:14 Jason Zietz wrote: > In my most recent project, I communicated with the developer as I worked > on the documentation, providing him with samples of different options > (in the context of the project) so he could choose which type of > documentation best suited him. > > Additionally, I'd recommend encouraging communication during the > development process when possible as things invariably arise that > weren't covered in the documentation. I always prefer to work closely with developers, but that doesn't always happen. That is why I am so interested (and concerned) about deliverables. A wireframe can be both a helpful and dangerous tool, depending on how much you read (or don't read) in to it. Also, developers are used to different kinds of documentation, so a written point-by-point specification might resonate with them more than a picture. Who knows? (That is why I am asking these questions). On Tuesday 04 March 2008 16:02:55 Ari Feldman wrote: > most developers never get more than a few bullet points for specs or as > inputs while many others still work in environments of "oral history" where > deliverables are verbally explained but never written! > > > So, when a developer gets design docs and/or functional specs - even > imperfect ones, they are often happy. I totally agree unless they are handed an 80 page report of 6 months of research. And a cup of coffee. And some aspirin. There are lots of things that "should" happen in a project -- clear product goals and documentation, communicating with developers, writing perfect reports, lots of extras to tape on the wall -- but they don't always happen. Maybe it is just the capacity I work in (aka miracle worker) that nothing goes as planned. I usually get called in to the middle of a project which is in serious trouble and get caught between backfilling necessary user research and "fixing it now". It is really about making the best of what you got and hoping your message gets across. And being thankful the client is thinking about these things at all. Is there a SIG for Guerrilla Design? -- Celeste 'seele' Paul www.obso1337.org ________________________________________________________________ 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
