Earlier | Home | Later
Wednesday, February 19, 2003
Ed Krimen shares the insider insight on Macromedia blogs (bold is mine)
Companies like Macromedia don't normally use blogs to communicate with customers.
We had some explaining to do. For example, Blogger co-founder Meg Hourihan, found it a little disturbing at first. She brought up many issues we had considered, and some that we hadn't. Most notably, she points out that we don't even link to the blogs from macromedia.com. Honestly, you may find this surprising, but it's true: our intent was to get the information out to our customers as quickly as we could—that's why we did the blogs in the first place. Everything else was secondary. We really didn't have an elaborate, detailed strategy to these blogs. If we had spent time discussing where the links on our site should be before we got the blogs set up, we would have lost time we needed to spend communicating with you.
Let's see how many others will follow...
what can we do to make blogs stick?
Spike Hall about the need for edublogs critical mass:
Now it's moved to evangelism, to a greater commitment. We're all writing, speaking, selling, thinking, convening. And wondering. The early returns aren't great. As George Siemens says "...it is frustrating to stay in unrealized potentialities too long." Everyone loves the idea, but relatively few have put it into practice. In a response to George, Sebastien Paquet notes that
Sociological change is slow... I'm skeptical that such a big change will take place on a large scale in educational settings before significant pressure is exerted from the outside (i.e. blogging students learn more from blogging than from school, come to class knowing more than their professors, stop going to class...)
And I tend to agree that change is slow. But I don't agree that it will take such drastic measures to bring this mainstream. I think it's incumbent on teachers and professors to bring the technology to students, not vice versa. (And that list of Educator Web loggers is growing, by the way.) It has to come from inside, from us. And since we're the ones who realize the potential, we need to hasten the tipping point by making sure we have at the ready resources and support for the converts we bring into the fold.
I'm working on the BlogTalk paper and I'm targetting the same question: what can we do to make blogs stick? I'm thinking of running a short questionnaire for it, so I'll be back for your help.
How comes that Spike and me are thinking in the same direction so many times? :)))
Lack of project data accessibility study
Intel IT research white paper Information Overload: Inaccessible Data and a Knowledge Management Solution (bold is mine)
Problem: lack of project data accessibility
Date collection: semi-structured interviews (questionnaire is included) with users of project documents at different organisational levels and job functions
Inhibitors of finding documents
- Many document repositories exist. "Different groups used these repositories in different fashions and without a consistent process for depositing documents in any of the repositories".
- Lack of communication about "where the documents were stored and what other document repositories exist".
- Current location of a document is not known.
- "Information was not well archived with proper revision controls, resulting in the original version of the documents often being inaccessible and sometimes nonexistent".
- Documents are mailed around and not posted to a common repository.
- Users rely on finding people involved in the project to find project information. These people could be busy or hard to find.
- Documents could be too long to be useful.
- Waste of paper, disk space and time
- Rework because of (1) changed, but not communicated requirements, or (2) inconsistent interpretation of requirements
- "In general people tended to share information only at its end state, when it was ready for consumption, and not during discovery" -> duplication of efforts
- Searching results in a significant loss of time
- "The difficulty in accessing the right information created a new behaviour trend for some users: They sought out information in meetings"
- "When documents were not easily accessible, users could get only a snapshot of the environment unless they knew whom to ask. To resolve this problem, specific groups or projects established unique processes to address this problem".
- User segmentation is number one priority
- Different user needs regarding depth of the document (management summary vs. data about reasons for a specific decision made before). Two user segments were identified: "technical expertise" and "support and environment".
- "Interviewees rarely had an inclusive picture of the different ways the project documents were used"
- Proposed user segmentation for further investigation: role or job function, prior experience, geographical location.
- Understanding users with the proposed segmentation
- Improving finding documents
- Single repository with revision control and posting process + discipline to follow it
- Adding metadata to documents
- Improving finding information in documents
- Executive summaries
- Using knowledge discovery in databases (=summary extraction)
- Adding unique metadata tag to a specific piece (e.g. project requirement), so it's possible to follow it through different documents
Hmm... It's good as an example, but I wouldn't call it "KM solution" :)
What is more interesting is look how people adapt to the situation: start relying more on meetings or on personal contacts. I guess that document searching behaviour should be studied together with informal communication (see public vs. private discussions), so at the end one can arrive to the solution that combines strenghs of both sides.
Printer-friendly version of blogs?
Does anyone know how to make a printer-friendly version of a (Radio) blog?
I'm printing some of my older posts and I hate loosing so much space with navigation bar. I guess that it's should be possible to make a printer-friendly version of my pages with CSS, but I have no idea how. Any help?
Earlier | Home | Later
© Copyright 2002-2005 Lilia Efimova.
This weblog is my learning diary. Sometimes I write about things related to my work, but the views expressed here are personal and do not necessarily reflect the views of my employer.