Wednesday, October 21, 2009
Exercise 8.3 Data portability, FOAF and the Semantic Web
Tuesday, October 20, 2009
Exercise 8.2 The avalanche of applications self-interview
Exercise 8.1 The 30-minute walk
Wednesday, October 14, 2009
Exercise 7.2 New devices, aged care and people with disabilities
Saturday, October 10, 2009
How is a work-related social network developed and sustained?
Building a successful social network (particularly in Professional Development) means aligning the people with the purpose through clear and mutual aims and objectives, reward and acknowledgment for contribution, clarity and access to information and feedback, leadership, celebration of achievement, technology support and training.
This post points to two websites that illuminate how social networks can be developed and sustained.
Connectivism
Firstly, George Siemans in 'Connectivism: A Learning Theory for the Digital Age' retrieved from http://www.elearnspace.org/Articles/connectivism.htm says
"The pipe is more important than the content within the pipe. Our ability to learn what we need for tomorrow is more important than what we know today. A real challenge for any learning theory is to actuate known knowledge at the point of application. When knowledge, however, is needed, but not known, the ability to plug into sources to meet the requirements becomes a vital skill. As knowledge continues to grow and evolve, access to what is needed is more important than what the learner currently possesses."
What he means is that the quality of the connection (ie number of connections, the number of different connections, the timeliness of the knowledge) is more important than the knowledge itself.
Getting members active and addicted
Secondly, in 'Community building: Getting members active and addicted | Community Building retrieved from http://www.communityspark.com/community-building-getting-members-active-and-addicted/ Martin Reed presents several practical strategies for sustaining an online community. Some of these that I believe are most valuable in a closed system dedicated to the professional development of its members are:
Engage at every opportunity
All members should post, chat, complain, email, emote, ask, refer etc. as much as possible. Every interaction affects the quality, flexibility and integrity of the network.
Delegate community building tasks
The manager of the network need to find things for users to do. It might mean sharing experience, voting in polls, online questionnaires, contributing to blogs - anything to move users from being lurkers to being participants.
Earn and retain trust
Ensure you have strong, clear community guidelines that you enforce professionally and impartially. It’s hard to earn trust, but very easy to lose.
Get involved. Be contactable and approachable
You need to get involved in the community. Why should you expect members to get involved if you can’t be bothered to do so yourself? You need to be visible. Don’t be anonymous – be sure to share information about yourself.
The subject matter of your community and your aims and goals should determine how involved you are in your community. Regardless of how involved you are, you should always be approachable and contactable.
Be aware and follow up. Show concern.
It is not much use if you are on the fastest network in the world if you take eons to reply to anything. If a person needs to know something they usually need to know it yesterday. Understand and respond to their urgency and they'll hopefully do the same for you. The pipe will get bigger as a result.
Create a ‘dummies’ guide
No matter how easy you think your community is to use, some people will still be confused. You need to cater to these people. Ensure you have guides on how to use the community and make them easy to find! Have a section for frequently asked questions. Even better, create videos so people can see how to use the community.
Conclusion
Its interesting that all of the above discussion does not refer to the 'magic bullet' a system of piece of software that will 'build a community in a day'. All of the points raised above are just about quality professional interaction in a 21st century connected world.
How do Web 2.0 tools (blogs, wikis, podcasts and video lectures) complement such social networks?
Top 100 Tools for Learning 2009 - Centre for Learning & Performance Technologies http://www.c4lpt.co.uk/recommended/index.html
Twitter, Delicious, Google Reader, Google Docs and Youtube were voted (in order) as the top five 'Tools for Learning ' in 2009. It is interesting to note that all are open source products, all are products that search and compile knowledge according to the direction of the user rather than purport to be static 'Walled Cities' of information such as Encyclopedia Britannica or even Microsoft Expedia which is updated periodically. Even Wiki only made 17 on this list.
My point here is that the choice of tools for a network needs to be based on 'services' rather than software. It doesn't matter what the software is, it just needs to respond easily, efficiently to the needs of the network. It needs to be scalable, cross platform, cheap enough for many users and it must be able to be configured completely by the IT departments of the companies that use it.
Information
One of the most important function is establishing the project network is to compile and present the key project documents. As well as including purpose, goals, roles and timelines more supporting documents will be created and discovered as the process rolls out. A project wiki would be an important platform in order to compile and co-ordinate the key information. Wiki rules require that all information is annotated and the sources documented. The project moderator should also monitor the evolution of the wiki.
Discussion
In addition to key information, an important project process is discussion. This can occur asynchronously as blogs and forums or synchronously as video conferencing, skype sessions or chat rooms. Each technology has pros and cons. Blogs and forums ensure that the information is presented so that it can be evaluated and debated and that people can add comments and further pieces of information in the form of links, posts, images, video files etc that enrich the initial posts.
Synchronous communication is especially useful for multi location 'brainstorming'. Disadvantages are that these platforms are that not all systems allow archiving, the conversations (even if they are moderated/lead and that users agree to use 'threads' during the session) need to be 'digested' or processed in order to distill all the good interaction and eliminate lots of typos. This requires more project time (and therefore money).
Documentation
In question 1, I suggested that the CIO and IT manager need to be supported by other senior level management. One crucial manager should be the Knowledge Manager (KM). The KM's project responsibility would be to propose the information architecture for the project and then update this container with fresh information from all project sources so that all stakeholders could access the 'freshest' information.
In many cases this can be an automated process through Web 2.0 tools including Delicious (for archiving urls), log stats and other dynamic database data presented using graphical user interfaces (GUI) and Twitter (to keep users updated on the locations and activities of key project stakeholders. In other cases, the KM will need to filter and compile all project information into project knowledge that can be accessed and acted upon.
Project management
There are many project management software products and the company might have several products on its network. However, in order to manage the project well, the information needs to be available in one place on the network. The information needs to be updated and acted upon often by people who are spread all over the world. Webex is one tool that is suitable for allowing access to project management information by several stakeholders simultaneously across networks. Webex allows stakeholders to take turns in 'driving' the software in order to ensure their role is understood and documented at a very 'deep' level.
Testing and authentication
A crucial part of project management is the testing and authentication of products and systems that the company is responsible for either to support its own operations or that of their clients. Network tools to facilitate this process include polls, data analysis tools, video files depicting user experience and podcasts presenting voice interview of product testing. The results of this testing will affect the progress of the project through the milestones in the project management cycle. The presentation of testing and evaluation materials on the network can motivate company employees, ensure that project decisions are transparent and provide the opportunity for easy and repeated analysis in solving problems as part of the 'extreme programming' method of product development.