Note: This post is adapted from its original publishing by Konica Minolta Canada and its IT Services Division, IT Weapons.
Recently, our colleagues at Konica Minolta Canada chatted with Giles Crouch, Chief Digital Officer and Digital Anthropologist at NordSpark. He was their webcast guest speaker for Rethink Efficiency & Workplace Culture in the Digital Age. The session sparked some brilliant Q&A, the best of which are included below.
Giles: A community of practice is long-term, it’s ongoing and it always stays there. A steering committee, on the other hand is really talking about a project with an end date and a desired outcome. A steering committee is often tasked with choosing the right tools for the organization, be it a small business or a larger organization that is looking to change and adapt to something better as they grow. For example, Microsoft environment versus Google Workspace? The steering committee would set out to get to that decision process. The community of practice is something that exists forever, so that you have representation from across the company that is always learning and can experiment with new technologies. If there is a need for a newer, better project management software, they can talk to vendors and figure out the best move forward. Most importantly, a community of practice allows you to ensure constant learning in the organization that never goes away.
Giles: Technology innovation can be led by your community of practice. They can ask questions to industry leaders or maybe just complementary organizations that support their organization’s role in the industry. Questions should be specific to the business outcomes that you are looking for. This ensures a constant state of learning. As technologies change, you have to always be learning. You must try to understand how you can leverage technology and help your organization as well as your customers? That’s where innovation comes in – making sure that the community of practice has a charter and the permission to explore alternative answers. It ultimately helps you map out the territory of where you’re going and see the bigger picture.
Giles: It sure is! You can build a wiki right in SharePoint. It is not too hard, and you can use apps from within Sharepoint to build it. You can enable it so that it’s by department, but still have everybody able to view it. Videos, documents, internal and external links, everything goes there. A different tool might be necessary if it becomes too large over time. SharePoint is an excellent place to start.
View the webcast on demand here.
If these insights have given you some ideas and you would like to learn more, visit us online.