Archive for the 'Document Control' Category

Easier collaboration with SME’s via Google Apps?

Google has demonstrated Google apps to the public as a way for groups to establish quick colloboration via the web.  Of course you have to pay for your own domain name. Is this right? it’s only $10 a year.  I’m assuming that where you’re really going to pay is for server space to put and maintain your e-info.

Of course, there are a few things I would make sure are in place before diving into this type of system. 

  1. Regular Data Back up (which I assume we will have to pay for as well)
  2. Web Administration. As the article notes…it’s important to have web trained administration types in place (depending on the size of my effort/company this would be a dedicated individual… god, I hate making people do things on top of their normal job because it insure one or more of three things:  a.) the person responsible burns out b.) the (web-)crap never gets done c.) the crap gets done but it’s crap.
  3. Security. Proper security protocols are set up.  If the material you’re sharing is sensitive then make sure that you can set up a secure, password protected environment.
  4. Intellectual property and Privacy conditions. Also make sure that there is no condition (and that you have this in the form of a legal contract) that because you are storing information on Google’s servers it will be accessed or touched even considered their property because they house it. You are paying for a service, that is storage and access to material, but just as there are privacy laws. If you agree to anything of this nature make sure you review it thoroughly first. 

Nuggets/News articles:

Advertisements

Now that I understand 2.0, what next?

Through this blog I’ve been exploring the following ideas:

  1. Informal learning – learning through social networking and informal on-the-job documentation may directly help individuals learn on the job much more quickly and effectively
  2. Web 2.0 technologies provide easier ways to collaborate electronically with others and thus enable this infomal learning better than ever
  3. As training organizations we could focus on empowering better social/informal learning rather than producing the traditional costly training end products (face to face training, media rich e-learning). – However, the problem with this is you often have to deal with a lot of crusty managers who think that this is normally built into employee’s job responsibilities (even though it isn’t formally/properly addressed)

If I’m obsessing over focus on informal learning, I considered -what about the formal and more permanent forms or products of learning? How do we make sure that we’re doing an adequate job of capturing what needs to be put in formal form? What about Librarians? What possibilities do they see in applying 2.0 technology?  In my searches I found one blogger/librarian, Meridith,  who openly discusses the uses and challenges of applying the technology to practice.  I’d like to find out and listen more to what bloggers in the library world are doing about 2.0, and hopefully I can keep track of this in future posts.

In reading Meridith’s blog posting, and recounting some of the dialogue I’ve been seeing lately about 2.0 hype, I started to think about how tenuous ideas and proposals are when they first come out.  Although Web 2.0 gives us a lot of glitzy promises through it’s beta concepts, 2.0 application in the real-world is still in it’s "toddler years."  (It’s just given up crawling, and has started to learn how to walk clumsily on two legs). People in the workforce are really just beginning ot apply things like wikis and blogs, and their exploration of these things naturally will be clunky on the onset. I think as I’ve heard a lot of skeptical discussion about the staying power of blogs that some people are becoming overly saturated with 2.0 hype.  However, I still believe that if those of us who enjoy using the technology and benefit from it keep on using it to allow us to grow, learn, expand and collaborate better for success, there’s no reason to assume that 2.0 apps like blogs/wikis have to die away. I think Blogs have been around for at least 4-5 years maybe more… and public awareness has just hit mainstream proportions.   Wikipedia is still going strong, and many companies are now adopting use of wiki-software to communicate and collaborate.

I’ve felt that being a tech-evangelist for waves like 2.0 is a tricky position.  My feeling is (being the victim of Sharepoint-evangelization or more Sharepoint mandate) don’t force tools down people’s throats – Instead use this approach:

  1. Understand what the resistance points are to adopting the tools and methodologies
  2. Understand  and get to know the users who will be using the tools
  3. Just focus on finding out how best they work with the actual users
  4. Model and demo good examples
  5. Gather valid/reasonable proof (data) that these tools are achieving your goals
  6. Share with management (during all of the above steps) – build and communicate in a simple language that they can understand and connect with

 I’d like to build out this strategy in more detail, because I’m currently working on a team right now that’s assessing the application of wikis and other new tools to our group.

  


Why?

My place outside of work to explore and make connections with the ideas and things (sometimes work-related) that I'm passionate about.

My Tweets

Blog Stats

  • 290,999 hits
Advertisements