Interesting issue of where to draw the line. I agree that the very broad
view is the best place to be in understanding how KM works, and especially
knowledge creation. However, when engaged in designing products that
actually work to improve KM rather than just contribute to info overload or
confusion, lines must be drawn.
Taken through the past few years, this issue could very well be why so many
tech products that attempt to serve KM are too complex, bloated, and
questionably efficient at best. The psychological needs and technology
limitations often conflict with the lure of the ability to manipulate
technology for internal quarterly gain or protection of other investments,
rather than simply to attack the barriers to KM.
I've been working on the problem from a business consultant's perspective
in the beginning to developing code recently and am becoming more convinced
that a new level is close at hand from a different foundation of simplicity
and universality.
We are seeking board members and advisors for a nearly mature enterprise
product that marries some of the issues discussed here. If you have an
interest and feel qualified, please e-mail me privately. We have several
hundred of the world's largest decision makers waiting on us.
Thanks, and thanks for the thought provoking discussion.
Mark Montgomery
Founder/CEO
Global Web Interactive Network LLC
[log in to unmask]
http://gwin.net
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|