Potential and pitfalls of using service design to facilitate soundscape thinking in city making

Federico di Fresco*, Luca Simeone

*Corresponding author for this work

Research output: Contribution to book/anthology/report/conference proceedingArticle in proceedingResearchpeer-review

44 Downloads (Pure)


Soundscape thinking - i.e., the capability to consider the experiential possibilities offered by a sound environment - has been characterized as critical for all those design activities connected to city making. Yet, traditional design disciplines operating within the urban domain (architecture, urban planning, service design, etc.) do not routinely engage with processes that systematically identify, control, and change soundscapes. This paper explores how customized service design methods - user journey, service blueprint, and a facilitation toolkit - have been envisioned and piloted within the context of a service design project anchored to the main football stadium of Copenhagen. These methods allowed the service designers and stakeholders involved in the participatory design project to understand existing soundscapes and tweak them by adapting specific touchpoints.
Original languageEnglish
Title of host publicationServDes 2023 : Entanglements and Flows. Service Encounters and Meanings. Conference Proceedings
EditorsCarla Cipolla, Claudia Mont’Alvão, Larissa Farias, Manuela Quaresma
Place of PublicationRio de Janeiro
PublisherLinköping University Electronic Press
Publication date2023
ISBN (Electronic)978-91-8075-476-7
Publication statusPublished - 2023
EventServDes 2023: Entanglements and Flows. Service Encounters and Meanings. - Rio De Janeiro, Brazil
Duration: 11 Jul 202314 Jul 2023


ConferenceServDes 2023
CityRio De Janeiro
Internet address
SeriesLinköping Electronic Conference Proceedings


  • Service Design
  • Soundscapes
  • Urban Studies


Dive into the research topics of 'Potential and pitfalls of using service design to facilitate soundscape thinking in city making'. Together they form a unique fingerprint.

Cite this