So, let’s take a closer look at the business services in both cases. Capture Process 1 In this case, the government agency had plenty of customers walking in to submit their visa and residency documentation to the Receiving unit. The high volumes required an optimized capture solution in place while a tight budget required the solution to maintain if not decrease manpower
The best predictor of Information Management Success is your Staff's ability to find the Content they need In this webinar, we will show out-of-the-box automations (many securely using AI) to actually get Content in order. Privacy (PII), Classifications, ROT (Redundant, Obsolete, Trivial)... these are problems with Content that are beyond human scale to "clean" for use in things like ChatGPT/LLMs
See matching posts in thread - Get your information in order f...
Keeping information that has no value just in case is not a sound business decision. What happens to your analytics in this case? I would argue that it would be a monumental task to separate the wheat from the chaff to gain the insights that are buried in the morass of content. Effective analytics has to start with information governance. Just in case you need it, doesn’t cut it as far as I am concerned
" In their study " A Bias against 'Quirky '?...After all, idea-driven people may lack the social graces needed to play the advancement card. Creatives live in their own heads, observes management
Anyone remember that TV Show? In Search Of? It was a show that ran from the mid 1970s to the early 1980s, hosted by Leonard Nimoy, and focused on the investigation into mysterious phenomena
1 Comment - no search term matches found in comments.
And one of my pet peeves with SharePoint is that it lacks what I call "collaboration in context" . In other words, there's no linkage or capture of the conversations or activities within an associated item in a list
Themes are new in SharePoint 2010 and they are really easy to use, but modifying them in SharePoint is cumbersome
Last week my wife and I spent a few days in Charleston, SC...Overly elaborate structures accompanied by "mandates" for participation created initiatives that had little staying power in the long run and eventually withered on the vine
This environmental shift in your thinking must be reflected in your planning efforts before moving to the next version of SharePoint, regardless of whether it will be on prem, in the cloud, or somewhere in between. Regardless of your intent, the key is to understand the services you plan to consumer and their limitations, build a platform that meets your business requirements, and optimize that platform for your performance needs: Define the service applications to be deployed Understand their governance and management capabilities, map them against your governance and management requirements Fill in any gaps through 3rd party tool ecosystem, or building to suit Model your environment for scalability Define and communicate roles, permissions, and security boundaries Understand growth needs for your content, structure appropriately If preparing for a migration from an older version of SharePoint, take the time to clean up your information architecture prior to your move, and understand how you will enforce/manage once inside your new deployment While moving to the cloud may provide many plug-and-play solutions, allowing your organization to get out of the business of infrastructure management, the reality is that there may be a long (or even permanent) hybrid transition as your requirements evolve to fit the cloud paradigm, and as many cloud platforms mature