Coevolving Innovations

… in Business Organizations and Information Technologies

Evolving the Proposal to Collaborate on a Pattern Language for Service Systems from January, the initiative has now taken on a label of Service Systems Thinking.  The presentation at the 58th Annual Meeting of the International Society for the Systems Sciences in Washington DC was recorded, so that interested parties have the option of watching or listening ideas that have developed over the past six months, and reading the slides at their leisure.  Here’s the abstract:

“Service systems thinking” is proffered as a label for an emerging body of work that: (i) builds on social systems thinking (i.e. socio-psychological, socio-technical and socio-ecological systems perspectives) to advance a transdisciplinary appreciation of service systems science, management, engineering and design; (ii) explores opportunities to enrich Alexanderian patterns and categorized pattern catalogs into a generative pattern language; and (iii) collaborates on new platforms, moving from inductive-consensual wiki pages to a multiple-perspectives (federated) wiki.

The session was conducted in two parts, each of about 90 minutes.  The first part had a soft start playing some videos on the Smallest Federated Wiki by Ward Cunningham, since participants were coming back from lunch in another building.  The presentation alternated between projected slides, and live content on the federated wiki at  The agenda covered:

  • 1. Service Systems Thinking, In Brief
    • 1.1 An intentional representation
    • 1.2 An object-process representation
  • 2. Conversations for Orientation
    • 2.1 Systems thinking
    • 2.2 SSMED (Service Science, Management, Engineering and Design
    • 2.3 Generative Pattern Language
    • 2.4 Multiple Perspectives Open Collaboration
Part 1 Audio [20140730_1453_ISSS_Ing_ServiceSystemsThinking_128Kbps.mp3]
(85MB, 1h32m25s)
Part 1 Video (1h32m26s) nHD qHD
H.264 MP4 [640×360
238Kbps m4v
] (243MB)
716Kbps m4v
] (846MB)
2028Kbps m4v
] (1.4GB)
3341Kbps m4v
] (2.4GB)
WebM [640×360
135Kbps webm
] (176MB)
289Kbps webm
] (282MB)
0688Kbps webm
] (557MB)

In the second part after the break, the agenda covered:

  • 3. Conversations for Possibilties
    • 3.1 [Multiple Perspectives Open Collaboration]: We could have federated authored content on open source platforms
    • 3.2 [Generative Pattern Language]: We could be reoriented for unfolding wholeness, layering systems of centers and/with creating interactive value
    • 3.3 [SSMED]: We could have trans-disciplinary cooperation on service systems improvement
    • 3.4 [Systems thinking]: We could have service systems evolving from the systems thinking tradition

August 26th, 2014

Posted In: design, services, systems, technologies

Tags: , , , , , ,


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.

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 …

October 28th, 2009

Posted In: practices, technologies

Tags: , , , , ,

One Comment