Communities of Need & Community of Solutions

Much of my thinking recently has been on Culture in Organisations. I am also interested in the Culture in Communities, and in particular Communities of Practice like Agile and Kanban. My thinking has lead me to observe that there are two distinct communities within a Community of Practice. One community based on solving problems, or a “Community of Need” and the other based on promoting solutions or a “Community of Solutions”.


Crossing the Chasm by Geoffrey Moore is a well established way of looking at technology adoption. It is so well established that Seth Godin rebranded it as Purple Cow for the Marketing Community over a decade ago. To summarise, through out its life time, a technology will be adopted by “early adopter”, then the “early majority”, “late majority” and finally the “Lagards”

crossing chasm

Between the “Early Adopters” and the “Early Majority” is the Eponymous Chasm that many great ideas have fallen into, never to be seen again. “Crossing the Chasm” is about getting an idea across that Chasm to the riches and success on the other side.

It has helped my understanding of this to overlay Julian Everett’s excellent work on “The Meme Lifecycle“.

Meme Lifecycle

From Julian’s Meme Lifecycle, all meme come about as the result of a need. Before the meme or solution exists, there is simply a need*. There are often several independent groups or individuals working on solutions to the need which it is why there are often several independent and competing solutions that occur at the same time. Once a meme has come into existance, it goes though a period of evolution and natural selection. During this phase, the meme is tested in different contexts, or fitness landscapes. In each fitness landscape, the meme might take a different form or expression known as an extended phenotype. The key issue about this stage is that a great idea might fail because of the context, and as a result it will need to evolve to satisfy the needs of that context. As a meme approaches the chasm, the uncertainty about the contexts it will and will not work in is resolved. A necessary condition of a meme exiting the chasm is that there is certainty not only about the meme and how to use it, but also which contexts it will and will not work. People who claim that a meme fits all contexts and then modify it to fit a new context are preventing the meme from exiting the chasm. In my opinion, Scrum needed Kanban to leave the Chasm.

For example, Recently someone asked Richard Warner and I about Scrum and Kanban. In fact, they knew what they were and how to do them, what they wanted to know, was “when to use Scrum or Kanban”. Richard came out with the following conditions:

  1. In order to put work into Scrum, you have to be able to estimate it (or time-box it). This means for discovery (PM/UX) work, Kanban is a preferred mechanism.
  2. Scrum is only possible when the work is predictable for at least the next week or two. For highly unpredictable work, such as IT Operations or UAT, Kanban is preferred.
  3. Kanban works best when the person responsible for prioritisation (Product Owner) is highly available, preferably co-located. In situations where the prioritiser is not highly available, it preferable to batch requests using Scrum. So for an off-shore development team, the PO team might use Scrum to manage prioritisation. The development team might use Kanban inside the Scrum framework.

Its is now known when to use both Scrum and Kanban most of the time. This makes them far more appealing to the risk averse who hate uncertainty.

Next, I overlaid Dave Snowden’s Cynefin. Doing this helped me link to the cultures associated with each part of the curve. (More to come later on this)

memes cynefin

Cynefin maps nicely to the Meme Life cycle. From creation of the meme to exiting the chasm, agents engage in safe to fail experimentation to test multiple hypothesis in order to map the meme to the different fitness landscapes.

Mapping to Cynefin made it easy to map to Real Options. An option’s value is only greater than the intrinsic value when there is uncertainty. When there is certainty, there is no value in deferring a commitment. This is where “unless you know why” comes in. If you know why, if you have certainty, then you can commit early.

cynefin real options

And finally, it is possible to map to principles versus practice.

real options principles

Those operating before the chasm act based on principles. They understand that they may be operating in a fitness landscape where the meme they are using fails. Once the meme has exited the chasm, the users expect that they only need to follow the practices, and the principles become less important. Often the principles are forgotten or ignored and this leads to failure as more obscure fitness landscapes are discovered. This failure corresponds to the cliff in the Cynefin Model. Fundamentally, principles should dominate before the Chasm, and practice dominates after the chasm. This causes real problems for memes that are principle driven like many of the Agile practices.

Communities of Practice

There are two clear communities of practice that overlap considerably:

  • The “Communities of Need” are centred on the creation of memes. Members of this community operate in the area of “Need” to create a meme and then work with the meme to identify fitness landscapes where it fails, and evolve them accordingly. These communities have problems that need to be solved. They take solutions developed for one context and attempt to implement them in their own context (exaption), and modify (evolve) them as appropriate.
  • The “Communities of Solutions” are centred on the Chasm. Members of this community attempt to extend the number of fitness landscapes that a meme works in and then sell the meme to the early and late majority on the other side of the chasm.

Communities of Need

Communities of Need can easily be identified by their gatherings. For example, conferences would consist of the following:

  • An un-famous Keynote, often talking about ideas that are unfamiliar or novel to the community. The keynote has practical experience of the material they discuss. The keynote is not normally a draw for the conference., (The gathering of the community, and exchange of ideas is often the draw.)
  • Experience Reports dominate, and spark discussion. There is an understanding that Communities of Need grow based on experiences. An experience prompts others to share stories and a “model” is built accordingly.
  • The conferences have a heavy open space element as the participants are often as knowledgeable as the speakers/facilitators. Organised sessions are often workshops ( Gold fish bowls ) to harvest community knowledge.
  • Context is everything.

Examples of “Community of Need” conferences include XP Day, Lean Agile Scotland, Agile Lean Europe 20xx, Lean UX NYC.

Once a need has been resolved, communities of need may dwindle, or move on to solve another need. A classic example of this is XTC. The needs of the London XTC community have pretty much been met. They know how to write software in small teams, and there are no significant community needs outstanding. As such, those interested in personal development now gravitate towards the software craftsmanship community.

Every member of a “Community of Need” is a leader. They are Problem Champions. As such, these communities do not tend to have leaders. If anything the leaders are often servants of the community who support the community, organising events but no one knows who they are.

Communities of Solutions

Communities of Solutions are about promoting meme across the chasm and beyond. Their conferences are also obvious:

  • The keynote is famous. More often than not talking about a subject they have no practical experience in. They have either read a book or done a bit of study. Malcolm Gladwell is the ultimate expression of a keynote for a CoS. If they do have any experience, it dates back years in the past.
  • There are normally workshops added onto the conference on subjects near the chasm.
  • The sessions are organised in advance and consists of talks, workshops and “taster” sessions where the attendees learn from the speakers. Attendees want to be told what to do.
  • The Conferences are organised as commercial ventures with the profits generated going to the organisers.
  • Context is not considered relevant.
  • “Community of Needs” individuals are normally the speakers and hold small impromptu conferences in “The Corridor”

Examples of “Community of Solution” Conferences include Agile20xx, QCon, Goto.

These communities have leaders with a clear pecking order. The leader often annoints the next generation. The leaders of a “Community of Solutions” are often not practitioners or even members of the “Community of Need”. Their position is normally due to their relationship with the existing leaders. “Communities of Solution” have leaders and followers. The leaders are the Solution Champions.

Scaling Agile

So where am I going with this?

The Communities of Need in the Agile Community are in a terrible state. Very few members of the Community of Need attend Agile 20xx anymore. There just aren’t enough practitioners around to create a decent corridor conference.

There is a belief that Agile is crossing the chasm, or that it has crossed the Chasm. Merging these different views has helped me to understand the following:

  1. Some Agile Practices have crossed the Chasm.
  2. Agile has not crossed the Chasm.
  3. Scaled Agile certainly has not crossed the Chasm.

Picking on Safe as an example of Scaled Agile, there are three parts:

  • Team level Agile – This has crossed the Chasm. Safe provides a nice packing of the established Agile Practices.
  • The Agile Release – This is halfway toward the chasm. There are several successful case studies.
  • Portfolio Vision – Agile at this level has not even identified all the needs. There are still several problems to be identified.

So some of the Safe practices are across the chasm with the uncertainty resolved. Others have not. You need to hire people from the “Community of Solutions” to train and coach your organisation. That is not enough though. Any company considering an Agile Adoption at Scale should also hire a number of people from a “Community of Need”. The people from the “Community of Need” will help you with the context issues. They will also help you create safe to fail experiments for those problems where there isn’t a known solution. To misquote Dave Snowden “You need Chefs as well as cookery books”.

I’ll end there. This is part of the Keynote I’m preparing for Agile Lean Europe 2015. My next post will be to discuss the problems caused by the lack of structure linking these two sets of communities.

* This is known as the entrpreneurs in “Crossing the Chasm”


About theitriskmanager

A IT programme manager specialising in delivering trading and risk management systems in Investment Banks. I achieve this by focusing on risk rather than cost. A focus on costs can lead to increased costs. View all posts by theitriskmanager

11 responses to “Communities of Need & Community of Solutions

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: