Re: [agile-usability] Usability testing a UI that has limited functionality
- The "Napkin Look and Feel" is a great idea but could one just use "comic sans" or a similar font to mark non functional areas?On Fri, Jun 20, 2008 at 12:49 AM, William Pietri <william@...> wrote:
Hi, Leina!Why would you create a shell with some functionality that works and some
> What is the best way to conduct usability evaluation with real users on
> an interface that has limited functionality (created in an agile
> fashion - shell with funtionality that works and others that don't).
that doesn't? Typically, Agile teams of my acquaintance keep things in a
releasable state, with no visible loose ends. Is it so that you can see
what things will look like down the road?
If you do want to set up the whole UI but have some things not work, you
can communicate the state of various items by making the rough parts
look rough. The "Napkin Look and Feel" project is a neat way to do that
I'm not sure if that would help your usability tests or not, but I
thought I'd mention it.