A couple of teams in my company are trying to promote the idea of
building a learning organization by developing groupware applications
that support specific business processes. While some team members
are specializing in mastering the groupware tool, there are others
who are facilitating in gathering requirements from the process users.
Key Question:
What are example roles and responsibilities that non-programmers
in the team can specialize in so that they can
* feel valued,
* increase their contribution potential, as well as
* create a learning organization?
Motivation:
This question arises from the fact that groupware application development
is just one aspect of creating a learning organization.
Thanks for any insight.
--Ramu Iyer
--riy542@casbah.acns.nwu.edu (Ramu Iyer)
Learning-org -- An Internet Dialog on Learning Organizations For info: <rkarash@karash.com> -or- <http://world.std.com/~lo/>