P2P

Fall22

Peer to Peer: ILTA's Quarterly Magazine

Issue link: https://epubs.iltanet.org/i/1480787

Contents of this Issue

Navigation

Page 19 of 78

20 P E E R T O P E E R : I L T A ' S Q U A R T E R L Y M A G A Z I N E | F A L L 2 0 2 2 security and compliance requirements. To avoid this problem, IT needs to get ahead of its users, establishing protocols that prevent individuals from setting up their own instances of Microsoft Teams. Firms should also automate team creation, since setting up a Microsoft Teams instance manually is both time consuming and error prone. Implementing security, governance, and lifecycle management controls for Microsoft Teams —using measures such as security at creation, ownership rules, agreed-upon file formats, naming conventions, and renewal policies — ensures that users are set up to succeed at keeping track of information flow and matter status. And by providing structure and rules, you can prevent user frustration and noncompliance. Law firms store and manage large quantities of important client data in intake, financial, practice management, and document management systems throughout the client lifecycle. Any system that drives client-matter collaboration must be able to connect to these core systems and respect their placement in the firm's systems of record. Planning for your firm's Microsoft Teams implementation Proactive planning helps to ensure that you can anticipate and prevent pitfalls. Stay on track by documenting a blueprint for your Microsoft Teams implementation, including the key considerations you need to address for a successful rollout. Read on to learn more about the steps and best practices your firm can employ for the best possible outcomes with Microsoft Teams. B E S T P R A C T I C E Specify the types of Microsoft Teams workspaces you need Start by identifying the appropriate Microsoft Teams information architecture within your firm to establish use cases. Although common cross-team uses will surface — such as chat, files tabs, and wikis — each team will likely also have unique requirements. Next, establish the various categories of teams present in your firm's environment, document the types, and capture that information in the overall Microsoft Teams information architecture. For example, your firm may have teams that collaborate on administrative functions — such as HR, IT, and finance — as well as teams that need to collaborate with clients and third parties. Your firm will likely have teams that are focused on specific practice areas and geographies, as well as matter-centric teams for which Microsoft Teams serves as the forum for a diverse set of stakeholders. For matter- centric teams, you'll find it impossible to apply a common approach, because each matter will present its own set of unique requirements. F E A T U R E S "By providing structure and rules, you can prevent user frustration and noncompliance."

Articles in this issue

Links on this page

Archives of this issue

view archives of P2P - Fall22