Requirements are the devil. No enterprise design initiative wastes more time, more effort, more money — while squandering goodwill — than the quest for requirements. I’ve lost track of the number of software development teams and innovation groups I’ve worked with who invested weeks eliciting, gathering, and prioritizing customer requirements — then carefully built and demo-ed a prototype — only to hear, “Well, I know that’s what we asked for but, now that we’ve seen it, it’s not what we really want.”