Coevolving Innovations

Digital cameras have become so common that they’re often now a feature in mobile phones and audio players.  Pressing a button to capture a snapshot of time is so easy.  The workflow of storing, printing and sharing those images is complicated.  Many would like to return to the days when we would just take the film cartridge out of the camera, and drop it to a photo lab for processing (often in about an hour).

People take more photographs digitally than they did with film cameras.  In a six-month study in 2000, when digital cameras were relatively uncommon, subjects (aged 24 to 38) took 200 to 1000 (with an average about 500) photographs, compared to their prior non-digital accumulated collection of 300 to 3000 (with an average of about 1000) pictures (Rodden & Wood 2003).  This means that when digital cameras were relatively expensive — and camera phones didn’t yet exist — people were averaging about 1 to 5 photos per day!

People presumably use cameras because they want to be able to retrieve the images later.  In a study of 18 parents, the value of long-retrieval of family pictures was high (i.e. around 4.7 on a scale of 5).  On experiments of 71 retrieval tasks — finding birthdays, family trips, first pictures of a child, etc. — 61% were successful, taking about 2.5 minutes each.  On the 39% of unsuccessful retrievals, subjects gave up after about 4 minutes  (Whittaker et al. 2010).  This effectively means that, on average, nearly 40% of the digital photos taken last year are lost, and considerable persistence is needed for them to be refound.

I. What activities, platforms and artifacts are involved with managing digital photos?

Digitalization in photography has replaced trips to the photo lab with the copying of electronic files.  Industry standards have stabilized so that image files can be readily copied from cameras to personal computing devices, and onto web servers.  Here’s a diagram of some of the activities, platforms and artifacts in digital photography.

Based on this diagram, let me (a) pose some questions for reflection on the choices we implicitly make about managing photos, (b) outline some popular alternatives, and (c) describe the way I do it, myself.

II. What type of photographer am I?

In the Adaptive Enterprise research that I had conducted between 1998 and 2001, I was primarily focused on conversations for action, towards a commitment action protocol. I extended, in 2008, those ideas into a research paper to recognize (at least) four types of obligations:

• commitments to produce a deliverable;
• commitments to follow a process;
• commitments to provide a capability; and
• commitments to contribute to a relationship.

These four types were not considered exhaustive, but helpful in understanding how service systems work.

In the background, I’ve always known that there are other kinds of conversation.  To be explicit about these, I’ll refer to a 1987 article by Terry Winograd (that was a revision of 1986 workshop paper reprinted in 1988).

Winograd provides the foundations back to speech act theory, from Austin, and then Searle.

Austin (1962) noted that not all utterances are statements whose truth or falsity is at stake. Performatives, such as I pronounce you husband and wife are actions, which can be made appropriately (felicitously) or not, but which are neither true nor false in a simple sense. Similarly, the language actions of commands, questions, and apologies are not descriptions of a non-linguistic world.

Searle (1975) identified five fundamental illocutionary points — things you can do with an utterance:

While some of my activity on the Internet is recreational, I continue to play with web tools to learn about the ever-evolving technology.  While the average person has become comfortable with e-mail, web feeds are still pretty much a mystery to many.  The RSS and Atom specifications first used by newswires has become the principal form of web syndication for blogs and social media.

I’ve recently rearranged my pattern of web use (again).  To encourage readers to think about how they use the Internet, let me pose four questions.

• 1. Which principles on web content do I have in mind?
• 2. How do I post content, and flow it?
• 3. Why have I recently changed my use?
• 4. What consideration should web users have for their content?

With the way that technology continues to evolve, the specific web applications may change … but the pattern should remain the same.

1. Which principles on web content do I have in mind?

My attitude is reflected in two ideas:  (a) open content with attribution, and (b) open platforms with interoperability.

(a) Open content with attribution reflects that I like to share my learning with other people.   Posting the content on the Internet improves access and distribution.  I understand the workings of copyright — there’s a Creative Commons license on this blog — which means that I retain ownership of my words, on the condition that if someone wants to formally cite the work, he or she should cite me as the source.  I’m not an author who makes his living at writing, so simple acknowledgement is normally sufficient.

(b) Open platforms with interoperability means that I don’t want my content inappropriately trapped in places inaccessible to others.  I appreciate instances when content should remain private, respecting the needs of others and/or commercial conditions, but secrecy should be the exception rather than the rule.  The content should flow freely (i.e. free as in liberty), rather than having to stumble through technological obstacles.

2. How do I post content, and flow it?

With these principles in mind, I’m reforming the way that I interact on the web.  Here’s a diagram (linked to another page in an interactive map).

When a group of people come together for sensemaking about a situation, it’s pretty typical for someone to start sketching out boxes and lines to improve the clarity of the ideas.  Amongst 2 or 3 people, this might be sketching on a napkin.  Convening in an office usually suggests that a flip chart or a whiteboard will be used.  These media have the advantage of expressiveness — effectively conveying ideas — with the challenge of replicable precision and subsequent intelligibility to people beyond the original participants.  As the average business professional has become more adept with computer-based tools, presentation graphics — often as dreaded Powerpoint slides — are common.  Although more advanced drawing tools (e.g. vector graphic editors) and specification languages (e.g. UML and SysML) are easily available, the gulf between “easy-to-use” office productivity tools and “rigourous” modeling tools has yet to be bridged.

Based on a legacy of collaborations with IBM Research, my colleague Ian Simmonds pointed out the upcoming workshop on “Flexible Modeling Tools” at Cascon 2009 — a short commute within the Toronto area — with the following description.

This workshop will explore why modeling tools are not used in many situations where they would be helpful and what can be done to make them more suitable.

For example, during the exploratory phases of design, it is more common to use white boards than modeling tools. During the early stages of requirements engineering, it is more common to use office tools. Yet in these examples, as in many other tasks, the advantages of modeling tools would be valuable – providing multiple views for visualization and convenience of manipulation, providing domain-specific assistance (e.g., “content assist”), ensuring consistency, etc. Why, then, are they not used? The many reasons include: learning curve, interaction medium, rigidity and lack of support for informality.

This workshop will bring together tool builders and people who have or might use tools for their software development activities to explore the barriers inherent in current modeling tools and what can be done to remove these barriers. It will also address what key research challenges remain.

• Chairs: Harold Ossher, IBM Research; Andre van der Hoek, University of California, Irvine; Margaret-Anne Storey, University of Victoria

The day-long workshop on November 2 should be more of a generative conversation, rather than an exposition of completed research.  Contributions to the workshop are in the form of position papers.  On my last visit to the UK, I had some discussions with Gary Metcalf and Jennifer Wilby on current research into an emerging science of service systems, as well as ongoing client work with municipalities in Canada.  We wrote this up, and the position paper was accepted for the workshop.

Introducing modeling tools to non-technical business professionals: some cases with preliminary observations

A position paper prepared for the Flexible Modeling Tools workshop at Cascon 2009, by …

In engagements with clients/customers, my work often includes system envisioning: facilitating the description of a collective desirable future (on a horizon of maybe 1 to 3 years out).  Once a group has converged on a future state or vision, moving forward is merely a matter of will.  Defining that future state, however, is more art than science.  In addition, with many more businesses operating as service systems, getting a handle on the invisible work that will be performed can be a challenge.  Work practices will coevolve with new technologies in ways unfamiliar to experiences to date.

In discussions with my colleagues, differences between their engagement approach and mine became clearer.  I understand and appreciate the process-based methods (e.g. process consultation by Ed Schein) used by large consulting teams, but my typical engagement is now timeboxed to a few weeks elapsed time, with just a few interviewers.  Some executive sponsors may ask for an interview guide in advance of coming onsite, but I don’t use a formally-structured guide.  The context for 60-to-90 minute interviews are light — we want people to talk about time-intensive activities and annoyances in their jobs — and generally find that interviewees would be happy if small adjustment could be made so that each would have to do less work.

Reflecting on these methods, I’ve seen a pattern of three stages in this approach:

• (1) Induction: Rather than coming in with a preconceived model of how work gets done in a particular business, let those closest to the activities speak freely.  From the data collected, converge on common patterns in issues and/or problems that can be reviewed, validated and prioritized for resolution.

When the Master’s program on International Service Business Management started up at Helsinki Metropolia University of Applied Sciences in 2006 — then it was Helsinki Polytechnic Stadia — I was one of the original authors for the curriculum.  I happened to be in Finland in September 2006 and 2007, so I gave some of the early lectures.

My schedule in 2008 didn’t line up, but I did happen to be back in Finland in September 2009.  Thus, I gave an updated version of the lecture in one of the first classes for the session.  The content included:

• A. Introduction
• B. The changing world, and SSMED
• C. Service-dominant logic
• D. Service as a paradigm
• E. A smarter planet
• F. Artifacts / feeds to follow

The lecture ran just under 2 hours.  I’ve posted the slides on the Coevolving Innovation Commons, under Publications.