Wireframes
Out of context: Reply #17
- Started
- Last post
- 21 Responses
- mg330
Doesnotexist,
That wireframes shouldn't dictate positioning is a common opinion, I've found. I worked with a visual designer at an agency earlier this year who would have been happy if I'd just placed shapes at random within a wireframe, and he'd figure out where they should go. I couldn't stand it. He was a good guy and really talented, but his ego - like that of many creatives I saw there - prevented him from relying on the UX team for the job they were meant to do.
Problem was, he wasn't as involved as I was in the initial conversations with clients, and how the layout was conceptualized. The wireframes reflected those things, so they indeed were meant to illustrate positioning. Yeah, I know that stuff will shift a little bit when the visual design is done, but wireframes IMO are definitely meant to show close-to-accurate positioning of page elements.
That's extremely important when it comes to responsive projects. If UX architects/designers are involved in decision making that impacts responsive layouts - it should be clear to the visual designer that page elements are positioned that way because that's how the site will function - especially if they're not that knowledgeable about responsive design.
I mean, look at that wire example above. By dictating positioning, I'm saying you wouldn't expect a designer to come along and move the Recommended section below Vouchers, Local Deals, and Spend ePoints. It's where it is for a reason.
- its a case of juggling the wireframe (business case) with the creative (aesthetic case) to get an effective (for all parties) resultfadein11
- resultfadein11
- you're both not doing your job right then.doesnotexist