I'm currently facing a shift in our documentation process. We recently invested in Microsoft 365 CoPilot and are now tasked with reporting AI successes weekly. I'm supposed to use CoPilot daily to highlight these 'AI wins' as part of my annual review. Our team has been using Confluence for all our documentation, which I really dislike—I've tried various wiki software, and in my opinion, Confluence is among the worst. Management insists on using Confluence and JIRA because we're 'Agile', but I'm strongly considering migrating our documentation to SharePoint instead. While I'm not a huge fan of SharePoint either, at least CoPilot works with it, allowing me to claim some successful AI usage. I've experimented with SharePoint's Wiki feature, but it's not great, and I want to avoid reverting to simple Word documents stored in a folder. Does anyone have any recommendations or guides on setting up SharePoint effectively for team and end-user documentation?
5 Answers
Honestly, moving from Confluence to SharePoint may not be the upgrade you expect. SharePoint tends to be a poor documentation repository. You might want to explore connectors that allow CoPilot to interact with Confluence instead—sticking to the tools that do the job better could save you a lot of headaches.
I also think looking into other options could be beneficial. Have you considered alternatives like Hudu or BookStack instead?
You might want to think about using Microsoft Loop for your documentation needs. It's closer to what you're used to with Confluence and integrates nicely within the MS ecosystem, but you should weigh it against the effort needed for migration and training.
Loop does seem promising! However, be cautious since it requires a different mindset. Make sure everyone on your team is onboard.
You could also set up a Copilot Connector for existing Confluence data. It could be the best of both worlds.
I second the recommendation against SharePoint for documentation. If you're looking for a smooth experience, consider alternatives like Hudu or MKDocs, which are designed for better usability. SharePoint can turn into a complicated file system that makes it hard for teams to find what they're looking for.
Absolutely! We automated our documentation processes with Hudu and it worked wonders.
Plus, at least Hudu has a better structure for navigating documentation. I can't imagine going back to a folder system on SharePoint.
If you really have to go with SharePoint, just know that the search capabilities and overall user experience are lacking compared to Confluence. But there are ways to make it work. You can create many small pages for specific questions or tasks instead of trying to pack everything into long documents, it could help with searchability.
Good point! Their search can be tricky, but organizing smaller, targeted content could help. Just remember to set up good taxonomies to categorize everything.
Definitely, having a clear structure from the start will save you endless amounts of time!
Consider your team's willingness to adapt as well. Moving to SharePoint could complicate things further, especially if the necessary training isn’t in place. It's a cultural challenge and buy-in is crucial for a smooth transition. Just tread carefully with this change.
True! Getting everyone on board is half the battle. Maybe host some meetings to discuss potential tools before making a switch.
Exactly, creating a solid transition plan together could alleviate some of the stress orchestrating this change.
Yeah, I agree! If the goal is to rack up those AI wins, keeping your documents in Confluence might actually serve you better in the long run.