Recent reads - using data

February 2nd, 2010

The Birth (And Death) of Market Research: Why Design Research Will Prevail (Sam Ladner)

This article suggests that summary statistics relied on by market research companies are no longer relevant and qualitative research of the long tail is where the money’s at:

  • “Design research uncovers how long-tail niches develop and what differentiates them.”
  • “…design research is about knowing what to build as well as evaluating the prototype.”

When Data Gets Up Close and Personal (Stephen Anderson)

A good contemplative piece about tracking performance and creating feedback cycles. As an example, Stephen has considered how you could make a “game” out of email by considering motivating factors and presentation of progress.

  • “What we’re really talking about is setting up systems whereby individuals can (1) see in a tangible way (2) reflect on, and (3) learn from their past behaviors.”
  • “Get creative with how you represent the data– our brains will thank you for that with extra attention.”

The 4 Big Myths of Profile Pictures (OkTrends - Christian)

Well… the post is about dating site profile pictures, but I think that it’s a good showcase for data analysis. They’ve done extensive research and they’re using it to give advice to their users = users get more successful results from the site = spreading the word to friends = more money for the business.

The 2 in 100 who might matter most - your core web audience (Seb Chan)

Seb Chan from Sydney’s Powerhouse Museum provides an example of how he looks deeper in to the museum’s site traffic data to realise that 2% of people are visiting the site 10 or more times in a quarter.

  • “Whilst we all like the big figures of casual visitors we get to our websites many institutions, having flirted with social media, we are beginning to realise that casual visitors, much like casual visitors through the door of a museum, aren’t so useful for building sustained co-creative relationships with.”
  • “This 2.10% is one that needs a lot more analysis as does the ‘5 or more’ category. How do they arrive at our site? What are they looking for? What do they spend most time looking at?”

Analysis Ninjas: Move Beyond The Top Ten. Find Love (/Insights) (Avinash Kaushik)

  • “You know what is the one thing stopping you from finding truly actionable insights from your web data? Web analytics gems lie deep in the data and we spend our lives looking at the top ten rows of data.”

This article encourages investigation of the long tails in site traffic data to pin-point opportunities and shows how to make sense of what at first might seem like data overload. Avinash provides examples of how to apply advanced table filtering in Google Analytics, generate tag clouds (I’ve given this a try with a client’s search keyword data and it sprouted some very useful visuals), and how to set up keyword trees with Juice Analytics.

Back to Basics: Tip for exporting rows (Google Analytics blog)

This is a brief tutorial to show that while Google Analytics allows you to export up to 500 rows of data normally,   to export more (eg. all your search keyword terms) you can add &limit=xxxx (where xxxx is a number more than the total number of results) to the URL and then download the CSV to retrieve all the data.

Charting the Beatles (Michael Deal)

Beautiful infographics [swoon] !

Recent reads - accessibility

January 30th, 2010

Web accessibility myths (Ian Pouncey)

“…open content that is inaccessible to 50% of people is better than content that is never published. Ideally it is published with a license that allows others to take it and convert it to different forms which may be accessible, but this isn’t possible if it only exists in a file on someone’s desktop.”

Testing for Accessibility (The Pennsylvania State University)

Suggested protocols and tools for testing web sites for accessibility.

[Draft] Contacting Organizations about Inaccessible Websites (W3C)

Advice from the W3C Web Accessibility Initiative on how to approach companies with inaccessible web sites and the type of information those companies may need in order to help them make their web sites more accessible.

Recent reads - form design

January 24th, 2010

Last week I was doing some research on form design and jotted down the following links and thoughts:

The Apple store’s checkout form redesign (Luke Wroblewski)

A lengthy article reviewing the old and new Apple store checkout process highlighting the good and bad points.

  • Under “Dynamic Indication” is an explanation of how you can detect the type of credit card people are using based on the first few digits of the card. Minimising the amount of information people enter on a form is good.
  • Under “Primary Action” is an example of helping users move forward through a process by clearly distinguishing the “continue” button from every other item on the page.
  • Under “Error Messaging” is a point about clearly distinguishing which fields have errors and why - Apple’s use of yellow field highlights can be confusing. I disagree with the authors suggestion however to use red alone for error highlighting - a differentiating colour backed up with simple instructions may be sufficient and less likely to make the person feel stupid/at fault.

Marking required vs. optional form fields (Luke Wroblewski)

Suggests showing the word “optional” with the field labels instead of marking mandatory fields with an * is more user-friendly.

23 forms and data entry usability guidelines (User Focus)

A usability checklist when designing and building forms.

In-line tips (an example)

I personally like the treatment on the PlainFrame Early Access form to show tips in-line with a form - hover your mouse over a question/field and you see tips on the right-hand side. It reduces the length of the form and can be easily ignored by people more familiar with the terms they are being presented, or those who don’t wonder why they’re being asked particular questions.

I haven’t checked out how accessible it is, but if it’s not then there would be work-arounds to make it accessible.

PlainFrame In-line tips

Oz-IA 2009 - general thoughts

October 5th, 2009

The Oz-IA 2009 Conference was held on Friday 2nd and Saturday 3rd of October 2009 at StarCity’s hotel in Sydney. I missed the 2008 conference, but I have compared my experience with the Oz-IA 2007.

The conference maintained the two-day, single-stream format which allows you to take in all sessions and relax a little in between. I enjoyed the mix of short and long sessions and in most part I think the session-lengths were matched well with the presented topics. Overall organisation was good, everything rolled along smoothly, and there was plenty to see, hear and ponder upon.

A point of difference to me was the use of video in a number of presentations - I don’t get the chance to attend conferences too often but I can’t recall any presentations at Oz-IA 2007 including video clips while this time around video was used a number of times. The presentation styles in general were engaging, with the occasional bit of quirkiness thrown in.

Day 1 at Oz-IA

There was a greater focus on discussing the application of IA and related themes in real-life scenarios. In 2007 I had made note in my feedback that I enjoyed the presentation about the re-design of the SMH home page. I was happy to find that this year many of the presentations included case-studies.  On the other hand, I felt that the focus in 2007 was more-so on tools and the practice of IA which was very educational to me at that stage of my learning.

Over the next week or so I’ll write up notes and thoughts on some of the presentations I most enjoyed, but until then here are some general thoughts about aspects of the conference. They’re not intended as criticisms, just observations - I thoroughly enjoyed the conference and I will be recommending people go to Oz-IA 2010 (I’m sure I’ll be there!):

Location - I made my way to Oz-IA on the Light Rail but then found myself a bit confused about where the ballroom actually was. A little wandering around in circles and asking someone for help, I found my way. The venue itself was very good - a large room with circular tables seating around 8-10 per table. There was a very large screen and good audio for the presenters.

Wifi - Although wifi was provided, there were a few hiccups with it. I connected fine on my laptop but my iphone didn’t want to play ball. A few others were in the same boat and the organisers setup an alternative access point. I decided to use my 3G access because I only wanted to check twitter and emails occasionally.

Coffee - A barista churned out coffees through-out the two days and from reports he was very accommodating to people’s requests for particular coffees and teas. The line to get a coffee was usually quite long but I got my fair-share of coffee-fixes. IAs (and others) definitely love a hot beverage!

Mocktails - IA-themed drinks were made freshly and although the line to get them was significantly shorter than the coffee queue, it took a while to make each fresh mocktail. In between sessions I chose to ask for plain juice to quench my thirst quicker. It was peculiar that there weren’t any help-yourself juices (or perhaps I just didn’t look hard enough).

Food - The food was tasty although not as varied as the 2007 buffet at Mercure Sydney. I made a suggestion for next time to ask for labels on the food to help those of us who don’t chow-down on some food groups to make the right choices.  There was definitely a lot of food to go around and I’m sure I piled on a few kgs from the constant munching :)

Twitter - Although pre-conference emails had suggested using #ozia09 to tag tweets, late on the first day I realised that there were also #ozia tweets I was missing out on.

Goodie-bag - Great to receive a Sharpie, highlighters, post-its, a 20% discount from Rosenfeld Media, a beautiful recycled-paper Oz-IA sketchbook, all in a re-usable un-ugly bag :)

A big thanks to Eric Scheid for yet again organising an information-packed, friendly conference.

Oz-IA Day 2

Recent reads

September 23rd, 2009

Short notes on articles I’ve read recently:

Audience Segmentation Models by Steve Baty

Outlines methods (other than personas) such as market segmentation, mental models, and capability levels, to segment audiences for understanding user requirements and defining the user experience. “The use of a variety of different audience segmentation models can inform the design of products and services in different ways.”

One particularly interesting off-shoot is an Experience Lifecycle diagram for when Lego’s senior execs travel.

Designing Tables 101 by Mike Hughes

When to use tables and how to present data. There are suggestions for what information should be in columns and rows based on readability. Unfortunately no general insights about accessibility*, but these suggestions can be applied not only to reading tabular data on web pages, but also when writing documents for clients, etc.

* it wouldn’t have been appropriate for the aims of the article, I’m just personally interested in exploring that topic more.

Testing Your Own Designs: Bad Idea? by Paul J. Sherman

Tries to answer the questions: “Is it possible to do both design and usability testing effectively? If so, how can we test our own designs well?” Includes thoughts from others on the topic that focus on the idea of avoiding bias, or being aware of it. If you have to test your own designs, focus on the negatives (things that don’t work) and remember the requirements you’re aiming to fulfill.

A shorthand for designing UI flows by Ryan Singer

Demonstrates a simple approach to sketching a user path for completing goals by jotting down what they see and what they do at each step. The idea is summed up well by his response in the comments: “Sketching a flow isn’t about meticulously documenting everything that’s possible on a given screen. It’s about taking a single goal and asking how does the user get started, what happens when they execute the action, what are the main forks in the road, and what happens when they are finished. If you scope the flow by a specific goal instead of by screens, then there should be fewer complexities.”

Integrating Prototyping Into Your Design Process by Fred Beecher

Explains how combinations of low/high visual/functional fidelity in prototypes can achieve particular goals. Consideration is given from sketches through to “production ready” prototypes. The article also provides tips on how to encourage the use of prototyping to different types of project stakeholders. At the heart of it all, “‘Appropriate fidelity’ refers to a level of prototype fidelity that allows you to achieve the goals you’ve set for doing a prototype in the first place.”

Second-degree conference value* from UX Australia

September 10th, 2009

Although I didn’t make it to (what sounded like an amazing) UX Australia conference in Canberra the other week, I’ve been learning from the presentations that have been posted so far on Slideshare.

I haven’t looked through all of them but here are a few particular presentations and my notes about points I found useful:

  • Uxau09 More Content Quality B - David More
    Looks at how to develop collaborative/useful information architecture in complex organisation with plenty of stakeholders; and getting non-expert authors to generate content.
  • Emerging a User Experience Strategy - Penny Hagen
    An example about the process in creating a user experience for UNSW.
  • Experience Visions: A Case Study - Fred Randell
    About experience visions and dealing with Telstra, which provides good tips for dealing with large/complex organisations/developments.
  • More, Better, Faster! Agile Design for Fun & Profit - Matt Balara
    A useful overview of agile development. There’s a short case-study from slide 57 onwards about the redevelopment of the ecco shoes web site which visually shows the process.
  • Design For Multiple Touchpoints - Shane Morris
    Has some information about the process behind developing the Lonely Planet Surface, and includes information about how people interact with things they can touch (which can also relate to iphones, mobiles, screens, etc)
  • Ka-chunk! When customer experience design fails and how to avoid it - Joel Flom
    I like the general statements in this presentation, and the diagrams on Slides 21 and 22 showing balance between business, customer and implementation.

* “second-degree conference value” is a quote from UX Australia organiser, Steve Baty, when I referred to how much I was learning without being there.