As a long-time desktop applications developer, I have a lot of experience shrugging my shoulders at the "Enterprise" side of development. However, the reality is that the "captive audience" mentality dooms you to mediocrity:
I'm not entirely sure that there is as huge of a barrier to adoption from the corporate side. Office Communicator and Windows Messenger before that offered private network IM capability. Additionally, the Millenials and like-minded young adults are starting to filter into the workplace as interns and entry-level employees... Watching job websites, I often see articles about attracting the younger workforce. Microblogging is one way.
The true barrier is *not* the old school management thought (although it is a realistic barrier). The true barrier is old school employee thought. Microblogging escapes the mindset of even much of the 30-something crowd.
Another possible barrier to Yammer could be seen in a private network microblogging installation. Ultimately, this is Yammer's barrier to growth. However, much like AOL IM vs Office Communicator, grassroots adoption of microblogging will occur long before critical mass is achieved to provide a business justification for paying for or even just installing such software on a server and client machines.
The company e-mail validation on Yammer counteracts such software installs as well; however, a departing emploee would still have his or her access to internal company updates after departure, as long as the employee's e-mail has been validated. In Twitter, you can make updates private or block people from following you, but having to do this in Yammer would probably defeat the purpose it was created for.
Yammer, much like AIM, has the potential to put company information outside of the company’s hands. Of course, every user does need to sign up and verify through a corporate e-mail address. Moreover, those who have left the company can be requested for removal (one would have to wonder the validation steps here.) Nevertheless, there is no guarantee or auditing of the controls that would keep a company’s data private.
From the site, Grow Your Wiki.
Of particular note from my experience is the following article:
wikis should replace email for collaboration
the bigger issue here is that organizations have to look at how email is being used, and what activities would be better served by other tools, like wikis and blogs. Email has become a crutch in business communications because it’s being stretched far beyond its intended use as a communications tool. Organizations are trying to use it to collaborate and it was never designed for this, so it makes a very poor collaboration tool.
It always seems like formal documentation as a whole is abandoned in collaboration mode for a furious chain of e-mails. I would prefer collaborative documentation to not be embedding in one of 10,000 e-mails archived somewhere. In place of thread progression, how about version control in the wiki?
Part 4 in a 4-part series: Email overload killed the businessperson