Send me problems, not wireframes(medium.com)

5 years ago from Ariel Verber, Product Designer

  • Charity De La CruzCharity De La Cruz, 5 years ago

    There's a few different reasons as to why a client would give you a wireframe or mockup but in my work there were 2 major scenarios:

    1.) She has a vision in her head that she can't seem to articulate so she would create a mockup to give you a visual idea - as a designer, you can experiment with the wireframe, make it better or provide an alternative solution because the wireframe simply doesn't satisfy the purpose of it's creation. Either way, providing a wireframe is a supplement for her to help communicate an idea. It doesn't necessarily mean she thinks she can do your job better.

    2.) The purpose of designing is just to "enhance" and work with whatever is provided. Oftentimes these types of work has a set deadline already and the "design" part of the work is typically "just" to make sure that it's presentable. It's like going to an audition with a sh*tty script to work with. You do your best in delivering the lines, maybe modify it a little bit to exert the right presentation. Compromising doesn't have to be horrible. Work with the problem and use the wireframes as reference.

    Maybe it's just me, but as long as the person provides me with what the problem/purpose of the design creation, I just look at the wireframe as a reference, not the ultimate "be all and end all". At the end of the day, they're asking me for my expertise and counsel and it is our job as a designer to evaluate the impact of the work and eliminate the negative impact if there's any.

    0 points