Hot answers tagged

4

If you are doing paper mock ups and testing; you can take some images and try to show paths. Try to document your design process while paper prototyping. There are some free apps for that, check POP if you have a IOS device. Other than that, scanning is also fine, it will take longer time in my opinion. Gifs are also working really good if designs ...


3

As Michael Lai has mentioned in a comment there are tools for rapid prototyping as Balsamiq Mockups, Webzap, Axure, etc which let you make a fast and simple prototyping without losing time and energy. Also they save the energy of thinking "is it well sketched? is it too messy? what if I have to change a little thing, should I add it in Photoshop or by ...


3

I would say it's a great approach: People are (on average) more familiar with phone interfaces than desktop interfaces these days Phone interfaces require less drawing: big buttons big text, on a small screen. This means that they can draw many ideas fast, and iterate quickly in a short workshop. The difficulties are more immediate: with a desktop, people ...


2

Mobile first is a nice way to find MVP and designing the golden path[compose an e-mail for a mail app; ordering a meal for home delivery service.]. However; starting from the screen is not a good idea but start from service itself. Here are some more: Have a demo project with you before starting such workshop.If it is not clear show them a finished ...


2

Good question. I often like to go with sketches early on, a few pointers: If you want to present sketches, set that expectation with the client. Tell them why you're presenting sketches (quicker than doing higher fidelity wires) and that eventually you will get to wireframes. Give them the option to go right to wireframes, but of course, this would impact ...


1

ask your clients up front make sure they "look natural" - not all gray, not total saturation, ... photos of a whiteboard usually look better than photos of a paper sketch


1

Since your group of stakeholders is so varied it may be a good idea to first have them list their priorities for the core functionality; and then have them sketch out how that functionality would translate to a mobile environment. I would also recommend familiarizing them with the needs of interface design. Jakob Nielen's "10 Usability Heuristics for ...



Only top voted, non community-wiki answers of a minimum length are eligible