CASE STUDY

Microsoft Teams: Business-oriented use

Ekan Management led the creation of concepts and development of solutions for business-specific use of Microsoft Teams.

The client: The customer is a medium-sized international technology company that develops and manufactures world-leading products.

The client's challenge: The customer needed to replace and develop their current use of collaboration surfaces for line organization, project operations, management, etc. Therefore, they saw great potential in their use of Microsoft Teams. At the start of the project, Microsoft Teams was available but not structured or adapted to the needs of the business and therefore suffered from a wild growth of new collaboration areas, and a lack of structure to the business's information.

Our solution: As with many other missions, it is not the technical limitations/possibility that are decisive. That is the importance of understanding the real needs of the business. Ekan Management worked together with different parts of the business to understand the basic needs around collaborative spaces, and strict requirements around information security and retention/retention of information. Through interviews and workshops based on the existing working methods of the business, we were able to identify what types of collaboration spaces were needed in the future, how they should be structured from a user perspective for efficient use, and what type of information should or should not be handled on the collaboration spaces.

The result: Through the work, a more efficient cross-functional collaboration in line and project was ensured on an overall level. More concretely, several capabilities were created in the business:

• A logical, efficient, searchable and purpose-oriented structure of team sites/collaboration areas that makes it easier for users to find and share information and collaborate in different constellations (line, project or other).
• Lifecycle management of the Team sites (creation, ownership and archiving).
• Effective authorization structure that allows transparency and openness but with the ability to limit access when necessary.
• Basic set/template based on type to achieve recognition but at the same time allow continued customization for the unique need.