| NEW! FREE Do-It-Yourself Press Release Kit Get It Now (Adobe PDF) |
Close This Window
Free Do-It-Yourself Press Release Kit
Fill out the information below to receive our free e-book. We'll automatically redirect you to the download area.
Close This Window
Seven Mistakes to avoid with Wireframe Software
by: pidoco1 on
Date: Wed, 8 May 2013 Time: 2:50 AM
I hear stories from UX designers frequently about projects that have gone wrong with clients. Often these are mistakes that could be avoided by setting out clear requirements and communicating clearly with clients. Many of the UX designers I know use wireframe software. While this can be a tool that helps communication and can help to generate clear specifications, very often people miss the true value of wireframe software within the process of the conceptualization of a website or mobile apps. By focusing purely on creating wireframes without bearing other considerations in mind, this can lead to costly mistakes, however. When designers create wireframes with wireframe software, they should try to avoid the following mistakes
Not seeing wireframes as a tool
Often wireframes are seen as a sign-off process that a client expects. Rather than looking at wireframes as an obligatory process, see them as one part of a larger process. There are many other processes that UX designers go through, including focus groups, creating personas and user flows.
Not testing early enough
Many people do not realize that it is never too early to get feedback from end users. Sometimes showing a paper sketch can be enough to get an understanding of how a user would use an application. The more detailed a wireframes is, the more reliable the user’s feedback will be. Nevertheless, feedback generated early on in development can help to save costs.
Not getting the right feedback from stakeholders
Often clients and other stakeholders give the wrong feedback. Sometimes they focus on color and typography rather than interactions and layout. The best way to get the best feedback is to explain to stakeholders clearly what the function of the wireframes is for and what type of feedback you would like.
Not adapting for mobile
Too many companies ignore the value of the mobile market. Rather than starting out using your wireframe software to plan your website, begin by planning the mobile website. Then create wireframes for tablet and so on. Mobile can be difficult to adapt for and is rife with usability issues, but the benefit is that it forces you to focus on the most important interactions and content.
Not thinking about the context
How will your end users be using your mobile app or website? What is your target audience? Will they be in a place full of distractions, or will they have time and patience to scroll and click through your design? These are all important things that will help you understand your users better.
Not selecting the right wireframe software
One of the best ways to get feedback from stakeholders is to let them collaborate on a project in the wireframe tool itself. There are some tools that let you send URLs of your prototypes, so other collaborators can make comments. One tool that I use has real-time collaboration and because it is easy to use, clients can generate pages themselves how they think applications should look.
Not generating clear specifications
One of the main benefits of using wireframe software is that you can avoid costly mistakes that result from poor communication. Some tools allow you to create specification documents very easily. If you do this, make sure that any relevant comments and annotations for designers and developers are included.
About the Author
Pidoco.com – User Interface Design, Wireframing Software, Wireframe, Interface Design Software, Wireframing Tool, iPhone mockup, Prototyping Tool, Wireframe Software, Prototyping Software and UI design.
Rating:
Not yet rated
Login to vote | Not Registered?
Create an account
Comments 
No comments posted.
Add Comment
You do not have permission to comment. If you
log in, you may be able to comment.
