What is the official document lifecycle story between collab and publishing?

%3CLINGO-SUB%20id%3D%22lingo-sub-1730875%22%20slang%3D%22en-US%22%3EWhat%20is%20the%20official%20document%20lifecycle%20story%20between%20collab%20and%20publishing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1730875%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20it%20comes%20from%20collaborating%20on%20a%20document%20to%20the%20point%20when%20it%20is%20finished%2C%20it%20often%20gets%20a%20new%20audience%20that%20may%20exceed%20the%20members%20of%20a%20team%20and%20should%20also%20contribute%20to%20enterprise%20knowledge%20for%20search%20etc.%20To%20my%20knowledge%2C%20Microsoft%20never%20mentions%20to%20transfer%20content%20from%20Teams%20to%20explicit%20SharePoint%20sites%20nor%20gives%20any%20inline%20tooling%20to%20do%20so%20without%20further%20individual%20configuration.%20Why%20is%20this%20so%3F%20The%20collaboration%20story%20with%20Teams%20and%20the%20Enterprise%20document%20storage%2Fmetadata%2Fhub%20site%20story%20in%20SharePoint%20seems%20to%20lack%20a%20connection%20somewhere%20when%20looking%20from%20a%20document%20lifecycle%20perspective.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1730875%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1731268%22%20slang%3D%22en-US%22%3ERe%3A%20What%20is%20the%20official%20document%20lifecycle%20story%20between%20collab%20and%20publishing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1731268%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F98706%22%20target%3D%22_blank%22%3E%40Carsten%20B%C3%BCttemeier%3C%2FA%3E%2C%26nbsp%3B%20am%20curious%20to%20know%20if%20you've%20been%20following%20Microsoft's%20developments%20coming%20out%20of%20Project%20Cortex%3F%20Based%20on%20what%20I'm%20reading%20in%20your%20question%2C%20I%20believe%20you%20will%20be%20excited%20as%20I%20am%20when%20they%20make%20SharePoint%20Syntex%20broadly%20available.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fresources.techcommunity.microsoft.com%2Fsharepoint-syntex%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fresources.techcommunity.microsoft.com%2Fsharepoint-syntex%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1731272%22%20slang%3D%22en-US%22%3ERe%3A%20What%20is%20the%20official%20document%20lifecycle%20story%20between%20collab%20and%20publishing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1731272%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F7475%22%20target%3D%22_blank%22%3E%40Alex%20Cross%3C%2FA%3E%26nbsp%3BJup%2C%20everything%20read%20and%20understood%20since%20the%20first%20announcements.%20But%20Project%20Cortex%20still%20e.g.%20won't%20override%20permissions%20or%20would%20transfer%20information%20though%20the%20different%20stages%20of%20a%20document%20lifecycle.%20I%20see%20that%20the%20various%20parts%20of%20Project%20Cortex%20may%20provide%20great%20ways%20for%20smart%20content%20combination%20and%20presentation%20like%20some%20sort%20of%20an%20automatic%20SharePoint%20Site%20generator.%20Granted.%20But%20this%20still%20does%20not%20close%20the%20gap%20what%20people%20should%20do%20when%20their%20work%20in%20Teams%20is%20finished%20and%20content%20out%20of%20this%20work%20has%20to%20be%20published%20to%20the%20common%20knowledge%20pool.%20Microsoft%20did%20not%20fill%20this%20with%20advice%20since%20we%20started%20with%20Teams%20in%202016%20early%20beta%20and%20-%20from%20everything%20I%20have%20seen%20-%20never%20did%20so%20even%20when%20all%20those%20adoption%20topics%20arose%20to%20the%20growing%20mass%20of%20Teams%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1731275%22%20slang%3D%22en-US%22%3ERe%3A%20What%20is%20the%20official%20document%20lifecycle%20story%20between%20collab%20and%20publishing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1731275%22%20slang%3D%22en-US%22%3EOh%2C%20and%20by%20the%20way%3A%20Project%20Cortex%20just%20begins%20with%20Systex%20and%20even%20this%20will%20have%20to%20tie%20to%20local%20data%20privacy%20standards%20here%20in%20Germany%20until%20we%20can%20use%20this%20officially.%20So%20this%20is%20no%20story%20for%20neither%20the%20present%20day%20nor%20for%20the%20last%20four%20years%20of%20Teams.%3C%2FLINGO-BODY%3E
New Contributor

When it comes from collaborating on a document to the point when it is finished, it often gets a new audience that may exceed the members of a team and should also contribute to enterprise knowledge for search etc. To my knowledge, Microsoft never mentions to transfer content from Teams to explicit SharePoint sites nor gives any inline tooling to do so without further individual configuration. Why is this so? The collaboration story with Teams and the Enterprise document storage/metadata/hub site story in SharePoint seems to lack a connection somewhere when looking from a document lifecycle perspective. 

3 Replies

Hello @Carsten Büttemeier,  am curious to know if you've been following Microsoft's developments coming out of Project Cortex? Based on what I'm reading in your question, I believe you will be excited as I am when they make SharePoint Syntex broadly available.

 

https://resources.techcommunity.microsoft.com/sharepoint-syntex/

@Alex Cross Jup, everything read and understood since the first announcements. But Project Cortex still e.g. won't override permissions or would transfer information though the different stages of a document lifecycle. I see that the various parts of Project Cortex may provide great ways for smart content combination and presentation like some sort of an automatic SharePoint Site generator. Granted. But this still does not close the gap what people should do when their work in Teams is finished and content out of this work has to be published to the common knowledge pool. Microsoft did not fill this with advice since we started with Teams in 2016 early beta and - from everything I have seen - never did so even when all those adoption topics arose to the growing mass of Teams users.

Oh, and by the way: Project Cortex just begins with Systex and even this will have to tie to local data privacy standards here in Germany until we can use this officially. So this is no story for neither the present day nor for the last four years of Teams.