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.


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

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware