Archive for September, 2008
Picking a frame: Activities vs. Goals vs. Needs
Tuesday, September 30th, 2008 | reactions | 1 Comment
Joshua Porter discusses frames and concludes that activities are a useful frame for thinking about products:
I believe that thinking about design from an activity-centric viewpoint is the most efficient way to get where you need to go…which is to create a piece of software that is valuable to people.
Put another way, we should think of products in terms of the activities that people do with them.
A commenter points out goals as an alternative to activities, and Alan Cooper’s technique of goal-directed design. In this paradigm, we should think of products in terms of the user’s goals. The advantage here is that goals are the end; the activities people have are the means towards that end.
These are both useful ways to think about things. Both tear us away from the details and force us to think about the purpose behind our designs.
I prefer needs as the central concept of product vision and design. In this frame, we think of products in terms of the needs they fulfill for people. The difference between goals and needs may seem subtle, but I prefer it for several reasons:
- Thinking in terms of needs forces us to think about what is going on at a deeper level, below the goals customers might articulate, below the activities we see them do, below visible design, to the underlying reason: the “why.” In other words, what needs are fulfilled. This mental exercise of understanding the “why” is invaluable for deeply understanding both customers and products.
- Activities presume that an activity is necessary. Sometimes a clever designer can find satisfy the needs while obviating the activity. The need stays constant.
- Goals implies that the user has a conscious idea of what they want. However people have plenty of needs of which they are not aware. We can design to these needs without customers thinking of them as goals. For example, Apple evokes latent needs for aesthetic pleasure in all of us. Facebook does us the favor of eliciting, and then addressing, our need for social connection with others.
- Goals connotes finiteness: once we reach a goal, we’re done. A given need, on the other hand, may be satiable or insatiable. Insatiable needs include the needs for enjoyment, social distinction, novelty or mental stimulation.
- Needs are connected to SSNiFs – the underlying scenarios. Every Need is traceable back to a Stakeholder in some Situation, and is resolved by a Feature.
- Satisfying needs is the ultimate reason that the product, its features, and even the company exist. As marketing guru Philip Koltler puts it, the purpose of business is to “meet needs profitably.” The term needs segues with traditional business discourse.
- Needs are the operative concept in product vision. I will say a lot more about this over the coming months.
Josh points out how a sample set of sites can be described in terms of the primary activity. For example, Amazon’s activity is shopping and eBay’s activity is auctioning. The trouble is, the activities alone are not enough to characterize the product or service. If Amazon’s activity is shopping, then what is there to distinguish it from Zappos, Gap or Overstock.com?
If we think in terms of stakeholder needs, we quickly get to the heart of each site’s vision:
- Amazon: the need to learn about and buy consumer products economically and efficiently (needs: education, economy, efficiency)
- YouTube: the need (for the publisher) to self-promote; the need for the viewer to be entertained in short bursts
- Del.icio.us: the need (for the bookmarker) to remember and recall useful information and to share it with colleagues; the need (for the reader) to keep up on new, high quality information that is relevant to him or her.
- eBay: the need (of the seller) to get rid of unneeded stuff and recoup some money; the need (of the buyer) to obtain obscure or used things economically and efficiently
- Netflix: the need for high-quality, economical, efficient, passive entertainment
- BigTent: the needs for community groups to communicate, coordinate and exchange goods
Some of these needs are activities, some of them are goals, but some are neither.
By thinking about what is below the design, below the visible activities, below the stated goals, we can get to the deeper underlying purpose of the product and each of its features. This puts our business in perspective and reminds us of what really matters.
For example, Netflix understood the needs it was addressing with its DVD-by-mail service (high quality, efficient, economical, passive entertainment). It realized that the same needs could be satisfied at least as well via Internet delivery, a profoundly different operating model than warehousing and shipping millions of discs every day. They were smart enough to make themselves a pioneer in the field.
The proverbial railroad barons, on the other hand, were under the impression that they were in the rail business. They defined their business in terms of the technology they happened to be using. At a deeper level, they were in business of meeting the customer need to have their goods transported. If they had thought in these terms, they might have embraced trucking when the network of highways was being paved. Instead, they stuck to their established solution and watched as their business shriveled.
There are countless other stories of companies losing track of the underlying needs they exist to fulfill. It’s what makes needs such a powerful concept for understanding and envisioning products.
See also: Design Pyramid | SSNiF Scenarios | Choosing the Right Problem to Solve
If you find this sort of thing interesting, please add a comment, or sign up for the RSS feed or the product vision newsletter.
—
Philip Haine is principal of Product Vision Associates, a product innovation consultancy that helps product leaders and their teams envision new, breakthrough products and reboot older ones. To follow him on Twitter click here.
Product Vision Defined
Monday, September 29th, 2008 | vision book | 2 Comments
“Product vision.” We hear the phrase all the time. We have a sense of what it means, but there’s a vagueness to it. A crisp definition is hard to come by. But if we’re going to get serious about product vision we’d better straighten out our semantics. So what is product vision, really?
Let’s start with the dictionary definition for the word “vision” alone, excerpted from the New Oxford American Dictionary:
Vision
1. the ability to think about or plan the future with imagination or wisdom
2. a mental image of what the future will or could be like
This is already pretty close to how the phrase “product vision” is used. When we say “Apple has great product vision” we mean vision in the first sense of the word, that Apple is “thinks about and plans its future products with imagination and wisdom.”
When we consider a specific visionary product like the iPhone, the thousands of decisions that went making such a coherent product must have been driven by a clear vision, or “mental image of what the future [product] would be like.”
This leads us to a first cut at a definition for product vision.
Product Vision
1. the ability to think about or plan future products with imagination and wisdom
2. a mental image of what a future product will be like
There is one more usage sense that is missing. Product vision is also a field of study. There are conceptual models and practical methods that help us envision great new products. These frameworks can be taught, studied, tested and refined. Product vision is a discipline that can be studied, just like engineering, medicine, law, or design.
This leads us to our third definition:
3. the branch of knowledge and practice involved with envisioning future products
Having a concise, definition to reference will help us know when we’ve got a vision and help us to tell whether it’s any good. The definition the is a stepping stone to deeper ways of thinking about vision that will help us to conduct it systematically and with clarity.
How well do these definitions hold up to your usage? Please let me know in your comments.
See also:
—
Philip Haine is principal of Product Vision Associates, a product innovation consultancy that helps product leaders and their teams envision new, breakthrough products and reboot older ones. To follow him on Twitter click here.
Welcome to the Product Vision Blog
Monday, September 29th, 2008 | news | No Comments
Welcome to the Product Vision blog. I decided to branch this topic off from StealThisIdea.com, to keep a tighter focus on the discipline of product vision.
My name is Philip Haine and I approved this message.
Free Product Vision Newsletter
Monday, September 29th, 2008 | news | No Comments
Sign up for the FREE Product Vision Newsletter, and be the first to know about happenings regarding the vision book. (I will do something nice for the early subscribers!)
If you want to receive ALL postings to ProductVision.org as they happen, just enter your email in the box in the right hand margin and click Subscribe.
You can also subscribe to the RSS feed using big fat RSS link at the top of the page, if you are that kind of person. (I highly recommend NetNewsWire, a free Web/Mac/iPhone app that keeps your feeds synched up.)
Finally, if you want to tune into what is on my mind design- and vision-wise, please follow my Twitter feed at @dphaine.
Subscribe to email list
Subscribe to RSS Feed
Follow @dphaine on Twitter