“…success comes entirely from people and the system within which they work. Results are not the point. Developing the people and the system so that together they are capable of achieving successful results is the point.”

Leading Lean Software Development

Recently, that quote stirred some controversy among my peers. The part about “results are not the point” was hard for some people to understand and come to grips with. Aren’t results always the point? Well, as with most things, “It depends”.

Many a project has gone down in flames because they failed to take the time to really think through a communication plan that educated their stakeholders of the organizational value of their project.  Communication is one of the most important factors to the success of your community. Without communicating your project or program’s benefits and successes, users and stakeholders alike won’t be aware of new offerings, program progress, or the goals and direction of your project.

Imagine being lost on a deserted island with no hope of being discovered with only a volleyball named Wilson to keep you company.  There’s a reason pirates used marooning as a form of torture.  It’s a miserable existence (if you can call it that) that usually doesn’t end so well.  But yet that’s what becomes of most corporate knowledge.  It’s left on various file servers and websites across the enterprise with little hope of discovery or rescue (aka. reuse).

Community managers have a tough job. They deal with lots of different stakeholders trying to find that elusive “middle ground”. They incessantly cheer on community activities and push adoption of collaboration best practices; but when it comes to validating their position through tangible and quantifiable metrics it can sometimes seem daunting. Is the best measure user participation? How about community size? Each of these seem like great things, and they are, but typically organizations don’t have a lot of tolerance for soft measures that don’t directly impact the “bottom-line”.

“Build a better mousetrap and the world will beat a path to your door.”

–Ralph Waldo Emerson

Is there any more familiar quotation related to innovation?  I doubt it.  However, “build a better mousetrap” was actually a misquotation. What Emerson really said was…

I recently stumbled across a great post called Communities Manifesto: 10 Principles for Successful
Communities by Stan Garfield that I highly recommend. In his post Mr. Garfield lays out 10 principals that define community and also has suggestions for helping them grow and mature.

The amount of control a community has over process and direction within a project has recently come up in a situation I’ve been involved with and I think it’s a great topic for a post since it strikes at the heart of many company’s trials and tribulations in creating vibrant communities.  The real question in these situations is not one of control but of trust.  Can you just be along for the ride and let someone else influence your project even if you don’t agree with everything they do?