Design Challenge #3 - Convincing project teams of the need to normalize

In our last design challenge (click here to read the response to the last design challenge) we agreed that we should normalize regardless of database platform, and we discussed a number of benefits the normalized design can offer. Some of these benefits are longer term and have broader scope than the current project to which you are assigned. This can sometimes cause conflict with a project team who has short term objectives to complete the project deliverables within tight deadlines. Project teams that are “under the gun” are less concerned about long term benefits and heavily focused on the deliverables for next week or next month. Have you ever heard phrases like "We don't have time for that exercise" or "Don't hold up our project"? Please address the following two tasks as part of this design challenge: 

  • Describe at least one technique or tactic that has worked to convince or educate a project team that the benefits of normalization outweigh the near term additional time and money investment? Why do you think it worked?
  • Describe at least one technique or tactic that has NOT worked. What could have been different to make it work?

Note that this is not an easy challenge. We are dealing less with the facts around relational database theory and more around emotions running high when project deadlines are fast approaching.

To read the response to this design challenge, please click here