automatic phased deployment
Wait, wait hear me out. What if you could target a deployment to a single collection and ConfigMgr just thought up random groups of 20-30 machines at a time and made the deployment available to the next group after a specified period of time. Essentially creating an automatically built phases with no real requirements other than "x" amount of time has passed since the previous groups.
Jim Webb commented
The Task Sequence feature bdam refers to still requires creating multiple collections so I think this uservoice is needed.
Robert Stein commented
Agreed - one collection being the thing. I have enough trouble maintaining collections for phases/rings/tiers/whatever. If I want to deploy Application XYZ to Collection 123 but not hit everybody at once I don't want to create the phases.
This feature was introduced in the product in 1802 and came out of pre-release in 1806: https://docs.microsoft.com/en-us/sccm/osd/deploy-use/create-phased-deployment-for-task-sequence