frontpage hit counter

Archive for the 'ux' Category

UX spectrum of methodologies

Tuesday, November 11th, 2008

Jared Spool has written an interesting continuation to the discussion he started at IA Summit 08 in the IxDA mailing list. He proposes that Activity-centered design is a subset of User-centered design. Where the former is concerned with the activity/tasks necessary to interact with the system, the latter is more aware of the context of use, goals, and motivations of the user of the system.

I created a quick diagram to wrap my head around the spectrum of methodological approaches Jared speaks to:

ux spectrum of methodologies

I see the larger bubbles requiring more process to complete while the smaller bubbles have lower and lower user involvement.

And to define each methodology I’ll borrow from Jared directly:

“0) Unintended Design: The design that results from teams that don’t pay any attention to design. This is the true rubber-band-and-spit approach to creating things. Everything ends up with a design, but not every design is intentional. Some very lucky teams end up with successful unintended design, but the odds are against this.

1) Self Design: The design that results from teams that design purely for themselves. (This happens more with single-person teams than multiple-person teams.) This design approach has better odds of success than Unintended Design, but not by much (unless the designer is the only user, such as when a bachelor arranges the contents in their kitchen cabinets). This design approach is only informed by the team members own use of the design.

2) Genius Design: The design that results from teams that use their experience at creating designs for others, without doing research. This starts with Self Design, but extends to role playing and consideration of users who are not quite like themselves. This design approach is informed by previous experience the design team has with similar work. (For example, a team that creates shopping cart systems for many clients can reduce their research efforts with each subsequent implementation, assuming the systems are pretty much the same each time. Eventually, they could create very successful without further research, since they’d basically “seen it all”.)

3) Activity-Centered Design (ACD): The design that results from teams that only research the activities. Because research is part of the design process, it extends beyond Genius Design (which solely is based on the team’s experience). This is necessary when the activities are new or foreign to the team. (For example, a team developing an application for consolidating personal finances when they’ve never thought about personal finances in any of their previous projects.) Activity-based research techniques, such as workflow diagrams and task-based usability tests would come in very handy to help inform the teams using this approach.

4) User-Centered Design (UCD): The design that results from teams that look beyond just the activities, to the goals, needs, and contexts of the users. Because usage is all about activity, this approach needs to have the activity at its core. (Early UCD definitions always included an essential “task analysis” phase — something that’s disappeared from the lexicon, but is still essential to this design. Task analysis is, as far as I can tell, research about activities, and thus the core research component of ACD.) This design approach is informed by techniques such as field research (ethnographic techniques) and persona creation, which help the team to see contextual items and goals.”

Personas - to do or not to do

Friday, October 24th, 2008

Where I work we occasionally create personas as a deliverable. The problem is sometimes it’s fabricated, sometimes, it’s based on marketing data, and sometimes it’s based on design research. Personas are a tool like anything else in a UX designer’s toolkit. It may or may not be the right tool for the project but the danger of distributing them without real research is it can derail the project and have the client holding on to archetypes that aren’t real.

Elizabeth Bacon and Steve Calde presented these slides at Catalyze webinar on July 23, 2008. They’re a great summary of why, when, how to use personas.


CanUX 2008

Wednesday, October 22nd, 2008

As always Jess and Gene have put together a great lineup for CanUX from Nov 16-18th. Unfortunately I won’t be able to attend but if you’re into breathtaking scenery as well as a great intimate workshop/conference experience this is definitely one to consider :)

Dave Gray, Founder and Chairman of XPLANE.

Dave GrayDave Gray is the Founder and Chairman of XPLANE, the visual thinking company. Founded in 1993, XPLANE has grown to be the world’s leading consulting and design firm focused on information-driven communications. Dave’s time is spent researching and writing on visual business, as well as speaking, coaching and delivering workshops to educators, corporate clients and the public.

He is also a founding member of VizThink, an international community of Visual Thinkers.

Brandon Schauer, Director of Experience Design at Adaptive Path

Brandon SchauerBrandon Schauer is an experience design director for Adaptive Path. He speaks, writes, trains, and practices experience design as a differentiator for business strategy.

Brandon’s passion for finding and understanding the unmet needs of customers has led him to diverse environments, from the homes of cancer patients to tunnels beneath Walt Disney World. This insight with customers — plus a solid grounding in business analysis and a mastery of design methods — allows Brandon to help organizations define and design more meaningful experiences for their customers.

Brandon has over a decade of experience developing new products, services, and user experiences for the web, desktop, and devices. He’s keynoted, presented, and conducted workshops at such conferences at Business to Buttons, IA Summit, Designertopia, and UIE Web App Summit. Brandon is a co-author of Subject to Change: Creating Great Products and Services for an Uncertain World.

Luke Wroblewski, Senior Principal, Yahoo! and LukeW Interface Designs.

Luke WroblewskiLuke Wroblewski is currently Senior Principal of Product Ideation & Design at Yahoo! Inc. and Principal of LukeW Interface Designs, a product strategy and design consultancy he founded in 1996. In 2008, Luke published Web Form Design: Filling in the Blanks. Luke has also authored a book on Web interface design principles titled Site-Seeing: A Visual Approach to Web Usability and numerous articles on design methodologies, strategies and applications including those featured in his own online publication: Functioning Form. He is also frequent presenter on topics related to Web startegy and design and a former member of the board of directors of the Interaction Design Association.

Lisa Anderson, Microsoft Surface.

Lisa C. Anderson is currently the Microsoft Surface User Experience Director. Previous to this role, she held similar positions at Intuit and Autodesk in the Bay Area. In years past, Lisa acted as User Experience Director for several other teams at Microsoft: Windows XP, MSN, Real Time Collaboration. She was also Executive Producer at Corbis for several years, where she produced award-winning, high-end documentaries on CD-ROM (Leonardo da Vinci;  Critical Mass: America’s Race to Create the Atomic Bomb; FDR; The Barnes Collection). Her background and education are in Design, Art History, English Literature, Writing, Editing, Publishing.

Dennis Wixon, Microsoft Surface.

Dennis Wixon directs research at Microsoft Surface. Previously he managed the user research team an Microsoft Games Studios which is recognized throughout the industry as a leader in user research methodology. Prior to Microsoft Dennis was usability manager in the Software Usability Engineering group at Digital Equipment Corporation, where methods such as usability engineering and contextual inquiry were developed. He co-edited a book Field Methods Case Book for Software Design with Prof. Judy Ramey of the University of Washington. Dennis holds a PhD. in social psychology from Clark University.

Why Designers Fail

Tuesday, October 21st, 2008

Scott Berkun conducted a survey surrounding the topic of

“why designers and people who work with designers believe designers don’t achieve the results they desire”

His top findings:

The 389 survey respondents self identified as:

Designer 33.7%
Project manager 16.5%
Programmer / Tester 11.8%
Usability engineer 9.5%
Group manager 6.9%
Business / Marketing 3.9%
Documentation 1.3%
Other 16.5%


The top 15 issues, ranked by average scores were:

People in non-design roles making design decisions 4.18
Managers making design decisions w/o design training 4.14
Designers don’t seek enough data before designing 3.92
No time is provided for long term thinking 3.81
Not receptive to critical feedback 3.69
Lack of awareness of the business fundamentals 3.66
Only lip-service is paid to “User centered design” 3.64
It’s never made safe to fail or experiment 3.62
Designer’s power diluted by too many cooks 3.60
Over-reliance on one kind of design style 3.54
Poor collaboration skills 3.51
Poor persuasion / idea pitching skills 3.49
Poor communication skills 3.49
Poor understanding of domain 3.48
Pressure to use first solution, not a good solution 3.45
Big Ego / Expects others to cater to their whims 3.41

More summary and breakdown of the results here

Content Aggregators!

Friday, October 17th, 2008

I’ve been really into content aggregators lately. These sites gather information around specific topics and troll the internet to find out what is top of mind and any moment in time. There are many ways to do the feed but here are a couple that do it well:

Lou Rosenfeld’s UX Zeitgeist

Rating the top UX topics, books, people across the blogosphere, amazon, etc

and

perspctv

Following discussion trends for the major party leaders through news, blog mentions, and tweets.

What I would like to see is the evolution of this through dialogue. The artifacts on Flickr have a one to many relationship without discussion. But with conversation around, how a photo was taken, or how to reproduce the results of the photo, it produces that many to many dialogue that creates a rich set of tangents and a more human way way to stitch information together through conversation.

I guess in a way this is an extension to the post I wrote about APML feeds. Except the ambient feeds are around topics of interests instead of people. Still with these types of feeds becoming more prevalent and the future casting of the Aurora concept, feeds associated to people and topics will only become more popularized and embedded within the technology we use.

Prototyping RIA: Adobe Thermo

Thursday, November 1st, 2007

A new prototyping tool on the horizon from adobe:

” ‘Thermo‘ is an upcoming Adobe product that makes it easy for designers to create rich Internet application UIs. Thermo allows designers to build on familiar workflows to visually create working applications that easily flow into production and development.

Features:

  • Use drawing tools to create original graphics, wireframe an application design, or manipulate artwork imported from Adobe Creative Suite tools.
  • Turn artwork from Adobe Photoshop, Illustrator, or Fireworks directly into functional components that use the original artwork as a “skin”.
  • Define and wire up interactive behavior, such as what to do when a user clicks on something, without having to write code.
  • Easily design UIs that work with dynamic data, such as a list of contacts or product information, without having access to the actual data source. Design-time sample data can be used as a realistic placeholder when laying out an application, testing interactivity, and choreographing motion.

Applications created in Thermo are Flex applications that can be loaded directly into Flex Builder, providing a great roundtrip workflow for designers collaborating with developers. The designer’s work can be incorporated directly into the production application with no loss of fidelity, and designers can continue to refine the design throughout the iterative development process.”

See a demo from Adobe MAX Chicago. I haven’t looked through it yet but thought I’d share

CanUX 2007

Wednesday, October 31st, 2007

As always, Jess/Gene and the gang are hosting CanUX, a Canadian User Experience workshop, Nov 25-27 in Banff. The lineup looks terrific:

  • Lou Rosenfeld, founding figure in modern information architecture, author of the best selling Information Architecture for the World Wide Web, and publisher at Rosenfeld Media.
  • Dave Armano, VP, Experience Design for Critical Mass. An active thought leader in the industry, David authors the popular Logic + Emotion blog currently ranked in the top 20 media + marketing blogs according to Advertising Age.
  • Derek Featherstone, leading authority on accessibility and its implications for user experience.
  • Gene Smith, author of the definitive book on tagging, coming early 2008 from New Riders, and principal at nForm User Experience.
  • The Banff Leadership Arts Ensemble, world-renowned facilitators who work to help executives develop leadership capacity through the combination of the arts, creativity, and leadership principles.
  • Kes and Sue Sampanthar, founders of Metamemes, producer of generative thinking tools and experts in moving beyond brainstorming for innovation.
  • Jess McMullin, business and design evangelist, advocate for increasing practitioners’ influence in the organizations they serve, CanUX program chair and nForm User Experience founder.
  • Brad Nemer, Product Portfolio Manager for Motorola’s Asian 3G business, and pioneer in combining business and design thinking.

If you’re want to find a very inclusive, intensive workshop with the beautiful Canadian Rockies as your inspiration, this should definitely be an event you consider.

Attention Data -> Interest clouds -> Interest networks?

Wednesday, October 31st, 2007

I stumbled upon this site about apml a few weeks ago from a post on the Sig-IA mailing list.

When i saw this diagram

I immediately began thinking about how a browse could be created through these interest clouds. If we took the interest clouds and mapped the information to a critical mass of users you could get a collaborative filter that would allow users to browse interest based on their own. If we want to add reputation we could remove anonymity as well (of course this would be voluntary). In essence it would be a creation of Interest networks from ambient attention data. Passive behaviour = a very cool user driven browse.

UX Fund Revisited

Wednesday, October 31st, 2007

About a year ago I mentioned that Teehan + Lax started a UX Fund where they invested in stocks they deemed to have good user experiences. Well I’m happy to report the fund is up more than 42%! Of course good UX isn’t the only factor in making these stocks appreciate but when your senior management buys into design and crafting good holistic experiences the outcome is proving to be quite positive for everyone.

Agile and Design

Wednesday, April 18th, 2007

For the past year I’ve been working on projects in a traditional waterfall model. I’ve come to realize that this favors the design team since we have lots of time to research, conceptualize and design. This model puts a lot of pressure on technology to make assumptions based on documentation. The reality is that once the coding begins is when our back end team gets a real sense of how large a beast they are dealing with. Each project presents new challenges and getting into the sandbox as early as possible helps technology make better estimates.

Fair enough, so now we are trying to work agile into our projects but it seems we’ve went from one extreme to the other. Where agile puts little stock in up front research it puts pressure on design to create an overarching vision for our products without properly understanding the domain or the users.

We had general training on agile and the principles I got from it I loved:

  • less documentation
  • working code
  • people over processes
  • a lot of collaboration

Although I left the training with some less than desirable feelings. My gut was telling me that without the upfront research we only have a partial plan of attack and as things change in future iterations they affect all of the previous iterations. As the evolution of interaction evolves by iteration 5 it means we need to refine iteration 4,3,2,1.

Anyway I’m still open to agile but I think a hybrid approach makes the most sense.

  • A good amount of upfront research which will provide a solid foundation and a plan for the site.
  • The equivalent of stubs for wireframes with enough detail or a guess at the interaction
  • Usability testing of the foundation and then iterative testing as more user stories are incorporated.

In the end we need to service these three areas:

With waterfall we focus on users and business, with agile we focus on technology and business. Fingers crossed in my hybrid world we get it right in the middle.