"Business users will have the option to set their own update cycle, so they can see if any of the patches accidentally break anything for home users before trying them out."
Stripping away the spin, updates will come out as soon as they're ready (which is probably a good thing on the whole), and business users will have to test and deploy them at that time, whenever it happens, rather than having a monthly scheduled day to do so.
That "option to set their own update cycle" spin is nonsense. If you do that, every single security fix Microsoft ever rolls out goes public days or weeks before you get it -- like what happens when a zero-day goes public and it takes Microsoft several days or weeks to get the fix out, but it'll be like that for you for every single security update ever. Yeah, no, that is not the way any reasonable large business is going to handle it.
This means effectively, if you are a large company, you will really need to have people on call or otherwise available every day in case an update comes out. But, in 2015, are there any large businesses left that *don't* already have IT people on the clock every day? I see this as Microsoft catching up with the reality that at this point large businesses *do* have IT people on staff full time -- they *have* to have them -- and everyone, including the large businesses, is put unnecessarily at risk when security updates that are ready to roll out are held back to wait for a certain day of the month. It does mean occasionally an IT department's going to have to reschedule a day full of department meetings and team-building exercises to test and deploy an update that just came out, but it's worth it.
So it's the right thing to do, but Microsoft's spin is so much nonsense.