One thing I was thinking about: In an effort to start collaborating right away, what about going to the employees to explain that Acme values the "wisdom of crowds" and wants to capture the intelligence of the employees as a group in order to build a stronger employee community, enhance the corporate culture, and ultimately benefit the employess because they could learn from each other via a different way other than email/vmail etc. Depending on the general skillset of the employees, wiki may need to be described (benefits/drawbacks) and demo'd. Then ask them to provide ideas for the "policy." How could a wiki be used? Who could manage it? Who would "control" it? Would employees like you use this? How could we, Acme leadership, capture and learn from the group in a way that was legally compliant and non-inflammatory? What features would the group want to see? What are their expectations with something like a wiki?

Then the Acme leadership "board" (COO, CEO, CFO) could review the ideas/submissions and implement what they felt was appropriate, thus making the skeptic leaders still feel they have a sense of control for the implementation and use. The expectations would have to be set with the employees that not ALL policy ideas would be applied but I think that the employee base would have more of an emotional positive reaction to just being asked directly about what they would like to see/want/use.

2  out of 2 found this valuable. Do you find this valuable? Do you?    

• Post reply

Show Last Reply

Hi to all.....now back and melting in Dubai! Am wondering if I'm missing the content regarding Mobile Devices (end of our Day 3, which Elliott was going to add). It's most probably somewhere I'm not looking!! Look forward to knowing about how the mobile devices capabilities are evolving, and how they will be able to support the idea of learning anywhere, anytime, with a student simply doing his reflections, or adding to a wiki, whilst waiting for the dentist., for example. (At least it would take his mind off the needle!!) I suppose my dream is that I work with a group in a Moodle environment, yet they can take any part of the content from Moodle, onto their mobile phone, and use it when it fits their life, and yet meet 'classroom required deadlines', allowing the merging of lifestyle, formal and just-in-time learning and reflections.

Deb

 out of  found this valuable. Do you find this valuable?    

• Post reply

I agree with other's comments that postioning the value of wiki's would help to dissolve siloh or 'Not Invented Here' syndrome for colleagues who are afraid to share expertise and lose control. Gaining agreement for policy, content and governance up front will drive usefulness.

In our horse group we discussed that the corporation gains value in rapid deployment of content and sharing via a wiki. This is high value. However, participation needs reward, so motivating colleagues to share may require creative incentives to reward collaborative behavior.

In my own corporate environment, I can imagine a Wiki site that would provide system engineers (as well as their account managers) to share best practices and lessons learned about implementing technologies with their customers. I could envision SE's sharing how they postioned a new feature with a customer and/or sharing how a specfic technology would solve a customer scenario. Extending that type of 'shared learning' in a wiki would provide opportunities for more engineers to gain access to the group's collective learning. This provides value to the corporation because they learn by sharing remotely, not necessarily by attending a class.

 out of  found this valuable. Do you find this valuable?    

• Post reply