Skip to main content

Prescriptive versus Descriptive Rules

When debating terminology, I have several times run across the issue of prescriptive versus descriptive rules. A prescriptive rule states how people should use a word; a descriptive rule states how people do use a word.

For example, many people pronounce "nuclear" as "new-cue-ler". Webster's has even accepted this oddity as one among several pronunciations. But does Webster's inclusion of the pronunciation mean that it is "correct" to pronounce the word that way? I don't think so. The inclusion of the pronunciation is descriptive; they included the pronunciation because it describes how a significant portion of the English-speaking population pronounces the word. They are not endorsing the pronunciation.

Interestingly, the same sorts of issues arise in the rules of games. I have debated rules of poker, for example, with people who insist the rule they follow is "correct" because everyone seems to play that way. But when I look up the rules in an authoritative source, such as Hoyle's Rules of Games, I sometimes find that the "official" rules differ from the common way in which people play.

I favor acting according to prescriptive rules rather than descriptive rules. Discrepancies between prescriptive and descriptive rules typically arise from ignorance - a larger and larger number of people who aren't familiar with a traditional rule begin to behave differently until few people even know what the original rule was. I want my rules to be based on full knowledge of both common usage and history, which sometimes means dismissing common usage as based on ignorance.


Roger L. Cauvin said…
The fact that a descriptive rule is one that people actually use doesn't make it "true" or "false". We might define the "truth" of a rule as depending on its popularity. In that case, descriptive rules would be empirically verifiable (subject to the possibility of surveying use of them). However, no rules are true or false in isolation.
I'm not sure is prescription NEEDS to be justified. It certainly is not always justified in English!

Why not justify the action of prescribing rules by the need for a group of people from varying backgrounds (each with descriptive rules of their own) to efficiently converse with one another.

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

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