3
Nov

Off to Defrag, but here is a quick peek at enterprise microsharing late entrant Co-op, which launched October 20th and narrowly missed inclusion in the Enterprise Microsharing Tools Comparison report we released this morning.

My first impression is that Co-op is a bit like Status with time-tracking and an agenda view, but until we can dig in more I’ve added them to the matrix under the pure-play classification.
Picture 11.png
Integration with Iridesco’s other tool Harvest means time tracking in Co-op can be used for invoicing. They point out that microsharing can eliminate or reduce routine “status” meetings, and the agenda feature looks especially helpful for this.

Here’s the run-down:

Name: Co-op
Company:
Description: Co-op is a “casual” communication tool for small teams with built-in time tracking capabilities.
Inside Firewall: Will consider if there’s demand
Directory Integration: No
Twitter’s Functions: Most
Groups: Yes
Location: No
Sharing: Links
SMS: No
IM: No
Desktop Client: Future

Smart-phone App: No
Twitter Integration: No
Underlying Software Platform: Ruby on Rails
API: Soon
Twitter Compatible API: Future
Largest Company: N/A
Largest Group: N/A
Pricing /month: Free
Additional Notes: Integrates with Iridesco’s Harvest, a time tracking and invoicing tool. Agenda feature allows teams to plan out their days together, sharing who is working on what and what they will be working on later.

Related posts:

Want to talk to us about enterprise microsharing for your company? Please let us know.

Category : Touchbase Blog | microsharing | Blog
3
Nov

WE HAVE LIFTOFF

This post officially launches our first research report on the 19* applications vying to bring Twitteresque networking and communications inside the enterprise.

Download the .pdf here or use Scribd to view, embed, share or download. You are welcome to share it freely within your organization and networks.

Enterprise Micro Sharing Tools Comparison 11032008

Read All About Them (coverage of each application, from all around the web)

This post is an (evolving) index to blog and media coverage of the applications profiled in the report. It’s striking how much more coverage some applications have received, and while we’re not sure that’s a reliable mark of their suitability for the role, it’s certainly a marketing advantage.

What We Did
We compiled 19 criteria and basic information from 19 applications. Our work combines survey results, independent web research, verification of new features and analysis of how the 19 applications relate to one another and the marketplace.

We did not yet fully demo each application and we’re not choosing favorites in this preliminary comparison. We do mention observed advantages and reservations, and suggest six categories to distinguish between the applications.
Picture 10.png
We’ll cover much more on the rationale for enterprise microsharing, use cases, case studies, trends and future speculation in future research, on the TouchBase Blog, in speaking engagements and in client work. For the time being, I’ve compiled an Enterprise Reading List which ran as a post last night and has a permanent home under the Microsharing menu, above.

Have Your Say
Please ask questions, discuss the report and suggest future criteria and research topics in the comments here.

APPLICATIONS ON PARADE
Nevermind what we think, what have the pundits said?

Pure-Play Microsharing

Twitter
So much has been written about Twitter, Let Google be your guide.

Present.ly
Webware review, CNET by Rafe Needleman
Present.ly Takes On TC50 Winner Yammer, TechCrunch by Don Reisinger
Present.ly packs a solid punch against Yammer, ZDNet By Jennifer Leggio
Is Yammer Bad for Business? Robert Richardson

Communote
Enterprise Microblogging Ein Neuer Hype? by Dirk Roehrborn
Communote Presentations on Slideshare
Microblogging for the Enterprise, SocialMediaCamp, London

Trillr
Trillr Usage Inside Coremedia

Iron Feed (nothing available)

Enterprise Microsharing

ESME
ESME Enterprise Social Messaging Within an Enterprise SOA Framework, ZDNet by Oliver Marks
ESME: Is This What an Enterprise Twitter Could Look Like?, ReadWriteWeb by Marshall Kirkpatrick
ESME Enterprise Microblogging and Real World Business Problems, by Dennis Howlett
Enterprise Social Messaging Experiment by Anne K Petterøe

BlueTwit

Big Blue Embraces Social Media, BusinessWeek by Stephen Baker
Social Networking: The Twitterverse Debates
Porting Twitter Script for Ubiquity to BlueTwit
Twitter Behind the Firewall (Photos on Flickr)

OraTweet

OraTweet: Tweeting in the Enterprise
OraTweet Bot, an XMPP/Jabber Listener for Twitter
Social Observations, OraTweet Edition
On OraTweet and Open Social
OraTweet, Oracle’s Enterprise Microsharing Application, TouchBase Blog by Laura Fitton

Open Source Microsharing

Identica
Taking on Twitter With Open Source Software Daniel Terdiman, CNET
Twhirl Gets Pushy with Identica, CNET Webware by Rafe Needleman
Cooking With Linux: Warp Speed Blogging Marcel Gagne, LinuxJournal
Open Source Microblogging May Become Twitter Fallback, Ars Technica
Identica Federated Twitter, ReadWriteWeb
Identica is More About What Comes Next, by Chris Brogan
The Problem with Identica is…, TechCrunch

Jisko
Jisko the Open Source Microblogging Application
Jisko: Competition for Identica?
Jisko: Twitter Clone

Yonkly
Major Update to Yonkly: Widgets, Ads & More
Yonkly Groups and new Look
Backup Your Twitter Messages @ Yonkly

OpenMicroBlogger
OpenMicroBlogger Monetizes with Opening of App Store

Psuedo Microsharing

Prologue

Twitter - Public Timeline = Prologue, Mashable by Mark “Rizzn” Hopkins
Prologue Theme for Wordpress: is it a Twitter Killer?
Part Twitter, Part Basecamp, All Business, VentureBeat

Status (Status Blog is The What)

Integrated Microsharing

Socialtext Signals
Socialtext 3.0: Will Wikis Finally Find Their Place in Business?, BusinessWeek By Rob Hof
SocialText 3.0 blends Facebook, Twitter, and the Enterprise, TechCrunch by By Steve Gillmor
Exclusive video: SocialText brings enterprise Facebook and Twitter to wikis by Robert Scoble
Socialtext co-founder: Enterprise Twitter isn’t enough By Rafe Needleman
Socialtext Signals Marks Wiki Provider’s Entry into Enterprise Microblogging By Clint Boulton
Socialtext enters Twitter for the enterprise sweepstakes By Larry Dignan

Socialcast
Socialcast is FriendFeed for your business, CNET Webware by Rafe Needleman
USA Today (Quotes client Hot Topic)
Intranet Journal: Socialcast Harnesses Power of Online Conversations
NASA Case Study Presentation from KM World
A Social Function, Business Trends Quarterly Magazine by Analyst Jon Arnold

HeadMix
Best Buy’s Enterprise Twitter, ReadWriteWeb by Laura Fitton

Self-Serve Microsharing

Yammer
Yammer Launches at TC50: Twitter for Companies, TechCrunch by Erick Schonfeld
Yammer, a Twitter for the Enterprise, CNET by Rafe Needleman
Hmmmm Yammer, by Daniel Siddle
Mahalo on Yammer
Yammer TechCrunch50 Profile
TechCrunch50: 10 to Watch

QikCom
QikCom Adds Its Own Twist To Enterprise Twitter
Five Questions With: QikCom
Mahalo on QikCom
Competition Heats Up in the Enterprise Twitter Market

*And then there were 20. Not getting off easy, nope. In a perfect illustration of how dynamic this segment is right now, we noticed Iridesco’s Coop just as our research went to press, but were unable to get in touch with their team over the weekend to administer the survey. More to come on that soon.

Reblog this post [with Zemanta]

Category : Touchbase Blog | microsharing | Blog
2
Nov

Enterprise Microsharing Tools Comparison

Directly download the .pdf: Enterprise Microsharing Report

…or use the options below to view it online, embed it on your blog or email a copy. And please feel free to contact us about microsharing at your company. For use cases and more information, try this enterprise microsharing resource list.

1. Read it online using Issuu

OR

2. View, embed or download the document from Scribd:
Enterprise Micro Sharing Tools Comparison 11032008

View Fullscreen at Scribd

OR:

3. View and download the updated Comparison Matrix only at Scribd

View the Scribd matrix document full screen
Enterprise Micro Sharing Tools

Future in-depth research will include detailed reviews, market assessment, screenshots and case studies where available. At every stage we will provide free summaries, single-purchase reports and the option of subscribing to current ongoing analysis. We will also be rolling out additional research products including case studies, recommended best practices and interviews with CTOs, CIOs and other technology professionals in the space.

Almost all Pistachio research includes free, publicly shared information and insights. The exception is privately funded research which will only be publicly released with the express permission of our research clients.

We’d love to talk to you about microsharing at your company.

Category : Uncategorized | Blog
2
Nov

this page is a work in progress…

Some Good Overviews:

Clint Boulton: Gartner reports that Twitter and Facebook are being used productively in the Enterprise. They also argue against banning Facebook and Twitter use at work.

So How Does This Work?
After reading Something New Under the Sun and How to Hit the Enterprise 2.0 Bullseye by Andrew McAfee, I scrawled:

Wow. This so precisely aligns with my thinking on the potential value of enterprise microblogging. What he’s put into words about weak ties, querying the corporate “social network” for business intelligence, having spaces for unstructured collaboration, could all be done in a corporate microblogging space. The importance of ‘converting a potential tie’ and helping people stay on top of their networks of loose ties maps perfectly onto the Twitter “Village”/Fox Taming metaphor that I’ve talked about before.

Case Studies
EMC’s use of Twitter by Len Devanna
How Twitter Can Work in a Corporate Environment FastForward Blog on Zappos
Best Buy’s Enterprise Twitter on Read Write Web
Microblogging in the Enterprise Case Study: (Janssen-Cilaq and Jitter)

Product Posts With General Descriptions

Mainstream Media Coverage

Some History
With all this “new” talk of Enterprise Microsharing, it’s funny Twitter itself started as an internal communication system for the guys at Odeo. It worked so well they shifted focus to produce Twitter.

But it was a while later before serious discussion of “Enterprise Twitter” crept into the conversation. Like any good innovation, the idea pops up in parallel in many minds at once. Here is Niall Cook writing in June 2007 about internal business use of Twitter.

Bill Ives wrote Twitter Enters the Enterprise on September 5, 2007, but the blog and post he’s responding to are gone. JP Rangaswami writes in late December 2007 about the inherent difference in communicating via microsharing vs. email, and follows that up with thoughts on Publish-Subscribe and ways collaboration could play out. His thoughts in Twitter and Agile are worth quoting:

What I see in Twitter is this: The ability for members of a distributed peer workforce to describe precisely what he or she is doing, and to share that description.

Out of this, I can foresee enterprise magic happening. Geographically dispersed team members are able to help each other out because suddenly they have line of sight of each other’s tasks, activities and processes.

Shortly after, Daniel Siddle provides examples of how an enterprise Twitter could be used, including something like the status channels - information feeds employees will want to check regularly - that we recommend to drive use, especially in early stages of deployment. Dennis Howlett covers one of SAP’s early experiments with Twitter in the Enterprise and reflects on some uses, and Curt Monash shares what improvements he would make and how Twitter could be useful in the Enterprise. His follow-up Enterprise Twitter includes a good index of other posts until then.

Please check out our report Enterprise Microsharing Tools Compared

Category : Uncategorized | Blog
9
Oct

A couple of weeks ago, my colleague, Joe Cascio, and I did a guest post on Mashable.com called “Is the Enterprise Ready for Microblogging Tools Like Twitter?” I would encourage you to take a few minutes to read the post but in the event that you just want the Cliff Notes version (remember those?) here’s an outline.

WHAT WE COVERED
The post focused on three basic areas:

Business Value - essentially, the “why would businesses want to use a microblogging tool like Twitter for internal conversations. The six areas we called out were:

  1. an emergency broadcast system
  2. for knowledge management
  3. internal training
  4. expert identification
  5. seeing who the “connectors” were and
  6. better connecting to external stakeholders.

Key Considerations - in other words, what would some of the demands be that companies put on vendors that provided microblogging tools for the enterprise. This included considerations like:

  1. Single Sign-On
  2. reliability
  3. analytics
  4. security
  5. scalability
  6. groups functionality
  7. distribution and
  8. interoperability

Current Players - in this section, Joe and I mentioned a few of the obvious players in the enterprise microblogging space like Yammer, Laconi.ca and Utterli. We went on to acknowledge the fact that many of the white label community providers like Jive, Awareness, Mzinga (the company I work for) along with open source software like Drupal would soon be in the microblogging game.

READER RESPONSE
Not surprisingly, the “enterprise microblogging” post received a fair amount of attention due to the all the press the best known consumer microblogging tool/site, Twitter, is receiving in the press these days. What was most fascinating and the impetus for this subsequent post was the conversation that took place in the comments.

For one, a number of other enterprise microblogging application providers chimed in about the fact that they too were in the game. Most notable was A-lister, Dennis Howlett (also a contributor to this blog) who is doing some work for SAP’s microblogging project called ESME

ESME has all these capabilities - and more. (Disclosure: I”m part of the ESME team)

Serendipitously, the owner of the TouchBase Blog (and one of the pioneers in the microblogging for business space), Laura Fitton had posted on Mashable just a few days before with a matrix comparing a number of other players in this space. While we didn’t get a chance to include a link to Laura’s post, I did make a point of including a link in the comments.

Equally timely was the announcement earlier that day that SocialText had jumped into the enterprise microblogging game. Commenter, Justin Kistner

Just in time for your post, Socialtext announced Signals, which makes microblogging ready for the Enterprise, and not the other way around. Disclosure: SocialText is my client.

So what is the key take away from our original post? Well, we confirmed the fact that people are interested in enterprise microblogging. We also confirmed that there are going to be a whole lot more players in the space before all is said and done. That’s one of the reasons that Laura has asked Joe and me (notice I didn’t opt to speak “Palin-ese” and say “me and Joe”) to guest post on this blog from time to time.

What other key considerations need to be discussed regarding microblogging in the enterprise? For one, we could sure use some case studies. If you’ve got them, we’d love to hear about them.

Aaron Strout is Vice President of Social Media at Mzinga, where he focuses on creating business value through viral marketing channels, including blogs, podcasts, twitter, and webinars.

Pistachio Consulting is putting the finishing touches on our report “Enterprise Microsharing Tools Compared: Sixteen Applications Your Business Can Profit From” which will soon be available for free download on our site. You can also register to have it emailed to you when published.

Read related stories on the TouchBase Blog

Category : Touchbase Blog | Blog
7
Oct
Best Buy is sometimes called the

Image via Wikipedia

IBM’s got BlueTwit. Oracle’s testing OraTweets. SAP’s experiments include ESME, SAP Talk (laconi.ca), ShoutIt and apparently others. Yammer has an ad-hoc base at thousands of companies. But so far, no large corporation has rolled out microsharing company-wide.

Enter Gary Koelling and Steve Bendt, Best Buy’s Senior Managers for Social Technology, and better known as the guys who built Blue Shirt Nation. Drupal-based Blue Shirt Nation went on to become the prime internal enterprise 2.0 case study in Charlene Li and Josh Bernoff’s Groundswell. Now they’re about to launch Mix, an enterprise microsharing application to better network, problem-solve and share ideas among Best Buy’s 160,000 employees. Around 24,000 employees are already active on Blue Shirt Nation, so the conditions are ripe for Mix to become widespread.

Gary and Steve took time recently to tell me more about Mix, HeadMix (the application it’s built with) and their plans for a “mobile Blue Shirt Nation.”

Until a few weeks ago, there weren’t many publicly announced applications that could do something like this. When did you start looking for a provider to build an internal “Twitter” for Best Buy?
We started talking to Headmix in March or April of 2008.

You’d personally just started on Twitter then, so how did you know what you were seeking?
We’re both social bookmarking junkies because sharing links is such a fast, easy way to share ideas. You just smack somebody with a URL. So we wanted something like that for Blue Shirt Nation. Something that combined mobile access with simple link sharing.

We also knew that for Blue Shirt Nation, the adoption rate drops off fast as you climb the hierarchy. Executives just don’t spend a lot of time using their browsers. Mostly, they’re attached to smartphones and Outlook, with some General Managers texting. So other than the short formats, the idea of a device agnostic network was appealing.

The other group of employees we want to reach better are General Managers in the stores. They don’t have a lot of time, but they might be able to fire off an update while they’re walking from the front of the store to the back. Again, looking at Blue Shirt Nation, the majority of use (by retail staff) is during breaks and before or after work. So for this group also, we wanted something with mobile access.

How closely will Mix integrate with Blue Shirt Nation?
We looked at a deeper integration and ended up with something simpler. It will look like BSN, and the applications will keep each other informed, but Mix will function like the mobile arm of BSN.

What’s the time frame for rollout?
It’s coming very soon. One big hurdle has been waiting for carriers to give us the short codes. That was long wait. There’s also been a lot of technical work on integration and authentication. By mid-to-end October we’ll have it live within one territory (out of 8).

How do you plan to manage the rollout?
Within that territory, we’ll focus General Managers, store GMs, territory managers, district managers — about 200 people. Really, we’re still wrestling with the rollout plan. Some mix of internal communications, Blue Shirt Nation, territory meetings, enterprise events and email.

Do you think it will be easier or harder than rolling out Blue Shirt Nation?
Harder actually, because there are more choices now of where (employees) can go to communicate online in general.

What do you think of Yammer?
We’ve seen some activity on it. A lot of excitement and conversation at the beginning, but then it tapered off. People didn’t want to maintain their Twitter and their Yammer accounts.

Also, we see a problem with Yammer. There are what, 160,000 employees at Best Buy? It’s like a few of you are thrown into a dark room together. You don’t really know who anyone is or who to trust. You’re told it’s okay, they’re all employees, go ahead, talk. But trust is an issue. Who are these people? How do we know them? What can we say?

What factored into the decision to build out Mix using Headmix?
We liked that it’s simple, but had the extra features when you wanted them. It sounds goofy, but we really liked the Outlook plugin — that’s where our employees live. That will make it easier to use. We really enjoyed getting to know the developer team and we’ve liked how flexible the application has been for moving data around and having different features.

We wanted to be able to make changes really fast, and had usually gone with open-source systems for other projects. But in the last 4 months the UI, features and data structure have been very flexible.

What’s Headmix itself built on?
Ruby on Rails. Ben Moore is a friend-of-a-friend met via a Ruby users meeting.

What else can you tell us about Headmix?
It’s a different but familiar feature set to Twitter — a few more places that you can click. We don’t have it set up to talk to Twitter but it could be integrated. There will be something like groups - channels, to use Headmix’ term, that act like containers for discussion. It’s behind a lot of security and encryption but it’s still an SaaS model. Location won’t be in the initial rollout, but might be in the future.

What has been the corporate perspective on doing this at Best Buy? Was it a hard sell?
Headmix has some good demo videos and was cool about explaining basically what it does — “here’s the cool use cases we see, etc.” We were able to talk about use cases and they were willing to adjust. Potentially this is just the advantage of working with a startup.

The initial assumption was that it would be hosted within Best Buy. But as is the case with a lot of enterprise systems, we had to look at whether we could really support and host it in-house, more politically than technically.

So many companies miss “Just Try It.” Nobody wants to just go ahead.

That said, we’re in a unique situation with BSN Labs — we essentially have a license to try pilots and see whats going to take off. So the conversation was, us: “We’re going to have a mobile version of Blue Shirt Nation.” Management: “oh, cool.”

People have stopped asking us about metrics, measurement and goals. They see that it’s a cost of doing business. Nobody questions whether you need to have phones anymore, its assumed.

Nice position to be in.
Whatever happens, it’s going to be cool to try it. We’ll learn something. Sometimes, the bigger things get the more fear it will fail.

I expect to see blowback on a lot of this stuff by next March. “I don’t need all this stuff.” People are going to start stepping back some. Enterprises are getting hammered so hard right now to try all this stuff. There will be some cutting back in what they can do, depending on what’s working.

Thanks guys. We look forward to hearing more.

More about HeadMix from our Enterprise Microsharing Tools survey:
HeadMix Inc.’s mission is to help employees collaborate and work more effectively by discovering knowledge that trapped inside their colleagues heads. It’s a lightweight, on-demand, easy-to-use messaging platform that promotes intuitive knowledge-sharing inside the enterprise via the web, email, mobile and SMS.

With HeadMix, users subscribe to other employees and/or relevant groups/topics allowing them to stay connected with the content that is most relevant. Questions get answered sooner; key conversations can weave into the workday; and news travels faster. HeadMix connects employees and makes them more valuable to other employees and their customers.

Features:

Deploy inside firewall? No. Most of Twitter’s functions? Most. Groups, Location and a Desktop Client? Yes. Integrates with Twitter? No. Size of largest company? 150,000 SMS? Yes. IM? Future. Built on: Ruby on Rails. Links and media sharing? All types. API? Yes. Largest trial group? 20,000. Price/user/month: based on active users only. Twitter-compatible API? Yes. Smartphone applications? Future.

Other notes:

  • Fully integrates into enterprise daily existing workflow
  • Ability to integrate custom applications
  • Make customers’ existing apps more valuable by adding a social layer around them via email (Outlook), Sharepoint, etc.

Mix will be the first major retail microsharing rollout at a giant company. We’ll have more on HeadMix in our eBook Enterprise Microsharing Tools Compared. Register here for your copy. It’s free.

Reblog this post [with Zemanta]

Category : Touchbase Blog | microsharing | Blog
1
Oct

Yesterday in rolling out Socialtext 3.0, there was a small (but much echoed) mention of their coming enterprise microsharing application Socialtext Signals. In our Mashable post last week, Signals was the 15th “unannounced” enterprise microsharing service. I got a sneak peek at Signals in July during Brainstorm Tech and have looked forward to more.

This is not “just another” enterprise Twitter clone. In addition to a look at what’s new and different about Socialtext Signals, this post (it’s the nature of such an emergent space) also includes a fair amount on what we believe enterprise microsharing can become.

THE ANNOUNCEMENT
Socialtext CEO Eugene Lee points out:

Most folks are likely to call it “Twitter for the Enterprise” but we are thinking about it much more deeply - particularly how integrating it with People, Dashboard, and Workspace will help make it much more of a tool that blends with the flow of real work, and not just another cool social app.

Socialtext Signals is just briefly mentioned in the official release and remains in private beta. Co-Founder Ross Mayfield’s blog post provides the most detail on Signals. Choice quotes “get answers without interrupting people” and “Socialtext Signals is social messaging for the enterprise connected with context” sum it up nicely.

What you say and what you do
Socialtext Signals tracks what people are saying and sharing and Socialtext combines that with what people are doing and working on. Capturing pulses of relevant work activity, not just what people think to post, makes this a more integrated work tool.

Using it internally we’ve learned how different usage is from Twitter… because it is in the context of a company. The social patterns of what people say and share has taught us a lot about potential use cases. …Socialtext Signals will provide an integrated user experience across Socialtext Workspace, Socialtext Dashboard and Socialtext People.

They observed improved signal-to-noise ratio - and less risk valuable information will be lost in one missed signal -because multiple actions can be expressed in one signal, and because ensuing conversation around important points amplifies those signals.

Microsharing with Context
Because signals are linked to profiles and to collaboration within the Socialtext 3.0 workspace, they start from a rich contextual baseline. Context can also be explicitly shared in the content of the signal or the link included. Activity in the system generates a feed that’s part of the microsharing environment.

Context and being a part of the fabric of people’s work increase microsharing’s value and make it more genuinely the connective tissue we envision between individuals and teams.

Get answers without interrupting people
He recaps how Twitter is a surprisingly effective and efficient way to find answers, information, people and solutions, and frames Signals’ value in similar terms.

You are tapping into the collective intelligence of participants. Rapidly. And without the costs associated with other communication mediums for asking people questions. This is because the constraints of microblogging actually support efficient communications:

  • Messaging is in near real time
  • Messages are kept to 140 characters, the length of an SMS message, which encourages brevity, summary and linking
  • While you can view all messages, you follow people to create a custom feed of the signals from the people you want, leveraging the social network as a filter
  • In most use cases, Signals is implemented as a “Reply-Optional” medium
  • @Reply conventions reveal when a message is directed to you in public, while letting others add value or benefit from the conversation

“The broader values include speed of communication, knowledge sharing, context sharing and collective intelligence.” This value - problem solving with fewer interruptions and more reach into networks of loose ties - will be even greater for “process-specific solutions.”

BLOG COVERAGE
Larry Dignan’s writeup for ZDNet echoes the importance of context, which “could be what separates Signals from efforts like Yammer and Present.ly.” But reserves judgment on market readiness:

That doesn’t mean micromessaging isn’t important. In fact, it could be a big deal inside a business. But it could also be a mere feature to be integrated later by the likes of Oracle and SAP. Is Socialtext a groundbreaking, but way too early company in your enterprise?

Rafe Needleman’s CNET Webware reviews of enterprise microsharing apps (Yammer, Present.ly, Socialcast) his Socialtext signals writeup does not disappoint:

…just giving users a Twitter clone doesn’t solve the dual problems of information overload on the one hand, and personal isolation at work on the other. He believes that the most important communication between workers in a company is what they are doing. “When I work,” Mayfield says, “I’m sharing knowledge as a byproduct of getting work done. In the enterprise, what someone does is more important than what they say.”

Clint Boulton spends most of his Socialtext 3.0 column writing about Signals as opposed to the launched suite. He quotes Mayfield:

“The conversations on Signals are very different than what you would find in a more public Twitter. It’s different because it’s within the context of an existing organization trying to get things done. Twittering without context is just frittering your time away.”

“When I work, I’m sharing knowledge as a byproduct of getting work done. In the enterprise, what someone does is more important than what they say.”

And he nicely sums up Socialtext Signals’ market position:

I’m glad to see a contemporary groupware company like Socialtext taking the longer view of the Twitter concept than upstarts like Yammer and Present.ly. In this space, I’ve been a fan of Socialcast more than those apps, because it’s based on the larger vision of integrating information from numerous group applications. That’s what Socialtext is doing, too, and it’s the right thing for business.

Dennis Howlett, writing at ZDNet, is deeply involved with conversations about enterprise microsharing in general and is personally involved with ESME. He had some good responses to Larry Dignan’s piece, and makes a bold statement “I believe this is one of the most important additions that company has made in its evolving enterprise 2.0 platform.” He also restates an anecdote that one-time Gartner analyst Erik Zeller predicted that “supply chain problems could be solved through some form of instant messaging.”

Steve Gillmor, writing at TechCrunch, added the context of interoperability:

The forthcoming Signals API will support the Twitter API, making it easy for IT to leverage the broad pool of third party micromessaging clients such as Twhirl and compatible tools from loosely federated Laconica-compatible servers. Social Signals goes beyond the current Twitter architecture with channels, essentially groups that can be managed via workspace creation and deployment.

Robert Scoble has a detailed roundup of many more of the blog reactions and an 18 minute cellphone video conversation with Mayfield.

Mayfield: “Standalone Twitter clones are very different from what we are looking to achieve here.”

Reblog this post [with Zemanta]

Category : Touchbase Blog | microsharing | Blog
18
Sep

Rafe Needleman/CNET’s Webware review of Present.ly finds several advantages over Yammer for enterprise microsharing. Present.ly:

  • supports file attachments
  • permits groups
  • does not require all users to share an email domain
  • can be installed behind the firewall
  • supports the Twitter API

Twitter API support is significant. Many tools that work with Twitter would be very useful to have for an internal version.

Rafe dislikes the email domain requirement for Yammer: “it makes it impossible to invite an outside contractor into a work group.” That’s easily solved by issuing an alias from your company’s email domain. Possibly more of a problem is that many companies have divergent sets of email domains (by brand, by business unit, or with different TLDs such as .com vs. .co.uk).

On the other hand, the ad-hoc, sign-yourself-up nature of Yammer fosters spontaneous adoption and use of the tool, which may later help employees “sell the concept” of microsharing and demonstrate microsharing’s value to decisionmakers. On the other hand, it may piss off IT departments enough to inhibit subscription growth.

Keep an eye on the TouchBase blog for our side-by-side comparison of all publicly announced enterprise microsharing tools.

(Via Chris Brogan.)

Reblog this post [with Zemanta]

Category : Touchbase Blog | microsharing | Blog
11
Sep

by Adele McAlear. Originally posted at Marketing Monster

Winning $50,000 at TechCrunch 50 last night, Yammer did what Twitter hasn’t been able to: create a simple solution for enterprise with a pre-defined business model.

Founded by David Sacks, former COO of PayPal and currently CEO of Geni.com, the management team is filled from the ranks of PayPal, eBay, eGroups and Tribe. Sacks wanted an enterprise version of Twitter to keep his company connected, but it didn’t exist. So they built Yammer and launched it at TechCrunch 50 on September 8, 2008. As of the morning of the 10th, over 2,000 companies and 10,000 users were registered with Yammer.

Why would a company need this type of service? Well, aside from increasing communications between employees, Yammer claims it can reduce email by doing away with “email inboxes overflowing with unwanted messages.”

Anyone in a company can be the first to start a Yammer network for free and answer the question “What are you working on?” They just need a valid company email address and then begin inviting others from the enterprise to join the network. They say this means that “Yammer can spread virally through a company like a consumer social network.” For some company cultures, this may represent lack of control over internal communications and be seen as a threat if it is not initiated from the top-down. Yammer would likely be a hard sell to be endorsed by management in those types of enterprises.

There is no need for an enterprise-wide IT software installation as the service is hosted by Yammer. However, employees wishing to use the Yammer desktop application will have to download the app and have Adobe AIR installed, leaving the possibility for a spike in IT support calls. Users can also send and receive messages using an iPhone application, blackberry application, IM, SMS or email. You can also subscribe to email daily digests of network activity.

Yammer’s business model is built upon administrative control. Although accounts are free, optional admin tools are available for $1 per month per member of your company’s network, charged to a credit card after a 3-month free trial. These admin tools allow you to:

  • delete messages and remove members
  • set password length and complexity
  • require email confirmation on new browser sessions
  • restrict access to Yammer to your office network or VPN using an IP range
  • brand your network with your company logo
  • give additional admin privileges to users on your network

continue

Category : Touchbase Blog | microsharing | Blog
11
Sep

Just after Yammer won the TC50, Jeremiah Owyang tweeted that Oracle had emailed him to add OraTweet to his list of “internal microblogging” applications.

Sure enough, two posts from developer Noel Portugal’s Oracle Application Express blog describe OraTweet’s origins:

Eventually one of their teams “stumbled over OraTweet while looking for a solution to bridge the communication gap within their global team.” They began to pilot test it and others stepped in to help with development.

“After one week of alpha/beta life and not much internal advertisement OraTweeters numbers went from a dozen to the hundreds and is still growing, which shows that there is a hidden demand for internal communication tools like this. I like the fact that OraTweet flattens enterprise hierarchies and opens communication between all levels.”

Jake Kuramoto’s Oracle Apps Lab post fleshes out how groups work (”more like topics than groups”) and describes the hidden demand they are noticing:

The warm fuzzy of having an app behind the firewall brings out the hidden demand. Hidden demand opens a new user profile to your app too, since most hidden demand users won’t use the consumer version of your social network or micro-blogger, they bring a clean slate of experience to the party. As a designer/develoer, this helps focus the tool.

Jake’s post has the most narrative about how the tool is working and what it integrates with (no longer with Twitter).

I’m also talking with some of the grassroots internal user-advocates by email, and will post those remarks when available.

Oracle CorporationImage via Wikipedia

Humorous aside, someone on OraTweet (wisely) reads TwitterKarma developer Dossy Shiobara. His August 19th tweet: “My blog’s referrer log just picked up oratweet.us.oracle.com - I wonder what _that_ web host does. :-)”

Reblog this post [with Zemanta]

Category : Touchbase Blog | microsharing | Blog