The Keene View on Web 2.0, Ajax and SaaS

Internet Explorer, particularly versions 6 and before, are the bane of any web developer's existence. The Internet Explorer versions Microsoft produced during the competion-free era between when Netscape died and Firefox came on the scene are masterpieces of monopolistic neglect. IE 5 and IE6 are slow, proprietary and just plain awful to work with.

Worst of all, Microsoft guaranteed themselves longtime domination of the corporate browser market through this cynical behavior because all the web apps built for IE 5 and 6 are so full of hacks that they won't run on "modern" browsers!

Nothing strikes fear into the heart of our professional services team quite like the words: "yeah, we're thinking about rolling out IE 7 sometime in the next 18 months."

But now there is a way out of the nightmare that is IE. Alex Russell at Google (of Dojo Toolkit fame) has figured out a way to run Chrome as a plug-in inside of IE - even the old versions. This means that web developers can build applications the way nature intended and IE is none the wiser.

For cloud computing in general and Platform as a Service in particular, this is great news. With Platform as a Service (PaaS), you develop and deploy apps from within your browser, so the power of the browser directly governs the power of the your development platform.

For WaveMaker and other PaaS vendors, this extends the reach of our cloud computing solutions to the back hinterlands of corporate America where technological change comes most slowly and where consequently frustration with IT is highest.

Labels: Web 2.0

Yesterday, KANA announced the release of KANA 10, whose killer feature is the ability for call center executives to do self-service customization of call center workflow to meet changing business requirements.

KANA is using a customized version of WaveMaker studio that allows call center execs to configure the business workflow using a drag and drop interface.

KANA 10 shrinks a process that used to take months down to minutes - all thanks to WaveMaker!

According to KANA's CTO, Mark Angel, "WaveMaker's visual Ajax studio turbocharged our web development effort for KANA 10, cutting at least 50 percent of our UI development time compared to a standard Ajax library."

The following screenshot shows an agent dashboard built using WaveMaker and based on the Dojo Toolkit. Pretty snazzy huh?


The following screen is intended for end user self service and gives proof positive that Web 2.0 has entered the enterprise!


KANA 10 was built using WaveMaker and the IBM SOA Foundation and was developed in conjunction with IBM customers. KANA did a complete rewrite of their entire suite of applications in less than a year (we announced the WaveMaker/KANA deal 10 months ago)- a terrific validation for Web 2.0, the Dojo Toolkit, Ajax and SOA technologies.

Labels: AJAX, DOJO, KANA, Web 2.0

Mashups is a pretty broad term. A good definition for a mashup tool is a solution that allows developers to combine interesting data and then visualize that data through a web application

Usually, mashups are web applications that can be created quickly using standard web services (e.g., REST) and components (e.g., Widgets).

There are three kinds of Mashup tools: front end, back end and integrated. The differences are:

• Front end mashup tools: these tools help build web front ends like dashboards using widgets/gadgets and little to no programming (iGoogle, PageFlakes)
• Back end mashup tools: these tools combine web-accessible data and services into more useful web services that can be called easily using a REST-ful interface (Kapow, Yahoo pipes)
• Integrated mashup tools: these tools make it easy to build end-to-end web applications that link web widgets to data and services.

When evaluating mashup tools, you need to think about what kind of mashing you are trying to do:

1. Do you want to create a visual dashboard from existing widgets? Try a front-end mashup tool. These tools make it easy to create a personal dashboard that tracks your stocks, local weather, the time in 51 timezones and the current price of titanium.
   
2. Are you wanting to turn web-accessible stuff (like ebay auctions or linkedin contacts) into a web service API? Try a back-end mashup tool to get at data programmatically that you otherwise have to do by hand (and mouse).
   
3. Do you need to create an end-to-end web app like a dashboard or simple business portal? Try an integrated mashup tool to build applications quickly and with minimal programming. Integrated mashup tools are effectively the modern version of MS Access for the web.
   

Another factor to consider is whether you have to download and install anything to use it. Mashup tools can be purely web-based (like Yahoo pipes or PageFlakes), purely download (Open Kapow) or available both as a download or hosted (like WaveMaker and IBM Mashup Center, both of which are hosted on Amazon EC/2).

Here are five free, open source mashup solutions you might want to check out:

iGoogle - Front End Mashup Screen Builder Tool

If you are looking for lots and lots of widgets, look no further. iGoogle has tens of thousands of gadgets (many of the most popular ones NSFW, but that's how it goes). Try iGoogle here.

Open Kapow - Back End Mashup Service Builder

The web is a wonderful place to find information, if you are a human and have a lot of time. Getting programmatic access to data on the web is a completely different story (wouldn't it be nice to see which of your favorite restaurants has a table open at 6 tonight automatically?) Kapow is a web-based tool for creating "robots" that gather data on the web and return the results as a web service. Try open Kapow here.

Yahoo Pipes - Back End Mashup Service Builder

Pipes is a web-based tool that allows developers to aggregate, manipulate, and mashup content from around the web. It is not as full-featured as Kapow, but you can try it without having to download anything. Try Yahoo pipes here.

IBM Mashup Center - Integrated Mashup Builder

Mashup Center was written with the non-developer in mind. That design objective increases the number of people who can use the tool, but limits the complexity of what you can build. In general, Mashup center requires that developers create a set of enterprise widgets (using IBM's iWidget spec) . There is also a cloud version of Mashup Center, but it requires that you have your own Amazon account set up. Try Mashup Center here.

WaveMaker Studio- Integrated Mashup Builder

WaveMaker provides a fast and easy way to build web applications. It targets Java developers who want a RAD GUI builder as well as novice web developers who want to build web applications with minimal learning curve. You can try the cloud version of WaveMaker here, or try the WaveMaker download here.

Labels: igoogle, kapow, mashup, mashup center, WaveMaker, Web 2.0, yahoo pipes

Today, we launched version 5 of our visual development platform for Java and web developers.

Java developers need the equivalent of MS Access for building Java Web Applications. Currently, a Java developer wanting to build a web application faces a huge learning curve, to say nothing of the coding burden.

WaveMaker 5 addresses the need for easy to use tools for building Java Web Applications. Wavemaker 5 introduces Enterprise-ready Data Widgets. WaveMaker generates these custom components automatically when a developer connects to a database.

With Enterprise-ready Data Widgets, WaveMaker reads the database schema and creates a widget for each table that the developer can drag and drop into an application. Enterprise-ready Data Widgets can display table data as an Ajax grid or as a form with automatic data validation and built in create, update and delete capabilities.

WaveMaker makes it possible for a developer to create a database-driven web application with literally three clicks:

• Click 1: connect to the database. WaveMaker studio automatically imports the schema and creates an Enterprise-ready Data Widget for each database table.
• Click 2: drag Enterprise-ready Data Widget from the studio palette to the application canvas
• Click 3: press Run to perform a test run of the application in a local Tomcat server. The final application can deploy to any Java server.

Try it today! You can download WaveMaker and try it yourself here.

Labels: cloud computing, Java, RAD, RIA, WaveMaker, Web 2.0

The much-hyped but poorly defined terms Web 2.0, Rich Internet Application (RIA) and Ajax are best understood when they are defined together.

Buzzwords represent job security for entrepreneurs like me who would be practically unemployable were it not for our secret knowledge of the true meaning of words like Web 2.0. However, even I must admit that these Buzzwords 2.0 get in the way of clear communication.

In addition, while there are many standalone definitions of terms like Web 2.0, it is much easier to understand these buzzwords mean by considering them together. With that in mind, here are my definitions of Web 2.0, Rich Internet Application and Ajax, complete with helpful graphics:

• Web 2.0 represents a market shift in consumer attention from expert-generated content (Yahoo) to user-generated content (Google)
• Rich Internet Applications represents a requirements shift for more interactive, PC-like web sites to simplify consumer creation of content (Blogger, MySpace)
• Ajax is an architectural shift to support RIA requirements

Definition of Web 2.0 - Shift In Consumer Attention

Consumer eyeballs still rule the web. The huge power shift over the last 5 years has been from expert-driven content (which could be created using expert tools like Adobe Dreamweaver) to user-driven content (which requires web based tools that are easy to use). The shift in consumer attention is also driving a shift in business focus as corporations look at ways to engage more effectively with their customers and employees.

Definition of Rich Internet Application - Shift in Web Requirements

In order for more people to participate in creating content for the Internet, the content creation tools have to be both simpler and more interactive. Rich Internet Applications seek to erase the difference in user experience between browser-based applications (Gmail) and traditional client/server applications (Outlook). A quick comparison of Gmail versus Outlook shows that RIAs have a big usability gap, but the Internet brings the offsetting benefit of dramatically simpler application distribution.

Definition of Ajax - Shift in Web Architecture

Ajax is an architecture which makes the browser smarter and more interactive by running Javascript programs on the client. Don't tell anyone, but the old name for putting logic on the client was fat client programming. Everything old is new again and it turns out the only way to make an interactive client is to do more processing in the browser.

The following diagram shows the fundamental changes between the Web 1.0 architecture (circa 2000) and the Ajax architecture.

Where is all of this leading?

Web 2.0 is driving new application requirements and in turn creating a demand for new development tools that can meet those application requirements. Building increasingly visual and interactive web applications requires a WYSIWYG Ajax tool - something like a Microsoft Access for the Web. Flex and Silverlight, Adobe and Microsoft are providing proprietary tools for building RIA applications.

For an example of an open-source tool for building RIA applications based on Spring, Hibernate and Dojo, check out WaveMaker . Download Wavemaker to see what a visual Ajax tool looks like! Wikipedia also lists a number of other Ajax frameworks for building RIA applications.

References
A number of others have gone before me in defining these terms individually. Jonathan Schwartz recently pointed out that Java has always had RIA capabilities (but he also admits they didn't work very well until recently). Here are my personal favorites definitions:

• Web 2.0. Tim O'Reilly at O'Reilly Media has a good definition of what is web 2.0
• Rich Internet Application. Adobe initially defined the term rich internet application. The Burton Group also has a good white paper on Ajax and RIA (registration required).
  
• Ajax. Jesse James Garrett of Adaptive Path originally defined Ajax.

Labels: AJAX, RIA, Rich Internet Application, Web 2.0

WaveMaker just released a new version of its open source development tool, available here, that includes out of the box support for the Postgres/EnterpriseDB database.

Before now, Postgres developers had very limited choices for building graphical front-ends to their databases. Tools like Navicat provide support for building client/server applications, however web application development requires complex hand-coding in PHP.

With this new release, WaveMaker is offering a visual development environment for Postgres that greatly reduces the amount of code required to build a rich internet application on top of Postgres. By eliminating much of the Web 2.0 learning curve, WaveMaker greatly increases the number of developers who can build Ajax applications.

This release also reaffirms WaveMaker's commitment to the EnterpriseDB Blade Program which is building a trusted ecosystem around the Postgres platform.

Labels: EnterpriseDB, Postgres, Rich Internet Application, WaveMaker, Web 2.0

Lewis Cunningham, a database architect for EnterpriseDB, recently posted a review of WaveMaker Visual Ajax Studio that included an aha moment:

When I created my data model, it automatically turned that into a series of web services. This means that the data interface is completely separate from the logic to use that data, allowing data to be decoupled and changed at any time. You can build your UI without ever seeing your database.

Lewis has uncovered an important shift in development being driven by the Web 2.0 architecture: scaffolded development. Ruby on Rails originated the idea of scaffolding as a way to get a web application up and running quickly without having to connect all the back end pieces.

As the developer fills in the back end details for data and web service binding, the scaffolding goes away. Thus ushers in a whole new era of Web 2.0 rapid application development - in which business users can mock-up an application and iterate quickly on a user design, then hand off their prototype for IT to develop (with or without underlying dummy data).

Go ahead, download Wavemaker and get see where Web 2.0 and RAD are taking us!

Labels: EnterpriseDB, RAD, ruby on rails, WaveMaker, Web 2.0

Web 2.0 apps look all shiny and bright, but we all know what horrors lurk within the typical enterprise IT shop. Web 2.0 will not be able to transform the enterprise until it can deal with real world integration nightmares like CICS systems, flat files accessed through obscure SNA protocols and AS/400s programmed in RPG.

Who is going to tame all this real world IT stuff and bring it into the bright shiny Web 2.0 world? SnapLogic and WaveMaker, that's who!

WaveMaker and SnapLogic announced today a partnership to use SnapLogic's Really Simple Integration platform to wrap any legacy data source as a web service. Once SnapLogic has "tamed the beast", WaveMaker provides a point and click, WYSIWYG development platform to expose legacy systems via rich internet applications.

Although we are performing very different tasks, both SnapLogic and WaveMaker are getting incredible value from creating web service-based products. SnapLogic wraps any data source as a web service, while WaveMaker assembles applications from any collection of web services. Chris Marino of SnapLogic also blogged about our partnership.

The following marketecture diagram shows the power of this approach. Rather than a rat's nest of one-off adapters, replicated data and custom data conversions, there is one clean API to the data - web services - and one simple tool for exposing the web services - WaveMaker!
To demonstrate the power of the rich and thin approach to web 2.0, WaveMaker and SnapLogic will be demonstrating an application at Web 2.0 Expo this week that integrates mainframe, minicomputer and relational data into a simple inventory tracking and re-ordering sytem. Stop by our booths and check it out!

Labels: CICS, Snaplogic, WaveMaker, Web 2.0

The Meteoric Theory of Applications (to paraphrase Mary Loomis) is this:

Applications are like meteorites - they never migrate, they just land and stick.

With all the excitement over rich internet applications and Web 2.0, there is much talk of a vast migration of applications from client/server to the web (Judith Hurwitz describes when not to salvage legacy applications). While this will undoubtedly happen, it misses a much more important IT skills migration.

The real power of Web 2.0 lies not in modernizing legacy client/server applications, but in modernizing the skill sets of client/server developers. If an app was built in VB or MS Access and it works, leave it there. The real question is what to do with the developer who built that app?

Developers with 10+ years of experience with client/server tools have no clear way to "upskill" to building Web 2.0 apps. Consider the skills that a typical Visual Basic/Visual Studio developer would need to learn to start building an Ajax application:

• New database: MySQL
• New server language: Java
• New application server: Spring ($26.39)
• New database access framework: Hibernate
• New client/server messaging layer: Json
• New client language: Javascript
• New client toolkit: Dojo
• New styling language: css
• New IDE: eclipse

No wonder there is such a shortage of Java web developers!

WaveMaker is focusing on the skills migration - how to enable non-expert developers to build Ajax applications by using visual tools (for a good review of WaveMaker as an alternative to VB, see Java at the eye of a perfect storm).

Last week, WaveMaker hit 1,000 downloads a day - seems like we hit a nerve!

Labels: AJAX, WaveMaker, Web 2.0

I just waded through a good article in DevX by Alexey Gavrilov on building Rich Internet Applications with Adobe Flex, Microsoft Silverlight and Sun JavaFX. The article worked step-by-step through how to build simple web applications with each of these products.

I had expected that there was some connection between Web 2.0, open source and the leaders in RIA. Instead, I found a set of time-warp technologies, each embodying its own uniquely idiotic approach. For the sake of brevity, I will here summarize the crowning idiocy of each approach:

• The fat-client approach. Microsoft has determined that the only problem with browser-based apps is that it doesn’t run fat client apps. Silverlight fixes that bug.


• The supermodel approach. Adobe was so entranced with the beauty of Flex’s audio-video capabilities that they forget to add little things like the ability to work with strings or dates.


• The once more with feeling approach. Sun decided to take another stab at making good on their most famous lie about Java, “write once, run anywhere.” Unfortunately for them, the Javascript Genie is out of the bottle.

None of these approaches supports Javascript as the primary scripting language. Don’t tell Adobe, Microsoft or Sun that Javascript is hot and that those crazy open source people are starting to assemble lightweight applications to run in web browsers.

Having said all this, the open source AJAX community has plenty of work to do in cleaning up its own house. The good news is that if this is what we’re fighting against, we have only ourselves to blame if the evil scientists win!

Labels: Flex, Java FX, RIA, Silverlight, Web 2.0

I had a great conversation today with one of my blog-heros, Jeff Nolan. Jeff recently finished a stint as the CEO of Teqlo, a pioneer in hosted tools for building Enterprise 2.0 applications. Others in this space include Coghead and Bungee Labs.

The nirvana we are all shooting for is a world where developers can assemble useful business applications with minimal coding or scripting. The idea is to take simplify certain tasks that are hard to do with code (e.g., visual assembly of page layouts, hooking controls to services) without making it harder than normal to do the things that will always have to be done with some sort of logic. The reality to date has fallen short of this nirvana.

We identified 5 reasons that Enterprise 2.0 apps today often fail to live up to the hype:

1. “Slowest man sets the pace.” Chaining together service calls to build applications creates bottlenecks where the slowest service call tanks the performance of the whole application.

2. Look but don’t touch widgets. Although this is changing (see here for the latest on Google’s pub/sub widgets), the vast majority of widgets can’t exchange data. This allows for an infinite variety of cute clock and horoscope widgets, but a paucity of useful business functionality in widget form.

3. Web service alphabet soup. There are a number of web service standards and even within a standard there are few rules for how the standard should be applied. This means that creating widgets to integrate web services is unexpectedly time consuming.

4. Still too darn hard. The world of widgets and building AJAX apps is still far too complicated for the typical end user developer. Current state of the art tools still require a knowledge of IDEs, standards and languages far beyond the grasp of casual developers.

5. Service throttling. At ActiveGrid, we have found that a number of web services like Google Maps are easy to mash-up for demo apps but much, much harder to use for doing real work. Given that Google has to pay for all the servers, it is easy to see why they would want to encourage people to use their web services in non-intensive ways.

Jeff believes a big market lies in creating “people, place, thing” applications like project management and time tracking. I would add that the killer app is tying Internet data presentation and collection with email workflow – sort of an updated Lotus Notes.

The market and the tools are evolving quickly, so in six months the landscape will look fundamentally different. For now, however, the vision of idiot-proof assembly of Enterprise 2.0 apps using rich business widgets has yet to be fully realized.

Labels: ActiveGrid, Bungee Labs, Coghead, Enterprise 2.0, Google Gadgets, Jeff Nolan, Teqlo, Web 2.0

David Precopio recently blogged here about Portals, wikis and other transitory technical phenomena. In 2000, portals represented a vision for how a new, user-driven web was going to develop - one which paradoxically required lots of new proprietary software and teams of developers.

Shortly after 2000, application server vendors looking for a way to boost sagging license revenues (what do you mean we can't charge a premium for a commodity J2EE product?!) glommed onto portals as a handy revenue extender/floor wax. They immediately shifted into high gear, selling the whitening and brightening qualities of their "collaborative" web products.

Into the middle of all this crept the real collaborative web products. Using social media as their proving ground, they pioneered user generated content, interactive UIs (remember those nice client/server UIs - they're back as AJAX) and web services (remember those nice objects - they're back as services).

We met a company recently that referred to their 20 person portal project as "our latest boat anchor." Portals are just the latest example that technology vendors often have the right idea about what the future needs but too often try to implement the tools of the future from the worn out components of their past successes.

Labels: AJAX, David Precopio, j2ee, portal, Web 2.0

Shel Israel has a good post in which he interviews Chris Shipley of Demo fame on the significance of social media and Web 2.0. She says:

I do think that the rapid and broad dissipation of power/influence/control
that is at the core of social media (Web 2.0?) is as fundamental a shift as from
mainframe to mini and mini to PC. When power moves from central
control out to the edges, things change dramatically and forever. This
Genie isn't going back into the bottle. Full article here

This puts a pretty profound spin on the effect these technologies can have on how applications are developed in the enterprise. If Enterprise Web 2.0 tools allow more business-focused developers to be more effective in building business apps, IT can start to have a much more decisive effect on the business.

I would add to Chris Shipley's comment two additional predictions about how collaboration and Web 2.0 will drive business change:

1. Collaboration technologies will improve the developer/user dialogue to produce a better understanding of user requirements
2. Lightweight prototyping tools will enable more iterative development to product products that better meet business needs.

ps I got a chuckle out of this Web 2.0 love letter - who would have thought that all these wacky company names could be turned to such good use!?

Labels: Chris Shipley, Shel Israel, social media, Web 2.0

Through my friend Peter Christy, I was recently introduced to Kent Beck, the godfather of Extreme Programming. In the ensuing email conversation, he gave a pithy example of why his thinking has been so influential:

It seems to me like the new generation of UI technologies creates the
opportunity for artfully simplifying tools. The general technology is incredibly
powerful and flexible, but the cost and complexity of using it is high. Along
comes someone with a version of the technology that can do 20 or 40 or 60% of
what the original can do, but that opens the door to many more people using it.
The trick is always discarding the right 40 or 60 or 80%.

Kent puts his finger on the challenge for the next generation of enterprise tools – how to democratize the development of web applications. The challenge will be draining out the bathwater (development complexity) without also dumping the baby (expressive power).

Extreme Programming 2.0 Anyone?

Labels: Web 2.0

Like many other technology fashions, the Rapid Application Development (RAD) process made many extravagent claims which crumbled under the demands of real-world development. The goal of RAD is to create a series of prototypes which incrementally close in on the ideal customer

The problem is not so much the RAD (or Agile, or Extreme) process itself, but the limitations of the tools used to implement them. There has always been a moment of truth in RAD tools when the team moved from prototyping to "real" development.

If the prototyping is done with a lightweight tool like Visio, the moment you move to a heavyweight tool like J2EE, you lose your agility to respond to user feedback. The ideal solution would be a tool that can create deployable prototypes.

Why do Enterprise Web 2.0 tools have the potential to support RAD where other worthy technologies have failed? There are several reasons:

1. Drag-n-drop web app creation: the ability to create a rich interface quickly makes the prototyping part of RAD much easier;
2. Assembly-based development: the ability to assemble lightweight applications that invoke more heavyweight web services keeps the development team nimble;
3. Web-based delivery: users are much more likely to provide feedback if it is easy for them to access and try out prototypes. Web-based delivery ensures better communication between developers and users, particularly for a distributed team.
4. Standards-based deployment: many traditional RAD tools like PowerBuilder and MS Access produce applications which don't meet corporate security and managability standards. Web 2.0 tools fit more naturally with IT requirements.

Along the same lines, I delicious-ed (to Haig-ize a verb) across an interesting link by Siorc proclaiming that Web 2.0 is the new RAD. I think his theme is right, but the more precise statement would be that enterprise Web 2.0 tools have the potential to fulfill many of the promises made by RAD.

Labels: Enterprise 2.0, Web 2.0

One clear indicator of the state of the Enterprise Web 2.0 market is the dearth of real case studies. ActiveGrid's partner, Eljakim IT just increased the number of meaty Enterprise 2.0 success stories by 1.

Social Computing Magazine just picked up a case study on an ActiveGrid customer who used ActiveGrid to build Web 2.0 attendance system. To read the Social computing article, click here or if you want to Digg this, click here

The system is tracking 200,000 students and is used by 500 school administrators and social workers. The application itself contains over 300 web pages. The full case study is here.

Labels: Enterprise 2.0, Web 2.0

Judith Hurwitz recently wrote a very interesting article comparing the Web 2.0 tools world today with the early days of client/server GUI builders. Her article is located here. Among other clever things, she says:

Just as PowerBuilder provided a way for the masses to create a graphical first
generation environment, so this next generation of development tools will bring
Web 2.0 to a broad audience.

This summarizes exactly the market opportunity we are seeing at ActiveGrid. The reality is that most corporations use internet for external, customer-facing apps but deploy old-fashioned client/server employee-facing apps behind the firewall. Observations about the cobbler’s children having the worst shoes definitely apply!

Our goal is to bring the web revolution to client/server developers who have been left behind by complex code frameworks like J2EE, .NET, even Rails. Mitchell Kertzman, who is on our board, is helping us undo the client/server revolution he started at PowerSoft. Our goal is to drive the pendulum from distributed, fat-client systems back to centralized, thin-client systems.

Labels: ActiveGrid, Cobbler's Children, Enterprise Web 2.0, Judith Hurwitz, Mitchell Kertzman, Web 2.0

Every software vendor dreams of having a vibrant user community to provide input, buzz and maybe even someday help make money! When I joined ActiveGrid six months ago, the user community on SourceForge was dead, with one to two posting per day. Now the community has over 15 posts a day, a more than ten-fold increase in less than six months.

This describes the steps we took to go from zero to somebody in the enterprise tools forum world. ActiveGrid is a visual tool for building web apps, sort of an MS Access for the Web. Our success as a tool is closely tied to the strength of our community.

1. Crown a community czar

Taking care of the community had been an ad hoc activity at ActiveGrid. As usual, whenever something is everybody’s job, it ends up at the end of everybody’s todo list.

The most important step we took to kick-start our community was to assign a full-time employee to manage the health and well-being of the community. The skills required for success include good technical and writing abilities combined with a genuine interest in open source communities.

2. Put all your eggs in one basket and watch that basket!

For historical reasons, ActiveGrid had several different forums. There was even an abandoned community started by an ActiveGrid fan. It was thriving, but only because spammers had loaded all the forums with postings that were off topic to say the least. It took over a month to get all the forum traffic funneled into just one community board.

3. Use best of breed forum tools

We found that the ActiveGrid SourceForge forums were hard to navigate and didn’t allow attachments. Our community czar moved the community to Drupal and rehosted it at dev.activegrid.com. The new Drupal site helped make it easier to post content, helping to drive a flood of new posts. In addition, the Drupal forum software handles attachments and graphics, making it much more valuable for sharing information.

4. Connect with your base

The first thing our community czar did was to reach out to the people who were actively posting (even though many of their postings had to do with how un-loved they were feeling). He contacted them directly through email and built personal relationships with what we called the “Fab 4” – the top 4 posters who became the foundation for the rebirth of our community. One important lesson is that a small core of active posters is the soul of a healthy community.

5. Turn off the spin

At the risk of sounding cluetrain manifesto-ish, we made an early decision to err on the side of transparency in communicating with our community. We admitted that we had been lax in our support of the community and asked for their help. We also kept the community strictly separate from the commercial side of the house. Using community to flog commercial ideas will go nowhere. It’s like the joke about why you shouldn’t teach a pig to whistle – it doesn’t work and it annoys the pig.

6. Coddle early adopters

In a new community, one active poster is worth 1,000 lurkers. Given this, anything you can do to help incubate people with the gift of gab is worthwhile. We gave away ipods, bought lunches, but most importantly built personal relationships with our community champions.

7. Foster healthy competition

Each posting at dev.activegrid.com earns the poster points, that aren’t redeemable in any way except in our rankings. Anyone in the community who wants to be seen by their peers as an ActiveGrid expert has to work pretty hard just to stay at the top of the rankings.

8. Find work for your users

Many of the posters in the ActiveGrid community are consultants. Every chance we get, we put our corporate customers in touch with community experts. This is classic win-win – our customers get their jobs done and our community champions have even more reasons to be enthusiastic about our products.

9. Take your lumps

Not all postings are positive. Not all community members are polite. Having a community manager actively working to address issues as they arise has proven the most effective way of keeping the overall tone of the community constructive.

10. Explore the boundaries

We are now at the fun stage in working with the community, where we are exploring the boundaries of what you can do with a passionate and committed group of people, all of whom are focused on helping you deliver a great product to market.

For example, the community has provided invaluable beta testing on our last three releases. Top community members have also had one-on-one meetings with our engineering team to help us engineer our next generation product. On the business side, we have asked the community for help in devising our pricing and licensing.

We have not yet fully tapped the potential of the community, but have absolutely turned the community into a powerful driver of momentum. It has been extraordinary how quickly the gains in the community have been reflected by increased business activity and enthusiasm among our commercial customers. Success is infectious!

Labels: ActiveGrid, Cluetrain, Community, social media, Web 2.0