Skip to main content

Wiegers on the Requirements/Design Distinction

Karl Wiegers and I have disagreed in the past on requirements terminology.

Now Wiegers has a good piece on the distinction between requirements and design. Or rather he attempts to sidestep the interminable semantic debate and focus on some important consequences of failing to understand the "why" behind product specifications.

In my view, the summary passage in the piece is:
When it comes to requirements specification and design, the essential issue is not one of what versus how. It’s a question of distinguishing the real customer need from just one possible description of how a clever developer might satisfy that need. Incorporating a solution idea into a requirement imposes a design constraint. The requested solution describes one way to satisfy some requirement but perhaps not the only way, the best way, or even a good way. Focusing on solutions masks the underlying requirement. This can make it difficult for a developer to understand what the customer is really trying to do, making it hard for him to devise the most appropriate approach to meet that expectation.
Actually, I think the "real customer need" is the what, and a "possible description of how a clever developer might satisfy that need" is the how, so the what versus how distinction makes perfect sense. Setting aside this quibble over terminology, however, Wiegers hits the nail on the head about focusing on underlying needs rather than dictating solutions to developers.

Wiegers elaborates:
The requirements analyst needs to detect when a requirement imposes unnecessary constraints on designers. This should lead to a discussion with the customer representatives about the underlying need that led to the customer proposing that specific solution. It’s important to respect the customer’s input. Don’t summarily dismiss the customer’s solution idea; important information is hiding in there somewhere. Use that input as a starting point to drill down to a deeper understanding of what the customer is really trying to accomplish. It’s possible that the customer’s solution idea will be appropriate, but don’t let the customer—or any other stakeholder—paint the development team into a constraint corner prematurely.
He then gives real-life examples (drawn from actual requirements documents). Here is one:
"A master power button shall be installed on the front panel." Further discussion might surface an explanation of why this precise design approach is necessary. Perhaps it’s required for compatibility with an existing product, or maybe it will conform to a pertinent standard or safety requirement. Or it could be an unstated ease-of-use requirement. If so, it would be good to know about any related usability requirements that could influence this, and possibly other, functionality or design issues.
In other words, customers don't care about "power buttons" per se. They care about compatibility, compliance, safety, and ease of use. If a requirements analyst fails to document these nonfunctional requirements in measurable terms, the product may end up with a "power button" but still end up being incompatible, not compliant, unsafe, and difficult to use.


Dave said…
Back in the late '80s, I went to a conference where a paper on formal requirements was presented. In that paper, requirements are decisions.

This doesn't change the WHAT of requirements.

Then, comes the notion that products enable and constrain simultaneously. Products used in the implementation phase are constraints that are ultimately mapped to requirements.

Design is the mapping of a media, software, with the carried content, the user's application domain (finance, markeing, not Oracle, or Java, or...).
rcauvin said…
Hmm, I little confused by the notion that "requirements are decisions", but that they don't "change the what of requirements".

After understanding problems in the marketplace, we do make decisions about which ones to solve. But once we make decisions beyond that, we are delving into HOW to solve them.

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

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

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