Voting, Collective Leadership, and Identity Commons

Thanks to next week’s Creating Space, Collective Leadership has been on my mind a lot recently. It’s also been a key element of the new Identity Commons. One of the issues we’ve been grappling with is decision-making. To understand why this is a challenge, you have to understand the underlying structure and philosophy of the organization.    (M5R)

Ultimately, Identity Commons is a Community Mark that represents a set of values concerning Digital Identity. It’s a name bestowed on the community of folks who care about User-Centric Identity. If you care about this stuff, then you are part of Identity Commons. There is nothing to join, and you are free to use the name and logo as a way of demonstrating your support of these values.    (M5S)

Why this is such a powerful and important construct is a topic for another day. What’s interesting about this particular community is that there’s also a corresponding legal structure, a nonprofit organization that is in the process of being incorporated. This organization consists of community “Stewards” — people appointed by the community to represent the interests of particular sub-communities (“Working Groups”) and who are responsible for managing the tangible assets of the commons. There are rules for becoming Working Groups and Stewards, but they are extremely lightweight.    (M5T)

All of the Stewards comprise a Stewards Council. Each Steward has an equal vote on all matters. There is a Chair, but that position is mostly facilitative. There is also a Chief Catalyst, someone (not necessarily a Steward) who is responsible for handling the operational duties of the organization and catalyzing action in the community.    (M5U)

It’s a fascinating, but delicate structure. The Stewards Council has an important leadership responsibility, but that role is distributed equally among all of the Stewards. How do Stewards exercise leadership effectively given this structure? Decision-making via voting is clumsy in many contexts, and yet that’s the only process that we’ve actually defined.    (M5V)

We’ve had a number of interesting conversations on the topic, and the latest discussion recently surfaced a lurker, Martien Van Steenbergen, who cited an interesting reference on holacracy. Martien quotes the following excerpt (emphasis his):    (M5W)

Another common question is about the “possible votes” in integrative decision making. At first it can sound like there are two possible votes on a proposed decision — “consent” or “object” — though that’s missing a key point. Consent isn’t about “votes” at all; the idea of a vote doesn’t make sense in the context of consent. There are no votes, and people do not vote.    (M5X)

People do say whether they know of a reason why the proposed decision is outside the limits of tolerance of any aspect of the system, and then decision making continues to integrate that new information. This isn’t the same as most consensus-based processes — either in theory or in practice — although it does sound similar at first, especially before an actual meeting that seeks consent is witnessed.    (M5Y)

This quote is keying on the difference between Collective Leadership and consensus leadership. They are not the same thing. With Collective Leadership, you are acknowledging the multi-faceted requirements of leadership, and you are empowering those best suited to meet those requirements to fulfill that leadership role. You are not voting on every decision, which would be a sure path to disaster.    (M5Z)

One of the ways this manifests itself is by making decisions “without objection.” This is a technique from Roberts Rules Of Order that Joaquin Miller brought to our attention. Essentially, you empower people to act, unless someone in the group objects, at which point an alternative process kicks in. Everyone still has a voice in the decisions, but it is a proactive rather than a reactive style, and it encourages action rather than stagnation.    (M60)

I believe that when you have great collaborative process, voting is a rubber stamping process, even when the topic is controversial. In other words, the actual decision-making process starts well before any vote happens. Healthy deliberation results in Shared Understanding, which in turn helps to surface clear courses of action that navigate through the obstacles of contradictory ideologies. When there is pressure for movement (another pattern of high-performance collaboration), then people will rally around those courses of action.    (M61)

On Sarcasm and Irony

While we were waiting for the OSIS session to start this past Monday at the Identity Open Space, Owen Davis told us about a study he had read claiming that only 20 percent of people understand irony. Upon hearing this, Joaquin Miller shared this great joke:    (L69)

A linguistics professor was teaching his class, and he explained that in some languages (like English), a double negative is a positive. “I am not unhappy with your work.” In other languages (like Russian), a double negative expresses stronger negativity. However, claimed the professor, there are no languages where a double positive is a negative.    (L6A)

“Yeah, sure,” responded one student.    (L6B)

You had to be there.    (L6C)

OCSI Meeting Synopsis

I was in Anaheim yesterday for the Open Collaborative Services Initiative (OCSI, pronounced “oxy”) workshop, which was part of the OMG Technical Meeting. Johannes Ernst, one of the OCSI organizers, invited me to present my manifesto on collaborative tools (which will be published in Dr. Dobb’s Journal and on the Blue Oxen Associates web site).    (WI)

OCSI is an attempt to get collaborative tool vendors to make their tools more interoperable. One of its early goals is to develop a shared architectural blueprint for describing collaborative tools, perhaps initially in the form of a white paper. This has been a refrain of mine for quite some time, and so I was very glad to participate in the group’s second meeting.    (WJ)

As it turned out, there was a tremendous amount of conceptual synergy in the room. I suppose I shouldn’t have been too surprised. At the beginning of my talk, I explained that one of our beliefs (also known as the The Blue Oxen Way) is that Shared Ontology (which results in Shared Language) is a prerequisite to effective collaboration. OMG is a very strong proponent of Model Driven Architecture, which is essentially an instantiation of Shared Ontology. Not surprisingly, there was universal consensus in the room about developing a shared model of collaboration — both on the human-level (e.g. Blue Oxen‘s work with Pattern Languages) and the system-level (the topic of my manifesto).    (WK)

In his introductory remarks, Johannes made several interesting points:    (WL)

  • The word “collaboration” means many different things to different people. This simply underscores the need for a common vocabulary.    (WM)
  • Collaboration seems to be an “it” topic among CEOs and CIOs. However, as often as they mention collaboration and as important as they claim it is, the collaborative tools market has been flat the past few years. At first, this seems to be a contradiction. However, the number of corporate downloads of free IM clients over the past few years indicates that the need for collaboration is real. One of the problems is that tools are not interoperable enough.    (WN)
  • There is no horizontal industry initiative for improving interoperability of collaborative tools. However, several vertical industries have expressed interest. One of the challenges is to get the different industries to realize that they share common needs so as not to duplicate efforts.    (WO)
  • Johannes chatted with a few tool vendors about this problem. Their response: “That sounds great, but I have a product to get out.” The way to get vendors more serious about interoperability is probably bottoms-up — via the user community.    (WP)
  • In this regard, the Open Source community could play an important role. The prequisite for standards is Shared Language and free implementations. We have the latter, but we don’t have the former. If we created Shared Language and if Open Source tool-builders adopted it, we could build a compelling case for standardization. Johannes feels that it is vital to involve both the proprietary and Open Source communities in the OCSI effort.    (WQ)
  • Collaborative interfaces should be as transparent as telephone numbers. When we see a telephone number, we know what to do, regardless of the underlying service provider, protocol (POTS versus VOIP), type of telephone, etc.    (WR)
  • Cut-and-paste is a type of interoperability between collaborative tools. (A poor one, as I and others noted later in the workshop, but also a relatively effective one — a good example of loose-coupling.)    (WS)

Other talks of note:    (WT)

  • David Hartzband, VP of collaboration technology at , provided a four axes view of collaborative tools: synchronous, asynchronous, inline, and contextual. He also observed two trends in the collaborative tools space: business communications convergence (e.g. telephone integrated with email integrated with your documents, etc.) and enterprise application functional convergence.    (WU)
  • Carol Burt, CEO of 2AB, shared her vision for model-driven access management. Not only could such a model have ramifications for those developing secure applications and those selling security software, it could also potentially plug in to an OCSI model for collaborative tools.    (WV)

At the end of the workshop, Joaquin Miller (the other OCSI co-organizer) led a discussion about the next steps within the OMG umbrella. The consensus seemed to be to propose the formation of an OMG SIG, which could potentially evolve into an OMG Task Force. Not being an OMG member myself, the conversation both baffled and fascinated me at the same time. Nevertheless, the folks there seemed to know what they were talking about, which is always an excellent sign.    (WW)

The next meeting will be at the next OMG Technical Meeting in St. Louis next April. We’ll continue to collaborate via an eRoom set up by David and via the OCSI web site. Our action item for now is to share our individual high-level models of collaborative tools in order to identify commonalities and to serve as straw men for additional discussion.    (WX)