Group items tagged

At the same time, a recent InformationWeek survey of IT departments are showing considerably wariness for doing the same thing inside the firewall with employees, with over half being either skeptical or wary of the utility of Web 2.0 apps in the enterprise.  The biggest concerns: Security, little expertise with Web 2.0 products, integration issues, and unclear ROI top the list.  In other words, the group inside most organizations that's most familiar with IT and software, is thinking carefully before deploying things like Enterprise 2.0. This is an interesting contrast, with a growing list of companies cautiously but clearly testing out the Web 2.0 waters with their customers while remaining largely on the fence for its use inside the enterprise.  Certainly, many organizations likely believe that consumer facing sites that extensively leverage user generated content, mass participation, and social networking have been proved to work on a large scale by sites like MySpace and YouTube.  And that organizations have already purchased and deployed countless IT tools that were already designed support internal business processes, ad hoc collaboration, and information capture and storage.    Another probably contributor to the increasing use of customer-facing Web 2.0 applications by large organizations is simple competitive pressure.  This is something that IT departments have only recently started facing in a serious fashion with outsourcing and other budget diversions in the enterprise as business units decide that they can do better by pitting their internal IT suppliers with external ones.  Thus, because of industry competition, a company's external products tend to improve faster and be more innovative since the concern over the displacement and dislocation of falling behind one's competitive peers is often pronounced in many industries.  Competition is usually much less, and often non-existent, for internal IT products.

it doesn't help us understand if Web 2.0 concepts like crowdsourcing actually work well in the enterprise.  For one thing, instead of recruiting people who have previously had no relationship with you and cost-effectively aggregating their time together to create large levels of new output, employers have a zero-sum game with Web 2.0 inside the firewall.

the best that Web 2.0 and Enterprise 2.0 applications like blogs and wikis can do it increase the productivity of existing business processes by improving efficiency as well as allowing them to self-improve through emergent structure and behavior.

Community, communication, consideration. The three founding principals of marketing your blog to an audience, whether general, or specific. People want to get be a part of the next thing, so give them a chance. 1. Community Whether you start up your own community, or join others, via means of MyBlogLog, MySpace, LinkedIn, Xing and others, this is a guaranteed and proven way to get visitors, to get hits, impressions, and often quality traffic, because you know that these people haven’t just clicked on a random link or search engine listing, but have seen you or your website’s profile, and followed it through to your homepage/landing page. The best ways to get the profiles themselves noticed? See below… 2. Communication I don’t mean ’spam’ by this either. Get involved in genuine discussions, with other people of similar interests, start up a civilized, profitable, knowledgeable discussion, then when you’re finished, ask if they’d take a look at your blog or website. You’d be surprised how many loyal readers have come to my own blog in this way. Simply leave comments in communities, on social networks, on other blogs, etc. Still not quite your way of dealing with people? 3. Considering All the time, you have to consider the reader. Who are you writing for? The reader. Who will be navigating your blog? The reader. Who should you devote your time, energy and attention to? The reader. Consideration is important, and you can show this in many ways. Either by having a clutter-free, easy-to-follow design, or you could alternatively try getting the readers involved, by asking questions in blog posts, or website statements, and opening up comments. If people comment, strike up a conversation with them, and keep them coming back. Answer their queries and requests with solid, reliable, dependable answers, and take note of the feedback they leave by using it, and putting it into action. If someone states that your text is hard to read, change the colour to stop it clashing so much with the background, or simply make it slightly larger. There are lots of ways you can show consideration to your audience, and it shows just how loyal you are to your readers through this. If someone spots an inaccuracy in a blog post and tells you, don’t be lazy. Go change it! They’ll keep coming back, they’ll tell their friends, and in turn this C will do word-of-mouth marketing wonders. The Element of Surprise You’ve looked at both SEO, content and the ‘C’s now, but my last tip is probably what has brought me the large majority of my visitors, both loyal and one-off traffic hoppers. Differentiate yourself, do something different. Be daring, be random! Try something wild, or something completely unheard of, whether it’s outrageous, or greatly beneficial to the reader. Sometimes, even beneficial to the writer! (http://www.techzi.net/donations/) Mad things work out great sometimes, other times, they really can lower your reputation, so it’s time to take calculated risks here. My advice? Follow your instincts. Be an entrepreneur. Take that risk. Make it happen. Throw a competition (http://www.techzi.net/competition/), for all the good it will do. Stand out and be different. Darren will sure know what I mean by that…

SearchTogether can benefit any group of people who are interested in investigating a topic together, such as students working on a group report, colleagues working on a joint project, or friends planning a shared vacation or other social activities. SearchTogether supports both synchronous and asynchronous collaboration styles.

The result is an egregious lack of productivity that may cost the U.S. economy $588 billion a year, according to a report by Basex, which has tabbed information overload as the "Problem of the Year" for 2008.

With e-mail as the biggest offender, Basex said users can save time by not e-mailing someone, and then following up with a phone call or an instant message two seconds later

Basex also said users must not combine multiple topics or requests in a single e-mail; make sure the subject clearly reflects the topic and urgency of the message; read their e-mails before sending to make sure they make sense; and will not hit reply-all unless necessary or reply with one-word e-mails such as "thanks.

The challenge I have been running into is convincing CTOs, CIOs and CKOs that there are network effects. These people have invested heavily in pre-Web 2.0 "knowledge management" solutions. They view blogs and wikis as a threat to the possible success of their existing investments. They fail to realize that adding a wider range of productivity tools to the Intranet will add value to existing tools, rather than take away from them.Do you have any suggestions on how to communicate this.

A short answer to your question is that in such cases an appeal to corporate competitiveness might make the most sense. Enterprise Web 2.0 (or to use the emerging enterprise 2.0 tag) evangelists such as Andrew McAfee and Dion Hinchcliffe are always on the lookout for corporate success stories to publicize. I'd pay close attention to what they have to say. Often in public presentations they are challenged by corporate audiences to "prove that this stuff works." They always like to point to public examples -- when they can -- in order to rise above the hype. Being able to point out that a comparable or competitive company "is doing X already - why aren't we?" can be a powerful motivator.

As a cost-conscious consultant I would first want to know whether the existing knowledge management system can be augmented with newer collaboration, social networking, and relationship management features in order to extend the investments in infrastructure that have already been made.

Work organizations increasingly adopt shared electronic databases. However, employees' unwillingness to contribute to shared resources undermines the utility of such technologies. Current research is limited to either a utilitarian or normative perspective. To advance understanding in this area, this study proposes a three-dimensional framework. It includes the utilitarian and normative perspectives as two complementary dimensions in addition to a third collaborative dimension. Based on this framework, the study identifies three key organizational processes and advances an additive model to predict employees' willingness to contribute to shared electronic databases. An empirical test was conducted to assess the model in a large manufacturing organization. The test showed both significant overall effects of the model and significant main effects of each predictor variable. The article will discuss the findings and address both theoretical and practical implications. Key Words: information sharing • collective action • organizational knowledge • knowledge management • collaboration • communities of practice • identification

Corporate Wikis reviewed: Confluence, JotSpot, WetPaint, Socialtext by Troy Angrignon on Mon 10 Jul 2006 06:30 AM PDT  |  Permanent Link  |  Cosmos Wikis are on the rise in corporations. And it's about time. One of the principles of Web 2.0 is that your user community can generate content that is better, faster, and probably easier to read than you can as a vendor. One way to enable them to contribute would be to build a wiki and let them flesh it out. Some good examples are coming up in this article: "Corporate wikis breaking out all over: MSDN Wiki" by Dion Hinchcliffe. (He has another great post as well called "Exploiting the Power of Enterprise Wikis") Quote of the day: "Not leveraging the contributions of a company's most impassioned and enthusiastic customers is starting to be seen as a significand oversight in many business circles." It appears in the article that eBay is using Wikis to better communicate between their users, partners, and suppliers. Now MSDN (Microsoft Developer Network) is using their pages to improve the quality of their developer documentation with the MSDN Wiki. THAT is a great usage. Your users often know your product better than your engineers and product managers because they have to live with it day to day. And guess what? If they tell the truth about some part of your product being broken - that's a GOOD thing.

Atlassian's Confluence is the best of them so far. Pros: the overall design is clean, it has advanced management tools, good security, and simple attachments.Its email function has to pick mail up from a POP box which makes it a little bit less ad-hoc but still functional. And most importantly, it also has great tools for moving pages around. Cons: Text editing, like with most apps these days is a bit dodgy, and pasting in blocks of text from Word is likely to cause problems. The pricing model is reasonable but for some reason (possibly because they're from Australia), they still don't have a directly hosted option so you have to use somebody like Contegix or deploy it on your own box. This seems to be a big and obvious oversight on their part these days. Also, their pricing model doesn't encourage small deployments right off the bat. I think this is the one that we'll use more of internally at the company where I work. Summary: The best of the enterprise wikis today, and one of the best options for scalability.

WetPaint is a newcomer that is doing some interesting stuff and that might be a better bet than JotSpot. Pros: The design is beautiful, the tool is very easy to use, the text editor is one of the best I have seen. Cons: I'm not clear on their entierprise suitability and it's not really their target market. It didn't appear that they had much in the way of administration tools, granular security, or any way to integrate into a back-end authentication system. Summary: I met one of the WetPaint guys at Gnomedex but he didn't seem to know the product very well. Hopefully next time, they'll put somebody more knowledgeable at their booth who knows the product in more detail. I think they're worth watching to see what they do in the next few months.

 Open issues for research/thinking on communitie

word 'community' and use and study the term collective action