Category: technology stewardship

CPSquare “Connected Futures” week 1 blog post

Week 1 Workshop Blog Post

I’m lending a hand for the CPSquare’s (http://www.cpsquare.org) “Connected Futures” workshop which started the last week in April. As part of our collective “end of the week activity,” we are all to blog a reflection either on the workshop discussion board, or on our own blogs. Since I am currently offline while I write this, my timing will be off, but I decided to share it on my public blog as a “peek in” to an ongoing experiment.

(Why am I offline? I’m currently at ILRI in Addis Ababa, Ethiopia where I’m co-facilitating a face to face element of an ongoing distributed workshop on knowledge sharing in international agricultural research. The network is down. Who knows for how long…???)

The workshop is devoted to looking at the role and impact of new technologies on communities of practice, and how we steward those technologies (or technology stewardship. If I were online, I’d be linking all these things to previous posts and definitions, but that will have to wait until later!)

This is not a workshop for the fainthearted. In the first week we are asked to register and acclimate to a fistful of online tools, from wikis to blog readers. While we have a “home base” on a discussion board, our activities will range across tools and modalities so we have some real experience to reflect upon and learn from. But all this jumping around right off the bat, before we’ve all gotten to know each other, feels pretty challenging. The brave post that they are feeling confused and I suspect others are quietly nodding in agreement in front of their computer screens.

What facilitates coherence? Especially in a complex world? What enables some of us to feel comfortable with incoherence, ambiguity and incompleteness while others take it as natural? Furthermore, how do we reconcile these differences when we are intending to act “in community?”

For me, these questions are always on my mind when I am in the technology steward’s seat. (Or on that keyboard!)

Noticing some nice non-profit wiki work

CCN Wiki HomepageA while ago Beth Kanter put out to her network a request to know about useful nonprofit wiki practices. I meant to reply, but, as usual, got distracted. Today I received an email update about a local coalition here in Washington State (USA) that reminded me about their great wiki work. Check out the Communities Connect Network Wiki . Early on, I had the pleasure of working with Peg Giffels who was their main wiki gardener (among many other roles.) Peg “got” that there was both an information architecture and a set of social processes associated with their use of a wiki as both a project communication tool and as a knowledge sharing tool.

Intially the blog was going to be a general place for coalition members to share stuff. But we all know how general stuff goes — slowly if at all. Then Peg hit on using the wiki to be the central point for the coalitions training programs. Now, at the completion of this last round, Peg has a site that is rich in materials (print, audio, video), has an integrated wiki orientation and training component, reflects specific member areas and contributions (for example here and here) and is well organized and “gardened.” The left navigation links to major areas of the wiki.

One of the things that came out of the early “Wiki Wednesday” hour long telephone based orientations was that people came to get trained, but left with new connections to other coalition members. When asked what was best about the calls — it was always the people they connected with. Peg lives that in the way she works with the coalition. While she stewarded the technology and the content, her attention to the people came across to me, as I observed the wiki development over the months and now years.

Like most wikis, there is a relatively small proportion of editors to page views. For example, in April, there was a rough average of 220 unique visitors per day, 2-3 editors and intermittent spikes of editing across the month. This makes sense given the ‘wind down’ phase as well. There was a huge jump in traffic between February and March. I should ask Peg what was going on!

Interestingly, while this wiki is very focused on Washington state, there are viewers from around the world. I really wish I knew what they thought, in what ways, if any, they benefited from visiting the wiki. I appreciate that the Communities Connect project worked with such openness. They have made a contribution that is bigger than their own project work. I like that about public wikis.

Anyway, I just wanted to share this cool wiki with you. Do you have any great wikis you’d like to share with the rest of us?

P.S. Beth, when I went to find the link on your blog, I noticed two things. Your search box is now waaaay down on the left nav bar of your blog – I almost gave up looking for it. And it is a Technorati search, so I have to go to Technorati and THEN link back to your blog. Maybe consider putting in a Google or other direct search option? I want to find your great stuff FAST! And yes, I’m finally becoming a searcher!

CPSquare’s Long Live the Platform Event Report

cp2llpreportimage.jpgI haven’t read through this report in detail, but I wanted to blog it to get it wider visibility because the sharing the learnings from our community activities is an important (and appreciated) contribution to improving our practices. IN this case – about doing online events for our communities of practice. Check it out — Long Live the Platform Report (application/pdf Object).

Scott Leslie on Trailfire

IMG_0798
Creative Commons License photo credit: Carnavas
As part of the online Knowledge Sharing (KS) in International Agriculture Development workshop, we are exploring KS tools and methods and then sharing our learning via the KS Toolkit Wiki. One tool that came up for review was Trailfire. I had not heard about it, so I put a query out on my Twitter network and in moments, Scott Leslie, a Northern Voice colleague, came to my rescue. Here is a 15 minute podcast with Scott about Trailfire and related tools used to share and comment on our journeys across the web.

Podcast: Scott Leslie on Trailfire

This tool is a Firefox plug-in, so if you want a defined group or community to use it, they all have to be FF users and agree to use the plug in. It would be interesting to test this in the international agriculture research community. (Or any other community.) There is also the wonderful bit about serendipity – finding trails left by others – their annotations and opinions — on sites that you are looking at.

Scott also shared his pre-call prep notes — which I find interesting. (Thanks, Scott!) I’ve put them below.

If you are interested in more blog posts like this, please let me know — and what tools or methods that might interest you.

Trailfire notes

Firefox plugin that works in conjunction with a main site

allows users to create “trails” which are made up of sequenced web sites

a trail mark also allows users to add an annotation to the page, so that when you are looking at that page
with the plugin enabled, you see a small mark, mousing over it shows you the full comment and
provides a link to the full trail

the website allows you to share your trails with others

you can also have the plugin show ALL trailmarks that have been made for a specific page, not just yours, which opens up
all sorts of possibilities for finding other users and finding other trails, other contexts in which a page can be seen

you can also add comments to other people’s trailmarks, meaning that conversations can actually break out “on” the web pages where the
marks were left without the need for any additional server software

cross between a social bookmarking and annotation tool

Educational and Other uses
obvious one is for instructors to create a trail through a series of web pages with some educational objective in mind

but as students/learners can also create their own trails and marks, it also becomes a way to connect with other informal
learners

it empowers users to connect and share with each other without requiring the individual sites to provide any facility or
containing mechanism to do so

simple way to add help commentary to websites – add a mark that leads off to further help documents and tutorials from whatever site
you are trying to use, or use the note to add help, like Greader shortkeys mark

a way to non-invasively annotate the web

a way to leave commentary for Others on websites

a virtual layer that overlays the web; this same technique is now being exploited by browser plugins like PMOG,
passively multiplayer online game, a game played ON TOP of the regular web through a browser plugin

cf. also medium (http://me.dium.com/ )

URLs mentioned in this podcast:

Harvesting knowledge from text conversations

Km4Dev wiki screenshotThis is the second in my latest series of online facilitation method tips and mini-podcasts. John Smith asked me to write up the practice some of us have been nurturing on the KM4DevWiki to encourage summarizing and harvesting of learnings from key community conversations in our email list on to a wiki. The podcast can be found here.

There are often amazing threads on email lists and web based discussions. Often they get lost due to the tyranny of recency over relevancy. We remember what we last read. How many times have you heard people say “hey, we discussed that before… where IS that conversation?” Some tools make it easy to search within message, but then you have to reconstruct a thread. There may have had subject line changes, interruptions, etc. It is hard work. That’s why it is useful think about practices to pull out useful stuff so it can provide wider and easier benefit.

One practice of harvesting learnings from text based discussions (in email or web forums) started as a small FAQ (frequently asked questions) project a small group of use did a couple of years ago as part of the KM4Dev community. KM4Dev is a global community of practice interested in knowledge management and knowledge sharing in international development.

We initially intended to create FAQ’s out of key discussions to answer what we thought were some of the “big questions” that often came up in the community. You can read about the project at the following links.

What we discovered was that often something wasn’t simply a response to a question, so the FAQ format started to limit us. We moved into harvesting what we called “Community Knowledge.” This is the basis of the technique I know use regularly.

Now, on the the technique. (Did I say these were going to be short? I guess I goofed on that!)

  1. Role model the harvesting behavior. Our initial FAQs gave people the chance to experience discussion summaries. But the next step was to role model it around current discussions. At first we would notice a “hot thread,” summarize it then post the wiki url back to the email list.
    • Templates can make it easier/more comfortable for people new to summarization and/or wikis.
    • Cross promote the wiki on the list to keep it in the community “line of sight.”
  2. Ask others to try the behavior. Next we started asking people to create and post their own summaries of discussion threads that they started.
    • asking in a private email is friendlier, but sometimes the public request can add some useful “pressure.”
  3. Time the request well. Usually we made the request for summarization after we saw a thread really get going — and hopefully near the end of the thread.
    • I have made the mistake of suggesting that the thread be summarized too soon and people took that as a “stop talking” signal.
  4. Expect resistance. (And I’m tempted to say “resistance is futile, but that’s not really true!) Initially people did not summarize. So I would set up a wiki page for them, send them the url and another small request. (I think I started signing my emails from “wikipest.”) Some people would then summarize and post to the wiki, and some would send me the summary to post. That was fine.
    • Reminders are often useful. I do wonder if I annoyed some times…
  5. Encourage those who adopt the practice. After about a year, others started recommending a summaries to starters of hot threads. So the initial part of the practice was being picked up by others. More people were creating pages, but it was still a very limited group.
    • Don’t expect miracles
    • Do thank those wonderful souls who will do this important community work.
  6. Make the value visible. Last year we had the need to review our technical platforms and lo and behold, the wiki was getting more page views that the community’s older, established content management based site. This validated that people were finding and in some way, interested in what we had harvested. I believe this external validation helped motivate and maintain the practice.
    • Share stories of use
    • Make pageview data available
    • If the wiki has been useful beyond the community, get the other users to send a thank you as well.
  7. Reduce barriers and support from the side. Some of us still have to go in and link pages to the index page.
    • We have had to require registration for the wiki due to wiki-spam, which creates some friction and overhead – it is not as easy as I wish it were.
    • The wiki still needs a lot of overall attention to make things easier to find. (That is on my to do list – and has been for a long time. )

All in all, the practice is valued. We are making our knowledge visible and available to the wider world and inviting them to help improve it. There are 76 entries. The entries on knowledge sharing tools and methods have been spread and reused by members’ parent organizations. Value has been amplified. I think it was worth it!

For more on harvesting: