Hot answers tagged mockup
13
This answer applies to most presentations, not just UX ones.
A good presentation is like a story, where you take your audience on the journey that you want them to experience. If you send the presentation to them ahead of time, you lose the ability to take them on that journey.
There are other potential negatives as well in that your audience may start ...
9
Just a few days ago, I accidentally stumbled upon Usaura. You should definitely first go to Take a public test and run through at least 5 or 10 different tests to see what kinds of mockups and interactivity there is. I think this will be a good solution for you.
Edit: I found an alternative solution, called Verify. I haven't tried it, but it seems to be ...
7
A/B testing is about optimisation. Mockups and user testing are about insight.
User testing (even with a small sample set) will help give you insights into what potential problem areas may be so that you can find ways of improving them. This should be your goal, not trying to optimise a design.
A/B testing, needs large sample sets to make any conclusion ...
4
In my own experience, low-fidelity mockups are rarely clear to the people who are not familiar with wireframes even if they're accompanied with a full description or comments, so I don't think you should send them ahead of your demonstration because it may introduce wrong assumptions and expectations (as it was already mentioned by @JohnGB).
But, taking ...
3
I can only provide you with my experience having experimented with many different types of stimulus for users.
The original statement about getting the right fidelity is spot on. In general it is possible to get similair results from end users in most situations but if it's too far from the final result you run a risk of some users not really getting it.
...
3
For quick and efficient mockup testing, I recommend using any program that can link 2 images and Silverback for recording the users sessions.
Build a small user panel (5-7 people) - more if you can...
Write up a short scenario which tells your users what they
should accomplish before testing the flows.
Build 2 versions of the same flow using your mockups ...
2
In design meetings part of my process with clients is making sure I show them all my wireframes. In other words I show them the key ideas I discarded as well as my more final solutions. I find that this really helps create a good open discussion about the options. And it forces me to explain my design rationale.
I tend to use very quick prototyping methods ...
2
I am all for presenting wireframes and other concepts in person.
Nothing better than seeing the reaction on first view and dealing with mis-conceptions ASAP.
That said - there will always be times when this is impossible. Perhaps an executive wasn't present at a meeting or you need to explain concepts to a third party.
In this situation I would recommend ...
2
Personally, I love Balsamiq because it allows you to focus on the information and interaction, and not needless details. This is right level for functional design that has to be passed around and agreed upon.
However, this has to be translated into detailed specific layout. This is best done by the actual developer, and possibly with an agile review cycle ...
2
The purpose of mockups is to communicate ideas. Depending on the stage of development you select the appropriate fidelity.
During the initial phases you are debating different features and layout options in your design, a low fidelity prototype easily captures this (animations/transitions are not the kind of features I am talking about here). You can add ...
2
A resource to consider is the 5 second tests site which can give you valuable inputs on the main focus points on your site.
Click Test is also another useful resource as it provides good inputs on where users are clicking via heatmaps and click overlays
However the 5 second tests might not work too well if your site has a lot of content (refer to this ...
2
Yes, they do. Low fidelity tends to get people to focus on the higher level aspects of the mockups, like the overall layout and concept.
While with high fidelity mockups people tend to focus on the lower level details like "this should be two pixels to the left", or "this needs to be a different shade".
That is one of the reasons that I recommend ...
1
With regards to your question about why paper prototypes dont seem to be too effective, I believe its because with paper prototypes you have to ask the user to visualize the environment (e.g. if its an app,he has to visualize its not a piece of paper with a drawing but an app with which he can interact and similarly for a website).
To quote this article ...
1
It sounds like your designs (or mockups) are overridden due to your client not having buy-in in the designs. You can do a simple think-out loud study with scripted tasks (and steps), even paper sketches or printouts might suffice. This process will still give you valid information to inform your design process.
Different sets of mock-ups will be useful if ...
1
Give users some guidelines of what to do next.
It could be done vertically: just place the information one after another in the desired order.
Or, in a case you have a lot of information, it could be a wizard-like bar at the top of the page which will guide user through the screens at desired order:
But in a case of the horizontal bar, let user jump ...
1
Some books, like Read This Before Our Next Meeting, suggest sending material on ahead of time. Of course, this only makes sense if they can make sense of whatever you send them.
If it's stuff they're meant to be reading before the meeting or it's related material (like research articles you found about the feature in question), the let 'em read, but if ...
1
http://www.bagelhint.com
It is easy to setup and the pricing is hard to beat. I used the click test to verify that the item we wanted to be most important was actually what drew the most attention.
They have click-tests that tell you where a person would click when looking at a screen.
A/B test reveals which design is preferred.
10-second reveal and ...
1
For annotating the mockups, it's good to use a tool like specctr, but anything which gives you a new layer is fine.
You mentioned that fireworks is not part of your toolset right now (it's a very nice tool), well, specctr is expected to have a photoshop version sooner or later, but on the other side, it's a matter of a few lines. Tools like Microsoft ...
Only top voted, non community-wiki answers of a minimum length are eligible
