False Comfort in Measurability

Seth Godin wrote:

The danger is when you keep score of the wrong thing because it's easy or precise.

The requirements for our products should be testable and measurable. When a prospective customer tells us the competitor's product is not secure enough and needs registration and log-in functionality, part of understanding what the prospective customer means is to determine how to measure security.

Your product manager may opt for specifications that are less challenging to measure. Rather than specify security metrics, for example, she may instead punt and simply specify the product will include registration and log-in functionality as the prospective customer requested. But doing so doesn't capture the problem the prospective customer is really trying to solve. What does it mean for the product to be secure?

What information is problematic for an unauthorized user to access?
What functionality is dangerous for an unauthorized user to employ?
What are the characteristics of an authorized user?

These questions are not easy to answer in measurable terms. There's precision in specifying that the product will require user registration and log-in, but it doesn't answer these questions. Yet answering these questions is critical to understanding the customer's needs and to ultimately testing whether your product satisfies them.

Comments

Dancer Test

Are you left-brained or right-brained? Supposedly, your brain lateralization determines how you view this animation. Some people see her rotating clockwise. Others see her rotating counter-clockwise. Some see her unpredictably changing the direction of her rotation. Supposedly, people who see clockwise rotation are right brained. People who see counter-clockwise rotation are left brained. I originally came across this animation here .

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

Cauvin

Search This Blog