I was taught to commence another phase after normalization: denormalization. This phase is where you weigh the pros and the cons of every part of your normalization and use common sense to produce the results. There may often be several issues with normalization; you may even decrease performance through excessive normalization if the complexity of the database becomes too rough and the normalized entities' problems were not even that big to begin with. Denormalization is also where you weigh space requirements vs. performance according to what the server can accept.

Of course, you are often able to do the denormalization in your mind during normalization and just ignore applying the rule at that point, but if you have to write documentation you need to do the normalization part first so you can provide reason later on as to why normalization was deviated from.