The Importance of a Prioritized List in Technical Requirements

My number one learning is never write a product requirement or functional requirement document that isn't prioritized. Never give engineering what I've called a flat list. That is an un-prioritize list. Give them a prioritized list, at least a high medium low, high medium nice to have kind of listing. Otherwise you're going to get the cool stuff first. There are things that customers need and they don't tell you that they need. Those buying decisions are harder to uncover than pure technical ones.