High and Low Level Requirements

I've seen some references in product management and requirements discussion forums about a supposed distinction between "high" and "low" level requirements. I have three main thoughts on this matter.

First, the distinction, if examined literally, doesn't seem to make sense. A user has certain problems she wants solved; requirements state the least stringent conditions that must hold to know that you've solved them. I don't consider problems as being either high level or low level, so why would there be "requirements levels"? Imagine saying to a user, "Oh, that's just a low level problem, so let's not worry about it now. I'm just documenting high level requirements." What?

Second, I believe the valid distinction is between requirements specifications and design specifications. If you specify user goals and constraints on those goals, you stay at a "high level", and you are documenting requirements. If you specify how the user will interact with the product in order to satisfy those goals and constraints, however, you are certainly getting into low-level details. But then you are specifying design, not requirements.

Third, both high and low level specifications are important. Denying that low-level specifications are requirements by no means diminishes their importance. It just helps to understand when you're doing requirements and when you're doing design. At Cauvin, Inc., specifying market requirements for a product is part of our product management services. We leave product design for design experts.

Comments

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

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

Cauvin

Search This Blog