Professional Documents
Culture Documents
Design For Civic Engagement: D.school Pop-Out // May 20-21 2017 // Holly May Mahoney & Megan Erin Miller
Design For Civic Engagement: D.school Pop-Out // May 20-21 2017 // Holly May Mahoney & Megan Erin Miller
d.School Pop-out // May 20-21 2017 // Holly May Mahoney & Megan Erin Miller
Welcome!
Your facilitators
Relating to citizenship
or being a citizen.
Service Design
as a toolkit…
Design Thinking framework
Service Design
Service
s
What is a service?
A service is…
UX
UI
Etc.
A service experience is a journey
A well-designed service can go
beyond providing & performing.
It can…
● Empower change
● Promote behavior
● Develop habit
● Impact society
So how might we design
services to enable
Civic Engagement?
Course Agenda
Day One Day Two
May 20, 1:00-5:00pm May 21, 1:00-5:00pm
● Introductions ● Create a journey map
● Building empathy ● Intro to Service Blueprinting
● Team formation ● Scenario breakdown
● Problem framing & ideation ● Blueprint your service
● Concept development ● Implementation planning
● Share out (what happens next?)
● Review course content
A message from
Rebeka Rodriguez,
Civic Engagement
Manager YBCA
ACTIVITY
Building Empathy
Group exploration of civic engagement topic using pre-work
You answered...
● How do you define civic engagement?
● What are the areas you are interested in making a difference?
● What do you currently do to be civically engaged?
● How do you know that your engagement has made a difference?
● How can services help you know that you’ve made a difference?
What is Civic
Engagement?
Civic Engagement
Themes
GO!
Introductions
● Introduce yourself
● What motivated you to join the class?
● Share an experience you’ve had around being civically engaged
Quick
Break
(5min)
EMERGING THEMES
Problem Framing
& Ideation
Articulate desired outcomes, and frame the design challenge as a
“How might we…” statement and brainstorm ideas
What are desired
outcomes around
theme?
Start individually, then share each idea as a group
Best practices for ideation
● No idea is a bad idea
● Build on each others ideas
● Move fast, get all ideas down
● As many ideas as possible!
● Respect each other
One idea per sticky!
Brainstorm ways to
help
Have an event Have an
Workshop together
Volunteer at town event
hall
Bad Good
Next, we’re going to
brainstorm solutions!
GO!
Quick warm-up!
GO!
How might we achieve
outcome through
civic engagement?
Start individually, then share and build.
Come up with as many ideas as you can!
GO!
Cluster & group ideas,
name your groups…
ACTIVITY
Citizen A B C Collective
Local C A B National
Low impact High impact
C A B
on _______ on _______
Develop your
service concept
Develop your service concept through the Service Concept Canvas.
Service Concept Canvas
Service Concept Canvas
Service Name
Name your service / brand
Description
What does your service do?
Guiding Principles
Key statements that your service stands for
Audience
The people you are serving (identify primary audience)
Motivators
The pain you are solving for your audience
Inconvenience of library
location, busy lives
Service Concept Canvas
Value
What do people get out of your service?
Channels
How will you reach people?
Partners
Who will help you?
Librarians, Software
developers, City officials
Service Concept Canvas
Startup Resources
What will you need to get started? (space, materials, staff, budget, etc.)
Sustainability
How will you maintain financial and resource stability?
Prototype
Journey Map
& Blueprint
Course Agenda
Day One Day Two
May 20, 1:00-5:00pm May 21, 1:00-5:00pm
● Introductions ● Create a journey map
● Building empathy ● Intro to Service Blueprinting
● Team formation ● Scenario breakdown
● Problem framing & ideation ● Blueprint your service
● Concept development ● Implementation planning
● Share out (what happens next?)
● Review course content
ACTIVITY
Draw
Describe
Doing -- -- -- -- -- -- -- -- -- -- -- --
Thinking -- -- -- -- -- -- -- -- -- -- -- --
Feeling -- -- -- -- -- -- -- -- -- -- -- --
A friend I go to the
Before Used to
Doing use
tells me to website
check out and d/l
Draw library
FSL app
Service Blueprinting
Break down your scenario into steps, and blueprint your scenario.
Introduction
to service
blueprinting
Before we talk about
blueprinting...
The “stages”
What is a service
blueprint?
A visualization of how a service works
both frontstage and backstage.
A blueprint visualizes...
● Actions
● Actors
● Touchpoints
● Systems
● Policies
● … and more
www.practicalservicedesign.com/the-guide
“Future-state” Blueprint
anatomy
Step --
Citizen --
Touchpoint --
Service Actor --
Line of visibility
Service Actor --
Touchpoint --
Systems --
Policies --
+
Step -- -- -- -- -- -- -- -- -- --
Citizen
Touchpoint
Steps in a scenario
Service Actor
Service Actor
Touchpoint
Systems
Policies
Step -- -- -- -- -- -- -- -- -- --
Citizen -- -- -- -- -- -- --
Touchpoint -- -- -- -- -- -- --
Service Actor -- -- -- --
Service Actor -- -- --
Touchpoint -- -- --
Systems -- -- -- -- -- -- -- --
Policies -- -- -- -- --
End-to-End
Step -- -- -- -- -- -- -- -- -- --
Surface-to-Core
Citizen -- -- -- -- -- -- --
Touchpoint -- -- -- -- -- -- --
Service Actor -- -- -- --
Service Actor -- -- --
Touchpoint -- -- --
Systems -- -- -- -- -- -- -- --
Policies -- -- -- -- --
Blueprinting multiple scenarios
So, how do we blueprint?
Our process
Scenario
Journey Map
+ Steps Blueprint
1 5
2 6
3 7
4 8
Which scenarios should
we blueprint?
Key scenarios
●
●
“Signature moments”
Critical service experiences
Just enough
●
●
Key points on the service lifecycle
When things go wrong
perspective...
● Things you want to test and validate
Remember… A blueprint is
a prototype
What makes a good scenario?
● Choose the right “altitude”
● Where does it start, and where does it end?
● Should capture a complete service experience
What makes a good scenario?
Too small: Too big:
-- -- -- -- -- -- -- -- -- --
Steps in a scenario
Breaking your scenario down into steps
● Define the start and end of your scenario
● What are all the steps (actions) that happen, both on the frontstage and
backstage?
Example scenario step breakdown
Future State Library: Order a book 8. Receives confirmation email
Step definition
Specific action happening within
the scenario Book gets
delivered
Blueprint Anatomy
Citizen (action)
What action the citizen is doing in
this step Signs for and
receives book
Blueprint Anatomy
Frontstage
Touchpoint
What the citizen is interacting
with in this step
Delivery form
Blueprint Anatomy
Frontstage FedEx
service actor delivery
(action) Driver hands
Who (from the service) the citizen
is interacting with, and what
over book and
action they are doing
gets signature
Blueprint Anatomy
Line of visibility
Blueprint Anatomy
Backstage
service actor Librarian gets
(action)
Who (from the service) is doing
the book
something backstage, and what
action they are doing
Blueprint Anatomy
Backstage
Touchpoint Book shelves
What the service actor is
interacting with backstage in library
Blueprint Anatomy
Systems
Technical systems, infrastructure,
automation, etc. that supports the
service
Library
database
Blueprint Anatomy
+?
Add your own layers!
...
Step --
Citizen --
Touchpoint --
Service Actor --
Line of visibility
Service Actor --
Touchpoint --
Systems --
Policies --
+
Step -- -- -- -- -- -- -- -- -- --
Citizen
Touchpoint
Steps in a scenario
Service Actor
Service Actor
Touchpoint
Systems
Policies
Top to bottom Left to right
Step -- -- -- -- -- -- -- -- -- --
Citizen -- -- --
Touchpoint -- -- -- Use the
Service Actor -- -- layers as a
Service Actor -- checklist for
Touchpoint -- each step
Systems -- --
Policies --
Step -- -- -- -- -- -- -- -- -- --
Citizen -- -- -- -- -- -- --
Touchpoint -- -- -- -- -- -- --
Service Actor -- -- -- --
Service Actor -- -- --
Touchpoint -- -- --
Systems -- -- -- -- -- -- -- --
Policies -- -- -- -- --
Example as warm-up
GO!
Blueprint your
scenario!
Create a service blueprint of your future-state scenario.
Adoption Implementation
blockers blockers
Step -- -- -- -- -- -- -- -- -- --
Citizen -- -- -- -- -- -- -- -- --
Touchpoint -- -- -- -- -- -- -- --
-- --
Service Actor -- -- -- --
Service Actor -- -- --
--
Touchpoint -- -- --
--
Systems -- -- -- -- -- -- -- --
Policies -- -- -- -- --
Harvest your blueprints for:
● Roles & responsibilities
● Policies/rules to define
● Touchpoints to create
● Space requirements
● Processes to define
● Design requirements
Create a plan!
● Who will do what? (RACI)
● What is most important to implement first? (backlog prioritized)
● How will you roll it out? (roadmap timeline)
● How will you communicate it? (communications strategy)
● How will you measure your success? (KPIs)
● How will people need to change? (change management plan)
Share your feedback on today’s class, and the class overall on post-its.
GO!
d.school class
feedback
Anonymous feedback for the d.school –
https://goo.gl/forms/Y7TwqjA1N2AsAcqO2
Stay in touch!
Holly Megan
holly@dschool.stanford.edu meganem@stanford.edu
@hollymaymahoney @meganerinmiller
Thank you!
Holly & Megan