Ruth Stalker-Firth

The Fresenius Kabi Applix Smart food pump is a masterclass in bad design. There is nothing smart about this food pump and its accessories. It has been designed without taking into consideration the context in which it is to be used. Consequently, some of its accessories are not just safe enough to used around patients and the home and could lead to the compromise of patient safety.

When designing any form of interface, a usability consultant will push for the interface to be: effective and efficient; easy to learn and remember; useful and safe.

After usability comes user experience (in this medical context perceived user satisfaction is enough, as it is never going to be fun to use a food pump on a chronically ill person) which encourages users to feel supported and motivated by a helpful interface.

Fresenius Kabi has failed the user of the Applix Smart food pump on usability and user experience. (more…)

So, you have decided to create your own website. You have read all the latest articles, bought a domain name, and now you are staring at your holding page wondering what your website is for and what you should put on it.

Never fear, function-behaviour-structure (FBS) theory can help. FBS is a popular artificial intelligence design theory and like all good fairy godmothers, it will answer your three questions:

1. Function: What is the purpose of your website?
2. Behaviour: What will your website do?
3. Structure: What structure will your website take? (more…)

A bridge, building, or piece of software may exist for many years. Or, as often happens in the case of new software, be scrapped before it is put into use. My mate Wayne, a professional software developer for over 12 years, has worked on several projects which were canned before they were completed. In a world of ever changing requirements and circumstances, ‘it’s not unusual’ as Tom Jones would say. Software development can take months, even years of effort, so scrapping the results is a waste. To counteract this, we have libraries for software reuse, design patterns and templates to avoid reinventing the wheel.

But why just reuse the product template or pattern? Why not template the tasks the artefact underwent during its lifecycle? By extending the theory of function, structure, and behaviour, there are eight tasks in an artefact lifecycle. (more…)