NuGet packages, just like any other release vehicle (binaries, installers, etc.), need to undergo rigorous testing and quality assurance before being released to the masses. One cannot just build a complex NuGet package, complete with custom PowerShell hookpoints, push it to the repository and assume everything will work as expected, every single time, over and over again. If you're that good, you should be able to convince your managers to code directly onto the production servers.
We like Eric S. Raymond's approach of release early, release often. This is exactly what you should do with your NuGet packages as well. You not only release the package contents, you also release the package itself. It is your release vehicle