Upgrade V2V or B2B
Will like to smooth process and see less down time when upgrade from 2013 to 2016 or installing patches/SPs.
It would be nice if the patch process were more modular, and only specific components required restart. I just patched my 3-tier dev SP2013 farm to Dec 2015 CU, and it would be nice if you could deploy patches at the farm level and somehow automate the deployment to each server in the farm.
Based on the news at ignite and in other posts I believe we have successfully responded to this request for SharePoint 2016.
I will not be something we can improve for SharePoint 2013 though I am afraid
Paul Flatt commented
Schema updates in particular should be automatic, zero-downtime, and more or less silent in the background.
An interface for resolving missing binary packages/version mismatches should be present in Central Admin. I would think that it should be technically feasible for servers automatically share missing patches with each other. Centralized update cache?
SharePoint updates should not be in GB. not sometime when site of actual software is 2gb where as CU is 4 gb