Skip to main content

Home/ Groups/ UI mobile
Rss Feed
Sort By: Most Recent | Popular Filter: All | Bookmarks | Topics Simple Middle
Merja Bauters

UXPin - 0 views

blog.uxpin.com

mobile design ux

shared by Merja Bauters on 30 Oct 12 - No Cached
Merja Bauters

Touch Usability - Touch Usability - 0 views

www.touchusability.com

usability touch blog ux

shared by Merja Bauters on 01 Oct 12 - Cached
  • Merja Bauters on 01 Oct 12
     
    look at the book list also
Merja Bauters

Mobile usability testing: Advice on how to use it - Usability Research - Spotless Inter... - 0 views

www.spotlessinteractive.com/...e-usability-testing-advice.php

mobile usability testing advice how to

shared by Merja Bauters on 01 Oct 12 - No Cached
  • Merja Bauters on 01 Oct 12
     
    A good o summarizes main points
Merja Bauters

A List Apart: Articles: Audiences, Outcomes, and Determining User Needs - 0 views

www.alistapart.com/...mes-and-determining-user-needs

users user needs UX

shared by Merja Bauters on 30 Sep 12 - No Cached
  • Every website needs an audience. And every audience needs a goal.
  • So we go to the source: we interview, we learn, and we determine who, exactly, these mystery users are.
  • who are our audiences, and what do they want from our website?
  • ...13 more annotations...
  • They begin as amorphous blobs of assumed stereotypes.
  • develop characteristics and quirks.
  • Outcomes must be measurable, otherwise they’re not goals—they’re aspirations. Without considering how an outcome will be measured, we cannot accurately represent the benefits—or the viability—of a user outcome.
  • use audiences and outcomes to create user personas
  • We refer to them by name in meetings
  • We are not the audience.
  • Step 1: The discovery meeting Step 2: User interviews Step 3: Project deliverables: audiences, outcomes, and persona
  • There’s one goal: to get this group talking. Invite a small number of people—five to seven—and make sure someone from the front line is there.
  • . One will lead discussion, the other will document the discussion and provide an extra brain to ask and answer questions.
  • The meeting should be an open forum for discussing the website’s needs and goals.
  • no more than an hour
  • introducing everyone, introducing the process, and explaining how it fits into the overall site plan.
  • Bring big markers and whiteboards and anything to get ideas up in front of the group. Then, make two huge spaces for the following headers: Audiences - Outcomes. Then it’s time to start asking questions.
  • Merja Bauters on 30 Sep 12
     
    Important
Merja Bauters

A List Apart: Articles: Beyond Usability Testing - 0 views

www.alistapart.com/...beyond-usability-testing

usability testing ux mobile

shared by Merja Bauters on 30 Sep 12 - No Cached
  • there’s no substitute for research conducted with actual users.
  • . I don’t know anybody who’s seen their work tested without being surprised about how wrong some of their best guesses were.
  • l. Even remote testing—which has its limitations—can be expensive, because analysis of the testing data is still no easy feat.
  • ...3 more annotations...
  • analysis is often the biggest component of the project.
  • testing videos and cataloging the qualitative data
  • standouts, expert review and heuristic evaluation,
Merja Bauters

A List Apart: Articles: Product Management for the Web - 0 views

www.alistapart.com/...product-management-for-the-web

project management web mobile design ux

shared by Merja Bauters on 29 Sep 12 - No Cached
  • , but when we’re evaluating UX and usability we must step away from our desks and spend time with customers
  • That’s why there’s a growing community of user experience practitioners who focus exclusively on user‑centered analysis and prototyping. On many teams, they fill that role exclusively.
  • Product managers spend most of their time meeting with others to discover new needs, and research the needs that others have voiced.
  • ...9 more annotations...
  • s using surveys
  • Filter all of the data you collect and share it with the people who’ve informed yo
  • The product manager's main deliverable is the user story.
  • User stories are not requirements, specifications, or designs
  • As the web product manager, it’s your job to set user story priorities,
  • A road map is a visual representation of the top user stories in the user story backlog,
  • : you must be passionately committed to your customers and colleagues, yet objective about setting priorities that help them.
  • This example shows how you can take a longer list of user stories and break it down into smaller amounts of work that can be spread across a team. Those smaller amounts of work can be communicated in release schedules, and you can report on those schedules in a product road map.
  • you user-validate what you’ve done, and see what needs to be improved next. Then the product manager prioritizes new user stories and sets new release dates to continue improving the site or the app.
‹ Previous 21 - 40 of 77 Next › Last »
Showing 20▼ items per page