Many organizations struggle with their knowledge work. The transition to using Microsoft 365 services is often IT-driven without proper orientation and training for end-users. The number of Teams teams may have gotten out of hand, not to mention naming conventions or owner information. Even Copilot does not provide a shortcut to success in finding information, as the data it processes is partly outdated due to inadequate retention practices and agreed storage locations. Skill levels often vary within the organization. Some employees can effectively utilize modern tools, while others feel they need guidance in using them. The solution to these challenges is to create a knowledge work playbook that provides guidelines and best practices to streamline and enhance knowledge work within the organization.
Knowledge Work Playbook
Knowledge work is done together. It is important for the organization to have collectively agreed rules and models for working and communicating with different tools. The Knowledge Work Playbook is a collectively agreed working model that makes work smoother, more efficient, and more secure. To make the Knowledge Work Playbook a successful project, it is important to include a wide range of representatives from different areas of the organization in the project team. The design and implementation of the playbook is by no means solely the responsibility of the IT department.
What Does the Knowledge Work Playbook Consist Of?
The project team should initially consider the goals for the playbook. What does the playbook aim to achieve? Is it, for example, to improve the smoothness of knowledge work, transform knowledge work with AI tools, ensure security and privacy in work practices, clarify the structure of Teams teams, or something else? At the start of the project, it would be beneficial to conduct a user survey to identify potential pain points and training needs that should be addressed in the playbook and its implementation. Based on the results, the playbook can address the specific needs required in the organization.
There is no single correct model for the structure of the playbook; it is formed based on the needs of each organization. Setting goals and conducting a user survey serve as a good foundation for planning. However, it is advisable not to bite off more than you can chew at once to avoid never publishing it. The playbook can and should be developed as an ongoing process.
The playbook can include topics such as:
Document Management and Sharing: Document naming conventions, where information is stored. How documents can and should be shared within the organization and with stakeholders.
Utilizing AI: How to leverage AI in your work. Rules for handling organizational documents with different AI tools.
Collaboration and Communication: Guidelines for collaboration and the tools used for it. How communication is conducted with different tools. What are the official communication channels of the organization? How should colleagues be considered in daily work and communication?
Security Practices: How information can be shared securely. What should be considered when handling sensitive information.
Structure of Teams: How Teams and channels are structured and intended to be used. What topics are meant to be addressed in each. Practices for when to create a new Teams team and when to create a new channel under an existing team. Team settings and naming conventions for both external stakeholder work and internal use only.
Implementation of the Knowledge Work Playbook
Particular attention should be paid to the implementation of the Knowledge Work Playbook within the organization. Implementation involves a change in knowledge work, which requires management commitment. The implementation of the change can be a lengthy process depending on the organization. To get the entire organization committed to the common change, the project needs a morale-boosting sponsor, typically from the organization’s management team. Additionally, the implementation should consider how training that changes knowledge work is organized. Should the organization select knowledge work ambassadors whom end-users can primarily turn to with questions related to the change in knowledge work?
Responsibility of IT Management
IT management is responsible for providing the framework for secure and privacy-conscious knowledge work. To succeed in this task, it is particularly important to have visibility and monitoring of the state of security and privacy. These aspects should be considered in technology and partner selections, aiming to build a model for managing knowledge work where decisions are made based on genuine information. IT management is also often responsible for organizing training. For example, regular short “coffee break” type briefings have been found useful and sufficient for training in many places.
Summary
The Knowledge Work Playbook is a shared concern for the entire organization. It helps the organization avoid common pitfalls such as uncertainties about where information is stored, how communication is conducted within the organization, and how security and privacy should be considered in information handling. Shared rules clarify operating models and create a better foundation for workplace well-being.
At Above IT, we have assisted organizations in implementing knowledge work playbooks. Our PilviCapo managed cloud service is also designed to support and enhance the usability, security, and privacy of Microsoft 365 services within the organization. You can learn more about our service here.