Modern Publishing Sites

I don't think businesses should be expected to beta test every service and software for another company while paying for the privilege.

The only group that has whole-hearted gotten behind the Office365 platform has been our Project Management team.

Then Microsoft pulled site mailboxes, even from PWA. Oops.

Now, we have a PWA site for a project, a Group for the same project (which our PMA is super thrilled about, let me tell you; he's got so many groups it is utterly ridiculous) so that they have a shared mailbox, and never the twain shall meet. It's pretty awesome, in that not really kind of way, when there are two sites for one function. So, where's all that information? Dunno. I'll need to look in the umpteen different places it might be. Case in point: Teams files. Let's say I have file.doc in a folder in the channel "General". I make a change to it, or want to announce that the file is there. It makes a copy and puts the copy in the root of the General folder. Oh, and different channels cannot see other channel files, because the view is one level back (the only workaround is making a SharePoint Document Library tab. Why even have the Files tab? Who thinks this stuff through? Oh, that's right we do. "Oh, you'll want to waste another X amount of time not doing your job, and doing ours by visiting UserVoice and telling all your friends to vote for your 'well, duh' functionality." Unacceptable in the biggest way possible. Again, we are paying Microsoft. There should be an expectation of enough stability to not be paralysed by tool overload and shifting priorities of a product management team.

Every few months, we have to up-end our processes, reinvent them, and then retrain. That is just not a way to run a business. I get Agile. I get DevOps. But you know who loses out with the Microsoft implementation of those? The customer; the one that was supposed to be front and center.

I know they are in a transnational period. They will forever be in a transnational period. That's fine. The process-breaking changes every few months: not fine, nor will it ever be.

I'll be glad when the Product Management team overseeing the Office 365 platform (if there is such a group, and not little groups that never talk to each other for each bit of the platform) takes a look at the harm they are doing to their clients, the third-parties that have built their businesses around custom solutions and support, and figures out that a more sane cadence is likely the best approach.

Oh, and the Communications site business... still doesn't do anything to answer "What about existing content?"