Week 2 of 6 Virtual Sprint school sessions.
This week we covered the following:
Guest Speaker - Ariel Sims: Problem Framing
Setting the Stage
How Might We
Lightning Talks
13. Ariel Sim
Director of Design Anthropology
MaRS Discovery District
Ariel is interested in relationships that support
better, more thoughtful design. She focuses on
building technologies, organizations, and spaces
that encourage both kindness and productivity.
#SprintSchool@Design4AHS
14. Problem
Framing
with MaRS Solutions Lab
Ariel Sim is the Director of Design Anthropology
at the MaRS Solutions Lab. Her expertise is in
user research, experience design, design
strategy, and product development.
15. Problem Framing | MaRS Discovery District
Problem Framing
Problem framing is the process of describing and interpreting a problem to arrive at a problem statement. It is
considered an important step in problem solving as slight changes in framing may lead to a vastly
different problem solving process and resulting solutions. A well framed problem may be easier to solve.
Because <why it’s important / how it’s different>
How might we <description of patient/doctor/care provider’s shared goal>
1
2
3
4
Understand. Read broadly about the
industry and consumer setting.
Empathize. Talk to end users including
patients, doctors, and service
providers to understand their desired
outcomes and their challenges.
Describe. Describe each type of user’s
desires and outcomes. Make a “user
frame” for each user type that
privileges their needs.
Synthesize. Bring the various user
frames together into a single problem
frame for the innovation team.
To <action/outcome>
19. Setting the Stage
#SprintSchool
CHALLENGE
Frame the Problem/ User Research
TEAM
Decider / Facilitator / Diverse team
TIME and SPACE
Room / 2- days / 6 weeks
SUPPLIES
Post-it / Sharpies/ Voting Dots / Paper
@Design4AHS
28. 5-10 minutes per person
User Research
Service/product challenges
Expert opinions + best practices
Organizational requirements
#SprintSchool
Lightning Talks
@Design4AHS
30. Key takeaways
•Healthcare Sprints require prep-work
•‘HMW’ helps you reframe problems into
opportunities
•Lightning talks help you understand the problem
from different perspectives and expertise
#SprintSchool@Design4AHS
34. Next week…
o Guest Speaker: Andrew Siu
o Picking a Target
o Goal setting
#SprintSchool@Design4AHS
35. Call me maybe…
•Design Lab: design.lab@ahs.ca
•Twitter: @Design4AHS
#SprintSchool@Design4AHS
Editor's Notes
Ali
aa
Pick 2. aa
Where did the problem come from? Tell me more about this problem.
End of every session we need a summary and we bring that back . aa
Zayna Recap
You cannot QI you way out of the bottom. Iphone example
We talked about that that to be innovative and start solving problems differently we need to shift our mindsets. So Underneath sprints are these key mindsets:
Focus on human values : empathy for the people we are designing for and getting feedback from them
Embrace Experimentation: Prototyping is not simply to validate idea. We build to think and learn
Bias toward actions: Sprints are all about doing and making over talking and meeting
Radical collaboration: bring together different viewpoints and background, enables breakthrough and insights that emerges from diversity.
Show don’t tell: Communicate your vision in an impactful by visuals and telling good stories
Mindful of process : Understand the steps of the methodology and each of the stages has a unique goal
Which mindset is missing the most in healthcare? And why
Day 1 you understand your problem, decide what part of the problem to solve and decide what solutions to test
Day 2: design prototype versions of your solution and test with real users to get their feedback
Ali
Indigenous land recognition
Lori welcome
Rules of engagement
Shalyn- What was your biggest Aha! Moment?
Day 1 you understand your problem, decide what part of the problem to solve and decide what solutions to test
Day 2: design prototype versions of your solution and test with real users to get their feedback
Josh
1- Framing the problem are the first step that we need to acknowledge.
2- Team really important -> Decider Has the final say and good know resources – Decider 2) Facilitator- running the show/ coordinating 3) diverse team.
3- Time and Space: Room –> Space/ 6 weeks / book 2 days out. ( first thing supplies)
4- Supplies -
Day 1 you understand your problem, decide what part of the problem to solve and decide what solutions to test
Day 2: design prototype versions of your solution and test with real users to get their feedback
Complex community coalition problem
Note taking method that we use during the understand phase, which helps us capture insight and pain points and positively reframe them.
This is the first instruction we give to people. To take out their post it note and pens and capture their thoughts, ideas and write them out.
How might we is a brilliant
“How” guides team members to believe the answer is out there.
“Might” lets team members know their HMW statement might or might not work, and either possibility is okay
“We” reminds team members that the Design Sprint is about teamwork and building on each others’ ideas
Type into text box – 2 mins
lightning talk is the first activity of the understanding phase of a sprint, our goal is to get everyone in the room to understand the problem from different perspectives.
During LT we identify key speakers from the team and sometimes we invite speakers during the sprint, to speak for 5-10 minutes on a relevant topic related to the challenge. The LT can range from 30-60 mins. Topics can range from
Environmental scan
User perspective (patient)
Frontline staff perspective
Management perspective (business goals/budgets etc)
Indigenous land recognition
Lori welcome
Rules of engagement