The reality in companies, however, is quite different. There is a fine separation between the transactional and the communicative world. From a technological perspective, these are often SAP systems with the corresponding process applications and, on the other hand, Microsoft Teams & SharePoint, Atlassian Confluence or special providers for employee apps.
From an internal perspective, this separation is also reflected in the responsible departments/areas. Separate responsibilities within IT, separate responsibilities in the departments responsible for the processes. For many years now, it has been a major challenge to get everyone involved in a Digital Workplace project around the same table at all. This is not intended to be a blanket statement, but it does reflect reality in many cases. This separation is not really good and, in my view, not conducive to the future!
Too often, artificial walls are created here that make life difficult for users. This is evident in various usage scenarios. In everyday life, for example, users need too much access knowledge and have to perform a difficult transfer. As an employee, I have to know "where something is or should be done" and how to combine it in a meaningful way. This is similar to the assembly of a car, where the individual production components are scattered in various warehouses and have to be collected in a cumbersome and time-consuming manner before assembly. Or the media break in the process application itself. For instructions, explanations or case differentiation, it is often necessary to leave the application and look in one of the many information repositories.
So instead of separation, the aim should be to bring together enterprise processes i.e. applications with the communication and business related information and combine them in an integrated way. Communication and the related information is a very important part of business processes. You can't do it without communication.