Since I’m asking fellow Aussies to share their Enterprise 2.0 and Enterprise Web 2.0 experiences, its only fair I talk about mine:
There are three enterprise level wiki experiments I’m aware of at CSC (there could be more, and I believe there are some project or team related wikis around). In July one of these experiments was integrated into CSC‘s global portal infrastructure as part what we are calling our Collaboration Portal Center:
“The Collaboration Portal Center boasts a wide-open experimental Collaboration Wiki; videos; podcasts (well only one to start); Yahoo Pipes, Blog, and RSS mash-up; comment areas following many content pages; documented solutions and case studies; a Global Google Maps mash-up; and RSS feeds on several portions of the content . . . not too shabby for just getting started.“
Right now this particular wiki is running on Twiki and is also being used to host a few internal blogs (like Stu Downes) using a plugin template. However, in Australia we are actually experimenting with Mediawiki, although we also have some local experience with Atlassian’s Confluence too. One of the quick wins I like with our Australian CSC wiki are the client profile pages that provide an overview of each client, including key links to different tools and reports plus filtered external RSS news feeds.
Of course there are other Web 2.0, Enterprise 2.0 and Enterprise Web 2.0 related activities going on, but right now there really is a lot of exciting buzz around the wiki experiments and a sense that no matter the outcome its going to be a good learning experience.
OK. I’ve shared a little about what’s happening where I am, now its your turn 🙂
I escaped to Sydney for lunch today, for what we’re calling – tongue in cheek of course – Coffee 2.0, to discuss Enterprise 2.0 adoption in Australia with Alex Manchester (also blogging over at Melcrum), Alister Webb from Telstra, Kolya Miller, Matt Moore, and Ross Dawson. The topic of the moment was of course the recent media attention on Facebook and other networking sites.
One outcome of the meeting was a general agreement to make an effort to find more examples of Australian organisations experimenting or implementing Enterprise 2.0 or Web 2.0 inspired technology inside the firewall. We all feel that many Australian organisations aren’t talking about their experiences in this space because they are either nervous about the publicity or don’t think they have something worth talking about… but if you’re reading this and you are in one of those organisations we would like to hear about your experiences with blogs, wikis, RSS, mashups, social networking, etc! To this end, I will share in my next post about what’s happening in CSC in this space at the moment.
BTW Coffee 2.0 isn’t an exclusive group, but small enough for us to have a good conversation. Let any of us know if you’d like to join us next time. Matt Moore suggested that next time should be a Beer 2.0 event 😉
Here is a great Aussie wiki case study shared by Nathan Wallace from Janssen-Cilag, a pharmaceutical subsidiary of Johnson & Johnson.
One of the interesting points in the case study is that after evaluating different wiki products, they opted for Confluence by Atlassian because it provide functionality such as “a hierarchy of pages, strong attachment capabilities, news features, LDAP integration, high quality search and a decent rich text editor.“
He concludes with some spot on points:
“Users do not perceive our Intranet as a Wiki, with all the anarchistic overtones that brings. Rather, they see the simplicity and flexibility as a natural evolution of Intranet technology… Problems of driving collaboration and content updates remain, but they are exposed as the cultural and people problems at their heart since the technical and workload “excuses” have been stripped away.“
Hat tip to Andrew Mitchell.
While playing around with Lotus Connections in the Lotus Greenhouse, I have been wondering if Lotus Connections would – in true Web 2.0 style – support a non-IBM, offline blogging client (like Windows Live Writer).
Firstly, there are some positive conversations going on around support for the ATOM Publishing Protocol API in Lotus Connections. And looking at the code in my Greenhouse blog home page, I noticed it contains the following code:
<link rel=”service” type=”application/atomserv+xml” title=”Atom Publishing Protocol” href=”https://greenhouse.lotus.com/blogs/services/atom” />
If I’ve understood correctly, then this bit of code that should tell an ATOM compatible blogging client what it needs to be able to publish.
Unfortunately, it looks Windows Live Writer doesn’t yet support the ATOM protocol but will in a future release. So, what to try in the meantime? Funnily enough it sounds like WLW doesn’t support the ATOM publishing API, but Word 2007 does. Shame I’m still on Word 2003, else I would try it out. Perhaps someone else with Word 2007 could try it out in the Greenhouse? Or can someone recommend an offline blogging client that supports the ATOM API?
I’m running a half day workshop at Key Forum’s Intranet ’07 conference in September. I’ll be looking at:
- Enterprise 2.0 opportunities and challenges;
- The technology building blocks: Blogs, RSS, tags, search and wikis; and
- Implementation approaches: Nature or nurture?
I’ll be drawing on material covered in my knowledge management masterclass around social software and also talking about what I’ve seen happening in this space at CSC and other organisations.
We’re talking about Facebook, and I talked about Facebook as a marketplace (I was thinking more in the classical sense, not necessarily an e-commerce hub) meanwhile Ross Dawson has been highlighting the trend to openness, which many others are commenting on.
This conversation reminds me of one of stories in The Adventures of English , where it describes the melding of Old Norse and Old English:
“The new grammatical meld tended to happen in the borderland market towns; word followed trade. Clarity for commerce may have been the chief driving force.“
Of course, English is the UK is still well known for its many dialects but has also continued to evolve around the world – we now have no dialects, such as Aussie Strine, Singlish in Singapore and many others. This original openness at the edges provided a platform for ongoing development.
Of course, information technology is a little different and unlike language, interoperability often calls for exact commonality. But perhaps a better comparison – and it pains me to say it – is email.
What do you think? Will openness make social networks the email of Web 2.0? This means walled gardens (or dialects) will exist, with different and unique functionality, but they will still understand each other just enough.
Considering all my recent telecommunications problems, perhaps I should have thought about going completely wireless? This option has been seen for years as a solution for developing countries – for example, even recently there was news about a province of Vietnam where community phones are being replaced with high-speed WiMAX broadband connections and VoIP telephony.
Now here in Australia, Virgin Mobile are offering a completely wireless home phone and broadband package as fixed line replacement. The only problem I can see is that the package only contains 4GB of data and supports speeds of up to 512 kbps – hardly the high speed direction we want to be heading towards. I’m not sure if the limit here is technology or network access cost by Virgin?
But perhaps what is more interesting to ask, is if we go wireless for the last mile why do we still feel like we need a home phone at all?