Re: Recommendation for KMS with specific features #tools
Robert L. Bogue
I was thinking about your response and I started to wonder if knowledge management was “not cool.” I’ve seen some truly awful SharePoint implementations – and some amazing ones. I think excluding software before identifying requirements and desires is probably not the right order – as many others have said or alluded to.
I like the idea of creating a listing of things that people have done but I wonder who will do the work of correlating and curating the content.
I’ve been pondering KM in the context of Adam Grant’s book Give and Take and how the goal of KM is to increase the degree to which people act like givers in their organizations and that we often do this by reducing or removing barriers. (Ala hassle maps, See Demand) It seems to me like we spend a lot of time building systems (human and technical) that reduce the ambiguity of how to share (give) and there by make it easier and less frightening. I was just reviewing my notes from The Tipping Point because I was recalling the study about students getting tetanus shots and that the key differentiator was providing a map to where the health center was on campus.
All of this to say… I think it’s wise to figure out the operating model that we’re trying to instill in the organization and then seek to develop the systems that we believe will lead to that operating model.
Robert L. Bogue
O: (317) 844-5310 M: (317) 506-4977 Blog: http://www.thorprojects.com/blog
Want to be confident about your change management efforts? https://ConfidentChangeManagement.com
Are you burned out? https://ExtinguishBurnout.com can help you get out of it (for free)
From: main@SIKM.groups.io <main@SIKM.groups.io> On Behalf Of Tami Dubi via groups.io
Sent: Friday, July 16, 2021 2:50 AM
Subject: Re: [SIKM] Recommendation for KMS with specific features #tools
H Lisa and Robert,
@Lisa_Austin, you actually read my mind. I was thinking of the holy grail while writing the specifications. I thought that a system with those specifications was non-existent, but I wanted to make sure that I didn't miss some magical system out there.
I agree with you that we can't have it all and have to be practical and focus on what we can achieve in what we have, and I also believe that strategy, processes, and people come before tools. However, companies today insist on tools, especially companies that are software developers themselves.
The company/ companies that I referred to are fast-growing High-Tech startup companies, where most employees are in their 20s.
And to answer your question, @Robert_Tylor, That is one of the reasons why I excluded SP, which is conceived cumbersome, outdated, and generally "not cool."