In a previous post I mentioned my exploration of the notion of design patterns and speculated on the possiblity of using a patterns approach to creating better live experiences and events.

I sketch one out as a first stab.

--

Name – Rapid, Auto-Forward Presentation

Problem – Presentations are poor ways to communicate information when more efficient methods that allow the receiver to consume information on their own time, in a formate that is most convenient (such as email, wiki, video, etc). Some people are poor presenters and go on for too long. Powerpoint presentations, specifically, are often badly designed and executed, which bores and/or overwhelms the consumer with too much information. There are not enough resources (money, time, space, contenct) to execute a full length presentation.

Context – There is the opportunity to present a limited amount of information in a novel way.

There is the technological capacity to present a Powerpoint presentation.

Presenters should be willing to prepare and rehearse the format or their struggles may become more engaging than the information they are trying to convey.

There are limited resources (time, money, space, experience, content, etc)

Forces (influencing the design) – Need to present information to live audience.

Expectation that an event feature a speaker.

Not every presenter has appropriate content knowledge or is an engaging performer.

Audience is bored with typical presentation formats, is looking for novelty, and/or wants to have fun while they learn.

Limit on amount of time to present because of costs.

Desire to use Powerpoint technology.

Solution – Limit the presenter to set number of slides, which will auto-forward after a set amount of time. The auto-forward feature is standard to Powerpoint-type presentation software.

Set up video projector and screen. Connect projector to laptop with presentation software and the specific presentation loaded onto the hard-drive. Setting up the laptop off stage, away from the presenter will discourage the presenter from fooling with the presentation during the presentation (ie. backing up).

Set up lights and mic/speakers for the presenter if they need it to be seen/heard.

Have someone at the laptop start the presentation, and load the next when it is done.

Often a series of these presentations are presented together.

Introductions between presenters is discouraged because it drags out the event and is contrary to notion of rapid advancement.

Too many presentations grouped together can exhaust the audience just as quickly as a single long presentation.

Examples – Two popular methods at the 20 slides for twenty seconds each (20x20 or Petcha Kucha) and the Ignite format.

Resulting Context – A satisfying amount of information can be quickly transmitted to a live audience. Presenters are relieved to have gotten through the experience. Audience may be interested to learn more and to talk with presenter further. Presents enough information to form the basis of further conversation and debate. Entertainment. Provides concise experience for audience to relate to friends as stories.

I have been fascinated by the notion and culture of "design patterns" of late. For those of you late to the game like me design patterns is the notion of capturing and communicating contextually relevant rules-of-thumb about a field of knowledge.

Rather than a set of abstract principles, best practices, or things like style guides...the key difference in the approach is that a design pattern is a typical solution to a specific, recurring problem.

It also seems to me that it is a great way to capture bodies of knowledge that are infused with a decent degree of subjectivity and complexity. It is also theorized that a bunch of patterns might fit together not just as a set of data but make up the units of a language for communicating a kind of design thinking.

Here is some wiki knowledge: 

http://en.wikipedia.org/wiki/Pattern_language
http://en.wikipedia.org/wiki/Pedagogical_pattern
http://en.wikipedia.org/wiki/Design_pattern
http://en.wikipedia.org/wiki/Interaction_design_pattern

Now is turns out that this approach was famously fleshed out in architecture by fellow named Christopher Alexander in a series of books that attempt to capture a humanist approach to building, that can be applied by even a novice. Alexander seems to have a bit of a cult following. The design pattern approach apparently set off a big movement in computer science, user experience design, game design, and even education.

There is also a fun notion of the anti-pattern, which is what not to do.

I came to this originally when I was talking to a user-experience designer earlier this year and he made an offhanded comment about UX patterns...I was curious about how he seemed to think you could capture the rather subjective issues we were discussing but I forgot about it until I was recently reading The Art of Game Design (a good one) and the author mentioned it and so I stumbled into a rather interesting world.

It seems like it is one of those internet conversations that has seen a flurry of activity but reached a dead end and has faded away. Particularly in the early 00's it seemed there was a bunch of discussion on the UX side but then it stops...see this discussion as a prime example: http://www.lukew.com/ff/entry.asp?347

What seems to be happening is that the language and the logic is easier to talk about than the subjective intangibles which then is smothering the fundamental insight. This is a typical anti-pattern I think best known as "There is nothing less funny than talking about comedy." In the blog discussion linked about you see that much of the debate is supposedly about what patterns are useful for and such but the currency of the debate is really about what makes up a good pattern and what categories make the best template for writing them.

An interested bit of internet culture aside the thing that intrigues me is the capacity for this mode of documentation to capture elusive things like performance and live experience design best practices.

On the art side for instance, performance art struggles as a discipline because it doesn't have a clear body of practice yet...it is more of a interdisciplinary hodgepodge which is interesting from an innovation perspective but less so from a credibility standpoint. How do you teach something for instance that has no fundamental set of skills?

On the live experience side of things, I have been struggling to find a way to capture this as a body of knowledge that is broad enough to approach any kind of live event...from a birthday party, to a corporate conference, to a day at the park. Seems like a series of live event patterns might be an interesting approach.

I attended the performance on Wed and was generally pleased.

I found the music appealing in filmic and populist way...it is similar
to the Kundun soundtrack minus the deep lingering tones but has the
same swirling flutes.

The playful and adventurous feel also reminded me of Danny Elfman's
film work and could have served easily as a Batman score.

I admit I barely paid attention to the transcription of the words. I
found the content too heavy and clunky to worry about. Absent that
baggage, the music was a nice platform to let my mind wander and
scheme.

I like the notion of this Kepler figure as the topic of the
performance. Supposedly he is credited with writing the first science
fiction novel and his mother was accused of being a witch. The work
was certainly spacing and ascendant.

Visually at times some amber light on the orchestra melded with a very
polite projection of space on the back wall to give some lovely
effects. But is general the visuals were too tight and civil for my
tastes.

I passionately hated the railing that stood behind the chorus. It was
exposed during the many time the chorus was absent. It created a
visual barrier between the orchestra which filled the stage and the
projections on the back wall. If seemed there for safety but negligent
in how it impacted the scene.

A few weeks ago I attended Social Change Camp in NYC. I led a session discussing on the merits of iterative vs. revolutionary/holistic design approaches. I asked if there are any other approaches to creating change.

This topic came up for me while I was watching the President's health care speech to congress and noticed that one of the big applause lines had to do with the idea that they would not make radical change. I recognized at that moment that I think there needs to be significant change, not only in health care but a number of areas of society. The question is how do you get there.

As a citizen, it worries me that perhaps we don't have the communication/collaboration tools, the political process in place to achieve real change. David Brooks makes this argument to Gail Collins in the NYTimes:

...there is a broad consensus on what we need to do to solve many of our major problems, but no political way to get there. Most experts of left and right believe we need a gas tax in order to address our energy problems. No political way to get there. Most believe that we need a flatter, fairer tax code, probably based on a consumption tax. No political way to get there. Most agree that the fee-for-service system drives up health care costs and the employer based insurance system is unsustainable. There is apparently no political way to change these things. Most experts agree that teacher quality is crucial to the schools and that bad teachers need to be fired. Again, no political way to do this. - David Brooks

As we now approach the endgame of the health care reform debate I think there will be a lot of rewriting of the recent history. There was a lot of fear around the tenor of the public debate with people talking over each other and questions raised of President Obama's capacity to keep a hold on the debate.

I found the degree of public investment in this debate interesting and appropriate following the degree of interest there was in the presidential election. I found it refreshing that the debate wasn't managed from the top for the most efficient and politically tidy outcome.

This line stuck out to me in the book "Washington's Crossing", by David Hackett Fischer:

Our republics cannot exist long in prosperity. We require adversity and appear to possess most of the republican spirit when most depressed. -  Benjamin Rush

Rush is a lesser known Founding Father. He felt it was a national habit to avoid dealing with difficult problem until it was nearly impossible. It is interesting that this was apparent even at the founding of the nation.

I also remember the Winston Churchil line - America will always do the right thing, but only after exhausting all other options.

America seems to have a reputation. I assume it is at least in part due to our geographic location which insulates us from much of our conflicts and our short election cycle...but as a creative it seems like creating change is also a design challenge. 

You can witness this same debate on how to create change also being fought in the development of websites & software applications. It is a debate between iterative Open Source development and more holistic design driven approaches...with the design of user experience being a main point of contention. You can tap into one such debate here at the Mark Boulton blog.

Mark Boulton is an interesting designer with a modernist, top-down, holistic midset. Perhaps not unexpectedly, when he took on the challenge of working with the open source Drupal community he encountered some challenges getting buy-in from the community and figuring out how to communicate his process openly but also maintain ownership. There seem to be reactions to the tone of some of his communications. But in the end there is a fundamental struggle between worldviews going on here. Does change need an architect or can it effectively be crowdsourced. Sounds a lot like the old Modernism vs. Postmoderism debates to me.

Now-a-days, I typically explore these question in designing events and live interactions. In my work at Double Happiness and putting on participant-driven events like Goodmeets, I am very attracted to open, collaborative approaches. Fr one thing they are effective and for another they are more affordable.

On the other hand when I make performances, I appreciate the importance of owning your ideas. It allows for you to work towards a kind of perfection.

I think the clash of worldviews here is tough to resolve but I am wary of defaulting back to a Modernist, holistic planning scenario despite the pleasures of seeking perfection. I wonder if there is not another way.

In our discussion at Social Change Camp, we ended up discussing a kind of "incremental revolution" approach to change. Saying that building consensus in small steps is important but with an eye toward reaching tipping points were real change takes place.

Some kind of incremental revolution seems like a interesting notion to me and it makes me aware that the key is still transparency...transparency that is often politically and personally challenging. 

One reassuring argument I saw in the midst of the health care debate came from Michael Pollen. He argues in the NYTimes that even if a weak healthcare bill passes that it would change the power dynamic in the food industry. That by placing the incentives on preventive care you place the health care industry on the side of reform and create a powerful counter-lobby to the entrenched food biz lobby. It would be easier for me to swallow incremental change in things like the health care bill if there was a clearer path to these kinds of tipping points laid out for me as a stakeholder.