2 ms·

This problem comes from the absolutist implication of the word. A better word is "Objectives". Objectives aren't created equal like calling them "requirements"

This problem comes from the absolutist implication of the word. A better word is "Objectives". Objectives aren't created equal like calling them "requirements" implies. Requirements must all be completely fulfilled for the request to be satisfied, while Objectives are ranked by importance and can tug against each other. Having contradictory requirements is a semantics error, but having contradictory objectives is normal: that's why they're prioritized. "Make me a billion dollars" may be your objective, and while it may not be an actionable one, it is in fact important to distinguish in your design whether your primary objective is to make money, rather than being a passion project for example. The cost-benefit analysis of various design decisions changes depending on how big a priority profit is. You may be willing to make decisions that are less profitable, but lead to a better product, when profit isn't your primary objective.

dalbasal 5y ago
Whatever you call them, attempting to formalise them as a discrete object is flawed. These aren't discrete objects. They're key parts of a formal, or semi formal decision making process, administration systems, management methods and suchlike. Look... there are outlining methodologies that playwrights or novelists sometimes use. It's fine to use such constructs. What's not fine is trying to build institutions based on them. It's just not reducible neatly into profit objectives and such. Those are fine tools, but they're not good models of the world.
- philipov 5y ago
  So what you're against is having a corporate-mandated policy for how customer feedback is to be turned into a product design?
  - dalbasal 5y ago
    No. I'm against framing design as "requirement gathering." If you're designing, deciding or otherwise doing subjective, creative work don't wrap it up in a fake-discrete process. Customer feedback is valuable information. It's isn't ore that you refine into cutlery.

dalbasal 5y ago

Whatever you call them, attempting to formalise them as a discrete object is flawed. These aren't discrete objects. They're key parts of a formal, or semi formal decision making process, administration systems, management methods and suchlike. Look... there are outlining methodologies that playwrights or novelists sometimes use. It's fine to use such constructs. What's not fine is trying to build institutions based on them. It's just not reducible neatly into profit objectives and such. Those are fine tools, but they're not good models of the world.

philipov 5y ago
So what you're against is having a corporate-mandated policy for how customer feedback is to be turned into a product design?
- dalbasal 5y ago
  No. I'm against framing design as "requirement gathering." If you're designing, deciding or otherwise doing subjective, creative work don't wrap it up in a fake-discrete process. Customer feedback is valuable information. It's isn't ore that you refine into cutlery.