A friend passed me the link to this blog today.
Two pyramid builders – Goofushotep and Gallanthotep – set out to construct a
pyramid for their pharaoh. Being the traditionalist that he was, Goofushotep
build the pyramid from the ground up and risked not finishing it before his
pharaoh’s death. Gallanthotep, the Agile architect, built a small pyramid first
and built additions sideways, so that there was minimal risk in having an
unfinished pyramid when his pharaoh died.
While the original intent of his blog is discussing about the benefits of the Agile methodology, I think it is also relevant to how we should tackle the adoption of E2.0
A lot of companies are currently waiting for the technology to mature before adopting it and they are researching around for the best practices. However there is no ultimate secret formula that fits all. Companies with different types of work environment and business needs might have to adopt a different approach order to succeed. I am facilitating the use of wikis in several teams with different needs and skillsets. While some teams are already actively using the wikis, other teams are still picking up the momentum.
So instead of waiting, it will be better to start small and gradually refine the approach. The investment cost for building a wiki is definitely smaller than developing a traditional knowledge management system. It is because the structure in wikis can be modified easily and can be gradually refined. There is no need to throw again the wiki and rebuild again. And once benefits have been seem from the small group, then it will be easier to justify for implementation on a larger scale.
0 comments:
Post a Comment