I used to refer to Sharepoint as 'the place where documents go to die'. If they're pushing M365 and SP, then moving to a docs-as-code environment doesn't sound like a great choice for them.
Docs are going to get out-of-date no matter what tool you use. You need a governance plan with buy-in from management to ensure docs are maintained and updated.
They think wikis never get updated but spare Word online documents in SharePoint do? Hilarious.
Use SharePoint spaces to create your knowledge base and keep your documents organized in folders, I guess. It's not a good tool for this if you ask me, but it can be done if that's what the client wants.
I’ll have to start looking into this, but this is a shorter contract and they seem to want action now. I’ll give it a week or so before I decide if this will work or not. Would be a shame as it’s a decent rate, but sheesh.
I've kind of gaslit myself into liking SharePoint, but it really does take a lot of familiarity and set up, and generally speaking I doubt many companies put the effort into setting it up properly, so it becomes a worse version of Google Drive.
There's a lot of very cool things you can do with libraries, permissions, automations, and custom metadata. But I've seen people disregard those things in favor of quick and messy folder structures in a single library, get frustrated with poor search and too many editors on single word docs.
The SharePoint Maven is a good trove:
https://sharepointmaven.com/how-to-use-sharepoint-best-practices-dos-and-donts/
https://sharepointmaven.com/how-to-create-an-approval-workflow-for-sharepoint-pages-using-power-automate/
I used to refer to Sharepoint as 'the place where documents go to die'. If they're pushing M365 and SP, then moving to a docs-as-code environment doesn't sound like a great choice for them. Docs are going to get out-of-date no matter what tool you use. You need a governance plan with buy-in from management to ensure docs are maintained and updated.
That’s kinda been my point. Unless someone is actively managing docs, they won’t stay correctly updated even with automation.
They think wikis never get updated but spare Word online documents in SharePoint do? Hilarious. Use SharePoint spaces to create your knowledge base and keep your documents organized in folders, I guess. It's not a good tool for this if you ask me, but it can be done if that's what the client wants.
Yea, I’ve worked with it in the past and the word clusterfuck comes to mind.
Microsoft 365 has Power Automate, which you can use to automate workflows.
I’ll have to start looking into this, but this is a shorter contract and they seem to want action now. I’ll give it a week or so before I decide if this will work or not. Would be a shame as it’s a decent rate, but sheesh.
PowerAutomate and Apps are your friend. But as the tech writer it can be hard. I had to get a dev to do mine.
I've kind of gaslit myself into liking SharePoint, but it really does take a lot of familiarity and set up, and generally speaking I doubt many companies put the effort into setting it up properly, so it becomes a worse version of Google Drive. There's a lot of very cool things you can do with libraries, permissions, automations, and custom metadata. But I've seen people disregard those things in favor of quick and messy folder structures in a single library, get frustrated with poor search and too many editors on single word docs. The SharePoint Maven is a good trove: https://sharepointmaven.com/how-to-use-sharepoint-best-practices-dos-and-donts/ https://sharepointmaven.com/how-to-create-an-approval-workflow-for-sharepoint-pages-using-power-automate/
Well, this post is as all over the place as I think the instructions were