One stash or many...
That is the question here!

How should I structure my SmartStash? Get to know the most important decision criteria!

SUMMARY

These are the most important criteria that help to structure SmartStash correctly from the start, at a glance.

Authorisations

Authorisations for editors and approvers in particular are crucial here.

Content quantity

With very extensive content that has little to do with each other

Compliance

For very sensitive data or different requirements for release processes

First of all... what content do you map?

The intended use of your SmartStash environment has a great influence on how you should plan the structure. Related content should always be mapped in a stash. Do you want to make life as easy as possible for your staff? Then cover as much information as possible that has to do with each other in one place.

For example, it is useful to provide a global stash for all policies or information from HR.

Do you map a quality management system according to ISO 9001? Then it is important that all information is stored in a stash and can thus be found in the same table of contents.

With different audiences, you can still narrow down the amount of content by target group. Employees then only see what they need to know.

If everyone is only allowed to see the things they are supposed to see, then surely each department can have its own stash?

In principle, it is possible and not unreasonable to provide each department with its own stash. Exclusive editors can then write there and no one else has access to the area that should not.

In reality, however, this is often at the expense of transparency and interdisciplinary knowledge transfer! When knowledge is freely accessible to all, it facilitates cooperation, ensures greater efficiency and promotes new ideas. Furthermore, unnecessary processes or duplicate information that differs only slightly are more noticeable.

If you represent several companies in your tenant, it is important to check whether it is legally permissible to share information across companies.

Decisive are demands for authorisations but also strongly separated target groups

Despite all the transparency, SmartStash should not overload the employee with information. If you have more than 200 pages in a stash that are addressed to completely different target groups and are also the responsibility of different editors, it may be worth dividing them into several thematic "manuals" just for the sake of clarity. A stash thus always represents a single book with its own table of contents.

If there is a requirement to strictly separate content and not make it accessible to other editors even in draft status, then a division into different stashes is indispensable in terms of content. For example, a stash specifically for management or for sensitive processes in the human resources department is conceivable.

The provision of different tags for filtering and different requirements for multilingualism and design are ultimately also decisive for how the stashes are divided.

In MyStash, a staff member can see all the stashes released for him or her.

More recent contributions

Knowledge is undoubtedly one of a company's most important resources. However, while physical means of production and employees are actively managed in almost every organization, knowledge is often simply available - distributed across countless heads and locations. Strategically, knowledge management is therefore often introduced out of a desire to make knowledge
Read post
Digital knowledge management based on Microsoft 365 As a modern, owner-managed service company with around 300 employees, impacx services GmbH, headquartered in Kleve, stands for sophisticated customer experience management. In 2022, impacx will become the new umbrella brand (formerly: tel-inform) of the family-owned company founded in 1846. As a digital service provider, impacx takes over
Read post
Following the successful introduction of Microsoft 365 by Fellowmind at Schüco International KG, the Product Lifecycle Management (PLM domain) department at Schüco was looking for a knowledge management solution. They were looking for a tool that would increase efficiency in knowledge management and facilitate the handling of knowledge articles. During the review of various tools, a tip came up
Read post