I feel this. What I do now is increase the points of the PoC (real estimated PoC time + optimization).

I get the PoC down asap then as soon as it’s proven (privately to myself) I move onto optimizing. If it fails then I communicate early to discuss a change of scope.

Assuming it succeeds, by the time I present it I have already done significant work making it production ready. So to request an extra 10-25% time to “smooth out the edges” goes over easy after the demo.

In reality I end up with 50-75% time to get it prod ready. The rest is QA + prod bug fixes to take it over the (practically scoped) finish line.

I did that today. Rewrote a bash script in to a perl script as Proof of Concept. it's now in UAT... but I like perl, hey ho.

This has caused me so much grief. I find it key to communicate to all stakeholders the production process from PoC to MVP to MVP+.

Still managers always push against redoing work they can see working for the happy flow.