Upload
servdes
View
109
Download
0
Embed Size (px)
Citation preview
LowThresholdServiceDesign:DesktopWalkthroughJohanBlomkvistAnnitaFjukVasilisaSayapina
MAY27,2016 2Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
Desktopwalkthrough
MAY27,2016 3Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
• In this paper, desktop walkthrough is considered as a collaboratively constructed miniature of a service, and of which a set of artefacts is used in the construction.
Lowthresholdservicedesign
MAY27,2016 4Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
• Leading service providers often fail to deliver superior customer experience due to inadequate attention to the customer journeys – (Rawson, Duncan & Jones, 2013; Wright, 2012)
• Desktop walkthrough – aligned organizational processes – Harvard Business Review (2015): there is an increasing
demand for simple tools that rapidly and easily help decision makers and non-designers to (re-)design the link between onstage and backstage processes.
Designgames
MAY27,2016 5Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
• Design games as an alternative to other business model innovation approaches that are based on rational processes and causal reasoning – (Gudiksen, 2015)
AcOvitytheory
MAY27,2016 6Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
Thecase
MAY27,2016 7Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
Stages
MAY27,2016 8Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
• Exploration • Constructing a shared organizational context • Adding complexity • Presentation and clarification
Stages
MAY27,2016 9Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
Exploration • Artefacts shape the activity
– P4: “where does this happen?” – P2: “I have this nice tree. Can it be in a park?”
• Knowledge shapes the activity – P8 (while pointing to different places on the floor of the
store): “the thing is- it’s most often a queue-“ – P8 (picks up a Lego figure): “then we must have a queue
here”
Stages
MAY27,2016 10Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
Constructing a shared organizational context • Setting boundaries
Stages
MAY27,2016 11Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
Adding complexity • AddingBiggest part
complexity• Backstage
Stages
MAY27,2016 12Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
Adding complexity
Stages
MAY27,2016 13Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
Presentation and clarification • … or, why is this here?
MAY27,2016 14Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
Conclusions
MAY27,2016 15Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
• Domain experts, no clear boundaries but self-imposed,
• Participant feedback: more facilitation, better than talking or sketching, fun and meaningful, time to evaluate whether they were working on the right thing
• Black boxes • Level of abstraction • Limitations as triggers
Desktopwalkthrough-characterisOcs
MAY27,2016 16Blomkvist,Fjuk&Sayapina–DesktopWalkthrough
• Participants create their own rules – autotelic • (Almost) no prior knowledge or skills needed, low preparation
cost and introduction time • Requires starting condition, has no end condition • Outcome: an abstract, miniature version of a service and the
knowledge generated during the activity. • Enactments (can) occur • It can: gather people from diverse backgrounds and provide a
basis for collective, materially mediated and highly situated activities.
www.liu.se
LowThresholdServiceDesign:Desktop
Walkthrough