In my previous post, I provided a brief overview of what Project Cortex is and how it can benefit an organization. In this post, I would like to focus on topic cards and topic pages. I’ll discuss what they are and what goes into creating them.
A Topic card is an overlay that sits within the Office 365 tool you are using (Word, Outlook, etc). A topic card is going to give you an overview of a knowledge topic (hence the name) within your organization. It contains a description/definition, any acronyms it may exist under, People who may be experts in the topic, any files that may contain any information pertaining to the topic and any other topics that may be related.
For the most part the different components of the card are self-explanatory, but related topics might need a bit of an explanation. Quite often if a topic is found to be related to other similar items people may want to know about these. If these items are also a topic in Project Cortex a link to that topic will also be listed here. For example, say your company is going through a massive records management overall and has a subproject within it related to configuring Microsoft 365 to organize and retain the information you are storing. If that project is also a topic within Cortex the link to it will be displayed in the “related topics” section of a topic card.
Think of a topic page as a full-page view of a topic card. The information is going to be very similar, but it also will likely be more extensive because more information can be fit on a page than a card.
Something that Project Cortex allows with a Topic Page that will be extremely beneficial to a communications team within any org is the ability to edit Topic Pages. While Cortex will build out the initial page for you, the actual page can be edited for both content and format. So if the information pulled and built by the AI isn’t quite right or you want to elaborate a bit more you have that ability.
Before I complete this post I want to ensure everyone is aware that everything that Cortex builds is completely security trimmed. In fact, if Cortex pulls data from a document to build a page or topic card out and you as the user viewing the card or topic card does NOT have access to the document (in a location you don’t have access to) then our experience will actually be a little different. Cortex will actually build the information on your card or topic page from documents that you do have access to. So users that shouldn’t have access to a particular component of data for a topic (whether a project or even general information on something within the company) won’t be able to get it via Cortex.
In a future post, I will discuss the next level in a Cortex topic card or page.. the knowledge center.
Thanks for reading!!