Library clips

sharing ideas thoughts and feedback

February 16, 2011

Enterprise activity stream - email conversations with externals staying threaded in the stream

On my tumblr blog I posted about email being sucked into an activity stream (dashboard), and the owner being able to make it public, or replying to the email from within the stream, etc… The idea being that email, is just like flickr, youtube, delicious…it’s just yet another source…but it’s different in that people only see it, if you click a button to make it public.

I suggest you read the tumblr post to get up to speed.

Now…

Imagine an enterprise version of friendfeed as your social network/microblogging/activity stream eg. Socialcast

Firstly, let’s get this out of the way…when having a discussion, and you need to write an extended reply, you don’t need to use email as the enterprise activity stream allows more than 140 characters…which is good as this doesn’t split up the conversation.

Now imagine if an enterprise activity stream allowed you to follow your email client (of course no-one else could do this for privacy reasons).

Wow, bye bye email inbox, as the enterprise activity stream is the new inbox.

From within enterprise activity stream you could reply to this email which would send an Outook email, or if the receiver is on enterprise activity stream you could reply with a comment…look at that a conversation thread where each element may have happened on different products.
At any point you can cherry pick one of your emails that you see in your enterprise activity stream and make it public in your profile stream. People following you will now see the Outlook email title and click it to read it.

You could also do this at the time of sending your email from Outlook ie. when you send your email to someone it will also appear in your enterprise activity stream profile.

Same when replying to an Outlook email from the enterprise activity stream ie. when in the enterprise activity stream you send a reply to Outlook and it can also be made public in the activity stream

Hmm, not sure if you could send an Outlook email (not a reply, but a new email) from within the enterprise activity stream…that would be like sending a tweet from Friendfeed…not a reply tweet, but an initial tweet..or a direct message, etc…

Now imagine this…

You are using your enterprise microblogging/activity stream to do a task with co-workers.

If you need to liase with someone in your company who is not on the task, you can still use the enterprise activity stream
eg. in the comment of the task post you could @reply to this person on the edge of the task, and they can comment back.
This way your co-workers know what is happening on your leg of the task ie. you don’t have to tell them (report back to base), or narrate your work…in this instance, there is no such thing as an “update”, as they “observing” you work in the open.

Now this ain’t gonna work if the person on the edge of the task is an external party eg a vendor, supplier, client.

But what if you were in Outlook and sent the supplier an email and also chose for it to post in the enterprise activity stream as well….or perhaps you are in the enterprise activity stream and choose to create an email which becomes a post as well (or create an email which becomes a comment within a post)…this is sending the Outlook email from within the microblogging app itself so it instantly becomes a post or a comment.

Voila, your co-workers know exactly what stage you are at. They don’t have to ask you how you are going with the supplier, they already know, as you cross-posted the email you sent the supplier as a comment under the task post in the stream…this didn’t have to happen after the fact, this cross-posting can happen at the time you are sending the email (keeping in mind the email can be sent from Outlook or from within the stream).

Now when the supplier replies to your email you will see that in Outlook or your enterprise activity stream, depending where you are at the time…we hope that our head is no longer in Outlook as the enterprise activity stream is the new inbox/dashboard.

If you are in enterprise activity stream at that time, you can click a button to make it (the email reply from the sender) public so it appears as a comment.
If you are in Outlook at the time, you somehow have to also be able to make it send as a comment to your activity stream…I haven’t thought this through technically or how user-centric it is (ie. you don’t have to think). Making an email cross-post to the stream as a post is easy enough, but to cross-post it as a comment within a post means you need to email it to the post email address (or something like that), which sucks as it means you have to hunt around for this emailID, which is not smooth and user-centric…it would be a hassle…drag and drop would be nice :)

July 19, 2010

Enterprise microblogging : you no longer have to report back to base

This is a follow-up to my post Enterprise microblogging needs a facelift to rival email.

In that post I talked about adding an item in the stream to your Watchlist

  • This way you can keep in the loop about a conversation without you having to be a poster or a commenter

I also talked about communally grouping items via contributors tagging them with a hashtag

  • This way you can keep in the loop about the greater task that is generating all these items

Differences

  • You are not being cc:ed, rather you "pull" the content to you (filtering your own information)
    • you can be @mentioned which is like the to: or cc: field
      • but this won’t happen in every post and comment, so it’s up to people to add it to their Watchlist
  • The sender has an understanding of who needs to be involved in a conversation, but this is not always apparent at the start of a task, and there are plenty of people on the edges who need to be consulted that emerge
    • Now anyone can find a conversation, add it to their Watchlist, get involved

Deeper than In-the-flow and Above-the-flow

A while back a defining post was made on the difference between working Above-the-Flow (volunteering to share information and experiences based on engagement, trust, audience, reciprocity), and In-the-Flow (communicating and asking questions about tasks using social tools rather than email…doing what you are already doing in new tools).

Well what I want to describe here is going deeper than In-the-Flow…to the artifacts of the activity itself.

Example

We have a web conference about a task that involves people across teams.

We set up a group space.

We use this group space to ask the task team questions.

We use this group space to communicate our individual progress to the task members.

Why do I have to go to a blog to describe to other task members about my progress?

Let me explain…

An action item that came up in the initial meeting was for a member of the task to contact someone in IT to find out where we can host our database.

Once he found this out, he communicated back to the task members by fowarding his email conversation with the IT guy

OR

By blogging about this email conversation he had.

But you kind of feel silly blogging about something when you can just easily fwd it…it’s just easier.

Yes blogging it stores it for all to see, and keeps the conversation centralised…but it needs to feel natural. One positive step is to forward your email to the blogs email address, this way further comments about this is centralised around the blog post.

Deep In-the-Flow (Embedded In-the-Activity)

There is a better way…

Why report your progress by updating task members about it (whether in email or a blog)…

when instead they can see your conversation as it happens.

MICROBLOGGING AND HASHTAGS

Watch what happens when all task members follow the hashtag for this task:

Task Member B’s filtered stream of #DMS_dev

Hi @ITguy we are looking for a place to host our new server…blah blah blah…#DMS_dev
Posted by TaskMemberA

Comments expanded

ITguy - No probs we have room in our data centre in Australia

TaskMemberC - When do you think this may happen

ITguy - We will have a meeting tomorrow so can give you a date

TaskMemberA - do you have a goto person that we can liase with

ITguy - just got out of a meeting and @ITguysfriend will do the hands on work, no date yet

ITguysfriend - I’m travelling soon, so it would be good to do this ASAP

Notice here how Task Member A does not have to write a blog post or forward an email to Task Member B or any of the other task members.

Why? Because all the task members are following the hashtag.

Task Member A is no longer the middleman to report the conversations he/she is having at the edges when doing their part of the task. They don’t have to forward an email or report progress as everyone can already know "as it happens."

ie. when on a task we don’t just converse with task members, we need to speak to random others in the organisation to get information from, authorise, or simply consult with as part of a task member doing their bit of the task

All task members (and anyone else) can now see the conversations each member is having with both task members and with indirect task members they need to consult with.

Indirect task members such as @ITguy can get involved at anytime without having to go through a task member; as long as they use the hashtag all task members will be in the loop.

What I’m getting to is you don’t need to report status or progress, as everyone can already see the conversations you are having.

Traditionally, if I were to report back to the group the progress of my task I would examine all my email conversations and write an email or a blog post on my progress…kind of like a real informal reporting. Or I would upload my emails which no-one will read.

But now people can have access to the artifacts without me having to forward them, or without me having to report about them.

This is a major difference between a closed system like email and an open microblogging system with the use of hashtags.

To reiterate the two main theme’s here:

1. People can now see the raw conversation as it happens, you no-longer have to report back to base…as people at base are privy to your conversation as it unfolds.

2. As a task member I am no longer a middleman in interpreting and communicating the progress of my part of the task, as you can see what I’m doing. Plus other task members can interact with the people on the edges (indirect task members) on the details of my part of the task.

Where it doesn’t apply

I’ve made clear that this works as a replacement to email, but when doing your part of a task you may have phone and face-to-face conversations with 3rd parties…in that case you do have to write a status update reporting your progress

Work products Deep In-the-Flow (Embedded In-the-Activity)

Aside from open conversations with both members of the task and people on the edges that are consulted about various parts of the task; we also have output documents eg. deliverables and supporting materials.

We no longer have to communicate (email or write a blog post) to people that we have just added a document related to our task. We simply do this at the time of adding the document.

The Activity stream of the microblogging app will suck in items added to the Document Management System (DMS) via an API

Task Member A is adding a document to the old DMS

Click here to browse and and Add the document.

Click here to add a description:

Here’s the information sheet about our server #DMS_dev I thought I’d better @mention you @ITguysfriend as pushing this to you may get to you quicker as I recall you are travelling soon
Posted by TaskMemberA

CLICK TO SUBMIT

If we take another look at the hashtag stream we will see that the act of adding this document and a description has resulted in posting a new item into the stream (see the 5th post down)

Task Member B’s filtered stream of #DMS_dev

Hi @ITguy we are looking for a place to host our new server…blah blah blah…#DMS_dev
Posted by TaskMemberA [Expand Comments]

Hey @Qualityguy I need you to sign off on this paper work…basically it says…blah blah blah…#DSM_dev
Posted by TaskMemberC [Expand Comments] [Link to Document]

Hey main members of this task, what do you think we can call the new DMS, any ideas #DSM_dev

Hey @Marketingguy are you able to come up with a brand logo for our new product, I gave you background to this task on your voicemail…also see linked document #DSM_dev
Posted by TaskMemberB [Expand Comments] [Link to Document]

Here’s the information sheet about our server #DMS_dev I thought I’d better @mention you @ITguysfriend as pushing this to you may get to you quicker as I recall you are travelling soon
Posted by TaskMemberA [Link to Document]

Comments Expanded

ITguysfriend - just about to hop on a plane, sorry, will login when I land

ITguy - that’s OK I’m gonna get @ITguysotherfriend to do this if she has time

ITguysotherfriend - no probs, I’ve added this to my watchlist and read up on other related posts in this hashtag, so I’m all up to speed

TaskMemberC - is Thursday OK

ITguy - I’ll be in the office on Friday so we’ll do it then

ITguysotherfriend - OK with me

TaskMemberC - great

ITguysfriend - just landed, good to see it’s all sorted

Summary

This post focuses on a sweet spot in performing tasks.

Why?

It’s as easy as email.

You don’t have to set up a group space.

All you need to do is use microblogging (utlising Watchlists and Hashtags)

But the real focus of this post is about what happens on the edges.

All people on a task go off and do their bit and either report back on progress via email or a blog. They are the middleman between the task members and people on the edges who they are consulting with in doing the task.

Now we don’t have to report back, as task members (and anyone for that matter) can see the the raw conversations with people on the edges as it happens. Both other task members and people on the edges can interact without having to go through a particular task member.

Related

This is taking my ambient awareness post to proper task use, and brings back into fashion Jim McGee’s post on the loss of observable work.

Paula Thornton talks about artifacts of work, and this is exactly what I’m tackling:

"Conversations are artifacts of work. Do not confuse artifacts of work with work products. Work products often miss much of the “real work” that occurred. Any evidence of “real work” qualifies as an artifact.

KM tended to focus on “work products” (often most closely aligned with ‘the explicit’). But the goal was never to document the “implicit” (as was often postulated), but simply to make it observable by others."

This post is not so much the difference between conversations and the end product (deliverable), but more so how the conversations happen, and how we don’t have to report progress on our daily work on achieving our task.

Well let me clear that up, sure if I’m doing my own brainwork I will report my results, but if I’m having conversations with people that I need to consult with to achieve my task, well then I don’t have to report that this took place, as other task members already know, due to me using the task channel (defined by assigning a hashtag) to converse with people on the edges…all without them having to be part of an official group space.

July 16, 2010

Enterprise microblogging needs a facelift to rival email

OK, here’s the solution upfront. You can read the rest of this post to know why this needs to happen.

SOLUTION

Requirements

  • More than 140 characters
    (like Yammer and Socialtext Signals)
  • Inline comments; also posts in their own right
    (like Yammer and Socialtext Signals)

Request

  • Add a post to your Watchlist
    • like an RSS Reader but subscribing at the post level
    • Imagine rather than "favouriting/liking" a post, you are actually subscribing to it
    • This way you can be notified of any new comments about a post
  • Tag posts in your Watchlist
    • a tagcloud/list would be accessible in the left hand pane of the microblogging app
    • list preferred posts from your Watchlist in the left hand pane for one click access
      • see it turn bold-which signifies new content-and displays a number-which signifies the number of new comments in that post
  • Follow a Hashtag
    • like saving Twitter search queries in your sidebar but more like an RSS Reader subscribing to a tag
    • Click on it to view as a stream
    • Reason for this feature is to catch new posts (and comments on those posts) on the same topic or task
      • accessible from the left hand pane of the client and turns bold-which signifies new content-and displays a number-which signifies the number of new posts and comments in existing posts

These requests are necessary to catch posts and comments that stream by that are important to you.

Microblogging in the enterprise is a different context from the consumer web; people are doing real work and need to be able to catch important posts in the stream. It’s not about just dipping into the stream and having a swim, it’s not just about following interests, it’s more about my boss, or people from a task I’m on, have posted a few things and I can’t afford to let them stream by unnoticed, I need the notification/subscription/follow mechanisms set up so I don’t miss anything essential.

This doesn’t happen in email, you don’t have difficulty sorting out the spam and the friendly email from the task type email…you don’t really miss seeing an email from your boss. This needs to be the same in enterprise microblogging; but it’s not as easy as email as the stream is much more a firehose than the email inbox.

Mary Abraham has talked about TMI (Too Much Information), and how do I differentiate the "good to know" stuff (it’s great to be aware of what’s happening in the organisation), from the "essential to know" (what’s the latest update I have to action today).

This brings up the need for enterprise microblogging to get a facelift by including a way to catch information that is essential to you…basically it needs a couple of simple features and functions.

READ ON

Not long ago I posted on how we do knowledge work via email because it’s easy, but we suffer later as it’s messy…and we miss out on these conversations living in a central place where others can be aware (and for possible diverse input), and later can be searched.

I explained the alternative in using a blog or forum. Which is OK, but it’s simply not in our flow to jump to a group space to communicate, especially when some of the people you want to communicate to are not subscribed to your blog.

At the moment if I need to have a conversation with a random group of people I use email (this is my ad-hoc tool)…I may even add an attachment if we need to do more than just converse. I’m not about to set up a group space for a conversation that may last a week or even a moment…it’s way too much effort.

Hence, no adoption of social computing tools for ad-hoc work. If we do get this design right, then not only will we get adoption for activity based work, but also for learning and sharing sites like online communities, online team spaces, etc..

It’s not just email; if I need to grab some relevant parties or have a discussion about a task we email or phone each other, and then get a room, or go to someone’s desk and have that chat. I want to be able to assemble this way using social tools, where there is not so much a group space, but a conversation space…kind of like a Twitter hashtag conversation, or a Yammer threaded post.

Group spaces (like CoPs) require facilitation to keep them active and you have to shift context to use them depending on the topic of your conversation, whereas network interactions are more transient, and only exist as long as they need to (just like email conversations).

Keith Swenson shares his pain:

"The solution is to make a shared “room” where all the toys can be shared equally within a group. That is the solution that many approaches have taken, and it is not difficult. But someone still has to set up the room in advance, in anticipation of the need to share, and most people will not take this step. It is just easier to send the documents as an attachment and force the work onto everyone else. In groups that I work with, even making the room available to people, they rarely get used."

What I’m alluding to here is the need not for a group space, but simply an ad-hoc conversation space…and networks, not groups is the answer.

In comes microblogging…

Here’s a fictional example…

@bob @sarah @jason @neil @brad @sally @jeff @denali @arielle @peter as you know the development of our new DMS has been on hold due to low resources. Well now there is an initiative happening that needs the use of a new DMS to store its documents, so they will sponsor it’s development…blah blah blah…please tell your people
Posted by John Tropea

Comments

Bob - do you have a new roadmap?

Sally - what’s the deadline?

John - the deadline is August 31st, and a roadmap will be shared soon

Neil - what is the initiative you are alluding to, and how far will they sponsor it’s development

Jim - hey guys just came across this conversation as I follow John. We are running a global Quality initiative and need somewhere to keep our output, so we are sponsoring the new DMS

John - apologies Jim, I forgot to @mention you in the original, come to think of it I forgot to add in our IT representative, hey @abby join in the conversation.

Jody - Neil told me about this resurrection, congrats guys

Abby - Hey guys, we ordered the new servers yesterday

John - Thx Jody, yes we are indeed very happy about this

Samantha - Hey guys, I’m from the DMS team, we are looking for some work for our intern, could they possibly get involved

So far so good, this is the type of thing you can do on Yammer as it has inline comments (and maybe Twitter soon via Twitoaster)

But the issue we have here is with notifications (which I will tackle further down in this post)

What new capabilities does microblogging bring to the table

Others can read this open conversation in the stream and be aware and get involved (diverse input…possible clashes with other tasks or what other teams are doing can be revealed as conversations are in the open to be found):

  • whereas in email it’s just the recipients and people who have been forwarded the email
  • microblogging makes for more chance of collaboration and awareness to better align and cooperate with other units

The recipients in the original post can re-post (retweet) the post including an @mention to other people so they are aware of it, or to get involved…or alternatively can leave a comment that includes @mention to others.

The recipients can re-post (retweet) the post to their group space (eg. as happens in Yammer group or Socialtext Signals) so their team can see the raw conversation, if they have not already seen it stream by anyway in the public stream

  • what I like about this is that people down the hierarchy can see the raw conversation, not some filtered re-interpreted conversation. And of course if the post has failed to reach them via their manager, there is a chance they will still see it as it’s online in the stream for anyone to see

The conversation is in one location and not messy like email, no-one is left out of the loop, new comers can join and see the past conversation…it’s searchable

And of course it’s essential that posts have a comments thread, and more than 140 characters to post content.

But what’s missing here…

NOTIFICATIONS

If we follow the Facebook model…

John is getting notifications that people are commenting on his post

Bob, Sally, Neil, Jim, Jody, Abby and Samantha are also getting notifications as they have left a comment…

BUT, they are only being notified of comments that have come after their comment. So they have to catch up reading on the earlier comments, unless they have already seen them stream by (remember comments are threaded, but are also a post in their own right)

Sarah, Jason, Brad, Denali, Arielle, and Peter ARE NOT being notified of any comments

Until microblogging can duplicate this uniqueness of email, it will not be as useful to do actual back and forth work

FILING/BOOKMARKING (FAVOURITE/LIKE)

When we have this typical conversation in email; people will individually file this conversation in a folder. This way they can find it later.

In microblogging we can favourite/like the post of this conversation so we can come back to it later, but we also need to be able to tag these favourites so there is more context to help us find them later.

And we need these tagged favourites browsable in a tagcloud/or a list on the left of our microblogging app, just like we have our email folders in the left-hand pane.

But we also need to be able to list some posts from within our favourites so we can see them right there in our left-hand pane.

Maybe they are not called favourite/like, perhaps Watchlist is better.

WATCHLIST

Ok, I think I just solved our notification issue…

What’s required is a Watchlist feature.

The recipients of the original post can click the Watchlist link on the footer of the post (it will also ask them to tag it ).

This will put the post in a tag in their tagcloud, and also list it under the tagcloud so at a glance they can see the current important conversations they are following.

When a new comment is added to a post that they have in their Watchlist it will become bold with the number of new comments.

See what’s happening here, a Watchlist is catching something for you that you may miss streaming by. Kind of like an RSS reader, but at the post level.

If the conversation becomes old, they can then remove it from their Watchlist and later find it in their tagcloud if they need it

MICROBLOGGING APP

An important aspect is that the microblogging app becomes the new email…so there is a battle here.

Similar to the screenshot I linked to in my previous post, perhaps microblogging can be integrated into the email client, and perhaps it’s no longer an email client, perhaps email is just a feature of Inbox 2.0.

The microblogging private message feature can perhaps replace email.

So why do we still need email?

We still need to email with people that don’t have access to the microblogging system. Our clients, vendors, friends, family, local shops, etc don’t have access. What I’m saying is different microblogging platforms don’t connect via a protocol like email does.

What about groups?

Earlier I mentioned microblogging groups, all this means is that you are not posting in the public stream, instead that post just appears in the group stream. And to catch these posts you just have a group tab to see them.

This is a great way to filter the firehose to see stuff that’s important to you…but often a task I’m in doesn’t really involve my whole team, instead it’s me and a handful of others from various teams, so the group stream doesn’t help here, instead we ad-hoc groups need a hashtag stream to filter the firehose (which I will tackle further down in this post)

Tag based forum

So what’s happening here? What is Twitter or Yammer? It’s conversations, but not confined to groups, instead it’s one massive group, but moreso a crowd as not everyone knows each other, just like you don’t know everyone in your workplace or suburb you live in.

So really it’s not a group, it’s a network.

Which kind of makes it like a giant forum, or a giant blog.

At work we have groups (CoPs) and each one has forums and blogs.

So to have conversations about a topic you need to visit the right forum/blog in the right group, and further to this you need to be a member, and you have to be a subscriber.

What if the appropriate topic doesn’t exist yet; I’m not about to create a forum and get people to subscribe…further to this they also have to become a member of the group space that they may not want to do.

For the sake of being open, this is way more difficult than email.

And if all we are having is one conversation I don’t want to subscribe to a forum and get further content that I don’t want to read.

And as mentioned earlier I want an ad-hoc conversation that doesn’t warrant the setting up of a space…you don’t have to do this in email.

Over 4 years ago I posted on Tag-based forum networks (I wonder if the idea for Twitter came from these sites)

It’s basically the idea of microblogging where a question about any topic can be asked, and the question is tagged, and further similar questions can be tagged the same so these questions can be collected into a browseable space.

Which brings us back to our fiactional example…

Collecting posts in the stream that are about the same task

The fictional example in this post is perfect for one off conversations, more appropriate than email and more designed to how we behave over having to go to a group space. This is not about groups, it’s about ad-hoc conversations.

Now what happens, is that the conversation stream on that post can get really long and cover lots of questions, which really should be their own posts.

What I mean is; what if this one-off ad-hoc conversation is part of a bigger task that requires many conversations on various items pertaining to the task. You’d hope that you could collect all these conversations into one browseable space.

To follow our example John needs to ask a question or give an update about the task. So again he has to @mention various people in a new post. This time he might @mention only a couple of people as the question or update is more contextual.

But what results is that unless all the recipients from the 1st question see this new post in the public stream they won’t be aware of progress…it’s not essential they see it otherwise John would have @mentioned them, but still the same they may want to be aware as they are part of the greater task. And for all John knows maybe it turns out it is essential for someone else to see it…that’s the beauty of these tools in that the it circumvents the sender having the power as they cannot always know who needs to know what.

Again people who see this post can tag it in their inbox and also add it to their watchlist so they can follow the conversation…keeping all the items about the task in a bucket.

The issue increases…

If people that are not @mentioned want to be in the loop about this task they have to catch these posts coming through the stream, there’s a good chance they are gonna miss them. What if you go on vacation for a few days. Are you gonna go through thousands of posts, add to your watchlist and tag them. How are you gonna differentiate the posts in the stream that are important to you.

So everyone will be doing the same thing, picking out these posts and personally tagging them to their collection.

See what’s happening here, we end up using microblogging just like email. Sure it’s open so you may catch these items race through the stream, but we need a way for the system to keep everyone in the loop on every conversation about the task, even if you it’s not your part of the task, it’s still good to be in the know of the greater picture.

And further to this, in the future we want to look back at all the conversations about that particular task.

In come hashtags…

In our example the 2nd post could have a hashtag #DMS_dev, and then perhaps the 1st post could be re-edited to add this tag as well.

Then anyone can follow this hashtag, which is listed in your microblogging app sidebar

When there is a new post within this hashtag, the hashtag in your left-hand pane would go bold and display the number of new posts. The same would happen if there was a comment on an existing post. Just click the hastag to access the new content.

In this scenario what you could do is remove the 1st question off your Watchlist and remove it from your personal tag cloud. As now you are following the hashtag stream which is accessible via your hashtag list or cloud.

A hashtag stream would actually be similar in a way to a group stream, but it’s post-created rather than pre-created.

NOTE: When you think of it following a hashtag would be similar to saving a Twitter search query in your sidebar, but more like an RSS Reader subscribing to a tag

So there you have it…

  • a way to follow ad-hoc conversations (using a Watchlist)
  • a way to follow many conversations about the same task (following a Hashtag)

This design has the uniqueness and ease of email in ad-hoc conversations, but the benefits of the awareness and emergence of microblogging

I haven’t played much with Google Wave or Socialwok (I guess 9cays can be included), but these may be the closest tools to my thinking…it’s not about groups, it’s about the conversation, and similar conversations can be channeled into a unique tag that becomes a type of group space (or channel) on-the-fly.

Perhaps ActionBase is worth a mention:

"A task oriented email client will behave like a wiki document in the sense that once you send it out, any response, question or comment made by recipients or yourself, will all happen on the same email entry… all the relevant information under a single line item - THIS IS COLLABORATIVE EMAIL. In ActionBase we call this email - ActionMail. ActionMail is the next generation of work email which is task oriented rather than message oriented."

Output

Oh yeah, where is all the output, where is the documentation for the task kept.

This could be kept anywhere it doesn’t matter. But somehow the Hashtag page needs to be able to store links to where stuff is kept.

Pull

But there still is one big difference to email, this is mostly still a "pull" system where you add posts to your Watchlist, or follow Hashtags in order to be updated about new content.

Sure it starts off as "push" for some by way of @mentions, but then it becomes "pull" if you need or want to be further updated of new content without having to constantly @mention.

For others unrelated to the conversation it’s all "pull" for them as they were not @mentioned in the original post.

In saying this:

…if you publish the post or have left a comment then you will be pushed notifications by the system, but if you haven’t done one of these things and it’s pertinent that you are aware, then you better add it to your Watchlist, or follow the Hashtag.

Yeah, but no…

In the first part of the fictional example I mentioned that the lack of notifications means some people that were @mentioned in the original post won’t receive further comments unless they make a comment…hence my idea to pull it to yourself via a Watchlist.

Facebook have a private message feature where you can have a group conversation and all involved received comments by default (you don’t have to leave a comment to be notified of new ones). This is less messy than email but is still closed like email

End thoughts

I can only imagine so much, but without using such a system I won’t know if it’s too complicated. At the moment there are all these possible streams/filters:

  • Public
  • My network (people I follow)
  • Various group streams
  • @mention
  • Hash tags I follow
  • Watchlist (comments in a post I follow)
  • Notifications (comments on my posts, and on posts I have commented on)

June 23, 2010

Ambient awareness is the new normal, c’mon already!

About 18 months ago I posted on how the way I communicate and am aware of the lives of people I know is much different to my parents-in-law…to me it’s the new normal.

I’m not referring to explicit communication (sure this happens), but I’m referring more to just being aware without necessarily having to directly communicate or push a message to one or multiple people…directly communicating can often happen once you become "aware" of something.

In that post I mentioned that my inlaws swap long Christmas letters with their friends (once a year), so basically at the end of the year in one big gulp they become aware of what a family has been up to.

Sure they could be aware of many points shared in a friends Christmas letter if they had phone contact throughout the year, but you are not going to ring, SMS or email every person on your Christmas list each time something happens in your life…and ringing them to tell them about minor events like "I just landed in Hong Kong" seems ludicrous.

The difference here is that online platforms like my Facebook network operate on a different paradigm, we become ambiently aware of each other. Sure we can have directed conversations like phone calls, SMS and email, and in the Facebook context we can send direct messages, leave comments on updates and photos, but the big shift is that we talk about ourselves or something that has happened to us out loud, we broadcast this to a spot, and whoever subscribes to that spot, ie. our network, will see that in their stream. This is a shift in how we communicate, and an off-line version of doing this would make you seem a bit crazy, but in the online realm it works.

In fact, we are so ambiently aware of our friends lives via Facebook that when we meet up offline, we don’t have much to say to each other in the way of "how you been?"…this kind of becomes a non-question.

The other day I was on the phone to my mum and she told me my cousin landed in London. And I said I know. And she said, oh, have you talked to her. And I said no. She said well who told you. And I said she did. She was a bit confused. I then told her she broadcasted this on her Facebook profile, and people in her network like me get to pay attention to these updates, if we choose not to pay attention it just streams by. I said I can also choose to leave a comment on her update, or a gesture that I like it. If my mum were to ask, I wonder how long the plane trip took, I would say well the flight was split in two, earlier on she updated that she landed in Hong Kong. My mum was so amazed that I knew this stuff without having to be personally contacted. And from my cousins point of view, broadcasting it is much more doable than sending an SMS to a hundred people each time she wants to say something, and then one-to-one comments splintering the conversation.

In fact without these new online networks you wouldn’t have this type of awareness, it’s as simple as that…technology and it’s use affects and changes culture.

As you can imagine this happens all the time. My mum telling me on the phone about photos or a family friend having a baby. And I already know all this by being ambiently aware, unlike my mum I know this without having to have one-on-one contact (direct communication), or waiting to hear it from someone else.

I told her I even know what others say about my cousins update, even from people I don’t know…all without having to be in a tele-conference or email chain conversation. I told her when someone leaves a comment on an update it will appear in my stream that this happened. I told even when my cousin adds a new friend to her network I will also be updated about this, in this case my cousin doesn’t even need to broadcast this, she wouldn’t have any motivation to do this anyway, but instead the system automatically posts this update. Further to this I can leave comments on this update ie. we can have a chat around the fact my cousin has added a new friend.

I mentioned that whenever someone in my network uploads a new photo to the system they appear in my stream and float on by, but if I’m in one of the photos I am more explicitly notified of this.

Anyway, my point is why do I have close to total awareness of people in my personal life that requires low effort, but yet in the workplace I don’t have this ambient awareness!

In my personal life the “how you been?”, translates to what we hear in work meetings or weekly tele-cons eg “let’s go round the world, starting with Perth, John update us on what you have been up to in the past week”

In fact it may be more crucial to have micro-blogging/activity stream networks in the workplace as we share and work on the same/similar/related goals and tasks within our teams, across teams, workgroups, and enterprise wide…so the more we are aware, the more we can be on the same page, and have better coordination, cooperation and collaboration…surface opportunities (emergence), have the best people on the right tasks, and generally have the ability to be more responsive and adaptive.

This is impossible to do with email, phone, face-to-face…these all have their place, but now we can really do something new, or enhance what we do or what we have always wanted to do, that doesn’t require centralised coordination. Now our classic organisational problems of communication and awareness can for once realistically be addressed. Further to this it cascades into self-organising social productivity, much better than email which is our current self-organising tool.

I said once before we are moving from PC to SC ie. from Personal Computing to Social Computing.

And we are moving conversations from private by default to public by default.

Hopefully this comparison by story in describing this concept is useful in explaining online networking to people in the workplace as an alternative or a pre-cursor to: what it is, the benefits, how it works.

May 5, 2010

Skip the buy-in and get ‘em addicted!

Filed under: km, presence, change

I’ve posted before on how I think micro-blogging is a low threshold to participation as it merges the concept of reading, blogging, sharing links, chatting, connecting; into the same window…kind of like we do all sorts of communications through the email window. But more accurately the low threshold to participation refers to the level of effort it requires to contribute. Basically, my dad uses status updates in Facebook, but I ain’t gonna see him using a blog or wiki in a hurry.

In Michael Idinopulos’s post, Launch E2.0 broad, then go deep, he talks about how different tools require a different type of participation effort on the micro level. For example micro-blogging requires great participation (network effects) to take off at the macro level, but at the micro level it doesn’t ask much of the user.

Here’s how Michael says it:

"Some modes of collaboration have a really low threshold of participation: It’s very easy to get started on them because individuals don’t need a ton of engagement to find them useful. Other modes of collaboration have a really high threshold: Users don’t see the point unless they invest a lot of time learning and using the tools.

Historically, Enterprise 2.0 implementations have focused on collaborative tools fairly high participation thresholds: blogs and wikis. That’s not by design, it’s by default. Until recently, those were the only Enterprise 2.0 tools that showed potential for high-value business use. Since these activities required a lot of engagement, we smothered our pilot participants with training and encouragement–which forced us to keep the pilots small.

Today, Enterprise 2.0 participation is a whole different game. At the "low threshold" end of the curve, we have low-engagement tools like social messaging (internal "Twitter"), social bookmarking. By leading your implementation with these low-threshold tools, you lower the risk of implementation while still launching at the scale required for success."

This got me thinking about the recent use of Yammer by a few of us at work…I was thinking about Buy-in vs Just do it (Proof of Concept)

At work, like anything, to buy a new product and implement it requires you to get buy-in and all that goes with it…most often something like micro-blogging won’t be seen as important. It’s a hard sell…but once you use it you can’t do without it…people have to "feel" it to understand.

Here’s another approach.

Start using Yammer as a Proof of Concept. It’s free, they host a secure network for you based on your email domain. Then invite someone, and they will invite someone else, and it goes on.

If it takes off and people become hooked, it’s hard for management to point the finger as no one person is responsible for it’s use, and rather than taking it away, they will see that it must obviously have value, and they can offer an installed version.
NOTE: This assumption is based on people actually using it to sense-make at work, and not for personal chatting.

And get this, you can continue to use Yammer or another product like Socialcast, Socialtext Signals, etc. as micro-blogging is different than other content platforms in that there is no need for migration. As it’s more about the moment, once posts are a couple of weeks old they don’t really matter that much (I’m generalising here, but it’s more true than not). This means you can jump to another system without a worry.

When you use free tools as your Proof of Concept, and get people to "feel" a product, and hopefully hooked on it, there is more chance of fulfilling your vision, rather than the big and slow approach of getting hierarchy buy-in, strategy documents, charters, implementation and training requirements.

Grassroots DIY Proof of Concept is how you can creep something into the organisation without being faced by a wall.

Participants in such an informal program are called IT Rogues, but they are just trying to do their job better, and this should be noticed. Something like a rogue wiki is easier to be shut down and point the finger at as it will have an owner and a group using it…whereas if micro-blogging takes off, who do you point the finger at…and how can hundreds/thousands of people be wrong.

The only way I see my advice as a problem is if people use Yammer for non-business use…and if the business will have the problem of not trusting Yammer with their data being leaked.

But if they can see beyond this and want to penetrate the hierarchy, then this experimentation and failure approach is how to cleverly penetrate the hierarchy.

This approach doesn’t have to be done without consent, part of the strategy with the powers that be may be the use of Yammer as a Proof of Concept as a first step, and if this shows signs of success and value, then a second step will be taken

You don’t have to use a free hosted approach, there are many free download and open source micro-blogging products. This addresses the security issue, but then the finger can be pointed at the person who installed it. In this case hopefully instead of getting buy-in, mention that it’s free, and you will get an approval to test it out…little do they know this test may go viral, and become a tool people can’t do without. The power of hosted freemium.

But, what’s for sure is that the problem is not investment. Like Euan Semple says, "if you make the ‘i’ small enough, no-one will care about the R”…as long as the concept is understood.

Why spend time and money on the usual buy-in, strategy, implementation, etc…when you can just get a product download for free and experiment right now….cut to the chase.

The point of this post is that requests for a new product will be slow, may be disapproved, may be implemented the wrong way…instead now we are empowered to demonstrate proof that this is a really good idea buy using a free-hosted service…this wasn’t possible a few years ago

At a meeting 6 months later you may mention to your manager that micro-blogging is a good idea. They may agree or disagree, but either way not have any leadership or time in harnessing the value and passion of your suggestion. That’s when you can say, you want value in seeing how it supports knowledge workers to sense-make, check this out, we are already doing it

In a way, we now have the tools and type of service available that allows knowledge workers to disintermediate management as we have access to the resources we need and make the decision to use them…again this wasn’t possible a few years ago

The goal isn’t disintermediation…humans are self-organising, we do what it takes to create conditions for better sense-making, to be more productive, to be more aware

Yammer seems to have a great business model, as they allow people to get hooked for free, and then offer a premium version if organisations want their own secure version…it’s win win for both Yammer, and organisations.

List of "free enterprise" micro-blogging platforms (either secure hosted or install)

Sources

[ADDED 10/06/10 - Another idea is to join the vendor community. Our document management vendor has a new microblogging/activity feed module. They drink their own champagne by using this module on their customer community. If it’s a selling strategy, it’s only by accident, as we “the customers” find it very useful that we can connect with lots of the vendor staff and other customers like ourselves…good from an engagement, help, and co-creation point-of-view.

Now if I want my work to buy this module, “show and tell” is the most effective way…you have to “feel” micro-blogging. So I could simply show my boss how we work on the customer community using microblogging (getting things done, sense-making, engaging with people, building relationships, sharing)…my boss could even give it a go to get a real taste.

There’s nothing that says “Yes” to buy-in like “seeing and playing” what you want in action, it makes it less a prediction of success for your boss and more a certainty (given cultural constraints of your organisation)]

Get free blog up and running in minutes with Blogsome | Theme designs available here

Related Posts Plugin for WordPress, Blogger...