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...

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the  four problems that companies face, or are trying to overcome, as they make product decisions .  Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions.  They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem...