Skip to main content

Dollar Coins

Has the government done any product management on its currency product?

Since 1971, the U.S. government has made several attempts to ween its citizens off of paper currency (dollar bills) and onto coins. In many other developed countries, similar denominations of currency have been coins, not paper. Supposedly, the similarity of dollar coins to quarters has been one reason that dollar coins have not gained popular acceptance.

If the government were to gather requirements for a currency product, what would they be? What would the use cases be? What would the attributes and constraints attached to these use cases be?

Some of the use cases might be:
  • Pay for Goods
  • Carry Money
  • Withdraw Money
  • Deposit Money

Some of the attributes might be:

  • Fit (Does it fit comfortably in pockets/wallets/purses?)
  • Weight (Does carrying a lot of it around weigh you down?)
  • Durability (How well does it withstand the elements and time?)
  • Identifiability (How easy is it to distinguish relative to other currency?)
I am personally sensitive to the fit and weight of currency. I don't like the feel of a lot of change in my pockets, and I can't stuff a lot of coins in my wallet.

Comments

Unknown said…
I think they did do their research. The Susan B. Anthony was a disaster because of its similarity to the quarter, but the Sacajawea dollar should have addressed all the requirements. I think Americans just aren't that receptive to changes in the currency. Americans are just very conservative about our cash - the new, "big head" bills still don't look like real money to me. And, there really isn't a strong reason for consumers to adopt the dollar coin - it makes a lot of sense for the government, but not the consumers.

And, bear in mind, that issuing the new dollar coins requires coordination with everybody else. All the vending machines, toll booths, cashier trays, etc... have to be ready to accept the new currency, so there's a huge barrier to entry.
Thu May 24, 01:31:00 PM 2007
Post a Comment

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
32 comments
Read more

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
12 comments
Read more

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
9 comments
Read more