Skip to main content

Measurement by Authority

When your product manager is documenting the nonfunctional requirements for a product, one of the biggest challenges is identifying metrics, the means of measuring a constraint.

For example, imagine one of the requirements that marcom wants for the product is consistency with brand colors. I.e. the appearance or user interface of the product should contain colors that the brand logo contains. Consistency with brand colors helps strengthen prospective buyers' association of the colors with their perception of the product.

How would you measure such a thing? Consistency is a somewhat subjective attribute of a product. Gause and Weinberg, in Exploring Requirements (page 184), describe a way of measuring subjective attributes:
Another way of resolving measurability conflicts is simply to define measurement by authority. "What person or group can be given the authority to say 'yes' or 'no' about the satisfaction of this constraint?" Sometimes there is an official agency: "If the federal bank examiners will accept the auditability of this system, then we will be satisfied that the auditability constraint has been met." Other times there is an official process: "If the standards committee conducts a technical review and certifies this system, then the standards constraint will be met."
If your product manager hasn't yet read Exploring Requirements, it's not too late.

Comments

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

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the