David Ing


What is properly required to take the learning on generative pattern languages from the built environment and software development communities, to a world of service system thinking?

This position paper winds back to early days of Center for Environmental Studies, and presents an alternative view on the 1968 Multi-Service Center work, informed by 21st century developments in service systems science. The conventional format for a pattern language has settled into a three-part rule of relations between context, problem and solution. An alternative format of (i) voices on issues (who + what), (ii) affording value(s) (how + why), and (iii) spatio-temporal frames (where + when) is proposed, with a straw man example.

Methods from the 1985 Eishin campus project, published in 2012, are compared against practices that have become common in agile development.

The conceptual shifts from built environment to service systems thinking are expressed as (i) amplifications, (ii) rephilosophizations, and (iii) reinterpretations. The generation and legitimization of pattern languages is considered across a community, with a shift from publishing in books on paper to collaborating with online technologies such as wiki.

At the 2014 PLoP and the 2015 PURPLSOC conferences, the idea of extending the pattern language for environment structure into a new domain of service systems thinking was introduced. In 2016, this idea has been further developed as a baseline for further discussion


David Ing, "Pattern Manual for Service Systems Thinking: A proposal for discussion", Proceedings of the 2016 International PUARL Conference .


Presentation slides


Audio [20161029_PUARL_Ing PatternManualS2T.mp3] (20MB, 20m19s) [20161029_PUARL_Ing PatternManualS2T_3db.mp3] (volume boosted 3db, 20MB, 20m19s) [20161029_PUARL_Ing PatternManualS2T_6db.mp3] (volume boosted 6db, 20MB, 20m19s)
Video HD (20m19s)
H.264 MP4 [1280x720 384Kbps m4v] (70MB) [1280x720 5000Kbps m4v] (76MB)
WebM [1280x720 110Kbps webm] (34MB) [1280x720 826Kbps webm] (153MB)

Previous Post Next Post

2016/10/28 Pattern Manual for Service Systems Thinking