Learning to Play UX Rugby

These are my slides from this last weekend’s excellent Agile UX NYC conference.  One clarification I need to make.  Early in the talk, I describe “designing ahead” as an anti-pattern.  From conversations that followed, I think a lot of people took that to mean that designing ahead is bad outright and something you should not do.  There is nothing inherently wrong with designing ahead; the problem lies in how you think of designing ahead, ie is it something you do as a matter of course, or is it something you try to do as little of as possible, and who is it that is designing ahead? The UX designer alone or the whole team?  More about that in my blog post on this topic.

So, with that out of the way, here are the slides from my talk:

And here’s a video of my talk, courtesy of Yasunobu Wayaguchi


UIE Podcast with Jared Spool: Applying Agile Values to UX Practice

UIE just published this podcast, where I have a great discussion with Jared Spool about how I’ve applied Agile thinking and values to UX practice. Here’s a sample from the beginning of the podcast, where I talk about how this thing we call Agile is really historically upside down…

Jared: …it feels to me sort of like an onion, in that you’re always seeming to peel things back, and at the core of it are these Agile values that really, I think, speaks a lot to what people are trying to do and why this really is something more than just a fad or just a re-branding of something we already were doing.

Anders: Yeah. So what’s interesting and maybe confusing for people who aren’t aware of the history is that even though the “Agile Manifesto” you know, was formulated in 2001, that was something that was many, many years in the making. And it’s really sort of turned upside-down, because the methodologies that people are familiar with, they actually existed before that term “Agile” was coined. And, in turn, those methods originated from what was generally referred to as lightweight software-development methods.

So I see myself as being more of an adoptee of these earlier, original elements that became the basis for Agile. And Agile is more just like a brand, a term. It’s something that we can all refer to. We can just talk about Agile. We’re referring to this kind of way of thinking about design in general and software specifically.

Check out the full podcast.

If you want to learn more about applying Agile values to UX practice, be sure to check out my upcoming UIE/Rosenfeld Media Next Step Series virtual seminar.


Be sure to check out my upcoming virtual seminar on this topic, which is a collaboration between UIE and Rosenfeld Media.

Agile UX For Developers (or why fluff is stuff too)

So I’m tooling around the web and come across this video of a workshop I did at Agile Roots 2010. The main audience for the workshop is Agile developers, and it seeks to convey how the UX practice is a different dimension of work, separate yet inseparable from software development, yet equally critically to the success of the overall product.

The sound quality is a bit iffy in the beginning (due to me waving my hands around and forgetting that one of them is holding the microphone), but get past that and there are a few good nuggets for anyone who wants to better understand how UX and coding are two dimensions of the same thing.