Monday, 12 July 2004

Usability Not Usable? – Part 2

“People are usually not receptive to a newcomer waltzing in and telling them they’ve been doing their jobs wrong.”

Usability departments exist in a number of our client organizations. Unfortunately, their organizational structural frequently instills an adversarial relationship between the project teams and usability group. The usability group is considered an outside agency – ony evaluating ‘ready for prime time’ work.

This relationship places the usability professional in the lose-lose position of telling the project team their baby is ugly.

Here are 3 tips for making this process more valuable for everyone:

  1. Invite everyone in all the project meetings from the start. This includes developers, usability professionals, project sponsors, clients, and even a customer or two. (and make the meetings working meetings)
  2. Evaluate early and often. The earlier in the project customer insight is captured, the more valuable is it to the project (and the customer). The project is less malleable as time progresses, more decisions (good & bad) have been made, more constraints exist. Everyone learns from early evaluation.
  3. Create, don’t just destroy. Usability evalutions are most valuable and insightful when participants are offered alternatives to compare. Perhaps alternatives don’t exist for the initial evaluation session, but they surely exist for each additional. To make the most of the evaluations the learnings from each session to the next participant in the form of a rough prototype.

The quote beginning this post is from from Ester Derby’s article Change that Fits. Her story describes a recently-fired software development quality engineer. Usability professionals should heed warning.

How to Stifle Teamwork

As an appetizer for an upcoming Work Better article on collaboration techniques, I’m pleased to present these team work worst practices from Ester Derby’s Software Managemet Process Improvement weblog:

A clear strategy to stifle teamwork

Establish two classes of membership on the team [WP NOTE: i.e. developers and testers, employees and contractors, or people with technical focus and people with business focus] , then follow these steps to ensure that all are aware of the distinction

3) Hold meetings to discuss project business, and exclude the 2nd class team members. If they ask to attend, tell them the meetings are to discuss topics they don’t need to know about… or say “This is meeting is only for 1st class team members.”?

4) Swap in new 2nd class staff frequently (2nd class team member are fungible, afterall, unlike more important 1st class team members). This is a double-header strategy – it slows down progress, too!

8) Blame the 2nd class when the so-called team fails to work together effectively…“They just don’t understand how to work as part of a team.”?

For all 8 helpful hints, visit A clear strategy to stifle teamwork.

As illustrated by this article, teams are about quality interpersonal relationships. If the office culture doesn’t support building collaborative relationships – failure is imminent. For the project, the team, and the organization.

Thursday, 8 July 2004

Mobile Phone Etiquette Tips

SprintPCS has partnered with etiquette expert Jacqueline Whitmore to compile an excellent list of 10 mobile phone etiquette tips

Number 1…

Let your voicemail take your calls when you’re in meetings, courtrooms, restaurants and other busy areas. If you must speak to the caller, excuse yourself and find a secluded area where you can talk

Thank you SprintPCS for publishing this list. It should be distributed with every mobile phone sold.

Wednesday, 7 July 2004

Back From the Holiday

The Work Better Weblog is back up and better than ever after a quick Holiday rebuild. Thanks to all the loyal readers for standing by during the past few days.

Thursday, 1 July 2004

Instructions not Inventory

To create a to-do list reflecting your ultimate goal, we highly recommend taking the advice descibed in Recipes Instead of Lists from Nerdherding for Beginners:

“A recipe will include infrastructure work and ‘planned re-work’ that might otherwise be forgotten the alternative is simpliy a list of ingredients.”