That depends on how you are doing the morph itself. At a value of 1, it represents the morph as it was imported. So if there is an increase in size, it means that while morphing the part you accidentally enlarged it.
I sometimes (in Silo) load the original part, make the morphed part transparent and check for potential problem spots.
However, the problem spots depend on what you were morphing, and how you morphed it. There is no easy answer.

Unless of course, you are scaling the obj files, either in Silo or in Poser. If you must do this, use an easy value (eg. 100 instead of 304.8) on scaling up or down, scaling by fractions can generate scaling errors because of different implementations of floating point calculations.

still hooked to real life and enjoying the siesta!
Visit my blog! :D
Visit my portfolio! :D