Archive for January, 2010

Performance, Data Pixels, Location, and Preattentive Attributes

This entry is part 8 of 12 in the series Medical Computing

A good principle for medical software is to design for the ED as a worst-case scenario. If it works there, it will work anywhere.No clinicians are as time-pressured as those in a busy Emergency Department. There, distractions – even seemingly minor ones like presenting a complete CBC instead of an abstract – slow the clinician […]

Share

Information Design

This entry is part 7 of 12 in the series Medical Computing

Wikipedia says: Information Design is the art and science of preparing information so that it can be used by human beings with efficiency and effectiveness. It goes on: the term has come to be used specifically for graphic design that has the purpose of displaying information effectively, rather than just attractively, or for the purpose […]

Share

Goals vs. Tasks

This entry is part 6 of 12 in the series Medical Computing

In past articles, we discussed human-illiterate computers, usability, memorability, learnability, Tognazzini’s Paradox, design integrity, simplicity, abstraction, discount usability testing, and personas. Now, we will discuss goals and tasks. These are similar terms, and sometimes used almost interchangeably. But using the terms task and goal sloppily is, according to expert software designers, an error that leads […]

Share

Personas

This entry is part 5 of 12 in the series Medical Computing

In past articles, we discussed human-illiterate computers, and we discussed usability, memorability, learnability and Tognazzini’s Paradox: how  changing a single word can make big differences in usability. We also discussed design integrity, simplicity, abstraction, and discount usability testing. Now, we’ll talk about personas. It seems to me that personas are a bit like Critical Incident […]

Share