I spent the morning doing research for a podcast interview I will be doing this afternoon with Andrew McAfee at HBS on the subject of Enterprise 2.0. The resulting podcast will be posted on the FastForward blog and on my own learning 2.0 podcast series. As part of my reading, I came across Dion Hinchcliffe's list of nine ideas for managing enterprise 2.0 projects. This is a really good list and I am going to use it to describe how we are thinking about our new Otter Networks community service, which we will start to demo the first week in February. Here is how we are describing the new service:
Otter Networks is a new service for building and managing peer-to-peer networks and communities. Otter Networks will enable enterprises and associations to organize loosely affiliated groups of people into valuable empowered networks of contributors who have new means to create, share, and learn.
Let's take a look at Dion's list and see how it applies:
1. It's about ease-of-use, first and foremost. As a recent Internet list rightly proclaimed, “EASY is the most important feature of any website, web app, or program.” Blogs, wikis, and other Enterprise 2.0 apps have to be the easiest thing to use. Preferably much easier than the tools users have now or they won't start using them. As we work through the design of our prototype, I keep reminding myself of this rule - if it can't be done in one or two clicks, forget about it. Our community 2.0 service is aimed at groups of people with very specific shared interests and needs. We are designing a start page that has a very basic navigation so that entry-level users only have three simple choices: search, subscribe, and contribute. To make things even easier, we are tying the “portal page” of the community to an AJAX desktop. With one click you can add all of the content channels into a single, unified view in your browser. From this desktop, you can read content, view podcasts and videos, and ask for and contribute advice to others in the community. One click to get the desktop set up. One click to contribute.
2. Change requires motivation. Provide it. In order for our communities to get going they need two things: a connection to a vital need or process and continuous education about the benefits of contribution. Our first prototype community is around negotiation and conflict resolution for a firm where this is a continuous problem. Any opportunity or means to improve how it's done will make a big difference in people's lives. But we are changing how people learn and communicate. To do that we will be providing regular online seminars where you can spend 20 minutes getting tuned up on what to do and the benefits of participation. And you can get your questions answered.
3. Emergent doesn't mean a blank slate. Empty blogs and wikis usually stay empty blogs and wikis. a little basic structure goes a long way and prevents contributors from having to figure out how to structure all the white space and provide a simple layer of consistency. To avoid the blank slate, we are populating our community with a good deal of foundational content that is in easy-to-follow templates: podcasts, videos, documents in a wiki. And all of this is choreographed by the Community Director (we can her a Learning Director) who maintains a continuous narrative of what is going on in the community.
4. Discoverability isn't an afterthought, it's the core. McAfee recommends setting up blog and wiki directories as well as good enterprise search based on link ranking (which is what Google does to make the right information come up in the first few pages of search results.) Enterprise 2.0 tools should also extract folksonomies and other structural information (from microformats and XML tags) into discoverability mechanisms like tags lists and clouds, making user organization schemes obvious, public, and emergent. On our start page, users find content navigation on the left and process navigation on the right. We will be using tags and display tag clouds to help people find what they need quickly. And everything is searchable.
5. It's OK to fear loss of control and misuse. But it's critical to put the fires out instead of preventing them altogether. Our back end system enables screening of posts but I don't think we will use it. One of the most powerful motivators of the new web is seeing your ideas published. Anything that interferes with that process shuts down the creative and motivational juices of people in the community.
6. Dynamic, effective advocates are a key enabler. Our goal is to convert readers to writers and listeners to podcasters. To do that we need to find people who are already providing these services informally and make them experts in the community. Give them status and a platform. They will be the best means of bringing others in.
7. The problems will be with the business culture, not the technology. Yes. And these communities need high-level sponsors who believe in them and will support them.
8. Triggering an Enterprise 2.0 ecosystem quickly is likely an early activity driver. This can mean a lot of things but the link structure of Web tools allows information to quickly flow, circulate, and mesh together. You can leverage this in a almost infinite number of ways to drive user activity, interesting content, create awareness of what the company is “thinking”, and more. In our communities, you can become a blogger, contribute to a wiki, or make and publish a podcast. You can also access “smart feeds” that combine RSS and persistent search to provide you with a flow of new information — jumping off points for your own ideas.
9. Allow the tools to access enterprise services. Uploading spreadsheets and other documents should be easy too. And the reverse should be true as well, getting data back out into traditional tools including Office documents, PDFs, and XML must be easy to inspire trust and lower barriers to use. We are building means to move data in and out of the community very simply.
So stay tuned. I'll be posting notice of when we will start to demo our service. We can arrange for you to take a look….
Share This