Skip to content

EPSScentral .infoREADER

Sections
You are here: Home » Previous .infoReaders » 28 March 2006 .infoREADER

28 March 2006 .infoREADER

Document Actions
Subscribe to the .infoReader newsletter. Enter email address:

Not receiving the newsletter? After subscribing, you may need to check your SPAM box for the confirmation email. Thank you.

$Account.OrganizationName
28 March 2006

in this issue

Mobile Interaction Design

2006 PCD Awards

Embedded Micro Browsers Offer Enhanced Navigation Within Web Pages

Evaluation of integrated software development environments

Users Interleave Sites and Genres

Interaction Modeling


 

Mobile Interaction Design

Matt Jones

Amazon's book description:

Mobile Interaction Design shifts the design perspective away from the technology and concentrates on usability; in other words the book concentrates on developing interfaces and devices with a great deal of sensitivity to human needs, desires and capabilities. Presents key interaction design ideas and successes in an accessible, relevant way Exercises, case studies and study questions make this book ideal for students. Provides ideals and techniques which will enable designers to create the next generation of effective mobile applications. Critiques current mobile interaction design (bloopers) to help designers avoid pitfalls. Design challenges and worked examples are given to reinforce ideas. Discusses the new applications and gadgets requiring knowledgeable and inspired thinking about usability and design. Authors have extensive experience in mobile interaction design, research, industry and teaching.
 

Purchase from Amazon.com


 EPSScentral Links

Evaluation for Learning, Competency and Performance

Part II:  Questions from our infoREADERs

I promised a follow-on to last month?s general remarks concerning Quality measurements that foster performance and competency.  To this end, let me respond at the same time to a number of readers who made inquiries similar to the following:

"Dear EPSScentral - I have not been able to find much in the way of measurement with respect to performance other than return-on-investment (ROI).  Although ROI is important to document and critical to success, I need more than comparing pre- and post-tests to justify true performance improvement.  Any suggestions?"

EPSScentral's Response:

A number of tools and techniques have emerged around measurement for performance support.  Such measurements are really nothing new:  They are the "Q"uality measurements a la Deming, such as unit time and cost, cycle time / cost and resource utilization.  For the manufacturing world, such measurements were fairly straightforward using the standard Quality tool set (Check Sheets, Pareto Charts, Histograms, Ichikawa diagrams (for determining root cause), and more.  Depending on the performance issue, you would measure things like total time to produce a complete widget, unit times for completing the sub-processes that comprise the widget (unit times), the costs involved, and examine these against resource utilization (percentage) and evaluate problems such as bottlenecks, broken processes and tasks that consume resources but are of no consequence (e.g., "checkers checking checkers"...busy work).

All of this is fine for manufacturing, but in the world of enterprise systems and computer-mediated work, the corresponding units, cycles and the like happen at a much faster rate and in situations where the business rules change frequently.  The same quality measures and principles apply, but until recently we have not seen tools capable of measuring even the basics for knowledge work within computer-mediated tasks.  More recently a set of Deming/Quality-based tool sets have emerged for making proper measurements and analyzing such work.  They include: 

The common principle is to capture system metadata at a very granular level while performers go about their business.  Process / workflow is inferred from actual action while the data required to perform the Quality measurements are captured (what processes / sub-processes are completed, aborted or broken; associated times; costs; cycle stats etc).   Far superior to any pre-and-post testing, these tools capture and calculate actual performance metrics, real-time, and analyze them against expectations (criterion referenced) or based on inferred best practices from actual work being performed (norm referenced).  Statistics such as Rasch can be applied to "performance items" (in a manner similar to ?test items?) and we obtain similar distributions (e.g., standard normal distribution of tasks in the 47-70% range, associated with "perpetual intermediaries."  We are seeing some truly useful and powerful measurements and patterns emerging.  Just a few MeasureLive? results are shown below based on remotely capturing system usage across a group of users and applications:

 

MeasureLive performance graphs

 MeasureLive(TM) Results. (Used with permission www.measurelive.com.)

The next generation of such tools would include coupling the measurement tools with real-time "sensing" tools that push appropriate support to users as the quality measures are being collected and analyzed.  In real time, you would then create an adaptive performance-centered system that self-corrects, continuously increasing performance and competency.  In many respects, such knowledge delivery is the Semantic Web vision.  Stay tuned!

 

Regards,

 

 Gary Dickelman

 

 


  • 2006 PCD Awards
  • It's that time again! EPSScentral LLC is now accepting submissions for the 2006 Performance Centered Design Awards! Here's your chance to gain recognition for yourself, your organization, your solution or tool, and your business sponsor.

    Read more from epsscentral.info ...
  • Embedded Micro Browsers Offer Enhanced Navigation Within Web Pages
  • "Micro, web-page embedded browsers, open up new possibilities for navigating and finding additional relevant content with great ease of use and while never leaving the original page."

    Read more from masternewmedia.org ...
  • Evaluation of integrated software development environments
  • Abstract Evidence shows that integrated development environments (IDEs) are too often functionality-oriented and difficult to use, learn, and master. This article describes challenges in the design ofusable IDEs and in the evaluation ofthe usability of such tools. It also presents the results of three different empirical studies of IDE usability. Different methods are sequentially applied across the empirical studies in order to identify increasingly specific kinds of usability problems that developers face in their use of IDEs. The results of these studies suggest several problems in IDE user interfaces with the representation of functionalities and artifacts, such as reusable program components. We conclude by making recommendations for the design of IDE user interfaces with better affordances, which may ameliorate some of most serious usability problems and help to create more human-centric software development environments.

    Read more from www-psychology.concordia.ca ...
  • Users Interleave Sites and Genres
  • When working on business problems, users flitter among sites, alternating visits to different service genres. No single website defines the user experience on its own.

    Read more from useit.com ...
  • Interaction Modeling
  • Interaction modeling makes design decisions explicit. In principle it's simple: record what users "should" do, what they actually do, and then explain the differences between the two. Of course there's more to it than that, and Matt Queen gives us all the details in this story.

    Read more from boxesandarrows.com ...
    Receive the infoReader via Email:
    Created by rdickelman
    Last modified 2006-08-08 07:48 AM
     
     

    Powered by Plone

    This site conforms to the following standards: