28. Service-Design logic is driven by an innate purpose of
doing something for and with another party,
and is thus customer-centric and customer responsive
33. Conclusions
• Understand Customer Needs & Expectations
• Map Customer Journeys
• Capture Events at Touchpoints
• Complete Event Data with CRM Data
• Use Patterns to Anticipate
• Adapt your Service Portfolio
• Use feedback loops to adapt and iteratively enhance
Interactions & Experiences
• Optimize for Business and Customer Outcomes
So we assemble all the data, and reconstruct the chain of events
Causes precede effects – necessary but not sufficient to understand causes
What of these things influence the purchase? Do people with loyalty cards buy more, or do people who buy a lot take out loyalty cards
You might focus on loyalty card – look at all the people who took out a loyalty card, and those that didn’t
Or this might be offering someone a discount – does that make a difference?
Most modelers spend 90% of their time on data wrangling
Turn this very granular data and semi-structured data into something more tractable