John Cutler's list is excellent, as it points to potential "org smells" or "process smells" that should catch your attention. As programmers, we are taught to look for "code smells" (things you should try to avoid or pay extra attention to). It helps to raise awareness and then figure out what is the best approach given different constraints. What would be possible answers to each situation? How would you know what to use when? Use it as a question to ask candidates who apply for managerial or technical leadership positions.