Visuals vs. prototypes

  • Started
  • Last post
  • 6 Responses
  • thatboyneave

    Just had a presentation where we showed detailed visuals of a site to a client.

    Basically 90 minutes of 'now we'd click here, and we'd go to this page'. 'What happens if you click that?'

    In the past I've been involved in projects where we prototype in very basic html first and show that to the client before or alongside some polished visuals... seems like the prototypes get the idea across much more succintly without all the mind-numbing discussion about how things theoretically would work when they're built.

    Anyone got strong opinions one way or the other?

    thatboyneave
    Flag
  • airey0

    nope. it's a fucking pain in the rectum and the moment you think you've solved it a new client comes along and redefines 'dumb fuck' for you. i think we just gotta wear it.

    airey 0Permalink
    UpvoteDownvote
    Dogear
    Flag
    Show [[ numHiddenNotes ]] more notesAdd Note
    SaveCancel
  • thatboyneave0

    I did one a while back at another agency where the first presentation to the client was a black and white html version of the site. Basically a wireframe you could click on.

    We gave it to the client and talked them through it while they clicked on all the links.

    Then gave them a visual of how the homepage would look with some colouring in and pictures applied to it. Bam, signoff.

    Compare that with the process I'm going through now which is bloody painful... the problem is selling in a PM or account manager on the idea if they're not familiar with a more agile/rapid prototyping approach.

    thatboyneave 0Permalink
    UpvoteDownvote
    Dogear
    Flag
      Show [[ numHiddenNotes ]] more notesAdd Note
      SaveCancel
    • whatthefunk0

      I always get stuck with issues getting approved content. This is continually messing with the process because after a design is approved they keep adding content. Did you do your presentation with your idea of content or with their approved site map?

      I make basic full page jpeg comps with rollovers in html and give them a script of what links to click, having them navigate these type of comps with back button functionality usually works wonders. When they forget their on a comp and think it's a live site I know I've done well.

      whatthefunk 0Permalink
      UpvoteDownvote
      Dogear
      Flag
      • With an idea of content. It's more explaining functionality on flat visuals that irks me.thatboyneave
      • I like your idea of putting the visuals in an html page and adding clickable bits. My PM might just buy that.thatboyneave
      • I've done that with sites too..particularly handy if you want to show basic flash too.tOki
      • BUT NOTE: This can make people think you're almost done when you're NOT!vaxorcist
      • I've also seen people think that they can swap out stuff waaay too easily with this approachvaxorcist
      Show [[ numHiddenNotes ]] more notesAdd Note
      SaveCancel
    • vaxorcist0

      Clients can't previsualize... but we have to, it's our job....

      This is why they hire us... it's also why they don't get it... and why it's so bloody painful to show prototypes with concepts while clients think literally, asking random out-of-context questions like "why can't we put the logo on top of this photo and crop it here"

      My previous experience with a REALLY GOOD creative director taught me what really matters is how you pre-sell the client on the idea, nail down the objective, target and approval process. When you present, you continually tie your choices to the objective, target market, and check off the approval process so that client randomness is less likely to appear and more like a mosquito than godzilla waiting to get you....

      He could present a notebook paper sketch just as well as a finished design once he had pre-sold the client and pre-agreed the objective, target and who approves what...

      vaxorcist 0Permalink
      UpvoteDownvote
      Dogear
      Flag
        Show [[ numHiddenNotes ]] more notesAdd Note
        SaveCancel
      • quack0

        i comp every page of an experience, sometimes into the hundreds of variations get made when it's all said and done

        quack 0Permalink
        UpvoteDownvote
        Dogear
        Flag
        • and you bill by the hour, not the project?vaxorcist
        • depends, i'll quote projects in terms of weeks, days or hours. if just experimentation by the hourquack
        • usually i'm on the losing end of this deal but i find the effort to be well worth the resultsquack
        Show [[ numHiddenNotes ]] more notesAdd Note
        SaveCancel
      • BattleAxe0

        been using http://gomockingbird.com/

        lets you mock up websites or webapps and lets you export a PDF that you can email around for feedback , it is drag and drop with ready made generic icons for all kinds of site/app elements

        these mock ups are for presentation of layout and element placement , nothing to do with styling , saves you time with making the visuals too pretty for the prototype presentation only to be axed

        once they are ok with the initial navigation and layout schema then we start photoshoping elements and putting a working CSS HTML prototype so they can see what the concept translates too and take it from there

        BattleAxe 0Permalink
        UpvoteDownvote
        Dogear
        Flag
          Show [[ numHiddenNotes ]] more notesAdd Note
          SaveCancel