ChiliPLoP, Day 4

Last Friday was the last day of Chili PLoP. Ofra Homsky, Josh Rai, Linda Rising, Joe Yoder, and I met at our usual spot outside of the dining hall for our morning kickoff. We had two items on our agenda: workshop the patterns we had discussed the day before and that Josh and I had written up, and discuss next steps.    (1DF)

Stone Soup    (1DG)

We started with Collab:StoneSoup and decided to temporarily combine forces with the GivingSpace group, which had independently come up with a pattern of the same name. That experiment resulted in some constructive feedback but was short-lived. The most important lesson was that “Stone Soup” was a completely inappropriate name.    (1DH)

The pattern had arisen from a point I had made the previous day about faith in process. I stated that people about to participate in a new process had to demonstrate a certain amount of faith up-front; otherwise, they risked subconsciously hijacking the process. You want to give the process the chance to succeed or fail on its own merit.    (1DI)

Joe suggested calling this pattern, “Fake It ‘Til You Make It.” Ofra was reminded of a story, “Stone Soup,” which went like this.    (1DJ)

A weary soldier discovered a village in the desert and knocked on every door asking for food. Everyone turned him away.    (1DK)

Undaunted, the soldier took his pot, filled it with water and a large, round stone, and put it over a roaring fire, constantly stirring and tasting.    (1DL)

The curious villagers came out of their houses and watched, until finally, one of them asked how it tasted. The soldier replied, “It’s good, but it needs some salt.” So the villager went inside her home and brought out some salt.    (1DM)

She again asked the soldier how the soup tasted, and he responded that it could use some carrots. So another villager brought some carrots. The process repeated itself until eventually, there was enough tasty soup to feed the entire village.    (1DN)

During our group writing exercise, it quickly became apparent that we all had slightly different understandings of the pattern. Mine focused on the point of view of the participant and on adopting new processes. Everyone else seemed centered on initiating new collaboration, setting up enough structure to make the collaboration seem real, at least until the collaboration became real.    (1DO)

When I started refactoring and combining our work into a single pattern, I decided that there were multiple contexts for the same pattern, but that the solution was the same. I also decided to call it, “Stone Soup” instead of “Fake It ‘Til You Make It,” mostly because the former was a noun phrase. I had reservations, however, and our final day’s proceedings confirmed them. When we combined with the GivingSpace team, it became clear that there were at least three different versions of the Stone Soup story, each with different morals.    (1DP)

After we split with the GivingSpace group, my team continued giving feedback about what I had written. I picked up lots of good advice and promised to incorporate their comments into a revision.    (1DQ)

Kick Off    (1DR)

I was happy when Josh willingly took on the Collab:KickOff pattern, because I didn’t think we were close to Shared Understanding. That said, Josh’s work on the pattern helped us make that leap.    (1DS)

Originally, we called the pattern, “Kick Off Meeting.” I had asked whether the Kick Off meeting was, by definition, the first meeting. Ofra and Joe had said that it was not. However, as we started fleshing out the pattern, it wasn’t clear to me what the distinction was. People were mentioning a lot of things that supposedly happened at Kick Off meetings that I felt would happen regardless of whether or not a meeting was designated, “Kick Off.” The key distinction, in my mind, was whether or not those things would happen well. It wasn’t clear to me that denoting a meeting “Kick Off” was enough to make those things happen well.    (1DT)

Josh’s work on the pattern made some of those flaws apparent. Having something concrete to work from allowed us to quickly zone in on the vital piece — benefits from the ritual celebration of initiating a new project. We decided to remove “meeting” from the name.    (1DU)

In the end, this made perfect sense to me. We had defined collaboration as needing shared, bounded goals. We had also cited a pattern, Grand Finale (discussed in Linda and Mary Lynn Manns‘s upcoming book). It made sense that we also had a pattern for the beginning of a project as well.    (1DV)

Next Steps    (1DW)

One of the things I made clear to the group was that I considered this workshop to be the Kick Off to Blue Oxen Associates‘s ongoing Pattern Language effort. One of my broader goals is to do an ongoing series of workshops involving philanthropic foundations, nonprofits, and a variety of other organizations. These workshops would involve telling stories, mining for patterns, capturing those patterns, reinjecting them into the conversation, refining them, and so on.    (1DX)

In the meantime, I plan on further developing the language that began forming at our workshop with the help of our Collab:PatternsWorkGroup. I also plan on submitting some patterns to the PLoP conference in September.    (1DY)

I had an exceptional time at Chili PLoP. Lots of great people were there, and Arizona is warm and beautiful this time of year. More importantly, I was fortunate to have a great group of participants. Ofra, Josh, Linda, and Joe brought a tremendous amount of experience and enthusiasm to the process, which made the process both enjoyable and productive. I’m looking forward to the challenge of continuing what we started here, including another date at next year’s Chili PLoP.    (1DZ)

ChiliPLoP, Day 3

Last Thursday, my workshop met for a second day. Having agreed on a working definition for collaboration (see Collab:Collaboration), we started working on the Pattern Language. As was the case the previous day, I knew exactly what I wanted to accomplish, and I made that clear when we got started. What differed this day, however, was that Linda Rising, Ofra Homsky, and Joe Yoder — our three experienced Pattern Language authors — led the way in terms of process.    (1CT)

We began by laying out the index cards we had collected the previous day onto a table. The goal was to see what patterns we had and what seemed to be missing. The definition that we had collectively agreed on the day before helped us tremendously with this process. For example, because collaboration — as we defined it — required bounded goals, that meant there were patterns related to the start and end of the collaborative process. There were also patterns related to interaction (meetings for example) and knowledge exchange (Shared Display).    (1CU)

Mapping out our cards also helped us identify gateways to other Pattern Languages, such as Linda and Mary Lynn Manns‘s patterns for introducing new ideas into organizations, Ofra’s patterns for leadership, Jim Coplien and Neil Harrison‘s organizational patterns, and GivingSpace‘s patterns of uplift.    (1CV)

Lots of brainstorming and storytelling happened throughout. My favorite was a story that Joe Yoder told about a factory where he had previously worked, which literally left its financial books open on the factory floor. Anyone who worked at the company could examine the books and suggest improvements. The open books were a form of Think Out Loud that showed that the company treated its operations as a collaborative process involving all of its employees, regardless of position. Tremendously empowering stuff.    (1CW)

Linda, Ofra, and Joe constantly stressed the importance of iteration and cautioned Josh Rai and me about getting too caught up with formality too early in the process. Ever fearful of being berated by Ralph Johnson or Jim Coplien, I would periodically complain, “That name isn’t a noun phrase!” Fortunately, the rest of the group kept me on track. We had plenty of time to weed out and refine our patterns after the brainstorming process.    (1CX)

We ended our brainstorming at lunch, at which point we had 36 cards. After lunch, we picked two patterns — Collab:StoneSoup and Collab:KickOff — and Linda led us through a group pattern writing exercise. (I’ll say more about these two patterns when I describe Day 4.) She gave us a letter-sized piece of paper for each component of the Coplien Form (name, problem, context, forces, solution, rationale, resulting context, known uses, and related patterns). Each of us took one piece of paper, wrote down our ideas, then exchanged it with someone else for another piece of paper. The cycle continued until we all had our say to our satisfaction. Afterwards, we discussed what we had written.    (1CY)

This was the first time Linda had tried this particular exercise, and I think it worked very well. It was particularly good at helping us reach Shared Understanding. We all had slightly different views of both patterns. Actually going through the group writing process helped make these differences explicit, at which point we were able to talk through our differences.    (1CZ)

Because Josh and I were the pattern-writing newbies in the group, we each collected the sheets for one of the patterns and promised to combine, edit, and rewrite them into a readable draft. I chose Collab:StoneSoup; Josh took Collab:KickOff. The plan for Day 4 (which was only a half day) was to workshop our results.    (1D0)

I ended the day with a brief overview of how blogs and Wikis integrated with Backlinks could be used to tie stories with corresponding patterns.    (1D1)

Chili Beer    (1D2)

Since that night was our last in Carefree, I decided to organize a margarita BOF. Earlier, somebody had told us about the Satisfied Frog, a legendary Mexican restaurant and bar that had “a thousand different kinds of margaritas.” This was the obvious place to hold our BOF, so Josh, Jerry Michalski, Gerry Gleason, and I trekked on over.    (1D3)

As with most legends, the facts had been slightly exaggerated. The Satisfied Frog only served one kind of margarita, although in fairness, it did give us the option of frozen versus on-the-rocks and with or without salt.    (1D4)

The restaurant did, however, brew its own special beer — chili beer — which was bottled with a serrano chili pepper. It had a nice kick to it, but it wasn’t overpowering. I recommend it to those with a a penchant for adventure and a bit of a heat tolerance.    (1D5)

ChiliPLoP, Day 2

Today, my workshop began in earnest. My goal for today was to collectively
develop a working definition of collaboration, and I’m happy to say
that we achieved that (see Collab:Collaboration). Tomorrow, we’ll
start exploring patterns in earnest.    (1BW)

I have a great group of participants:    (1BX)

We began the day by introducing ourselves to each other. I asked each
person to relate their best collaborative experience. Most people
found it a difficult question, which jives with my overall
experience. Nevertheless, we managed to get enough out of the stories
for a barebones definition to emerge.    (1C2)

I then sent the participants off to read Chapter 4 of Michael Schrage’s
No More Teams! while I refactored my Dialog Map, captured using
Compendium.
(I’ll post the final map at the end of the conference.)    (1C3)

After lunch, I showed the participants my Dialog Map for the first
time. From that point forward, the map became part of the
conversation (Shared Display). We walked through several scenarios —
some of which had emerged from the earlier discussion — deciding
whether or not they constituted collaboration and why.    (1C4)

Afterwards, I refactored the map again, and we started refining the
definition. The end result is at Collab:Collaboration. I’ll post
more commentary on the patterns mailing list.    (1C5)

Throughout the day, all of us recorded possible patterns on index
cards. We’ll use those as a starting point for our discussion
tomorrow.    (1C6)

Side Notes    (1C7)

I had made my expectations very clear at the beginning of the day: My
goal for the day was to have a working definition of collaboration.
(A pattern Ofra calls Set The Pegs.) So, having accomplished that at
the end of the day, we all were satisfied.    (1C8)

On the way to dinner, I ran into another workshop participant who
asked me how my workshop went. I said, “Great. We defined
collaboration.” He thought I was joking. We had spent the entire day
defining one term, and I was actually happy about that.    (1C9)

This was very much by design, and to be perfectly frank, I was glad
that we managed to come up with something workable by the end of the
day. I am a strong believer in Shared Understanding as a prerequisite
for effective collaboration. I’ve also been influenced by the
MGTaylor process, which suggests that spending about two-thirds of the
allotted time on Shared Understanding and Shared Language and the rest
on the concrete objective is actually more effective than attempting
to spend all of the time on the concrete objective. The reason is
that you are not capable of effectively attacking the concrete
objective without first developing Shared Understanding. The end
result is that you end up trying to solve both problems simultaneously
(and often unconsciously) and up doing both poorly. Additionally,
because you were not realistic with your expectations up-front,
everyone walks away disappointed.    (1CA)

The proof, of course, is in the pudding. It’ll be interesting to see
how my participants feel about our overall productivity by the end of
the day tomorrow.    (1CB)

Earlier that day, I described Blue Oxen Associates to another attendee,
who wondered, how will we make money if we give our pattern language
away? He was actually trying to tactfully ask how we make money,
period. I don’t think he realistically thought that we could make
money selling a “proprietary” pattern language.    (1CC)

My response: The real value is in the experience, not in the text
itself, which without context is simply more information in the
infoglut. If you can gain value from merely reading our material,
outstanding. We give it away to heighten the potential impact.
However, to truly appreciate the research, you need to experience it
firsthand. I see Blue Oxen Associates as a new type of learning
organization, where members learn by experiencing and participating in
what we study and what we learn. The value is in the experience and
in being part of our community, and that’s what we expect people to
pay for.    (1CD)

Finally, in the evening, Jerry Michalski demonstrated The Brain, a
Personal Knowledge Management tool. Sadly, it was late in the evening,
and only a few people saw the demo; tomorrow, I’m going to suggest
that he do it again. I had seen The Brain before, but Jerry’s demo is
particularly compelling because he’s been adding data to it since
1997.    (1CE)

One thing that really comes through with The Brain is how little
semantic richness you need for a tool to be useful. The Brain supports
typed links, but Jerry doesn’t use them. Instead, he uses topical
nodes to relate other nodes. In essence, it’s a barebones graph model
with a great UI, but its utility is tremendous. We don’t have enough
tools like it.    (1CF)

ChiliPLoP Day 1

Yesterday afternoon, I arrived in Phoenix, Arizona for Chili PLoP
2004. I hitched a ride with Ralph Johnson and Joe Yoder to Carefree,
Arizona, and soon found myself at the Lutheran Retreat Center, where the
conference is being held.    (1BJ)

The post-dinner agenda was to discuss the structure of the
conference. Other than the meal schedule (which is strictly
enforced), there is no structure. This is what differentiates
Chili PLoP from Hillside Group‘s other PLoP conferences. The setting is
more relaxed, and the agenda is entirely flexible.    (1BK)

Once we got business out of way, the fun began. There were a lot of
great conversations, and a few of us stayed up late into the night
chatting about everything from Pattern Languages to politics.    (1BL)

Tom Munnecke got the discussion started by asking about the
generativity of Pattern Languages. This is an ongoing beef that Tom
has with Pattern Languages, a misunderstanding that’s important to
clarify.    (1BM)

Tom’s thesis is that society is too problem-centric. For example, our
approach to healthcare is to cure sickness rather than to promote
healthy living. Tom’s GivingSpace project — and the reason he’s here
— is to identify and propagate patterns of uplift. This is a
wonderful effort. It’s related to our work on patterns of
collaboration, and it’s an effort I fully support.    (1BN)

Patterns are often defined as solutions to problems in a context.
Tom’s complaint is about the term “problem”; he think it prevents
patterns from being generative. “Problem” in this context, however,
means, “Something that needs a solution,” not, “Something that is
wrong.” In other words, describing things in terms of problems and
solutions does not necessarily prevent the solution from being
generative.    (1BO)

In fact, Christopher Alexander stresses the importance of identifying
generative patterns. Linda Rising cited an example first described by
Don Olson (and is also discussed in Linda’s book, The Patterns
Handbook
). Beginning skiiers often have a tendency to lean back,
something that will cause them to lose their balance. You could say
that one pattern is, “Don’t Lean Back.” This is not very useful
advice. Leaning back is an instinctive, not conscious action.    (1BP)

Don’s suggested pattern is “Hands In View.” This is a conscious action
you can perform, and the end result is that you lean forward. This is
a great example of a generative pattern.    (1BQ)

Ralph cited a similar example in software development:
qmail. The motivation for qmail was to
build a secure mail server. The approach, however, was not to
identify and fix every security problem. The approach was to design
small, modular programs that were easy to verify as secure. In other
words, security was an emergent property of the software’s design.    (1BR)

Other topics of note:    (1BS)

  • Ralph offered the following advice on naming patterns: Use noun phrases, not verbs.    (1BT)
  • Some patterns are not easily cross-cultural. For example, we talked about The Mexican Wave as a pattern of uplift. (I didn’t know that it was “the Mexican wave”; I thought it was just “the wave.”) Ofra Homsky suggested that Israelis would never do the wave. Joe Yoder said the same about Chicago Bears’ fans. The reasoning was that these fans are culturally noncomformist, and that they would never reach the necessary critical mass of fans in order to get the wave going. Similarly, Ofra explained that in America, when people want to increase their applause, they applaud faster. In Europe, people start applauding in rhythm.    (1BU)
  • Jerry Michalski related a story from Dave Grossman’s book, On Killing. Prior to World War I I, the U.S. military did a study that showed that in previous wars, only 10 percent of American soldiers were shooting to kill. This is because most humans naturally do not want to kill other people. The military reacted by changing its training methods, and by the Vietnam War, that number had increased to 90 percent. The point was that we are capable of changing people’s behaviors through training. The result, however, was not only increased killing efficiency but also the emergence of post-traumatic stress syndrome, which only started appearing after the Korean War, and an increase in the suicide rate among soldiers in wartime. The military had managed to change soldier’s behaviors, but at a terrible psychological cost.    (1BV)