Summary: Ever find yourself spinning in a conversation where the discussion of ideas gets stuck in a circuitous route? In the world of software development, where the need to effectively communicate elaborate and complex ideas is most important, such conversations end up being counter-productive. In this week’s column, Jeff Patton shares a technique that keeps such conversations on a straight and productive path. Find out how he channels different ideas and categorizes them-all within one
How the push to reduce story size pulls us farther from user goals and forces more up-front-design into Agile processes
It’s not so much the decrease in size that’s concerning, but the lack of practices and techniques to
an unfair characterization of user experience professionals
Three personalities in the user experience community
This article is about how I stereotype people in the user experience community. It’s not very nice to stereotype or categorize people. But, Ux people are in the business of it. Most of our user models like personas, roles, and profiles help to generalize our understanding of our
I have two heads… and so do you. When I’m making a decision to buy or use a product, I use my buyer head. I try to look at the product I’m considering objectively. I identified this product because I have a problem, need, or goal, and I think this product will help me solve that problem, meet that need, reach that goal.
12/08/2006 I’ve been seeing a pattern lately with Agile projects. It’s not a new pattern. It’s one we’ve all likely seen on more traditional development projects for years. The story goes a little like this: A customer needs a software solution to a problem. An Agile team swoops in and in a reasonably short amount of time, and in collaboration with customers and end users, writes