Hi,
Great questions.. Here goes:
* Physical access restricted (we use digital cypher locks on the doors
for this)
* We've setup a separate briefing/conference area for leadership
briefings in the event something does occur - it keeps the ops area
sterile
* The website is outsourced, but secured and encrypted (it's on the
internet) - only users with proper authorization can post / edit
information - but commenting will be available.
* Some of our confidential internal stuff will be on our intranet only
* Backup is handled by the vendor, I think that's pretty solid, but I
need to confirm (this was handled by our HQ folks and I wasn't involved
in that project)
* The records will stay at least through the end of our contract - but
we'll be keeping our own communication / internal logs and other
documentation for an After-Action Report & lessons learned.
Thanks for the insights --
Bryan
On Jun 21, 2004, at 10:26 AM, Christina Pikas wrote:
> Bryan -
> This sounds like a great use of k-logs, sorry I can't offer any
> experience. I am wondering, though, how you intend to lock it down
> so only your people can see it. Will it be on an intranet? Will
> users have to log in? Who will have the authority to post to it?
> Comment on it? Are you worried about backing it up if something
> happens? How long will you maintain the records after the event?
> Christina
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
Bryan -
This sounds like a great use of k-logs, sorry I can't offer any
experience. I am wondering, though, how you intend to lock it down
so only your people can see it. Will it be on an intranet? Will
users have to log in? Who will have the authority to post to it?
Comment on it? Are you worried about backing it up if something
happens? How long will you maintain the records after the event?
Christina
I lead the security operation in the Metro Boston area for a large
national retail chain. One event I'm planning for right now is the
Democratic National Convention, which is going to create significant
traffic and business disruptions for our stores - and that's if nothing
happens.
We're going to be standing up a temporary operations center at our
offices outside of Boston in order to monitor the situation and manage
a crisis if there is an event. We're going to be using some knowledge
management tools - notably Mission Mode - http://www.missionmode.com
and am planning on keeping an ongoing diary of our experiences using
Movable Type in a weblog format - this will allow us to share our
experiences in realtime with our counterparts in NYC, who are planning
for the Republican Convention later this year.
The questions that I have for the group are as follows:
1) Any resources or examples of similar situations that you're aware
of? or your own experiences? I certainly don't want to reinvent the
wheel here.
2) Any other knowledge management tools that may be beneficial for us?
Thanks - have been enjoying the conversations here in the group,
Bryan
Dear K-Loggers,
Here is an excellent article by Giles Turnbull for the BBC on weblogs in
education:
http://news.bbc.co.uk/1/hi/magazine/3804773.stm
Selected quotes:
"Children at Hangleton Junior School in Hove, Sussex, have been using weblogs in
their spare time to learn more about things that interest them, but as a result
their performance in class has improved."
"There's a degree of trust involved. They know that if they post anything they
shouldn't, their weblog will be taken away from them."
John set up an after-school club about weblogging at Hangleton, and it has
become so popular that nearly half the school turns up for some sessions.
The school's weblogs project has been so successful that it has just been
shortlisted for a New Statesman New Media Award, an annual event highlighting
the best web development in the UK.
"Rather than using a weblog as a platform for an individual voice, you can use
it for a collaboration of many voices. A class of students doing a project on
the environment might want to start a weblog about their local river; because
it's online, it might attract interest from local residents and policy-makers
too. The local community can be drawn in on something that, without the weblog,
would have been isolated within the school."
Sincerely,
John Robb
[Non-text portions of this message have been removed]
Ross Mayfield wrote:
>We just published a case study that would be of interest to the list as
>a way of articulating value propositions. One of our customers saved a
>month in a four month project and reduced group emails from 100 per day
>to zero.
>http://www.socialtext.com/weblog/040603zeroemail.html
>
>
Obviously a positive move for the customer, but it's not actually clear
from the release what applications were providing the benefit - Wiki +
blogs + RSS? What kind of combination? What kind of client software, or
was it all in-browser?
Cheers,
Danny.
--
Raw
http://dannyayers.com
I am currently working on the preliminary program for a Web
conference "Integrating knowledge into the life science product life
cycle" for the KM in Pharma & Life Science Hub
(http://km.colayer.net/). The perspectives in this discussion are
intended to come from a broad and diverse set of experiences.
I would be interested in obtaining a couple of perspectives that
include the use of blogging, k-logs, wikis, social software tools,
etc. into knowledge integration around product management.
Implementation and associated cultural, business, process, and legal
issues can be within the context of a) large company environments
(e.g., big pharma), b) medium and smaller-sized companies (e.g.,
medium-sized pharma, biotech, medical), and c) communities and groups
of organisations.
Please send me an email or give me a call if you are interested in
discussing further.
regards
Barry Hardy
Barry Hardy
Douglas Connect, Switzerland
www.douglasconnect.com
+41 61 851 0170 (office)
+41 79 755 2340 (mobile)
Email: barry.hardy@...
We just published a case study that would be of interest to the list as
a way of articulating value propositions. One of our customers saved a
month in a four month project and reduced group emails from 100 per day
to zero.
http://www.socialtext.com/weblog/040603zeroemail.html
Ross
On Jun 1, 2004, at 10:41 AM, Jevon wrote:
> Better Project Management
>
> Conversations are the key
> When we have a conference to plan, a system to change, or a topic to
> research, we need to have conversations around what we want to
> accomplish. To do this,
> we need a project management space that is focused on these
> conversations.
>
>
> Project leaders and team members can comment on existing
> conversations, or compose their own messages in the project space, or
> in a sub-project.
> Composing a message is an easier process than sending an email, and
> it is a more reliable
> way to communicate information.
>
> We avoid
>
> The SPAM factor
> Many of the people we send emails to are already drowning in
> email, and they have
> learned to implicitly lower the value of anything they receive over
> email
>
> Destructive forces
> When our conversations are taking place out in the open, we
> eliminate confusion
> about the decision making process. Transparency is key to a healthy
> process, and it
> eliminates any internal conflicts that might find life in
> off-the-cuff conversations.
>
> The demand for attention
> When we aren't emailing, phoning or visiting a co-worker, we
> are giving them the
> freedom to work when they are at peak efficiency, both mentally and
> physically.
>
> More importantly than what we avoid are the things that we can then
> promote. We
> encourage
>
> The experts among us
> By giving a voice to our entire team, we can quickly establish
> the experts and the
> most keen among the group. As more and more work gets done, a
> cohesive team can
> emerge, with different members exhibiting specific strengths that
> benefit this team.
>
> This avoids forcing the project manager to guess who is good at what.
>
> Collective Responsibility
> It becomes the individual's responsibility to stay current,
> and the burden of updating
> the entire team is taken away from the Project Manager. Each person
> involved can enter
> the system at any time and can see everything that is going on.
>
> Creative thought
> Finally, there is a place where creativity can be put to the
> test. A team member can
> post a message with a radical new idea, and the rest of the group can
> weigh in on where
> to go next.
>
>
> We want to concentrate on getting the work done
>
> To do this, we have to shift away from meta-data: the useless things
> that don't move us towards the goal, and we want to shift the
> focus to the conversations
> that we need to have about the project we need to complete. We want
> to set goals for our
> project, these come in two forms
>
> Milestones
> Milestones are date sensitive goals which are assigned to a
> group or an individual.
>
> To-do Lists
> To-do lists are composed of a series of tasks, which will
> complete a goal. The tasks on
> the to-do lists can be assigned to a group or a single person.
>
>
> No more silos
> An open environment is key to working across departments and by
> developing this community of practice around project planning; we are
> opening up a
> new line of thought regarding work-process towards a much more
> efficient and effective
> model. A project team is no longer restricted in who can participate,
> and we
> effectively eliminate the need for many of the meetings that normally
> plague our projects.
>
> We do it right
> The end-user is no longer forced to turn to expensive software in the
> hope of addressing
> these non technical problems. We can use low cost tools that we have
> been using
> extensively ourselves, and we focus our resources on enabling the
> organization to make
> the best use of these ideas as possible. Proper training and
> facilitation is critical to the
> sustained success of any tool -- in the end, the tool is a minor
> factor.
>
> Best,
>
> Jevon MacDonald / Rob Paterson
> http://www.laudably.com
> http://www.socialwrite.com
> http://smartpei.typepad.com
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
Dear K-Loggers,
Here is a nice overview of really simple syndication (RSS) by the online
journalism review. Basically, RSS is starting to become the standard way to
consume news (which should serve as a signal to organizational K-Loggers that
they should distribute RSS aggregators -- either desktop or server software --
as part of their efforts).
At minimum, an RSS aggregator as part of your portal solution is a must-have
(note: you don't have to pay for most of this content, so you can save some
serious money by avoiding the content aggregation companies that charge for this
-- see the list in the article for some news feeds you can use).
http://ojr.org/ojr/technology/1086293132.php
Note the ramp in the growth of files served by the Christian Science Monitor
(see the stories graphic).
The NYTimes, Reuters, the BBC, and most other news organizations have opted to
offer RSS delivery.
It's time to increase the productivity of your organization by making it
possible for them to utilize this new delivery mechanism. BTW, I helped to
negotiate the NYTime's launch of their RSS feeds, which served as the critical
early adopter that drove the rapid growth of this trend.
Sincerely,
John Robb
My sites:
http://jrobb.mindplex.org/http://globalguerrillas.typepad.com/globalguerrillas/http://globalguerrillas.typepad.com/klogs/
Wayne asked whether its standard for blogs (specifically MT) to
support file attachments and inclusion of those in the RSS feed.
You have to consider both the blog software capabilities and the RSS
reader capabilities.
Not sure if Movable Type has this functionality. It will depend on
how they handle attachments in the first place (are they put in a
directory and referred to, or are they attached directly to a post)
and on how they write their RSS feed.
Traction Software (fair disclosure, I work at Traction) does allow
for attachments and inclusion of them. I use Newsgator in my
outlook. Newsgator lets me discriminate based on the feed whether or
not I want to include file enclosures. In some feeds (i.e. my own
intranet blog) I often want to see all attachments without clicking
through. But I dont want to download 1MB+ attachments from other
feeds, it would eat my bandwidth and unnecessarily take storage on
my system (the problem I am trying to get away from).
The key to me, in context of John's discussion about making K-Logs
(or P-Logs or B-Logs or plain old weblogs) work is to provide that
file in context of the situation it was used, rather than on a shelf
somewhere. Whether it was the note about the meeting where the PPT
was presented or if its the product requirement writeup with an
attached timetable or phase review presentation.
Jordan
--- In klogs@yahoogroups.com, "infosential" <wayne@i...> wrote:
> John
> fascinated by the RSS enclosure functionality.
>
> Is this widely available - now? and if so do you know if Movable
> Type has the capability.
>
> many thanks
> Wayne
>
Better Project Management
Conversations are the key
When we have a conference to plan, a system to change, or a topic to
research, we need to have conversations around what we want to
accomplish. To do this,
we need a project management space that is focused on these
conversations.
Project leaders and team members can comment on existing
conversations, or compose their own messages in the project space, or
in a sub-project.
Composing a message is an easier process than sending an email, and
it is a more reliable
way to communicate information.
We avoid
The SPAM factor
Many of the people we send emails to are already drowning in
email, and they have
learned to implicitly lower the value of anything they receive over
email
Destructive forces
When our conversations are taking place out in the open, we
eliminate confusion
about the decision making process. Transparency is key to a healthy
process, and it
eliminates any internal conflicts that might find life in
off-the-cuff conversations.
The demand for attention
When we aren't emailing, phoning or visiting a co-worker, we
are giving them the
freedom to work when they are at peak efficiency, both mentally and
physically.
More importantly than what we avoid are the things that we can then
promote. We
encourage
The experts among us
By giving a voice to our entire team, we can quickly establish
the experts and the
most keen among the group. As more and more work gets done, a
cohesive team can
emerge, with different members exhibiting specific strengths that
benefit this team.
This avoids forcing the project manager to guess who is good at what.
Collective Responsibility
It becomes the individual's responsibility to stay current,
and the burden of updating
the entire team is taken away from the Project Manager. Each person
involved can enter
the system at any time and can see everything that is going on.
Creative thought
Finally, there is a place where creativity can be put to the
test. A team member can
post a message with a radical new idea, and the rest of the group can
weigh in on where
to go next.
We want to concentrate on getting the work done
To do this, we have to shift away from meta-data: the useless things
that don't move us towards the goal, and we want to shift the
focus to the conversations
that we need to have about the project we need to complete. We want
to set goals for our
project, these come in two forms
Milestones
Milestones are date sensitive goals which are assigned to a
group or an individual.
To-do Lists
To-do lists are composed of a series of tasks, which will
complete a goal. The tasks on
the to-do lists can be assigned to a group or a single person.
No more silos
An open environment is key to working across departments and by
developing this community of practice around project planning; we are
opening up a
new line of thought regarding work-process towards a much more
efficient and effective
model. A project team is no longer restricted in who can participate,
and we
effectively eliminate the need for many of the meetings that normally
plague our projects.
We do it right
The end-user is no longer forced to turn to expensive software in the
hope of addressing
these non technical problems. We can use low cost tools that we have
been using
extensively ourselves, and we focus our resources on enabling the
organization to make
the best use of these ideas as possible. Proper training and
facilitation is critical to the
sustained success of any tool -- in the end, the tool is a minor
factor.
Best,
Jevon MacDonald / Rob Paterson
http://www.laudably.comhttp://www.socialwrite.comhttp://smartpei.typepad.com
John
fascinated by the RSS enclosure functionality.
Is this widely available - now? and if so do you know if Movable
Type has the capability.
many thanks
Wayne
--- In klogs@yahoogroups.com, John Robb <jrobb@o...> wrote:
> Dear K-Loggers,
>
> A defining aspect of a K-Log network is that it is an extremely
effective
> one-to-many publishing system. What makes a K-Log network
effective (as opposed
> to communications systems like e-mail, phone, and IM) is its
passivity. What do
> I mean? People aren't forced to read what's published. Readers
only visit or
> subscribe to a K-Log when they have a need to do so or if they
deem what the
> author says is important. This passivity allows readers to batch
process their
> reading and be selective about who they read. This optimization
saves time.
>
> This feature makes K-Logs a great distribution system for files
(like
> multimedia and office documents). Increasingly, employees are
using easy-to-use tools to create
> audio and video files of meetings, events, interviews, and more.
They already
> produce loads of documents that are often quite large.
>
> So, how should people distribute this content? One way is through
e-mail
> attachments. However, this method has two major drawbacks. First,
it bogs down
> e-mail servers. Given that most people keep a significant portion
of their
> e-mail on a server, an e-mail with a 2 Mb attachment sent to 300
other employees
> produces 600 Mb of bloat in the e-mail database. That's not a good
thing and it
> drives sys-admins nuts given the limitations on e-mail databases.
Also, it
> forces people to download it whether they are interested in it or
not. This is
> particularly bad over a slow connection when on the road.
>
> A second way is to just post it to a file folder on a file server.
The problem
> with this is that it strands the file, without sufficient context.
This context
> is necessary. It provides people with a reason to download the
file.
> Additionally, given the status of most files systems I have ever
seen, it will
> likely be lost forever in a jumble of shared files. A third way is
to use
> shared workspaces (collaboration tools). Unfortunately, while
these systems may
> provide a small modicum of improvement in delivering crucial
contextual data,
> they share the same limitations of communications tools like e-
mail: they work
> best within the context of small groups and not very well in a one-
many
> environment.
>
> In my view, the best way to distribute a large file is to publish
it via a K-Log
> to the Intranet. Here's why:
>
> 1) Sharing. Using this method people reading a K-Log can find out
how file
> relates to the author's worklife; before they download it. For
example, "Here
> is a video of a example sales presentation for product xxx," or "I
just revised
> my marketing presentation for product yyy. It includes some new
graphs on
> performance of the system that the product team thinks are
necessary to explain
> to customers." This relevant information saves time, effort, and
limits
> confusion. It makes effective sharing possible.
>
> 2) Trust: K-Logs introduce a large measure of trust into the act
of
> distributing files. The file is attached to an identifiable person
within the
> organization. Additionally, there is little threat of virus laden
files on a
> K-Log relative to e-mail. The very nature of K-Logs contains virus
propagation.
>
> 3) Archives. With K-Logs, Intranet's become an archive of what
goes on within a
> company. In regards to file storage, K-Logs provide the archival
data
> necessary to understanding why the was created, when it was
created, why it
> should be used, where it should be used, and much more. Intranet
search
> functionality is also improved because the value of the file is
enhanced by the
> number of K-Logs pointing to it (particularly when Google's
appliance is used).
>
> 4) Economics. Since only the people that want to download the file
download it.
> Additionally, forwarding large files within a K-Log context
becomes a snap.
> All I need to do to forward a file is to either post a link to my
K-Log for my
> readers to use or send the link via e-mail directly to people that
could benefit
> from it. Very simple and lightweight. There is very little wasted
bandwidth,
> storage, or server utilization.
>
> Another aspect of a K-Log network that is starting to gain
traction is distributing
> files as part of an RSS subscription (Disney is using this
technique to distribute
> large files to 2 m users). K-Logs automatically publish
syndicatable
> content in the form of RSS (a standard syndication format). That
means if I am
> using an RSS aggregator tool on my desktop, I can subscribe to the
K-Logs I find
> interesting and get all the new posts automatically without having
to visit the
> sites. Further, all of these subscriptions are aggregated on a
single "news"
> page for easy scanning. Most people use this functionality to keep
track of an
> order of magnitude more sites than they can through simple
bookmark-enabled
> browsing.
>
> What isn't well known is that it is possible to include a large
file as an
> enclosure with an RSS feed. That means that subscribers can
automatically get
> all files I publish, delivered to their desktop, without having to
go through
> the process of active downloading. Enclosure downloading can also
be time
> shifted to occur only during the wee hours of the night to prevent
congestion
> problems (this can be done by simply typing in the time you want
things to be
> downloaded). This also means that when a reader clicks on a large
file that has
> been distributed as an enclosure, it launches immediately. There
isn't any
> world-wide-wait.
>
> There has also been some good work integrating P2P (a clean
corporate version of Napster
> and KaZaA) into RSS enclosure distribution. This would make
distribution even
> less expensive to do.
>
> In conclusion, if you are a company that deals with lots of
multimedia files and
> multiple revisions of documents, K-Logs should be a simple
solution to many of
> your woes.
>
> Sincerely,
>
> John Robb
>
> http://jrobb.userland.com
>
>
>
> [Non-text portions of this message have been removed]
Bren wrote: Next, for small departments, one K-Log per person seems
like overkill, especially considering my hunch that most folks won't
participate initially (envision a ghost town of empty K-Logs). Do
you see any downside to a single K-Log, with categories and sub-
categories that an entire (small) department had author rights to?
Once the early adopters got it wired, they'd want to control their
own K-Logs and new ones could be carved off for them.
--> Good point, at least based on my experience with implementation.
I rarely see a good implementation of a personal k-log in a work
environment. Its better done minimally as a community of practice or
maximally in a way that simply fits the work process of the
individual(s) doing the posts. The small department approach is not
spot-on either as typically the group unit of focus is a natural
group or cross-functional group that spans departments.
Jordan Frank
www.tractionsoftware.com
Timely post, John. I've just been pitching the idea at work (a small
private university). My pitch hit most of what you note, and my biggest
concern by far is whether it will be friendly enough software for the
majority of our users, who are relatively unsophisticated computer users.
If the tool isn't friendly and *really* easy to learn, most of our folks
won't bother with it and they'll stick to traditional channels of
information exchange: email, informal desk huddles, etc. (This is
experience speaking--I rolled out a wiki about a year and a half ago, and
I've been the main contributor. Most folks timidly make a post in the
SandBox, then forget about it--until they want something, then they go
search the wiki.) :-)
Your point #1 seems a little glossed over to me. From watching our users,
the process is more like: 1) find the link to that new software thingy -> 2)
remember my logon info and type it in -> 3) navigate to the part where I can
type my stuff in -> 4) what was I thinking about, again? Type it in -> 5)
hit post to weblog.
Next, RSS isn't on most folk's radar. I watch around 50 feeds, but I don't
personally know anyone else who does the web this way. Shooting the feed to
Outlook is a good solution, but there's definitely a learning curve involved
in yet another piece of software. I guess we'll just have to wait for RSS
to *really* go mainstream and evangelize like crazy in the meantime.
Next, for small departments, one K-Log per person seems like overkill,
especially considering my hunch that most folks won't participate initially
(envision a ghost town of empty K-Logs). Do you see any downside to a
single K-Log, with categories and sub-categories that an entire (small)
department had author rights to? Once the early adopters got it wired,
they'd want to control their own K-Logs and new ones could be carved off for
them.
--Bren
> Date: Wed, 26 May 2004 04:38:20 -0700 (PDT)
> From: John Robb <jrobb@...>
> Subject: Will people use K-logs?
>
> Dear K-Loggers,
>
> The biggest hurdle that faces any knowledge management tool
> is: will people use it? The key to surmounting this hurdle is
> threefold:
>
> 1) The tool must be EASY to use.
>
> 2) The tool must deliver visible benefits immediately.
>
> 3) The tool must gain value as more people use it (network effects).
>
> A quick review of most existing knowledge management tools
> fails all three counts. They are often bewilderingly complex
> (Lotus), the benefits are difficult to measure (particularly
> from the perspecitive of an individual user), and the tool's
> value is the virtually the same regardless of the number of
> people using it.
>
> In contrast K-Logs measure up well. Here's how:
>
> 1) The tool is easy to use: a) write something > b) hit post
> to Weblog That is all it takes to contribute.
>
> 2) The tool provides quickly visible benefits: a) I create a
> K-Log > b) Iinform my co-workers > c) my co-workers can
> quickly and easily keep up to date on what I am doing
> (thinking) by reading my K-Log.
>
> 3) The tool provides network effects: a) the more people with
> K-Logs the greater the number of knowledge streams I can
> subscribe to (RSS), b) the greater the number of K-Logs the
> greater the searchable number of Web pages on the Intranet,
> and c) the more K-Logs the better the knowledge network cloud
> works (hotlists, most recent updates, etc.).
>
> Sincerely,
>
> John Robb
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
> ______________________________________________________________
> __________
> ______________________________________________________________
> __________
>
>
>
> --------------------------------------------------------------
> ----------
> Yahoo! Groups Links
>
>
>
>
> --------------------------------------------------------------
> ----------
>
>
>
>
>I guess there exist Blogs which have video and audio content ....!
>
>
David Davies has a tool for Radio Userland that allows embedding of MMS
video. I believe that MMS from mobile phones can be sound too.
>That would be a quantum jump in knowledge sharing
>
>
Why do you say that? Surely there would be a need for speech to text so
posts would be searchable. And it would be kinda hard to speed read
video. Writing descriptions of the video or sound file would be a royal PIA
Sure, I understand the value of video in training. And sure video from
phone to blog is a painless two or three click process, cutting out the
video team, editing, conversion etc etc.
John:
Shouldn't this discussion include something about business value, i.e.,
ability to easier/better tie the content in a K-Log to a company's business
priorities? It seems that content is a variable in usage.
Marv
-----Original Message-----
From: John Robb [mailto:jrobb@...]
Sent: Wednesday, May 26, 2004 7:38 AM
To: klogs@yahoogroups.com
Subject: [K-Logs] Will people use K-logs?
Dear K-Loggers,
The biggest hurdle that faces any knowledge management tool is: will people
use it? The key to surmounting this hurdle is threefold:
1) The tool must be EASY to use.
2) The tool must deliver visible benefits immediately.
3) The tool must gain value as more people use it (network effects).
A quick review of most existing knowledge management tools fails all three
counts. They are often bewilderingly complex (Lotus), the benefits are
difficult to measure (particularly from the perspecitive of an individual
user), and the tool's value is the virtually the same regardless of the
number of people using it.
In contrast K-Logs measure up well. Here's how:
1) The tool is easy to use: a) write something > b) hit post to Weblog That
is all it takes to contribute.
2) The tool provides quickly visible benefits: a) I create a K-Log > b)
Iinform my co-workers > c) my co-workers can quickly and easily keep up to
date on what I am doing (thinking) by reading my K-Log.
3) The tool provides network effects: a) the more people with K-Logs the
greater the number of knowledge streams I can subscribe to (RSS), b) the
greater the number of K-Logs the greater the searchable number of Web pages
on the Intranet, and c) the more K-Logs the better the knowledge network
cloud works (hotlists, most recent updates, etc.).
Sincerely,
John Robb
[Non-text portions of this message have been removed]
Yahoo! Groups Sponsor
ADVERTISEMENT
<http://rd.yahoo.com/SIG=1297u4o72/M=295196.4901138.6071305.3001176/D=groups
/S=1707281914:HM/EXP=1085658056/A=2128215/R=0/SIG=10se96mf6/*http://companio
n.yahoo.com> click here
<http://us.adserver.yahoo.com/l?M=295196.4901138.6071305.3001176/D=groups/S=
:HM/A=2128215/rand=576547096>
_____
Yahoo! Groups Links
* To visit your group on the web, go to:
http://groups.yahoo.com/group/klogs/ <http://groups.yahoo.com/group/klogs/>
* To unsubscribe from this group, send an email to:
klogs-unsubscribe@yahoogroups.com
<mailto:klogs-unsubscribe@yahoogroups.com?subject=Unsubscribe>
* Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .
[Non-text portions of this message have been removed]
Hi John
Interesting points. I'd also love to see the time when one can
verbally "talk" into a Blog !
I guess there exist Blogs which have video and audio content ....!
That would be a quantum jump in knowledge sharing
regards,
Gautam
http://gauteg.blogspot.com
On Wed, 26 May 2004 04:38:20 -0700 (PDT), John Robb <jrobb@...> wrote:
>
> In contrast K-Logs measure up well. Here's how:
>
> 1) The tool is easy to use: a) write something > b) hit post to Weblog That is
all it takes to contribute.
>
> 2) The tool provides quickly visible benefits: a) I create a K-Log > b)
Iinform my co-workers > c) my co-workers can quickly and easily keep up to date
on what I am doing (thinking) by reading my K-Log.
>
Dear K-Loggers,
The biggest hurdle that faces any knowledge management tool is: will people use
it? The key to surmounting this hurdle is threefold:
1) The tool must be EASY to use.
2) The tool must deliver visible benefits immediately.
3) The tool must gain value as more people use it (network effects).
A quick review of most existing knowledge management tools fails all three
counts. They are often bewilderingly complex (Lotus), the benefits are difficult
to measure (particularly from the perspecitive of an individual user), and the
tool's value is the virtually the same regardless of the number of people using
it.
In contrast K-Logs measure up well. Here's how:
1) The tool is easy to use: a) write something > b) hit post to Weblog That is
all it takes to contribute.
2) The tool provides quickly visible benefits: a) I create a K-Log > b) Iinform
my co-workers > c) my co-workers can quickly and easily keep up to date on what
I am doing (thinking) by reading my K-Log.
3) The tool provides network effects: a) the more people with K-Logs the greater
the number of knowledge streams I can subscribe to (RSS), b) the greater the
number of K-Logs the greater the searchable number of Web pages on the Intranet,
and c) the more K-Logs the better the knowledge network cloud works (hotlists,
most recent updates, etc.).
Sincerely,
John Robb
[Non-text portions of this message have been removed]
Dear K-Loggers,
A defining aspect of a K-Log network is that it is an extremely effective
one-to-many publishing system. What makes a K-Log network effective (as opposed
to communications systems like e-mail, phone, and IM) is its passivity. What do
I mean? People aren't forced to read what's published. Readers only visit or
subscribe to a K-Log when they have a need to do so or if they deem what the
author says is important. This passivity allows readers to batch process their
reading and be selective about who they read. This optimization saves time.
This feature makes K-Logs a great distribution system for files (like
multimedia and office documents). Increasingly, employees are using easy-to-use
tools to create
audio and video files of meetings, events, interviews, and more. They already
produce loads of documents that are often quite large.
So, how should people distribute this content? One way is through e-mail
attachments. However, this method has two major drawbacks. First, it bogs down
e-mail servers. Given that most people keep a significant portion of their
e-mail on a server, an e-mail with a 2 Mb attachment sent to 300 other employees
produces 600 Mb of bloat in the e-mail database. That's not a good thing and it
drives sys-admins nuts given the limitations on e-mail databases. Also, it
forces people to download it whether they are interested in it or not. This is
particularly bad over a slow connection when on the road.
A second way is to just post it to a file folder on a file server. The problem
with this is that it strands the file, without sufficient context. This context
is necessary. It provides people with a reason to download the file.
Additionally, given the status of most files systems I have ever seen, it will
likely be lost forever in a jumble of shared files. A third way is to use
shared workspaces (collaboration tools). Unfortunately, while these systems may
provide a small modicum of improvement in delivering crucial contextual data,
they share the same limitations of communications tools like e-mail: they work
best within the context of small groups and not very well in a one-many
environment.
In my view, the best way to distribute a large file is to publish it via a K-Log
to the Intranet. Here's why:
1) Sharing. Using this method people reading a K-Log can find out how file
relates to the author's worklife; before they download it. For example, "Here
is a video of a example sales presentation for product xxx," or "I just revised
my marketing presentation for product yyy. It includes some new graphs on
performance of the system that the product team thinks are necessary to explain
to customers." This relevant information saves time, effort, and limits
confusion. It makes effective sharing possible.
2) Trust: K-Logs introduce a large measure of trust into the act of
distributing files. The file is attached to an identifiable person within the
organization. Additionally, there is little threat of virus laden files on a
K-Log relative to e-mail. The very nature of K-Logs contains virus propagation.
3) Archives. With K-Logs, Intranet's become an archive of what goes on within a
company. In regards to file storage, K-Logs provide the archival data
necessary to understanding why the was created, when it was created, why it
should be used, where it should be used, and much more. Intranet search
functionality is also improved because the value of the file is enhanced by the
number of K-Logs pointing to it (particularly when Google's appliance is used).
4) Economics. Since only the people that want to download the file download it.
Additionally, forwarding large files within a K-Log context becomes a snap.
All I need to do to forward a file is to either post a link to my K-Log for my
readers to use or send the link via e-mail directly to people that could benefit
from it. Very simple and lightweight. There is very little wasted bandwidth,
storage, or server utilization.
Another aspect of a K-Log network that is starting to gain traction is
distributing
files as part of an RSS subscription (Disney is using this technique to
distribute
large files to 2 m users). K-Logs automatically publish syndicatable
content in the form of RSS (a standard syndication format). That means if I am
using an RSS aggregator tool on my desktop, I can subscribe to the K-Logs I find
interesting and get all the new posts automatically without having to visit the
sites. Further, all of these subscriptions are aggregated on a single "news"
page for easy scanning. Most people use this functionality to keep track of an
order of magnitude more sites than they can through simple bookmark-enabled
browsing.
What isn't well known is that it is possible to include a large file as an
enclosure with an RSS feed. That means that subscribers can automatically get
all files I publish, delivered to their desktop, without having to go through
the process of active downloading. Enclosure downloading can also be time
shifted to occur only during the wee hours of the night to prevent congestion
problems (this can be done by simply typing in the time you want things to be
downloaded). This also means that when a reader clicks on a large file that has
been distributed as an enclosure, it launches immediately. There isn't any
world-wide-wait.
There has also been some good work integrating P2P (a clean corporate version of
Napster
and KaZaA) into RSS enclosure distribution. This would make distribution even
less expensive to do.
In conclusion, if you are a company that deals with lots of multimedia files and
multiple revisions of documents, K-Logs should be a simple solution to many of
your woes.
Sincerely,
John Robb
http://jrobb.userland.com
[Non-text portions of this message have been removed]
Dear K-Loggers,
Bill Gates provides an easy to understand explanation of the power of weblogs
and RSS (notification) that may be useful as a way to explain it to your CEO...
_____________
"This (weblogs and RSS) is a very interesting thing, because whenever you want
to send e-mail you always have to sit there and think who do I copy on this.
There might be people who might be interested in it or might feel like if it
gets forwarded to them they'll wonder why I didn't put their name on it. But,
then again, I don't want to interrupt them or make them think this is some
deeply profound thing that I'm saying, but they might want to know. And so, you
have a tough time deciding how broadly to send it out.
Then again, if you just put information on a Web site, then people don't know to
come visit that Web site, and it's very painful to keep visiting somebody's Web
site and it never changes. It's very typical that a lot of the Web sites you go
to that are personal in nature just eventually go completely stale and you waste
time looking at it.
And so, what blogging and these notifications are about is that you make it very
easy to write something that you can think of, like an e-mail, but it goes up
onto a Web site. And then people who care about that get a little notification.
And so, for example, if you care about dozens of people whenever they write
about a certain topic, you can have that notification come into your Inbox and
it will be in a different folder and so only when you're interested in browsing
about that topic do you go in and follow those, and it doesn't interfere with
your normal Inbox.
And so if I do a trip report, say, and put that in a blog format, then all the
employees at Microsoft who really want to look at that and who have keywords
that connect to it or even people outside, they can find the information.
And so, getting away from the drawbacks of e-mail -- that it's too imposing --
and yet the drawbacks of the Web site -- that you don't know if there's
something new and interesting there -- this is about solving that.
The ultimate idea is that you should get the information you want when you want
it, and we're progressively getting better and better at that by watching your
behavior, ranking things in different ways."
___________
Sincerely,
John Robb
[Non-text portions of this message have been removed]
Dear K-Loggers,
We are making progress! Today, at Microsoft's annual CEO summit, Bill Gates
extolled the benefits of "bottoms-up" change with weblogs and RSS as prime
examples of how to make this happen. Nice! The time is ripe to push
weblogs/RSS (and all the ways in which we have explored on how to use them in
this forum) in your organization.
___________________
More goodness from Microsoft: Microsoft's Windows evangelist, Robert Scoble,
who used to work for me (he's the kind of person every organization needs),
recently was intreviewed on the value of weblogs/RSS:
___
One of the most popular bloggers out there is Microsoft's Robert Scoble, who
uses his own personal Web log to get Microsoft partners excited about his
company's technology. Thousands of Web sites and other blogs link to Scoble's
popular blog, and he is regularly read and interviewed by business and
technology magazines like EWeek, Microsoft Watch, and Fast Company. We asked him
five quick questions about this new phenomenon known as blogging, and how to use
it to spread the word about your products.
What is a blog, and how can it help companies promote products?
Scoble: Blogs are frequently updated personal Web journals than can dramatically
help both small and large companies communicate their product messages. They
increase people's ability to share ideas and information exponentially, and on a
worldwide scale.
What are the practical advantages of a blog from the customers' point of view?
Scoble: It makes it so much easier to get the information you're looking for
from the Internet. You don't have to waste time going to the sites that interest
you every day. You just sign up for an RSS (Really Simple Syndication) feed
using a news aggregator like NewsGator, SharpReader, or RSS Bandit, and you get
notified when something has been updated. I myself keep track of 1,400 different
sites a day in this way. This would be impossible in a Web browser, but blog
readers only need to read sites that have posted something in the last 24 hours.
Usually only 20 percent of sites publish anything in any one 24 hour
period—that makes an RSS reader many times more productive.
Plus, I don't have to use mental energy figuring out what's new. I receive an
XML file, which looks like an e-mail, and the new information is bold and with
no colored fonts to distract me. There are other advantages as well: Customers
get information that would not have gotten posted otherwise, and they also get
to ask questions of the author and have a conversation—build a relationship
with the author.
Why is blogging becoming so popular?
Scoble: What's really going on is a shift in how people relate to corporate
communications. Twenty years ago, the only way you could get product information
was from the PR departments. Even articles in newspapers were based on press
releases. Today people are getting their information from individuals within the
companies. People don't trust companies, even companies they like. I mean, who
would you rather get product information from, an individual from within the
company, an engineer perhaps, or the company's PR department? Ernst and Young
has done a study that showed that 70 percent of car sales are generated by word
of mouth. Blogs bring the power of word of mouth to the Web.
What are the dangers of blogging from the company's point of view?
Scoble: In order for the blog to be effective, the blogger has to have some
freedom. A blogger can't lose credibility with readers. If they sense that
you're phony, they're gonna leave. At the same time, you want to get the right
message out. I think of about five people every time I post to my blog.
Obviously, I think about my readers. They have to be at the center. But I also
think about my co-workers because I know that they're going to give me heck if I
don't talk about something I should, like when Longhorn [the code name for the
version of Microsoft Windows® currently in development] ships. And then,
there's my boss and Microsoft executives. I ask myself whether I'm taking
Microsoft strategy into account. Finally, I think about my wife, and what I'm
going to tell her if I get fired. Writing a blog always has to be a balance.
You're representing your company, but you have a responsibility toward your
readers.
What makes a blog work from a company's point of view?
Scoble: An effective blog is one that shares information and listens. The
[United States] presidential candidates have blogs, but they read as if they
were written by a committee, which they probably were. It has to come from an
individual, and it has to be genuine. If people come to realize that your blog
comes from a real person who has something valuable to say, then you'll get your
product message out. But, you also have to be credible. That means linking to
other people's opinions, even if they're negative about your company and
products. When customers realize that you're listening, the shrillness in their
tone goes down. Besides my primary audience of partners, Microsoft executives
and employees also read my blog, and they often interact. For example, the MSN
Spotwatch team reported a bug they read about on my blog one morning, and by
evening they had a fix.
___________________
This is great news for all of us. Let me know if you need any help getting
K-Logs going in your organization.
Sincerely,
John Robb
[Non-text portions of this message have been removed]
Hi, I´m a student in communication and I´m working about this
subject, the k-logs. I´d like to know if, for example, the Google
Blog [www.google.com/googleblog/] it coulb be considered like a K-
log, or the term "k-log" it refers only to the blogs used like
intranets? A K-Log is a "corporate weblog" or just a "blog used
within a company (intranet)?
I will be grateful for any comment.
Thanks,
JM Noguera (http://laazotea.blogspot.com)
John Robb wrote:
> Real-time information flow through the use of a
> search engine (ie. Google appliances) and prompted
> indexing (through weblog pings to the search
> engine when new posts are published).
If it is really "real-time information flow" that you need,
search engines aren't what you're looking for. This is because search
engines implement what can be called "retrospective search" (i.e. they
search data collected in the past) and they must be polled or
re-queried regularly in order to get results. At best, the latency for
delivery of any new information is a function of the indexing time and
the polling frequency... Even when pinging is used to encourage rapid
discovery of new data, you'll find that getting new data indexed will
cause unacceptable delays in disemminating time-sensitive data. This
is because most search engines do their indexing in "batch". (note:
Some, like Gigablast, do dynamic indexing, however, that isn't
common.)
To provide "real-time information flow" what you need is the
capability to do "prospective search" which utilizes a matching
engine, not a searching engine. A prospective search works more like a
filter or publish/subscribe system in that it continuously compares
persistent queries against a stream of information and can then push
results to a client. In such systems, there is no delay caused by
either indexing or by polling frequency.
bob wyman
http://pubsub.comhttp://bobwyman.pubsub.com/
Should an International org implement a gradual approach on KM or a
full force approach. The full force implementation means that the org.
is planning to purchase a high-end content management system with the
ability to accomodate KM. The idea to implementing a full force
approach was because another branch office (one office) in the world
had tested KM and apparently 'it works'. I realise that learning
culture plays an important role prior to adopting technology into KM,
and this can be supported by many articles.
I have no experience in implementing real life KM but I have been
studying KM for quite sometime and no, I do not get paid for this :)
It is just a query from someone who is implementing KM to their
worldwide offices and he was telling me of this idea. My query is,
what will the consequences be if an organisation adopt the full force
approach, which in my point of view, it is similar as applying a
top-down or 'push' approach - well it is not wrong. If I had the
ability to say something, I would say, 'No'. Is that correct?
Please advise. Thanks in advance.
Azlan
Cardiff
Dear K-Loggers,
As some of you may know, I have been working on national security issues for a
while (with a particular emphasis on networks and social technology). I wrote
an article today on building a national intelligence network that may be of
interest to you since it involves using K-Logs -- many of the same problems we
face building a nation intelligence network are very similar to those faced by
large companies and organizations.
Here it is:
Non-state terrorist networks enjoy many advantages over the traditional
hierarchies of nation-states. They learn, share, innovate, and survive
disruption better than hierarchies. This strongly implies that best way to
defeat these terrorist networks is to adopt a network architecture ourselves.
The best approach to begin this process of transformation is to establish a
nation-wide intelligence network. The advantages of a national intelligence
network are real. For example: almost all of the information needed to identify
and stop 9/11, the DC sniper, and the first World Trade Center attack was
present in the nation's intelligence/information system prior to the occurance
of the events. It was the current network's flaws: stove piping, one-way
flows, gaps, over centralization, security restrictions, interfaces, and
multiple technologies that prevented the timely use of this information. To
prevent future attacks, the Markle Foundation has prepared a 2003 report,
"Creating a Trusted Network for Homeland Security" that recommends building a
dynamic and decentralized national intelligence network.
See: http://www.markletaskforce.org/Report2_Full_Report.pdf (PDF)
Their proposed national intelligence network (dubbed SHARE -- Systemwide
Homeland Analysis and Resource Exchange) includes the following:
A decentralized architecture.
Real-time information flow.
Two-way publishing.
Ad hoc connections/information flow.
Scalable systems (to hundreds of thousands of participants -- 14 federal
intelligence agencies, state and local law enforcement, hospitals, fire
departments, and private industry).
Easily filterable.
Provides multiple nodes of analysis.
Many-node information sharing (within limits of security access level).
Easy directory development.
Open architecture (XML).
Able to handle multiple data types (docs, spreadsheets, multimedia, etc.).
What's needed: A national Weblog/Wiki network
These requirements beg the question: what system would enable all of this
functionality? The simple and powerful answer is (it is the only system I know
of that can accomplish this): a weblog/wiki network with fast search services
(along the lines of what we have been talking about on K-logs for the last three
years). A network of this type will:
A decentralized architecture for publishing and consuming information (via
Really Simple Syndication -- RSS).
Real-time information flow through the use of a search engine (ie. Google
appliances) and prompted indexing (through weblog pings to the search engine
when new posts are published).
Ad hoc connections and information flow through RSS subscriptions (an RSS
aggregator ala Bloglines, NewsGator, Radio, or Technorati).
Scalable systems -- already demonstrated via the millions of weblogs on the Web
today.
Easily filterable through Intranet search and through applications built on an
expanded Google API (see: http://www.google.com/apis/ ).
Provides multiple nodes of analysis (filtering and independent analysis) through
analyst weblogs. The operation of the weblog world demonstrates this everyday.
Provides many node information sharing through easy to use Web interface
standards (which implies zero training for users).
Easy directory development through a Wiki (see the Wikipedia
http://en.wikipedia.org/wiki/Wiki for an example) and OPML (Outline Processor
Markup Language -- based on XML -- see: http://www.opml.org/ )
Open architecture using XML. Weblogs use XML. Both RSS and OPML are XML based.
Able to handle multiple data types. Weblogs allow the publishing and the
reciept (automated if necessary through RSS enclosures) of multiple data types.
Also, search engines like Google allow these data types to be easily searched
once published.
Let's get moving!
A national intelligence system of this type can scale to a global level, linking
up open societies everywhere there is an Internet connection. The only
requirement necessary to start this is the decision to start -- the expense
would be negligible (tens of millions), training would be almost unnecessary
(Web standards are used -- almost everyone knows how to type an e-mail or search
using Google), and time needed to impliment short (less than a year from the
word go to launch of the basic system). If you would like to discuss this,
please contact me directly.
Sincerely,
John Robb
http://globalguerrillas.typepad.com
[Non-text portions of this message have been removed]
Perhaps there's an additional perspective from which weblogs could be
viewed, that of weblog tools as personal content management systems. When
thought about in this way the weblog becomes more than just a place to write
stuff. The tool can link the weblogger and his/her audience to interesting
data sources in a more personalized way than through generic access points.
Portalized you might say (would Paul Browning care to comment?). For
example, virtual learning environments. For me engaging with a VLE is as
much about managing the data as well as managing the process, particularly
from the teacher perspective though increasingly so from the student's
perspective. I have data kept in many different formats in many different
systems, some of which I use for personal development, research, some for
teaching, admin, and often the boundaries and unclear. Just as we're now
familiar with weblog aggregators assembling functional units of other
people's weblog posts, then so we might think of the more advanced
weblogging tools as being able to aggregate & assemble and disaggregate &
reassemble other forms of data. For me the weblogging revolution is just the
tip of the personal content management revolution iceberg.
Cheers,
David.
Dear K-loggers,
Here is an old post on e-portfolios that you may have missed:
http://groups.yahoo.com/group/klogs/message/333
Relevant sections of the post:
A new and exciting area of development that I have been talking to educators
about is the student managed electronic portfolio. This is a website that
documents everything a student accomplished while at school in electronic form.
These portfolios include original writing, links to resources, documents (Word,
Excel, and PowerPoint), pictures, audio files, and video files. It seems to me
that this is a perfect application of K-Logs in education. Here's why:
1) The construction of an electronic portfolio is a structured program. This
makes it very easy to identify what material needs to be posted and when it
should be posted. This eliminates the writer's block that impedes the
development of some educational K-Log efforts.
2) A K-Log's built-in time organization makes it easy to develop and maintain a
portfolio over an entire academic career. This would allow students and teachers
(or parents and teachers in conference) to review progression over a month,
semester, or year.
3) K-Logging tools support point and click posting of pictures, documents,
audio, and video files. Further, students can assign real world names to these
files to allow them to quickly re-publish them at a later date if warranted (for
example: all you need to do to include a photo in a weblog is type the name of
picture in double quotes and hit "publish." The picture would auto-magically
appear formatted in the post.)
4) K-Logging tools make it easy to move a site from one location to another.
For example, a copy of a 7-8th grade portfolio can easily be moved to the high
school's Manila server to allow the student (and readers) continuity.
5) A portfolio published as a K-Log is automatically syndicated as a newsfeed.
This makes it easy for a parent to subscribe to their children's portfolio with
their newsreader of choice (like Radio). So, in this case I could get news
headlines from the NYTimes along with updates on what my kids have been doing at
school. Nice.
Personally, I think its great that schools are starting to do this. The early
establishment of the habit of documenting work online is going to be something
that will pay dividends throughout life. This is an important step on the road
to a knowledge sharing culture.
Sincerely,
John Robb
[Non-text portions of this message have been removed]
--On 25 April 2004 23:02 -0400 "M. Sean Fosmire" <msf@...> wrote:
> Another would be areas-of-practice weblogs - logs devoted to a
> particular topic and area of interest for both lawyer and client.
There's also the ePortfolio angle: a reflective record
of educational progress maintained by the student and
annotated by the tutor.
Another example of a blog just for two people, perhaps?
Paul
--
The Library, Tyndall Avenue, Univ. of Bristol, Bristol, BS8 1TJ, UK
E-mail: paul.browning@... URL: http://www.bris.ac.uk/
We're working on a weblog approach to the provision of a current
awareness service for primary care health professionals. Should be up
and running soon. We're using it as a way of extending the reach of a
quite traditional service (current awareness). We're also hoping that
librarians throughout the NHS will work together to create a combined
service - at the moment there are several primary care current awareness
services, and a singleservice would be more effective and efficient.
Cheers
Ben Toth
---------------------------------------------------
Dr Ben Toth
Head of Knowledge Management
NHS Information Authority
Aqueous II
Birmingham
B6 5RQ
07775 993168
---------------------------------------------------
-----Original Message-----
From: M. Sean Fosmire [mailto:msf@...]
Sent: 26 April 2004 04:02
To: John Robb
Subject: Re: [K-Logs] Categorizing organizational weblogs
Another would be areas-of-practice weblogs - logs devoted to a
particular topic and area of interest for both lawyer and client.
====================================
M. Sean Fosmire msf@...
Garan Lucow Miller, P.C.
Marquette, Michigan
====================================
--Original message--
> Dear K-loggers,
> There has been significant progress in the application of weblogs
> to corporate/organizational networks since this group was founded.
> It's clear that people are starting to understand that weblogs can
> be used to filter and flow information that benefits organizational
> productivity.
> Here is how I would categorizing them:
> 1) General news weblogs. News from general news sources that are
> applicable to internal audiences. With or without editorial comment
> by the author. These may be automated (via search terms -- it is
> possible to build a RSS news feed from Google News and republish it
> as a weblog).
> 2) Organization specific news weblogs. Internal initiatives (HR,
> Sales, etc.). Press releases. Competitor information. Product
> updates. etc.
> 3) Joblogs. Weblogs that detail what an employee/member has
> accomplished during the day. This is an easy way to start
> weblogging in an organization. It can be used to keep track of
> consultants, geographically dispersed employees, work at home
> employees, etc. If you have people like that in your organization
> that you manage and your aren't using a weblog to track their
> progress, you are missing out.
> 4) Projectlogs. This is a varient on the Joblog but is authored
> by multiple project team participants. It is a great way to track a
> project's progress. It allows people that are infrequently attached
> to a project to keep tabs on progress. It can be used to spool a
> new team member up to speed quickly. It is also a great archive to
> project documents/files (with context as to why they are important).
> 5) Research weblogs. This is a more formal use of weblogs to
> publish research. It allows the analyst to publish finished
> work-product and supporting documents/sources. It allows the
> analyst to interact with the readers in a way that improves the
> quality of the research. This is a good way to publish original
> content.
> There are probably lots more, let me know the types of weblogs
> you are running that don't fall into these categories.
> Research Weblogs
> I have spent lots of time building research weblogs (for a
> research company I ran) since 1997 (although they weren't called
> weblogs at that time -- my effort was to chunk content and organize
> it in channels in a reverse chronology). Most recently, I have
> begun to publish a research weblog and have found what I think is a
> good format. The site is focused on the next generation of
> terrorism (tough topic, but I have some experience in these areas
> that I think can help):
> http://globalguerrillas.typepad.com
> The format is derived from a combination of my personal writing
> style and that of Forrester Research (I was the senior Internet
> analyst there). It is a combination of posted research "briefs"
> which are moderate length analytical content. These briefs are
> designed for scanning with multiple bullets for major points (most
> people scan the Web rather than read). Here are some examples:
> Destabilizing Terrorist Networks:
>
http://globalguerrillas.typepad.com/globalguerrillas/2004/03/destabilizi
ng_t.html
> Mapping Terrorist Networks:
>
http://globalguerrillas.typepad.com/globalguerrillas/2004/04/mapping_ter
rori.html
> The other post is a "journal" entry. This looks like a standard
> weblog post in that it usually has a few links and contains only a
> single idea. Here are some examples:
> Flight delays (power outages at LAX due to birds):
>
http://globalguerrillas.typepad.com/globalguerrillas/2004/04/journal_fli
ght_.html
> Attacks on Systems? (looks at the recent terrorist attack on Iraqi oil
systems):
>
http://globalguerrillas.typepad.com/globalguerrillas/2004/04/journal_is_
this.html
> I will be working on new ways to present research on a weblog. More
soon. Hope this helps.
> Sincerely,
> John Robb
> [Non-text portions of this message have been removed]
> Yahoo! Groups Links
Yahoo! Groups Links
This e-mail is confidential and privileged. If you are not the intended
recipient please accept our apologies; please do not disclose, copy or
distribute information in this e-mail or take any action in reliance on its
contents: to do so is strictly prohibited and may be unlawful. Please inform us
that this message has gone astray before deleting it. Thank you for your
co-operation.
Another would be areas-of-practice weblogs - logs devoted to a
particular topic and area of interest for both lawyer and client.
====================================
M. Sean Fosmire msf@...
Garan Lucow Miller, P.C.
Marquette, Michigan
====================================
--Original message--
> Dear K-loggers,
> There has been significant progress in the application of weblogs
> to corporate/organizational networks since this group was founded.
> It's clear that people are starting to understand that weblogs can
> be used to filter and flow information that benefits organizational
> productivity.
> Here is how I would categorizing them:
> 1) General news weblogs. News from general news sources that are
> applicable to internal audiences. With or without editorial comment
> by the author. These may be automated (via search terms -- it is
> possible to build a RSS news feed from Google News and republish it
> as a weblog).
> 2) Organization specific news weblogs. Internal initiatives (HR,
> Sales, etc.). Press releases. Competitor information. Product
> updates. etc.
> 3) Joblogs. Weblogs that detail what an employee/member has
> accomplished during the day. This is an easy way to start
> weblogging in an organization. It can be used to keep track of
> consultants, geographically dispersed employees, work at home
> employees, etc. If you have people like that in your organization
> that you manage and your aren't using a weblog to track their
> progress, you are missing out.
> 4) Projectlogs. This is a varient on the Joblog but is authored
> by multiple project team participants. It is a great way to track a
> project's progress. It allows people that are infrequently attached
> to a project to keep tabs on progress. It can be used to spool a
> new team member up to speed quickly. It is also a great archive to
> project documents/files (with context as to why they are important).
> 5) Research weblogs. This is a more formal use of weblogs to
> publish research. It allows the analyst to publish finished
> work-product and supporting documents/sources. It allows the
> analyst to interact with the readers in a way that improves the
> quality of the research. This is a good way to publish original
> content.
> There are probably lots more, let me know the types of weblogs
> you are running that don't fall into these categories.
> Research Weblogs
> I have spent lots of time building research weblogs (for a
> research company I ran) since 1997 (although they weren't called
> weblogs at that time -- my effort was to chunk content and organize
> it in channels in a reverse chronology). Most recently, I have
> begun to publish a research weblog and have found what I think is a
> good format. The site is focused on the next generation of
> terrorism (tough topic, but I have some experience in these areas
> that I think can help):
> http://globalguerrillas.typepad.com
> The format is derived from a combination of my personal writing
> style and that of Forrester Research (I was the senior Internet
> analyst there). It is a combination of posted research "briefs"
> which are moderate length analytical content. These briefs are
> designed for scanning with multiple bullets for major points (most
> people scan the Web rather than read). Here are some examples:
> Destabilizing Terrorist Networks:
>
http://globalguerrillas.typepad.com/globalguerrillas/2004/03/destabilizing_t.htm\
l
> Mapping Terrorist Networks:
>
http://globalguerrillas.typepad.com/globalguerrillas/2004/04/mapping_terrori.htm\
l
> The other post is a "journal" entry. This looks like a standard
> weblog post in that it usually has a few links and contains only a
> single idea. Here are some examples:
> Flight delays (power outages at LAX due to birds):
>
http://globalguerrillas.typepad.com/globalguerrillas/2004/04/journal_flight_.htm\
l
> Attacks on Systems? (looks at the recent terrorist attack on Iraqi oil
systems):
>
http://globalguerrillas.typepad.com/globalguerrillas/2004/04/journal_is_this.htm\
l
> I will be working on new ways to present research on a weblog. More soon.
Hope this helps.
> Sincerely,
> John Robb
> [Non-text portions of this message have been removed]
> Yahoo! Groups Links
Offline 
Send Email
