Today I am pleased to announce that we at Socialtext have taken a huge step towards our vision by receiving a significant strategic cash infusion by Bedford Funding, the $1.4 billion private equity firm behind Talent Management Solution provider, Peoplefluent™. The infusion of capital that we are receiving will accelerate the development of our industry-leading enterprise social collaboration tools and augment sales efforts for both sides. We will ramp up hiring in all areas, and will also serve as the new Silicon Valley hub for Peoplefluent.

via socialtext.com

Like Alan Leposky, I think this is good news overall for Socialtext.

Additional coverage in Techcrunch.

Socialtext Motley Fool's Social Intranet is Jingle

View more presentations from Socialtext

An overview of Motley Fool's "Jingle" intranet. The tangible stat shared in this case study is the 3/4 reduction of all-hands email being sent. For a general overview of Socialtext 5.0, see this presentation recording.

Back in September, with the release of Atlassian Confluence 4.0, I thought the new text editor was one of the particular highlights of this major version update.

Now with the release of 4.1 this week, there are further improvements to the new rich text editor including:

• Build richer pages, faster with Autoconvert (it automatically embeds content like Confluence pages, YouTube videos, Skitch images, Flickr photo streams, Vimeo videos, and Google maps when you paste a link). 
• Enhance documentation with Image Effects (see the screenshot). 
• Make bulk changes to pages with Find & Replace.

As well as enhancements to Confluence, the fast pace of ongoing improvements to Team Calendars also continues.

Finally, don't forget to get your Confluence Origami Necktie, a fashionable quick-reference guide. Make it, snap a pic and share it on Twitter with the #confluencetie hashtag :-)

“build a Wiki and crowdsource ideas". It’s similar to Wikipedia. It involves the creation of an internet platform that enables managers and employees to add relevant information, and that information can then be edited and peer-reviewed.

Another idea is to “build an internal social network.” Employees can design their own profiles, upload images, provide useful links, add work-related content, and eventually “this will reduce the volume of email communication". In an era of email overload, that can only be a good thing.

Other than this article spreading the usual FUD about social media in the workplace (here is an alternative view), this is pretty simplistic advice for SMEs thinking about trying to proactively utilise Web 2.0 and social software.

Even large businesses struggle with the idea of creating internal Wikipedias - small businesses simply don't have the critical mass. However, there are some practical ideas (use cases) for enterprise wikis (like Atlassian Confluence):

• Managing Meetings.
• Project Management. 
• Reporting.
• Document Drafting and Commenting.
• Publishing and Maintaining Policies and Procedures.

With some tools you can even build simple forms and workflows, although the emphasis is really on uisng a wiki as a lean management tool.

The internal network is a better idea, but in a small business they don't necessarily need to know who each other is but rather what each person is doing and using streamlined methods for sharing information. Microblogging tools - like Yammer - or even instant messaging - using tools like Skype chat - can fill that need. Better yet, these tools are often optimised for smartphones too and younger staff will love using them.

With the right tool, some or all of these ideas above can be combined. For example, Google Apps.

The key themes that small business should be thinking about using social media internally for are:

1. Communication. 
2. Team work. 
3. Productivity. 
4. Information management.

This is a long anticipated play by Yammer to expand the foot print of its platform. I haven't had a chance to play with these new features just yet, so can't comment on the user experience or maturity of the new tools. However, I am wondering how this will affect Yammer's business model in respect to the enterprise and government sectors - the more it adds, the more chance that a purely viral deployment approach will bump into other enterprise applications and systems, which may result in the need for a more formal adoption and procurement approach.

UPDATE: Alan Lepofsky provides a more detailed review and point of view.

The much anticipated Socialtext 5 has been released - see this announcement post from Sarah:

This release sees a complete overhaul of the user interface, introduces a world-class rich text editor and a barrel-load of other features that make Socialtext more accessible, social and successful than ever before.

I have to say, the refreshed out of the box UI looks great!

It seemed that my keynote talk at KM Singapore helped to change some people’s thinking about intranets. Challenging the notion that they are old, dull sites containing policies, I generated new enthusiasm for what intranets can (and should) do. But the most controversy came during the question-and-answer session, where I found myself saying:

“Blogs and wikis are dead.”

I certainly understand James' sentiment here. I'm also sure some intranet managers will draw a sigh of relief when they read this, thinking they don't need to worry about this social stuff anymore. Unfortunately, nothing could be further from the truth.

In fact, if we look at James' presentation it is full of refined examples of the software patterns that we call wikis and blogs... including REA Group (Jive), IDEO (ThoughtFarmer) and also Reynolds Porter Chamberlain (which integrates Atlassian Confluence along with a number of other platforms). I'm reminded that wiki is both a verb and a noun.

BTW I'm not aware of any leading enterprise 'wiki' that doesn't provide a rich text editor - even Atlassian are ditching wiki markup entirely in their upcoming version of Confluence.

There is no single cure for email overload and Inbox Zero doesn’t claim to perform miracles. At the end of the day it’s a system, and it’s nothing without your own personal input. It might work for you and it might not. It’s important to remember that productivity systems are subjective beasts and that can be their ultimate downfall or the reason for their success.

What works for you won’t necessarily work for me. And for that reason you can’t say wholeheartedly that Inbox Zero works or it doesn’t. That’s just like saying that having cornflakes for breakfast doesn’t work. It’s simply a matter of personal preference or taste.

I've always been critical about email 'diets', although I view more contemporary efforts by Luis and Geoff to eliminate email with great interest.

Years ago I recommended the following:

• Where possible, eliminate the root cause of the problem. 
• Take control of your own inbox by managing it appropriately. 
• Lead by example and practice better e-mail etiquette and style.

At the root of this advice is that email is a communication tool that is often misappropriated as a collaboration tool. You can keep trying to fix your own inbox, but the problem is actually with everyone else using email.

The good news is that I hear more and more frequently how social business tools in the workplace do help to reduce email overload. We really have moved beyond marketing rhetoric.

I can even see it in my own work practices too - I use a combination of email (yes, its still there!), wiki, microblogging (enterprise microblogging and Twitter) and instant messaging. Of course, its the wiki and microblogging that make the critical difference, as they create a open plan workspace online where everyone can work out loud.

However, the root causes I identified originally still stand. Working out loud works best when:

• Everyone is working out loud (or at least 'in the room'). 
• People know why and understand how to work out loud. 
• Users are able to control how they consume the online open plan space.

Part of the reason for this is that its not simply about shifting communication that takes place in email to other channels. That would simply shift the location of the problem. Instead, we use different tools in the flow to deal with transient, situational and ambient communication and collaboration in different situations. See my Architected for Collaboration presentation for more on this.

Overall, this is a very different approach to the problem from the simplistic 'occupational spam' mentality. We eliminate the root cause of email overload, not the individual messages.

On a strictly personal front, I've noticed that the vast majority of personal email I receive these days comes in the form of notifications from other public social tools, subscriptions and automatic notifications (like my bank). However, the dynamic of personal use is very different from the workplace. In the workplace, we have the advantage of being able to choose the commons spaces where we will work out loud (assuming you are proactive about it).