partial recall

a blog of ideas, links, and musings.

Links for 2010-04-01

  • The KJ-Technique: A Group Process for Establishing Priorities [UIE – May 11, 2004] – In our consulting work, we’ve found that, like the military experts, our clients usually have most of the answers already in their own organization. The trick is to get all the people with the right perspectives to reach consensus quickly. For this, we’;ve turned to a group consensus technique we’ve been using for years, called a KJ-Method (also sometimes referred to as an “affinity diagram”). The KJ-Method, named for its inventor, Jiro Kawakita (the Japanese put their last names first), allows groups to quickly reach a consensus on priorities of subjective, qualitative data.
  • Five Types Of Cell Phone Users [MediaPost – Mar 30, 2010] – 87% of Americans have mobile phones, up from 69% in 2006. 5 classes of mobile users:
    1. Mobirati (19%) – first generation to have grown up with mobile phones.
    2. Social Connectors (22%) – Mobile phone is essentially a social lubricant, and for whom texting is just as important as a voice call.
    3. Pragmatic Adopters (22%) – Just getting beyond using mobile phones solely for voice calls. If service quality is disappointing, they will switch to another provider. They also say once they find one they like, they will stick with it.
    4. Mobile Professionals (17%) – Extra features are more important than calling, and are more likely to switch to service providers offering the latest technology.
    5. Basic Planners (20%) – Interested in basic mobile packages only, and only use cell phones in emergencies, are confused by plans and don’t use other features.
  • What is Information Architecture? [MAYA Design- Feb 14, 2009] – When we say Information Architecture (IA) we are really talking about everything you can define about a solution without specifying the underlying system (the raw plumbing) or specifying the particular user interface that will be employed to deliver and manipulate the information. By thinking about the architecture of how information is used, how it flows, and how it fits within the user’s world (its context), you can capture the essence of how to build a system that is not only intuitive but futureproof.