Beware of the Frankenstein Design
Posted by Michael Gaigg
"It was already one in the morning; the rain pattered dismally against the panes, and my candle was nearly burnt out, when, by the glimmer of the half-extinguished light, I saw the dull yellow eye of the creature open..." (Chapter 5). Sounds familiar to us geeky programmers out there? Yes, and the root of all evil are clients that design their webpage from a sushi menu, picking whatever they like.
Usually I encourage my clients to look around, get inspired and show me what they like. It gives me a sense of how they think and into which directions they want us to go. But never forget: Clients identify problems, designers provide solutions! Understand why the client shows you a specific page or design element and what exactly they like in it. Don't feel pressured to include every detail in your final design otherwise you wake up at 1am facing a yellow-eyed creature and you'll end up with a Frankenstein Design.
Warning Signals
What are warning signals that your project might face a Frankenstein Design?
- Client mentions Stakeholders too often. Money makes the world go round, but will eventually ruin the user experience.
- Client fell in love with a bad design. Try to build solid knowledge about good and bad design principles so you can explain the pro's and con's of a particular design.
- Client needs to please too many interests. It's understandable that every party involved wants to see their logo on the page, but honestly, one is enough
- Client decides on a color scheme. Besides corporate colors clients feel strongly about certain colors that either clash with your design, psychological theory or existing color schemes or are simply bad taste altogether.
- Client has no idea at all. That means trouble! Not now, but once you are done. Guaranteed.
- Got more?
What you can do
- Listen. Hear what the client tells you and try to understand why they say it.
- Feel. Sense what the underlying need is and translate it into design elements.
- Talk. Speak up, don't shut up, don't wait until it's too late.
- Fight. Pick your battles, don't let rules overrule what you think is right, at least voice it.
- Reconsider. Don't get hooked to an idea too strongly, be open to erase your white-board drawings and start over.
- Document. Make notes, sketch ideas, capture screens, summarize. Send these notes out.
- CYA. Cover your ass, seek consensus and approval, set it in stone through written acknowledgments (mockups help).
Send me your experiences? What is missing on this list?
- Share this:
About Me
I'm Michael Gaigg, Lead UI Engineer at Esri's Prof. Services.
I have over 8 years of experience in designing map interfaces and can't stop thinking about improving them.
Help me by sharing your thoughts, ideas and comments.
Categories
- Accessibility (16)
- Code Samples & Tips (8)
- Conclusions (4)
- Design Guidelines (11)
- Designing Map Interfaces (3)
- Go figure (9)
- Good News (19)
- Here and there (21)
- Map Applications (7)
- This Week's Highlights (53)
- Usability & UCD (22)
- Web Design (21)
Popular Posts
- ColoRotate – 3D color scheme generator with social component
- Web Content Accessiblity Guidelines (WCAG) 2.0: Overview and Structure
- Powerpoint Wireframe Stencils as Free Download
- Go figure: 10 Comic Strips that have Something in Common
- Job Posting: User Interface (UI) Engineer at ESRI
Latest tweets
- Awesome resources for website designers http://t.co/oB77As8O 2 weeks ago
- I just contacted Rep. Jerry Lewis to oppose #SOPA #PIPA - Join me! http://t.co/BuFcgvqf #wikipediablackout 2 weeks ago
- Awesome #login #form #sample http://t.co/hob6dtvF 3 weeks ago
- Photo: Dude, just don’t pin the place you’ve been… ;) http://t.co/lwf3gIU8 3 weeks ago
- Photo: Who wants to buy a church in Los Angeles? http://t.co/0SJrYxCv 2011-12-31
- More updates...
Posting tweet...


