Usability broken.


Published on

This is a deck i would often use highlighting the mess of website irrelevance I call today, and its associate sites.

There is way to much noise and not enough signal and the deck hopefully highlights one slice of this reasoning.

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide Usability broken.

  1. What you gonna talk about Scott?<br /> A grab bag of ideas on evaluating design & principles that govern them.<br />
  2. UI?<br />User Interface?<br />
  3. What is a good user interface?<br /> A good user interface design encourages an easy, natural, and engaging interaction between user and a system, and it allows users to carry out their required tasks.<br />
  4. What is Usability<br /> Usability can be defined as “the extend to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context”<br />
  5. What is Context<br /> The setting in which an item of information appears<br />
  6. Chapter 1<br />THE WHY…<br />Why do we bother with design?<br />
  7. HUMANS<br />You know they are bloody annoying<br />
  8. Mental Models.<br />We humans have models of ourselves, others, the environment and the things with which we interact. Humans form mental models through experience, training and instruction<br />
  9. Habitual<br />Any change scares most humans. Humans are by nature habitual creatures.. we all have our daily rituals that when disturbed can really upset us<br />
  10. Emotional<br />Emotion plays a role with UI today. A poorly designed solution can increase stress levels of employees which can actually be linked to sick days and/or under performance.<br />Rage Against the machine (Compaq 1999), found that, for one reason or another, stress and frustration levels with workplace technology are rising.<br />Oct 2002. Research for British Telecom (BT) Home Computing found that 70% of personal computer users suffered from “PC Rage” – that is, the users surveyed admitted to shouting, swearing, or being violent to their computers when problems occurred.<br />
  11. The story?<br />How design begins…<br />
  12. Well…we need to rebuild our pipelines a lot, given plans have changed…<br />
  13. “..That sounds expensive.. Can’t we just upgrade / patch it a bit more?..”<br />NO!<br />
  14. We need tostopputting band-aids on broken limbs.<br />We need long-term vision and synchronization.<br />Stop gaps aren’t helping the ecosystems roles & skills out…<br />It’s not expensive..<br />
  15. Chapter 2<br />THE WHAT…<br />
  16. Let’s look at WHAT we own<br />Let’s work with those WHO<br />own them<br />Let’s BEGIN..<br />Where do we start?<br />
  17. What do all of these have in common?<br />They require you to think in multiple personalities and roles..<br />They can be quite frustrating to discover and use..<br />they all try and be different, but the end user is usually the same…<br />They require unnecessary persistence…<br />They echo the same data at times.. at a rate that<br />makes your head spin..<br />
  18. Question:<br /> Are these sites serving OUR needs or the CUSTOMERS?<br />
  19. Answer:<br />Well..that’s not fair…not all customers are the same!!<br />e.g. Designers and Developers are different from one another,<br />So therefore the content and approach is likely to always require different tactics.<br />
  20. Where we are today, doesn’t mean we’ll still be here tomorrow<br />
  21. Each role or skill we cater for is different, this is true.<br />Building multiple sites isn’t the answer to solving this. It just makes them more confused and helpless.<br />However, Contextual Synchronization is a possible answer…<br />
  22. CONTEXT?<br />(The setting in which an item of information appears)<br />
  23. Let’s use Zune as an example of context working..<br />
  24. You can explore based on taxonomy…<br />Or.. You can Search…<br />You can browse based on visuals...…<br />You can explore based on recommendations..<br />
  25. A: It’s always reminding you of the chosen context in which you are searching..<br />Context is when your answer will always come back in a manner that suites your end users needs…<br />Q: Do you notice how the zune results shows “The Fray” in black, and the rest of the words in gray?<br />
  26. How long do you think it will be before a new site is added here?<br />POINT?<br />We aren’t being contextually sensitive to our online consumers needs. Instead we’re separating context into their own branded existence. The problem is the answer is never obvious, it instead requires HUNTING….<br />
  27. Question:<br /> What’s the difference between an ASP.NET developer and a SilverlightDeveloper is?<br />
  28. Time to play the role of innovator..<br />Not follower..<br />