Have you heard about Project Cortex? The upcoming service from Microsoft that will help organisations to better manage their internal knowledge by using the best of breed content services such as SharePoint, One Drive and Microsoft search.
This is part one of the Knowledge Management series. For other parts, see links below:
Your current reaction probably sits in one of three places if you live in the Microsoft space.
- "I'm so excited" - you can't wait for darter and all the benefits it will bring to ease access to information,
- "It's going to be too expensive" -you might be excited about it or not but either way, you just don't think you'll get the budget To get anywhere with it.
- "Erm, what is Cortex?" it may be that you haven't heard about Cortex and the buzz that started at Ignite in 2014 -checkout https://aka.ms/ProjectCortex as a starter or listen to our first Grey Hat Beard show
Regardless of your current state of mind or Cortex, the aim of this series of posts is to get you thinking about knowledge in your environment. Where is it stored, how do your store it, formal informal knowledge and how can you get access to that knowledge for the right people at the right Time. Much of this will be made easier by Cortex but you can gain huge advantages by implementing some of these suggestions Without Cortex and if you will be implementing Cortex then you will still need to plan for many of these things.
• Add something about what is knowledge management • aim is to connect those with knowledge to those who want (need knowledge To help this series to be practical as well • theoretical, lam going to demonstrate some of the practices using the Greybeard etiquette of Microsoft 365 content. the ones will contain: -Considering where knowledge is stored -Organising knowledge -Creating a culture of knowledge -Records management us. knowledge might • Al driven access to knowledge • Searching and browsing through knowledge