Library clips

sharing ideas thoughts and feedback

May 12, 2008

Is knowledge hoarding all about your pay cheque?

Filed under: km, conversation

The other day I posted on, Participation is the currency of the knowledge economy.
The word “participation” can be interchanged for “social captial”, “conversation”, “contribution”, knowledge sharing”, but I chose “participation”, because “conversation” cannot happen without “participation.” And “participation” sounds more involved, sustained, or perpetual than “contribution” or “knowledge sharing.”

Anyway in that post I mentioned that the way companies currently operate is driven by each worker building their “intellectual captial” to get ahead, and to differentiate themselves. The more “intellectual capital” you have the more you are worth something or unique to the company. This kind of means workers compete with each other, or at least try to have unique power that will make them an asset to the firm. In this environment “knowledge sharing” would be the worst thing you could do, as you would be giving away your “edge”, giving away what makes you a unique asset to the company.

Of course we all know the “wisdom of crowds”, and an open and transparent participation model leads to ideas and conversation, which leads to discovery and collaboration. The act of sharing and finding saves others from re-inventing the wheel, saving money and project cycle-time.
A company that runs on a social captial model runs on the notion that “two minds are better than one”, so why not have a culture where these minds have open dialogue. In the end this opportunity for access to knowledge to help you with your work and to find new work brings the company closer to innnovation, and more honest client relationships.

No matter how simple the tools, and no matter even if people understand the benefits of “knowledge sharing” it just won’t happen if the company culture is about “intellectual captial” rather than “social capital.”

Enterprises ought to be thankful that enterprise 2.0 knowledge sharing tools can be a catalyst for culture change to a more social enterprise.

All the good stuff you knew about “social captial” but couldn’t practice because of the deficient tools, is now no longer a frustration.

Culture has to change to a learning organisation and social tools can help achieve and sustain this notion. And that’s what they are, “tools”…just because I have a hammer it doesn’t mean I can build a house. Likewise just because I have a blog doesn’t mean I will use it, I have to be guided facilitated, exposed to successes, see others doing it…build confidence.

Anyway the reason for this post was an article by David Fitch in KM Review Vol 11 Issue 1 March/April 2008, called “In pursuit of justice-and knowledge.” It perfectly illustrates the “knowledge hoarding” characteristic, and why I think knowledge sharing tools won’t do anything to allieve this unless the “culture of work” changes to a more social culture, and only then will these social tools augment this whole new attitude.

Here is this quote on why keeping knowledge to yourself makes sure you keep getting your pay cheque:

“Lawyers at large corporate law firms in the US tend to be paid on an “eat what you kill” basis - they earn according to the business they personally bring into the firm. That means that lawyers in the same firm are competing against each other, so there’s not a lot of incentive for them to exchange knowledge with each other. In fact, I’d go as far as to say that it kills knowledge sharing.
In the UK, by contrast, the system “lock-step equity” means that lawyers are paid according to the financial performance of the firm as a whole, so they’re more willing to share knowledge with each other.”

That’s a top-down move I’d like to see.
Basically we work for passion and to get paid, and if the ecosystem you work in pays you according to how well the family is doing, rather than how well you are doing, then it’s in your interest to help out your family.

The workplace has to change from the “competition” model to the “social” model.

I agree that competition is good for achievement and performance, and some might say that the people who get more sales are paying the slackers.

But this really won’t go unnoticed, if a slacker is not making use of the shared knowledge pool to apply to action opportunities, then that’s an even worse excuse to not getting results, as now they have the social captial to draw on, not just their own know-how.

Sure you get paid based on the holisitic performance, but if you’re not doing any work, you’re not gonna last long.
If you’re not a regular in online social conversations, then it’s seen you are not part of the family growth.

Basically, since each member of the team’s know-how affects everyone’s pay check, then it’s in the interest of the team to educate each other, and to make sure everyone member is “aware” of what’s going on in order to perform optimal output.

I bet in this type of “lock-step equity” ecosystem, enterprise 2.0 tools would be a god-send as it helps share knowledge which is crucial to getting your pay check.

In this ecosystem blogs and wikis help you share knowledge easier and more effectively, and the more tuned this system is, the more the know-how is spread. And the more you know, the better you can perform, and the better you perform, the better the enterprise performs, and inturn guarantees everyone a pay cheque.

In an indirect way knowledge sharing = money.

In this ecosystem taking away a blog or a wiki, is like taking away a hammer from a builder.

I still don’t think sharing knowledge in this environment is quite “altruistic”, as you are only doing it for personal benefit, it’s in your interest everyone does well inorder to sustain a good pay cheque. But you hope after a while this may evolve into genuine passion for the family.

May 9, 2008

Examples of re-purposing email

In a past post I talked about Re-purposing email, and after that I was going to give some examples, but I got sidetracked on what blogs an enterprise would have when it would come to communications, see Enterprise blog channels for communications.

If these examples seem universal, then perhaps we can start a “Re-purposing email wiki”…I’m sure Luis Suarez would agree.

Emails are not just about communications, sometimes they are about collanoration, tasks, sharing tips, etc…

This post is not just focusing on communication type blog posts, in fact it’s not focusing on blogs at all. It’s going through example emails and proposing how that email could be re-purposed.

What I have done is listed the email under the social tool it could of been delivered in.
Any notes have been denoted by an (*).

BLOG (team/project/personal/office-wide/community)

Announce

To:OFFICE-WIDE
From:IT
A new security patch on 25-12-07 will be implemented when you login, please let the PC do it’s thing

* This is an easy one, the general IT Office blog

To:OFFICE TEAM LEADS
From:Training Lead
We are running courses, on Access database training, please ask your team members if they are interested.

* All my boss would have to do is publish a blog post on our Team blog pointing to the post on the Corporate Training blog
- this would work as she would be subscribed to the CorporateTraining blog, and we would be subscribed to the Team blog
- in fact if I came across the training blog post (if I had access), I could potentially know before she even told me

To:TEAM and 2 other closely related teams
From: TEAM LEADER
A new banner and overview sheet has been included in our toolkit.
Please let others know.

* Perhaps this could be posted to our Team External blog, where we publish stuff that other team leads can see
- since our team and other team leads subscribe to this blog we will all be in the know
- each team lead can then let their members know by posting a brief blog post on their Team blogs, pointing to our TeamExternal blog.

To:OFFICE-WIDE
From:IT
There is now a colour printer in the office

* This is an easy one, the general IT Office blog

To:OFFICE-WIDE
From:Admin
Please welcome the new global manager for “social software” (hehe)

* This is an easy one, the general Office blog

To:PROJECT TEAM
From: A Project unit manager
The new project workspace has been set up at this URL.
Here is the getting started overview.

* This is an easy one, the general Project blog

To:TEAM
From:1 TEAM MEMBER
Here are the usage statistics for December

* This could be published on the Team blog
- then again this may be of no value to the Development team, or another sub-team, this is what lead me to my post on mesh blogs

To:OFFICE-WIDE
From:Admin
The trains are on strike this afternoon, you will need to make alternate arrangements

* This is an easy one, the general Office blog

To:OFFICE-WIDE
From:Admin
A staff member was mentioned in the national newspaper today for a job well done on one of our projects

* This is an easy one, the general Office blog

To:PROJECT TEAM
From: A Project unit manager
Our main repository does not support media files, please assist clients by using this alternative

* This is an easy one, the general Project blog

Status

To:OFFICE-WIDE
From:IT
We are having problems with internet access, we are speaking to our providers to resolve this

* This is an easy one, the general IT Office blog

To:OFFICE-WIDE
From:IT
The internet is now working

* This is an easy one, the general IT Office blog

Work

To:SUB-TEAM
From:1 TEAM MEMBER
If anyone is interested, here is a workaround to this problem

* Perhaps this could be posted to a Sub-Team blog,
- other sub-teams in the team can subscribe if they like

To:SUB-TEAM
From:1 TEAM MEMBER
The solution to this issue was a setting in Outlook

* Perhaps this could be posted to a Sub-Team blog,
- other sub-teams in the team can subscribe if they like

To:TEAM
From:1 TEAM MEMBER
I’m finding I’m learning a lot about our industry in Africa from my work on this deliverable….

* Perhaps this could be posted to a Sub-Team blog or personal blog
- others can subscribe if they like

FORUM (team/project/personal/office-wide/community)

Question

To:OFFICE-WIDE
From:Admin
We are looking for someone to offer their expertise on….

* Perhaps this could posted in a few community forums
- this way the whole office is not spammed

To:TEAM
From:1 TEAM MEMBER
Does anyone know how to do this excel formula…

* Perhaps this could posted to your team forum
- otherwise search for an excel or Office tips community that may have an excel wiki or excel blog

To:TEAM
From:1 TEAM MEMBER
Where can I find a file for our team logo?

* Perhaps this could posted to your team forum
- or IM blast a portion of your network

To:TEAM
From:1 TEAM MEMBER
What do people think of Windows Vista, what are your experiences?

* Perhaps this could posted to your team forum, or a community forum, it depends which audience you want to ask

To:TEAM
From:1 TEAM MEMBER
Where would I find information on…

* Perhaps this could posted to your team forum, or a community forum, it depends which audience you want to ask

To:PROJECT TEAM
From:1 PROJECT TEAM MEMBER
Does anyone want to car pool, I live outer eastern suburbs?

* Perhaps this could posted to the project forum, or the office forum, it depends which audience you want to ask
- or IM blast a portion of your network

IM

To:WORKER
From:WORKER
Can I use the Adobe writer on your computer?

* This is a quick question that can easily be done in IM, rather than an email in each inbox

To:WORKER
From:WORKER
I forgot to ask you was it cold when you were just outside…I’m about to go out.

* This is a quick question that can easily be done in IM, rather than an email in each inbox

To:WORKER
From:WORKER
The conference is about to start, where are you?

* This is a quick question that can easily be done in IM, rather than an email in each inbox

To:WORKER
From:WORKER
Are you free for a chat, I have 3 others that are free now.

* This is a quick question that can easily be done in IM, rather than an email in each inbox

WIKI

Collaborate

To:4 TEAM MEMBERS
From:TEAM LEADER
Can you all make a list of issues and email them to me and I will put them in one big list

* This could be a wiki task, see my post

To:4 TEAM MEMBERS
From:WORKER
Can you all review this attachment and send me the changes

* This could be a wiki task

To:4 TEAM MEMBERS
From:WORKER
Sorry, here’s another addition to the meeting agenda

* This could easily be added to the meeting agenda wikipage without emailing people

Knowledgebase

To:7 TEAM MEMBERS
From:1 TEAM MEMBER
If anyone is interested, here is a workaround to this problem

* This could easily be added to the solutions wiki
- or perhaps Tips and Tricks blog

To:7 TEAM MEMBERS
From:1 TEAM MEMBER
I can’t find the documentation on…where is it kept

* This wouldn’t happen if there was a centralised team wiki or a wiki that lists documents in the repository
- otherwise ask the question in the team forums

To:7 TEAM MEMBERS
From:1 TEAM MEMBER
When you load this in the database remember to change this element as the template is not yet fixed.
This is not documented in the procedures.

* This is a reply-email to someone who didn’t need to send the email request if there was a Workarounds wiki or blog
- otherwise ask the question in the team forums

Event

To:7 TEAM MEMBERS
From:1 TEAM MEMBER
I can’t find the email for when that workshop is taking place

* This wouldn’t happen if there was an Event wiki
- otherwise ask the question in the forums

To:TEAM
From:1 TEAM MEMBER
The workshop is kicking off today.
Here is the agenda.
This person cannot make it.
I will further email you the presentation attachments

* This wouldn’t happen if there was an Event wiki, with a wiki blog
- perhaps a community could be set-up for the workshop

Task

To: SUB-TEAM
From: 1 TEAM MEMBER
Could everyone please sign off that the new features have been tested and work

* This could be a wiki task, and perhaps posted on the wiki task blog
- rather than once person sending out an email to about 10 people with an attachment
- then each person sending back an email to say they have actioned it

To:7 TEAM MEMBERS
From:1 TEAM MEMBER
The test server will be going down for 3 days to be patched.
I will let you know the moment it is back up

* This could perhaps be posted on the wiki task blog
- or if it’s part of a bigger picture like a project where the wiki and blog could be in a community

To:3 TEAM MEMBERS
From:1 TEAM MEMBER
I am currently at stage 3 of my report, I’m now doing field research for stage 4.
Tomorrow I will fly to China, and need to find accomodation.
I will meet with client and let you know of the results.

* This could perhaps be posted on the wiki task blog
- or if it’s part of a bigger picture like a project where the wiki and blog could be in a community

To: SUB TEAM
From: TEAM LEADER
A new advanced editing feature will be rolled-out on 25-12-07
Please test this and report back.

* This could perhaps be posted on the wiki task blog
- or if it’s part of a bigger picture like a project where the wiki and blog could be in a community

To:3 TEAM MEMBERS
From:1 TEAM MEMBER

The server has been set up and the program installed, you can now proceed.
I had issues with the subscription module, so it’s not installed yet

* This could perhaps be posted on the wiki task blog
- or if it’s part of a bigger picture like a project where the wiki and blog could be in a community
- only members of this community will be subscribed saving other team members not having to be spammed
- so in fact this example is more a project communication, rather than a team communication
- I think it’s important that quick short-lived communities are set up to achieve tasks

To:1 TEAM MEMBER
From: TEAM LEADER
Can you please do this task, and report back and then contact Bill do take it onwards.

* This could perhaps be posted on the wiki task blog
- or if it’s part of a bigger picture like a project where the wiki and blog could be in a community
- just have to put up with other subscribers of the blog getting this post that is only intended for one person

To:1 TEAM MEMBER
From: TEAM LEADER
Can you please update the appendix on this report

* This could perhaps be posted on the wiki task blog
- or if it’s part of a bigger picture like a project where the wiki and blog could be in a community
- just have to put up with other subscribers of the blog getting this post that is only intended for one person

I’m finding with a lot of these tasks a more focused tool like Activities from Lotus Connections would be more appropriate.
Or a commuity or wiki that has social networking so you can message a member in the inbox of that wiki task, rather than your email inbox.
This way the task request is not separate from the task itself, you would only get a notification in your email inbox or perhaps a dashboard to alert you of your task.
It’s also bringing to mind Foldera…but then again there are heaps of task, workflow type tools.

The ultimate scenario is for a team to have a community site that includes:
- sub-communities
- social networking
- blogs
- forums
- wikis
- IM
- tasks

All your work and communications are together. The idea is not to have stuff in your email related to where the work lives, it should all be open and together…no siloes and no people out of the loop.

May 8, 2008

Google Reader Notes

Filed under: blogs, rss, readers

A while back I mentioned that Google Reader Shared Items (which is like a clip blog) needs to be merged with a service like Google Shared Stuff (which is like a clip blog).

The problem I was having is that I could not clip stuff I found outside Google Reader into my Shared Items stream, this meant I had to have two clip streams.

Well now this has been solved with Google Reader Notes.

In the Google Reader console there is now a page called “Your Stuff”, and under this there are two pages called “Shared Items”, and “Notes”.
Clicking on the “Your Stuff” link is a way to see “Shared Items”, and “Notes” in the one stream.

Share with Note

For any item in Google Reader there is an addition to the one-click “Share”, now there is another choice to “Share with Note”
- this pops-up a box where you can add a note/annotation (just like with my Facebook Posted Items).

Notes

“Notes” allows you to make a note without it having to be about a webpage, it’s just like blogging an item.

This can be done via going to the “Notes” page in Google Reader

This automatically shares the item into the “Shared Items” stream, as well as being in your “Notes” stream (which is private).
You can unshare a Note so it no longer appears in your “Shared Items” stream, and is only in your “Notes” stream.

“Note in Reader” bookmarklet

The “Note in Reader” bookmarklet allows you to add an item (along with a note if you like) into your private “Notes” stream.
The bookmarklet also has a box to check to include it in your “Shared Items” stream, before you press submit…otherwise you can decide to share it later on from your “Notes” stream.

Issues

- I wish a Note didn’t share by default
- I’d like to filter the Notes stream by Notes I have shared, and Notes I haven’t shared…this way I can keep some private notes in one spot.
- I can’t edit or delete a Note
- There isn’t a bookmarklet to create a new note (you can only do this from within Google Reader).

What could be next?

- Comments
- Tag “Shared Items”
- A calendar archive
- Template/sidebar additions
- Reblog and item from someone’s “Shared Items” to yours (like Tumblr)
- Merge your “Shared Items” with your friends (like a Tumblr group), or perhaps this could be a network instead like Friendfeed (this is more probable as there already is a “Friends Shared Items” feature.

Google Reader seems to be where I live, so instead of having another window for Webnote, I just like a tab in Google Reader…I wonder if there is a hack.

You’d think they may do this with there own set of products, at the moment at the top of Google Reader I have links to Gmail, Calendar, Docs, etc…what about tabs instead…maybe I’d use Google Notebook, rather then Webnote.

Actually this is what you can do with OtherEgo, but this is more of a profile aggregator by tabs (not quite a lifestream). Not sure if you can add a tab from a private service like Google Reader.

But I like this idea of a private startpage, but instead of widgets on the one page, it’s the whole page by tab.

In one window I could have access to:
Google Reader
Gmail
Twitter
Friendfeed
Facebook
Webnote
del.icio.us
My blog
…and several other pages.

May 7, 2008

Enterprise blog channels for communications

Filed under: blogs, km, communication

This post is an idea, thinking out loud, something to build upon, or perhaps something that is a bad idea…see what you think.

This is a follow-up to my post, Re-purposing email meme, which explained the email problem (overload, siloed) and how a “re-purposing email” idea with social tools can help reduce the anxiety and act as a catalyst for an open, collaborative, conversational and emergent social enterprise.

One thing to note is that you don’t save or waste time, you spend the same amount of time, only spread across various tools…what you are doing is spending your time more wisely (social productivity).

The focus of a future post will be examples of emails, and in what way they can be re-purposed.

But for now I want to examine exactly how blog communication is going to replace email, except emails for private or sensitive one-to-one correspondence.

This post is only about one type of blog use, and that is “communications“.
This is an In-the-Flow usage scenario as the concept is to use blogs instead of email for something we are already doing…this is not an extra thing we have to do, it’s substituting a tool.

This post does not include Above-the-Flow blog (sharing tacit knowledge) uses like:

- Personal/Group blogs (experiences, “thoughts out loud”, ideas, reviews, opinions, “work in progress”)
- Tips and Tricks blog
- Topic blogs
- etc…

If blogs are to replace team and cross-team communication I’ve realised blog channels are required.
Reason being is that when you email a communication, it may be to a:
- team email group
- sub-team email group
- directed at only two sub-team email groups
- directed at 3 out of 10 people in a sub-team
- directed to a team in another business unit
- directed to just two teams in another business unit
- directed to the whole office

I call these mesh blogs, as most blogs above are dedicated to 2 or more email groups.
This makes a blog two way in the sense that it can be a channel for 2 email goups to communicate through.
eg. In email you would have a manager emailing a “communication” to sub-team group
To: DM Support group
From: A DM Management member

Or a sub-team group member emailing a “communication” to the manager group
To: DM Management group
From: A DM support member

Now both these groups can “communicate” or broadcast announcements to each other through a mesh blog called “DM Management-Support blog”.

Both these email or Active Directory groups are auto-subscribed to the blog.
People from other sub-teams are welcome to manually subscribe to the blog.
People from other business units (permissions based) may also be welcome to visit the blog page or subscribe to the blog.

This is openess at it’s best, with visible and centralised content (corporate memory), where conversations (comments) are seen by all…content can evolve.

Other business units may want to point to a blog post in the “DM Management-Support blog” in one of their own blogs as a way to inform their own team…this is the beginnings of an open internal blogosphere.

NOTE: DM is Document Management - this is an example of a team or business unit

Issues

Now what about if the DM Management group wanted to communicate an annoucement to both the DM Support and DM Sys Admin, but not the other sub-teams within this business unit.

Would they cross post in the “DM Management-Support blog”, and the “DM Management-Sys Admin blog”?
Not sure about duplicate posts, as conversations will be fragmented.

If there are often communications directed at both these sub-teams communications, then maybe another blog is required, such as a “DM Management-Support-Sys Admin blog”

If the communication is directed to the whole team then it could be posted in the “DM All Team blog”

The reason I came up with the concept of a “mesh blog”, that is conceived to only serve 2 parties, is to overcome the subscriber issue and occupational spam.

Sometimes communications are not directed at your whole team, and if your whole team is subscribed to your blog, they will get new posts not directly concerning them.
This can be avoided using email as you can push the communication to just one group of people.
But at the same time it’s not an email silo, it’s visible for others to see or even subscribe to.

For an Above-the-Flow blog like a “Tips and Tricks” blog, a non-mesh approach is OK, you publish stuff and people with an interest in your stuff will subscribe.

This is where I get stuck, what if your communication is to your “All team blog”, and also to 2 other business units.

Well maybe this type of communcation could be posted on your “All team External blog”, where your whole team is subscribed and the leads of other business units. Then these business unit leads can point to this blog post in their own teams blog.

But again if there are 10 business unit leads, this post will be spam to 8 business unit leads.
At the same time, it is good for “leads” to be aware of what’s happening around the enterprise.

I guess this is the problem in enterprises at the moment, in that email is a closed system, where people in other business units are not in the loop…I’ve posted on this in the past.
With mesh blogs, even if they are not auto-subscribed, the communication is still visible to visit at the blog page, and they could choose to manually subscribe themselves.

So what was once an email to an email group, is now a blog dedicated to communications between these 2 groups, where blog posts to those same people in the email group (as they are auto-subscribed) are being delivered, and a clean conversation can happen in the comments.

The added value is that what was once a closed email communication, can now be subscribed to by others by their own choice, or they can visit the blog page.

I like that the existence of these pre-made channel like blogs welcome communications within sub-teams and across business units.
Email groups are there for you to post to a whole group if you want to, but having a blog channel as a place dedicated to 2 groups to communicate kind of welcomes or expects communication.

Cross-team awareness is the foundations of a competitive edge that creates conditions for inter-disciplinary conversations, which is a way to innovation…see more.

Tasks

Another issue I had was with emails that contain a task, whether it’s emailed to 1 person or 4 people.

In this case perhaps a wikipage can contain the task, and the wikipage comments can inform of progress and discussion. The wikipage can also have a subscriptions feature for all to be in the loop on the latest version without having to email each other.

Another option is a task specific tool like Activities from Lotus Connections.

In this case of tasks, perhaps email can be used to invite people to the wiki…in this instance blogs are not a suitable tool for this use case.

If a task is part of a bigger task or a project within a team, perhaps a taskforce (community of practice) can be used where members of this community can communicate and collaborate using wikis, blogs, and forums.

NOTE: I’m not referring to client projects, I’m refering to projects/tasks within a team

Team relationships

As I’ve explained above, in relation to “communications” (not Tips and Tricks blogs and the like), I have found each sub-team needs a blog for themselves and separate blogs to deliver communications to each other sub-team, I’ve called these “mesh blogs”.
They are almost an email/blog hybrid in a sense, or perhaps an open email channel.

To really blur the line, there could also be the availability to receive new posts in an email, publish new posts by email, and post comments by email.

If the team (business unit) is small eg. 10 people in an organisation of 100 people, well then perhaps there would not be much occupational spam (I suppose it also depends on the frequency of posts). In this case maybe mesh blogs would not be required, each sub-team could have a blog, and each sub-team could subscribe to each others blogs.
As a support person I wouldn’t be thrilled about getting 3 posts a day from the development blog about stuff I have no clue about, just in the case that they have a once in a while post that I need to know.
But then as a support person I wouldn’t need to subscribe to the development blog, as when they have something to say to the support team, they can post it on the All team blog.
If I like I can visit the development blog to be in the know about stuff that would have usually been closed in email.

Another thing to consider is instead of all these mesh blogs, they could be reduced to categories on a few blogs, and the correct sub-team subscribes to the correct category feeds.

This post is about enterprise business unit or teams, but the same concept could also be applied to bigger sized communities of practice and projects.

Before we start we need to know the relationship between the sub-teams, and from this we can create our list of blogs…here’s a team and it’s sub-teams.

DOCUMENT MANAGEMENT (TEAM or UNIT)
SUB-TEAMS
Executive
Management
Development
Sys Admin
Support

On top of the blogs below, each sub-team could have blogs to cross unit teams or sub-teams
eg. DM sys admin -IT sys admin blog
This is a channel for 2 cross unit sub-teams to communicate.

Another consideration is blogs could further be divided by location, or by function
eg.
DM Support team Perth blog
Server status blog
New release blog
etc…

Here are a list of the blogs for a business unit or team such as Document Management

1. DM All team blog
2. DM All team External (to rest of the organisation) blog

3. DM Management team Internal blog
4. DM Development team Internal blog
5. DM Support team Internal blog
6. DM Sys Admin team Internal blog
7. DM Executive team Internal blog

8. DM Management-Sys Admin team blog
9. DM Management-Support team blog
10. DM Management-Executive team blog
11. DM Management-Development team blog
12. DM Executive-Development team blog
13. DM Development-Sys Admin team blog
14. DM Support-Sys Admin team blog

These really look like proper channels for open communication.

Subscriptions

Any team member can subscribe to any blog.

But most subscriptions are already done at the group level via auto-subscribing groups (or individuals)
- a typical example is members of the DM Support team and the DM Sys Admin team are automatically subscribed to the “DM Support-Sys Admin team blog”

Exceptions

DM DEVELOPMENT TEAM
This team doesn’t really speak to the DM Support team
- they can go through the DM Sys Admin team which have a closer relationship with the DM Support Team
- ie. they can publish a post to the “DM Development-Sys Admin team blog”

DM SUPPORT TEAM
This team doesn’t really speak to the DM Executive team
- they can go through the DM Management team which have a closer relationship with the DM Executive Team
- ie. they can publish a post to the “DM Support-Management team blog”

This team doesn’t really speak to the DM Development team
- they can go through the DM Sys Admin team or the DM Management team which have a closer relationship with the Development Team
- ie. they can publish a post to the “DM Support-Sys Admin team blog” or the “DM Management-Support team blog”

DM SYS ADMIN TEAM
This team doesn’t really speak to the DM Executive team
- they can go through the DM Management team which have a closer relationship with the DM Executive Team
- ie. they can publish a post to the “DM Management-Sys Admin team blog”

DM EXECUTIVE TEAM
This team doesn’t really speak to the DM Support team
- they can go through DM Management team which have a closer relationship with the DM Support Team
- ie. they can publish a post to the “DM Management-Executive team blog”

This team doesn’t really speak to the DM Sys Admin team
- they can go through DM Management team which have a closer relationship with the DM Sys Admin Team
- ie. they can publish a post to the “DM Management-Executive team blog”

Conclusion

This post sounds like a lot of setting up (would it get confusing in a large organisation), perhaps it would be easier for all teams and sub-teams to have non-mesh blogs…that is, regular blogs that people can subscribe to be in the loop. The problem here is since regular blogs are not targeted directly to a group of people, you may have to get 30 unrelated emailed for every related email.

My idea was to leverage what we do with email, but augment it by meshing 2 email groups together with their own unique communication space…which is also visible for others to see or even subscribe to.

As I mentioned mesh blogs are probably not needed in small organisations, as long as the level of posts that are not directly related to you don’t outweigh the posts that are relevant (noise to signal ratio).
To re-iterate perhaps as a member of one sub-team, you wouldn’t need to subscribe to another sub-teams blog, because when that sub-team wants to communication something to your sub-team, they would use the All team blog.
Posting on the All team blog means the other sub-teams will also see this post, but I think this is negligible.

Or as I also mentioned perhaps blog by function would be better, only problem is what if a blog doesn’t exist for the type of communication you want to deliver, whereas mesh blogs are generic.

What do people think about the mesh blog idea, please leave a comment.

May 6, 2008

Re-purposing email meme

What actually is the email inbox?

It can be the latest private correspondence, news, questions, announcements, conversations, document collaboration, tasks, notifications etc…

This is a lot of different types of content coming into the one stream, where it’s hard to sort out priority, and also hard to organise what you’ve done, what the status is on what your doing, and where to find what your working on.

My post, Instead of sending an email…, poses that a better way is to receive this content in context
eg. IM for quick questions, forums for discussion, blogs for know-how and communications, wikis for collaboration, RSS for notifications, etc…

Now you have various places to go to do your work…email can be used for one-to-one private correspondence and for invite links
eg. you are invited to collaborate on this wiki, here is the link

Instead of getting an email about project status, a new forum topic, I check my RSS Reader where I subscribe to blogs and forums.

This has split my email inbox stream into various other services, and most of the time I can reply or take part within these other services.

And of course this content is in the open for all to benefit from, for conversation to evolve the content, and I can discover people, connect and learn.

Email stress is something that is relevant to everyone, but what are people doing about it besides re-appropriating content elsewhere as I have suggested above?

There are lots of ways to be productive to keep your inbox down, but this is still putting up with the firehose problem, you are just putting up with the problem by implementing a nifty method to deal with it. Why should you have to deal with it, why not treat the cause?

A comment I left on one of my blog posts, referncing Jack Vinson, is that the real issue is the “input problem”. Email is just a tool, it’s the way we are using it, that’s stressing us. What has to happen is a policy, rule, social norm on group behaviour using emails. If you tell Bill to use a blog or IM sometimes instead of email, then you don’t need to solve your inbox problem as Bill is doing it for you, by re-purposing the content in the first place.

We don’t use RSS Readers at my work, we are using email to subscribe to blogs and forums. This is OK as you can post replies and comments from within your email, you can even post a forum topic and blog post via email…people like this.
We are in the open, having conversations, discovering people, creating serendipity, which is doing the right thing as we are leveraging the social capital, creating a corporate memory, creating conditions for emergence, etc…
We are starting to collaborate with wikis.
NOTE: this is not enterprise wide, we are in pilot mode

Even though I still have the problem of all this stuff (notifications) coming into my inbox, at least it doesn’t live in my inbox, at least I’m not actioning stuff as a new email. Once I read the email I delete it, as I know where the content lives.

One other benefit I forsee is that when people get the hang of blogs, I won’t be pushed so much stuff anymore, I can choose to subscribe by email. We already have an issue with a flooded inbox with stuff that’s relevant, last thing I want is occupational spam.

Another option over the RSS Reader subscription model is to have profiles and be able to network by subscribing to people:
- your profile
- what your subscriptions are doing

Luis Suarez’s email detox posts and podcasts (and another) are a perfect example of this re-purposing email for both personal well being and social benefit.

One thing that stuck in my mind is when Luis said he was sick of answering the same question all the time.
- he would rather answer a question once in a community forum or blog post where it is visible, and allow people to search or be pointed to it
- if the question was asked in public perhaps others could see it and answer it if Luis was unavailable, or didn’t know the amswer himself

This is similar to our support database where people log calls…if I can’t answer a call or I’m absent at least someone else can see it in the cue.
When people email a call, I have been instructed to ask them to log the call, please.

Luis is proposing this concept to any sort of question, just search the blogs or forums, if no luck then choose a forum to ask the question, or ask your network.

He is also doing what I do with support calls that are emailed to me, he is letting people know that what they just emailed him could of been done by IM, or a forum topic, or a blog post, or a wiki, etc…and he is letting them know by using this social tool to deliver the message.

Since our community pilot I have been doing the same.
Everytime I get an email that is an announcement I remind that person that they could have blogged it.
Everytime I get an email that is a question or discussion query I remind that person that they could have posted a forum topic.
Everytime I get an email that requires a more synchronous feel I ring that person or answer using IM.
Everytime I get and email that asks to collaborate on something I inform that person that we can use a wiki.

My intention is that once all community leaders discipline their members, they will hopefully re-habitualise (is that a word?) people into using the right tool for the right job.

Another thing that came across is that “email detox” is a great selling term to get people social online. Email stress affects everyone, and a process/program to help with that is a great disguise for getting social tools adopted. It will soon be realised that email detox is just a by product of social tools, and the real benefit is being connected.

What if you want to annouce something and some people you want to reach don’t subscribe to the blog?

Firstly if it’s a team blog, perhaps you could subscribe the group email to the blog.
But sometimes a team announcement may affect another party, in a past post I suggested that if you can post a blog my email, just include these other people in the address bar as well.
The end of the email can contain a link to the blog homepage so these people are aware that the content is archived, and not siloed.

How do I share links with people?

If I want to share a link with a friend that is not private correspondence, how do I do it?
- and what if she doesn’t subscribe to my bookmarks, or what if I haven’t bookmarked this link anyway, but I just want to tell them about it

This is what I like about the Facebook comment wall…I can share a link with one person, but it’s public.
- others can see it when they visit that page
- others will be aware of this via their News feed.

What about if I want to share a link or an email someone sent me, with three other people?

I wonder what Luis does for this type of communication.

Wiki idea

I’m thinking perhaps we should do something similar to Andrew McAfee’s latest post with example scenarios of when a social tool would be beneficial.

Perhaps we can create a wiki for re-purposing email examples:
- blog
- forum
- wiki
- IM
- tasks

And also have wikipages for each wikipage above, example:
Blog
- status
- announcement
- news
- etc…

I have started going through my current inbox and am filing emails in re-purposing folders.

I’m finding that I don’t know where to file some emails…maybe we can have a wikipage for emails that we don’t know how they could be re-purposed. This is especially happening with task type emails.

If a task is to request the team to sign off on the latest server upgrade testing, then a blog post is OK.

But what if the task is just for me to carry out something on my own and report back…I guess this is where something like the Activities module of Lotus Connections is the right social tool.

In some cases a task request may be a question to me and cc:’d to two people in another team. In this case the requestee has perhaps spoken to these two people and has said I’ll email John and cc: you.
I really think that on-the-fly forums are essential, as not all work is done within a team or community. Sometimes you are cross-collaborating so you want to have a quick task and discussion space quickly set-up rather than resort to email.
Or maybe the task could be a wikipage and the comments can be used for discussion.

I’ll perhaps do a follow-up post with some examples of the type of content we could include in a “re-purposing email wiki”

Related

Wiki for gathering a list, and the need for comments and notifications
Blogs can solve cross-departmental communication silos
Email is not the centre of my universe!
Email needs to know it’s place
Enterprise email and blog processes

May 5, 2008

Participation is the currency of the knowledge economy

I just wrote a post on emergence, that basically points out that when a system is unstructured it allows people to use it how they like, and it’s use doesn’t have to follow a vertical value chain. Instead we can use these flexible tools to make our own work-flow, to connect horizontally…they are more organic and have a viral spread.

As I pointed out in the post, the concept of emergence isn’t just about non-rigid flexible tools, well this is the first step which is kind of a “use” emergence. The other aspect is “content” emergence, ie. people are are tagging their content, or we could run a concept tag script through a pool of content, which allows us to see what is being talked about.

An enterprise blogosphere and social bookmarks displays a tag cloud, and from this cloud we can see what is the most talked about topical content, ie. we can see the patterns that are emerging.

Aggregated content

I want to go a step back and see what is driving the content that makes up this emergent scape.
That is, what is the nature of participation.

Jeremy Thomas leads us into a hippie type altruistic notion of doing your unselfless bit for the community, which he, like Charles Leadbeater mention is what web 2.0 is about. I agree, without questions answered and blog comments, there is not much conversation, making for a boring web 2.0.
But Jeremy goes on to say that this is not the foundations of web 2.0, it’s more a personal motivation, akin to the del.icio.us lesson.

It begins by personal publishing, contributing, collecting, and during all this is conversation.
What is important is what drives the beginning; it’s loud and clear that it’s “personal benefit”. If a corporation acts like a person, then their reason for an internal web 2.0 is personal benefit (profits).

When you aggregate all this personal benefit you get a macro picture, basically, “The whole is greater than the sum of its parts.”

Jeremy relates this to economics:

“Adam Smith’s notion of the “Invisible Hand” that drives the Enterprise 2.0 ecosystem. A knowledge worker “…intends only his own gain”, he seeks recognition which can ultimately lead to promotion and increased salary. In describing the driving force behind free markets, Smith writes:

By pursuing his own interest he frequently promotes that of the society more effectually than when he really intends to promote it.

The “selfish” contributions made by knowledge workers makes the enterprise as a whole better off. And the services the enterprise opens up makes other enterprises better off, and this is consitent with the “Invisible Hand”.

Enterprise 2.0 is not based on utopian ideals. It is instead based on the very principles that drive all free-market economies. Organisations that adopt enterprise 2.0 will do so for auto-preservation and corporate gain - to help their bottom line.” Period.”

Charles Leadbeater adds to this:

“…counter culture of the 1960s, combined with pre-industrial ingredients it has resurrected, folk culture and the commons as a shared basis for productive endeavour. The web allows for a massive expansion in individual particiaption in culture and the economy.

Greater individual participation will not, on its own, add up to much unless it is matched by a capacity to share and then combine our ideas”

Shawn Callahan describes the tragedy of the commons:

“That’s when the individual actors operate to maximise their self interest and in the process ruin things for the wider group.”

From all of this we see the personal benefit is what drives this participation culture, and in aggregation we see trends, but it’s also the aggregate of people that creates a market of conversation, that is the dynamic of web 2.0. The Cluetrain Manifesto talks about “markets are conversations“…yet to read it.

Market economy

So if enterprise 2.0 is a “market economy” what is enterprise 1.0?

In “The Wisdom of Crowds“, James Surowiecki points out that companies should work more like markets, an Autonomous flow (based on Collective intelligence) rather than an Expectations model…and this is just what can happen with Enterprise 2.0.

The following is lifted off a presentation I made a couple of months ago:

Companies pay people to perform on an expectations (target) model
- Hiding information may happen
Markets pay people on what they do
- Don’t make more money if you exceed expectations
Markets have “incentive” to seek valuable information (eg. Buyer behaviour)
- When acted upon, it becomes public knowledge
Companies need to work in this incentive model
- The more a worker contributes the more they are recognised and the more prosperous job (money)…information goes back up the value chain
- This is a new incentive model for what a worker does
Aggregation/Network Effects/Emergence
- The worker need only worry about personal benefit
- Others can benefit from public aggregation of information
- Social Capital is leveraged

This is saying currently companies (managers) set levels of expectations and reward people financially.
eg. you get a holiday bonus if you make 10 more sales this month.

By setting these incentives the company also benefits, but is this a narrow approach; are there lost opportunities?

In this type of setting why would I want to share my knowledge, it’s my “power”, we are all on our own, and my personal know-how is going to get me ahead. If I don’t share I will meet my expectations (and no-one else), but on the same hand if I don’t find any knowledge, I may not meet my expectations.

So in fact this expectations model promotes “not sharing” information.

I see this as the parts on their own, and not coming together as a dynamic whole…siloed people with a fear of trust to connect.

What if a trend spikes or drops in the industry without us knowing, but indeed someone else in the enterprise knows, but they are not in the business of sharing this information, or perhaps the enterprise would share this information, but they don’t have a sharing ecosystem (tools and behaviours).

You lose, because without this information you don’t get your job done, and your managers loses as you have missed an industry opportunity.
Had your enterprise encouraged knowledge sharing, this information would of surfaced to your attention. So here we have missed an opportunity which may have dire consequences, and worse still, someone in your organisation held this information…a bit like the enterprise shooting itself in the foot.

If corporations, in respect to the law, act as one person, they should also think about doing this in respect to “one intelligence.”

The idea is a knowledge conversation market, connecting all the brains into one hive mind, the more we share and participate (as is done in web 2.0) the more we are contributing, and these contributions form new content, they are valuable to others…re-using knowledge.

The new model can be financial rewards for participating, but not by gaming the system, the participator has to demonstrate contributing valuable stuff, engaging in conversations, and some success stories that have come from the simple fact that you shared and conversed.

Now you still get your reward, you and the company still win, and it’s more holisitc as the company is not missing out on opportunities as people are connecting to get their work done. From this it seems a social enterprise is essential, I’d want one now if I was a manager.

It’s a different way to look at the model, the more you share and engage the more you are seen as a “guru”, so you actually become more powerful by letting go of knowledge.
If this knowledge can be used to add value to the work of 5 other people, then they and the company are better off.

In essence, Enterprise 2.0 enables the enterprise to leave an expectations model for a social model, as conditions for innovation is the new performance driver, and this will only happen if there is a participative ecosystem where knowledge sharing is the currency.

NOTE: By knowledge sharing I just mean: visibility, publishing, participating, contributing, conversing…

Rod Boothby has a great post on emergent environments:

“Emergent intelligence only evolves when agents have the freedom to act independently. The traditional command and control structures employed by most large firms do not lend themselves to fostering this kind of independence.

However, that does not mean that there isn’t still a roll of management to play. Their task now is to cultivate an environment that encourages innovation.

To guide emergent intelligence in an organization, you need to think about management techniques that foster innovation, and encouraging dialog and the exchange of ideas.

Imposing rules and taxonomies isn’t going to achieve the goal. Nagging people to add to the “knowledge repository” isn’t going the right answer either.”

In the above rant about markets have I really been talking about a knowledge economy?

I think the knowledge economy is about relationships (client and internal), conversations, and information flow as the new competitive edge.

As mentioned in previous posts, it’s now a level playground in that enterprise’s can easily compete with assests, people, cash, outsourcing, offshoring, perfecting supply chains…relationships, conversations, sharing and exploiting know-how is the new way to get ahead of the innovation curve.

But it’s not just about profit, it’s also about quality. When everyone is in the loop there is less chance of mistakes in processes and design, hence less chance of not getting things delivered on time and and the right cost, and less chance of damaging client relationships.

The World is Flat by Thomas Friedman goes into great detail about outsourcing and supply chains, and I just came across a few typical links of this nature this past week, Artemis (film-making), and Ponoko (for furniture).

As you can see both the provider and the consumer can take advantage of e-commerce by bypassing a number of logistic processes, but it’s more than that. In a past post I mentioned David Weinberger talking about how web 2.0 is granular, and how you can pick and choose components and put them together, creating your own personalised view of the world. Well I found the same with using a web 2.0 site to buy a t-shirt.
My wife visited Redbubble where she keeps her art, this site also allows you to make t-shirt versions of your art…that’s all you have to do as a provider to have a shop, as RedBubble will organise the rest.
As a consumer I browsed t-shirt designs for hours, I could choose colour, long or short sleeve, etc…
This is similar to what web 2.0 has done to the news…the change from one-to-many in a physical shop, where the shop decides the range, to many-to-many where the consumer can choose stuff from the globe, from supposed non-experts.

Since this new edge, is about sharing your know-how in a more social and visible way, I think it will make for an enterprise where people feel socially connected (happy) and that they have impact on decisions made and direction…the networked enterprise will catapult innovation, just look at how fast web 2.0 spreads and evolves ideas, reducing the global into a coffee room.

Charles Leadbeater points out the limits of markets [as compared to a knowledge economy]:

“But markets of this kind have limitations: they work for specific problems that need exactly the right individual to solve them. They do not provide the basis for sustained creativity and innovation to explore difficult complex systems. That kind of problem solving only comes from intense collaboration.

…crowds need meeting places, neutral spaces for creative conversation, moderated to allow for free flow of ideas.”

So it seems a market economy is more a demand/supply thing whereas a knowledge economy is more about collaboration, volunteering know-how, conversations, connections…all due to participating and visibility.

More from Charles Leadbeater:

“In the economy of things you are identified by what you own: your land, house, car. In the economy of ideas that the web is creating, you are what you share: who you are linked to, who you network with and which ideas, picture, videos, links, comments you share.
That matters because the more ideas are shared the more they breed, mutate, and multiply, and that process is the ultimate source of creativity, innovation and well being.”

“The web’s underlying culture of sharing, decentralisation and democracy, makes it an ideal platform for groups to self organise, combining their ideas and know how…

At root most creativity is collaborative. It is not usually the product of a flash of insight from a lone individual.

The factory made possible mass production, mass consumption and with that industrial working class. The web could make innovation and creativity a mass activity.

Our preoccupation in the century to come will be how to create and sustain a mass innovation economy in which the central issues will be how more people can collaborate more effectively in creating new ideas.

The factory encouraged us to see everything through the prism of the orderly production line delivering products to waiting customers. The web will encourage us to see everyone as potential participants in creating collaborative solutions through largely self-organising networks.”

Perhaps a knowledge economy is a way of being, the way you work, it’s the notion that “none of us is smarter than one of us”…mostly it’s about the intangibles.

Social Capital and Conversation

The title of this post is “Participation is the currency of the knowledge economy”, but perhaps I should have substituted the word “participation” with the term “social capital”. Chris Fletcher has more on this:

“…we are seeing a change in perspective around knowledge from one of a content centric focus on Intellectual Capital, to one where social capital will be the currency. It will be about who we know and what we will do for each other. In essence, we are seeing shift to people being central to how knowledge moves through the organisation.”

Chris has a great matrix of moving from Content & Collection to Context & Connection. The collaboration and innovation quadrants are where conversations and connections happen, and this is where knowledge in context is exchanged and created.

James Dellow picks up on a post by Sam Lawrence, pointing out that a new way of working is emerging, “social productivity” focusing on the “we” over the “me”…more from Sam:

“This more accurately mimics our work-with-others activity vs. the produce-alone-and-distribute part of our daily equation”

Maybe in the title of this post I could of substituted the word “participation” with the word “conversation”.
Chuck Hollis, who I have posted about before, has realised that conversation is gold, and creates more gold:

“These conversations were personal, honest and context-rich. And they were perhaps the most important source of innovation and value-add in our corporate culture.

To go even further, the really cool conversations I was having usually started with someone saying “you know, I was talking to so-and-so, and we came up with the idea that …” so we had one conversation feeding into another.

If you believe that conversations were creating incredible business value, maybe the focus should be on having many more conversations, much more easily.

Conversations lead to passionate topics of mutual interest.

Passionate topics of interest lead to ad-hoc community formation.

Community formation leads to collaboration around shared activities, including document collaboration.

Community collaboration is the quintessential magic of all things E2.0.

So, not to oversimplify, but if EMC got really, really good at starting interesting conversations, the rest would follow naturally and organically.”

I’d like to hear what others think the differences are between a market economy and a knowledge economy…please leave a comment.

[UPDATE: Just read an interview with Clay Shirky that seems relevant to this post.

Clay Shirky: Coase is the economist who asked and answered one of the most famous questions in all of economics: if markets are such a good idea, why have firms at all? Why do we have these sort of institutional and organizational frameworks? Why can’t you just have everybody offer their services to everybody all the time, and have markets and contracts put it all together? And his answer was that there’s a huge transaction cost in simply finding who’s available, what they offer, making some kind of deal. And so what firms do, in Coase’s answer, is they lower transactions costs for group effort. And that gives them an economic advantage over markets in certain situations.

Everybody has understood since that article was published in the mid-1930s that there’s a Coasean ceiling: a point past which, if a firm grows too large, it just breaks down.

What we all missed, because it was never really an open question until now, is that there’s also a Coasean floor. Which is to say, there’s a set of group activities that would create some value but it isn’t worth forming an institution to create.

And the Flickr photo streams are a perfect example of something that’s beneath the Coasean floor. The costs of being an institution are too high to make the activity worth pursuing that way. But if you can get people to do it for themselves, you can create that value anyway. And that value, the value that’s under the Coasean floor, is I think one of the really big surprises of the current era, which is: now we’ve got places where we don’t need institutions, necessarily, to take on large or complicated tasks. We’re actually seeing kinds of value created that were simply unreachable by society previously.]

[ADDED 12/05/08: Is knowledge hoarding all about your pay cheque?]

Related:
k-flow
Tap into the social capital

May 1, 2008

Roundup : YouTwit, Twist, Twistory, Twerp Scan, Twitternothing

Filed under: tools, roundup

YouTwit - see your tweets and people you follow on Google Maps, nice and easy…here’s the rest of the geo tweets apps.

Twist - see Twitter trends on a graph, once a upon a time we could do this on Twitterment.

Twistory - subscribe to tweets in your calendar
[via TC]

Twerp Scan - make a list of your contacts by how many people they follow eg. mark all of my followers who follow more than 5000 people.

Twitternothing

BONUS LINK
Twisney [via channel 10]

April 29, 2008

An ecosystem is emerging

Filed under: km, emergence, collective

A lot of people have different views on “emergence”, stating that this is the true essence of “enterprise 2.0″.
Using blogs and wikis doesn’t necessarily mean you are being social or are doing “enterprise 2.0″, it’s only when you these tools are certain way, and ultimately when a new social organisational culture has emerged.

Further to this, the best kind of “enterprise 2.0″ is when the participation and contributions are not just Directed In-the-Flow social ways of doing tasks, but moreso when people are Volunteering Above-the-Flow tacit knowledge.

Emergence isn’t just what content emerges from using these social tools, that would have never otherwise emerged. It’s also that these social tools are unstructured (not rigid) allowing people to use them for whatever purpose they like…rather than desiging tools for a specific purpose, we see new ways emerge in how people use these free-form tools.

For more see my posts:
Collaboration, Emergence and Culture
Why km 1.0 failed in a nutshell
KM 2.0 : catalyzing voluntary participation

Emergence is technology populism
- people start using a social or productivity tool as it helps them get work done, and it spreads virally
- it emerges as a tool of choice and method of choice to get things done

Emergence is similar to above but deployed by the enterprise as a bottom-up approach
- a pilot with ground level people may spread virally by word of mouth (rather than a roll-out)
- it emerges as a tool of choice and method of choice to get things done

Emergence is invention in the ways people creatively use free-form unstructured tools
- a team uses wikis to gather input from everyone to make a list
- it emerges as a great use as everyone is now using wikis this way

Emergence is collective intelligence
- a wiki is used to start a glossary of terminology and acronyms used by the enterprise
- it emerges a massive glossary, like wikipedia, via the collaborative input by the whole enterprise

Emergence is evolving ideas
- people have distributed blog conversations and leave comments
- it emerges a new concept or solution…an initial blog post may of had nothing to do with the end solution, but it’s existence spurred related ideas, and debate within the collective evolved a concept that no-one person thought of at the time

Emergence is seeing patterns in explicit data
- people that tag their wikipages, blog posts, bookmarks (folksonomies), etc…are contributing to a collective tag cloud
- it emerges concepts people are talking about, and we can see what they are most and least talking about…this tag cloud analysis reveals what’s going on in the enterprise and decisions can be made from this raw data

Emergence is seeing patterns in implicit data
- people click things leaving behind a recorded trail of what they pay attention to (clicks stream)
- it emerges a way to graph offerings like What’s Popular, and Personal Recommendations

Emergence is a new culture change in organisation dynamics and autonomy
- people are being socially productive using social tools; by participating, contributing, being visible and having conversations, they are drawing on the social captial to get things done, learn and create
- it emerges a learning organisation of an autonomous nature where people are tuning in and particpating to knowledge flow…you are aware of what’s going on, and perhaps the right projects and tasks fall into your lap (the right person is doing the right job as the enterprise social graph is aware of everyone and everything).

Explanation

Andrew McAfee
“Enterprise 2.0 is the use of emergent social software platforms within companies, or between companies and their partners or customers.”

Mike Gotta
“The emergent use of social software platforms” vs. “use of emergent software platforms”

Mike Gotta
“Enterprise 2.0 is not about “all collaboration”, “all types of information sharing” or “all types of communication”. The context of E2.0 is anchored around “emergence”. Addressing organizational dynamics, which includes culture, is important to fully leverage and sustain the goals associated with E2.0″

Gordon Taylor
“The traditional approach is to build something autocratic, and deployed from the top down, that works along vertical reporting lines. Working this way, silos of information are preserved. and communication is kept within the traditional areas.

The emergent approach is work from the bottom up, in a manner than allows the system to spread virally along horizontal functional lines. By making the system less restrictive, and easy to use the system is more likely to become the solution of choice for knowledge workers. And as they communicate better, they share information and increase their awareness.

For a system to be emergent, the emphasis needs to be on how quickly the users will adopt the system rather than on its structure. That explains why a hallmark of these Web 2.0 technologies is that they are accessible and less restrictive.”

Gordon Taylor
“Emergent systems are decentralized, self-organizing and organic — the antithesis of the top-down, rules-based engineering approach taken by most enterprise software. To build an emergent system — an ecosystem — you target the bottom of the pyramid, building it up one user, one connected node, at a time. The value of an emergent system is derived from its flexibility, adaptability, and responsiveness.

Emergence isn’t another feature to add to the enterprise technology stack. Emergence isn’t a feature at all — it’s an approach to solving a problem.”

UPDATE: I just noticed Ray Sims has a post about emergence.