Skip to main content

Commuting's Dormant Problems

A recent article by Nick Paumgarten in the New Yorker magazine examines the psychology of commuters (those who travel long distances to work each day). Commuting is a revealing example of how:

  1. People are not always aware of the problems they face in their day-to-day lives.
  2. People are sometimes unable to judge rationally how valuable it is to solve the problems they face.
Paumgarten observes:

A commute is a distillation of a life’s main ingredients, a product of fundamental values and choices. And time is the vital currency: how much of it you spend—and how you spend it—reveals a great deal about how much you think it is worth.
The root of a product manager's responsibilities is to understand problems in the marketplace. The behavior of commuters shows that researching these problems is not always straightfoward, however. For example:
“Drive until you qualify” is a phrase that real-estate agents use to describe a central tenet of the commuting life: you travel away from the workplace until you reach an exit where you can afford to buy a house that meets your standards. The size of the wallet determines that of the mortgage, and therefore the length of the commute.
Yet according to Robert Putnam, a Harvard political scientist:
There’s a simple rule of thumb: Every ten minutes of commuting results in ten per cent fewer social connections. Commuting is connected to social isolation, which causes unhappiness.
Thus:
The commuting paradox reflects the notion that many people, who are supposedly rational (according to classical economic theory, at least), commute even though it makes them miserable. They are not, in the final accounting, adequately compensated.
Interestingly:
Road-building doesn’t much help. Atlanta is a showcase for a phenomenon called “induced traffic”: the more highway lanes you build, the more traffic you get. People find it agreeable to move farther away, and, as others join them, they find it less agreeable (or affordable), and so they move farther still. The lanes fill up.
The article is chock full of profiles of actual commuters and accounts of actual commute experiences. If your product manager is not generating this sort of information, he is not likely to thoroughly understand his market. The article further illustrates the complexity of interpreting quantitative and qualitative information and understanding market problems.

Comments

Mike Lunt said…
I've also heard

NO

that people are

POLITICAL

susceptiable to

SLANT

subliminal messages.

HERE.

;-)
rcauvin said…
Oh, the irony. Mike, if ever I've seen an example of Roger's Theory of Bias, it's what you just posted :-)
Mike Lunt said…
I'm sure you've considered both sides of the commuter debate, so I apologize if an accusation has been inferred.

I was simply commending your Twain-ish ability to get a product management twist on it. Nice job, seriously...

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing