Some thoughts about Twitter
Random thoughts about Twitter as an ad hoc social platform, intimacy, the relative nature of phatic communication, and forgetting.
Random thoughts about Twitter as an ad hoc social platform, intimacy, the relative nature of phatic communication, and forgetting.
A look at how to put an Only statement together, as well as how it works using the I.A. Institute as an example.
Six ways to be more agile and better integrate user experience and information architecture into agile development teams.
Agile's focus on small iteration needs a team that can build the now, remember the future, and recognize the gap between the two.
In an agile process with a rolling series of sprints, UX requires two, parallel work streams, clear expectations, and constant status reports.
Dumb, aggregate metrics like unique visitors and total page visits give no real insight into your site's success. You need behavior-based metrics.
Just launched a new design. I'm proud. Not because it's the greatest design ever, but because it really matches who I am with what I need.
Clarify the "compared to what", and all of a sudden your whole team is now answering the same question.
I'm wondering how important is secrecy to the people who operate at our cultural borders. Does it really matter?
Nielsen shares how frequent usability tests keep you usability focused. I want to know how you keep yourself experience focused.
Holger Struppek writes a fantastic case study on the new interface design for Wells Fargo ATMs for 'Physical Interface'.
I'd like to get some feedback on the "health check", a method for quantifying the quality of a user experience.
For all our galumphing, we have only seven primary design activities, and these are them. Exterminate, annihilate, destroy.
Fred Collopy discusses the difference between designing and doing, and why you'd choose one over the other.
Wilson Katter's "business deal basics" provide solid guidelines to help you sell and negotiate design in any organization.
Revisiting Target's CleaRX and the tried and true prescription pill bottle: The design that gets built is the only design that matters.
If you have two seconds, I'd like to hear what questions about information architecture do you deal with on a frequent basis.
Clarifying the purpose for a rating can dramatically change the quality of the decisions you base on that rating.
Add clear, specific purpose to your rating scale help and your ratings actually mean something. Specify: why are you measuring this?