3 Ways to Add Design Thinking to Inceptions
Aug 20, 2015
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SUMMARY
OUR GOALS
!3
To share understanding about product scope
To focus on the most important users and their
journeys
To innovate on ideas to improve the user
journeys of key usersTo prioritize the features
OUR PARTICIPANTS
!4
Excellent participation from all attendees
TECHNOVATION
Mariana Rutigliano Samantha Quist Judy Ho
THOUGHTWORKS
Grant Joung Zichuan Xiong Natalie Hollier
OUR JOURNEY
!5
GO!
Define user need Identifying key users and prioritizing their
user goals
Building up customer journey
and identifying design challenges Set up journey
Prioritizing ideas and defining a
product roadmap Define roadmap
Ideate design Brainstorming ideas
to solve the identified design
challenges
PROCESS
STAKEHOLDER MAP
!7
We used two metrics to define the importance of stakeholders. As result we put our product focus on 4 user types: Students, Teachers, Mentors, and RCs.
Inte
rest
Influence
TeachersStudents
Mentors RCs
Ambassador
JudgesVolunteers
Partner Org Parents
V.CUniversities
Tech Companies
Prospective Ambassado
rs/RCs
PressFunder
STAKEHOLDERS RELATIONSHIP
!8
Discovering the relationship among the 4 stakeholders helped us understand how they interact with each others.
Mentor Teacher Student RC
Mentor
Teacher
Student
RC
“How did you approach this
problem?”
“How can you support the students?”
“I don’t know how to do this!”
“Here are the Technovation
updates.”
“How do we split up tasks in
curriculum?”“…” “This is too much
work.”
“Here are the Technovation
updates.”
“Let’s build this together!” “Let’s stay on task” “I’ll work on this,
you work on that.” “…”
“What are the resources available?”
“Are there mentors available?” “…” “What are your
best practices?”
SAYS TO
GOAL ANALYSIS
!9
Goal analysis helped us identify the goals of users, including as an organization our goals for them, and also their own goals in this experience. !The design will be focusing on these goals, and they are the success metrics for the future product - do we/they achieve these goals in new product?
Our goals
User
Their goals
GOAL DEPENDANCIES
!10
Goal 1
Goal 4
Goal 2 Goal 3
0
1
2
0
Goal1>Goal3>Goal2/Goal4
Priority
By identifying the dependancies among these goals, it helped us define the priority. The more dependancies by other goals, the higher priority it is in than others.
depends on
PRIORITIZED GOALS
!11
Student
Teacher
Mentor
RC
Be persistent Be innovative entrepreneurs Build meaningful apps Return and build
more complex apps
Use our curriculum Learn a new technology
Connect with teachers
Local partnershipProvide meaningful
feedback to improve Technovation
Dependency analysis helped us determine a list of highest user goals this product should achieve.
CUSTOMER JOURNEY MAP
!12
Student
Parents, teachers, or friend recommended
Learn about Technovation from source
“There’s a Hack Day!”
Recruit friends and form groups
Connect with a mentor
Register with Technovation
Start/follow curriculum
Attend field trips
Complete deliverables and submissions
Attend a local showcase
Receive score and feedback
May attend world pitch
Find resources to complete apps
Continue working on apps
Participate in alumnae community
Take more CS classes
Pre In After
User Goals
Be persistent
Meaningful app built
Return and build more apps
Innovative and entrepreneurs
CUSTOMER JOURNEY MAP
!13
Teacher
Learn about Technovation
Register with Technovation
Attend teacher training
Encourage students to attend a Hack Day and learn more
Connect with other teachers
Connect students for groups
Provide time and space for meetings
Connect with mentors
Provide guidance and resources
Recruit mentors
Initiate Technovation curriculum
Coordinate field trip logistics with mentor
Keep students on task
May run or work with RC to plan showcase
Celebrate and help student digest feedback
Pre In
User Goals
Use our curriculum
Learn new technology
CUSTOMER JOURNEY MAP
!14
Mentor
Hear about Technovation through professional mailing lists
Word of mouth
Mentor students as a Hack Day
Register with Technovation
Connect with team
Prep for curriculum provide guidance and resources
Be available for team’s questions
May volunteer for local showcase
Schedule and lead a field trip
Help keep students on task
Connect team to resources
Be available for questions
Complete post-survey
Volunteer to lead or recommend classes and careers.
Pre In
User Goals
Connect with teachers
Help students digest feedback
After
CUSTOMER JOURNEY MAP
!15
R.C
Hear about Technovation through partner orbs or word of mouth
Register as an R.C
Attend local R.C Training
Organize Hack Day sponsored by companies
Recruit mentors and teachers
Connect with teachers and mentors (local/org)
Technovation info source for teachers and mentors
Communicate time table to mentors and teachers
Coordinate and organize local showcase
Coordinate local press and media
Help regional winners find sponsorship
Organize workshops for students
Pre In
User Goals
Connect with local
partnership
Feedback to Technovation staff about teams
After
Recruit judges
Recruit alumnae to return and be evangelists
Disseminate information about CS opportunities
Provide meaningful feedback
DESIGN CHALLENGES
!16
Focusing on each step in the journey, we brainstormed the design challenges which will drive our design process.
Our design is aiming to take the challenges in the journey and all the solutions will be challenge-focused.
PRIORITIZED CHALLENGES
!17
How do we generate more interest in the platform?
How do we facilitate team creation?
How do we support teams to complete everything?
How do we inspire the girls to keep working on their
apps?
How do we make it rewarding for students to
stay engaged?
How do we evaluate program effectiveness?
We asked all our participants to prioritize all the challenges and as result we came up with a list of the most important design challenges.
IDEATION
!18
For each design challenge, we ideated on over 15 ideas on sketch paper. By sharing our ideas with one
another, everyone is on same page.
PRIORITIZED IDEAS
!19
We prioritized our ideas and put them back on the journey to see how they improved the whole experience which finalized our 7 core ideas.
FINALIZED IDEAS
!20
Curriculum Team Setup
Mentor Profile
Mentor Background Check
Mentor Matching
Consent Form Team Dashboard
Students can search for mentor profile, so that they can recruit a mentor more
easily
Technovation can perform checks on mentor’s profile, as
an assurance of mentor’s quality
Technovation can quickly match mentors and teams, so that it makes team prep
more easy
Technovation can make the consent process easier which
will can help enroll more students
A more trackable and supportive curriculum
ensures more persistent learning experience
Students and other team members can set up a virtual
team on the platform
Technovation is able to visualize and manage the
teams’ progress during the 12 week program
IDEA DEPENDENCY
!21
Team Setup (1)
Consent Form (1)
Mentor Profile (2)
depends on
Mentor Background CheckMentor Matching
Team Dashboard
Curriculum (1)
Dependency analysis helped us define the priority of each idea. Fewer dependencies mean more
fundamental and higher priority features.
PRODUCT ROADMAP
!22
Curriculum
Team Setup
Mentor Profile Mentor Background Check
Mentor Matching
Team Dashboard
Consent Form
v1.0 v2.0 v3.0 v4.0
Team setup and curriculum are two epics we think should be included in first release.
PRODUCT DESIGNSome conceptual design ideas
SUGGESTED SCOPE
!24
Curriculum Team Setup
v1.0Minimum Viable Product
▫︎ Student can see curriculum content ▫︎ Student can see tutorials in each section of curriculum ▫︎ Student can see what are required to do in each section of curriculum ▫︎ Student in a same team can see uploaded deliverables to each section of curriculum ▫︎ TBD
▫︎ Students can setup a new team in Technovation ▫︎ Student can invite friend to join the team ▫︎ Student can see all the team members in my team ▫︎ TBD
Curriculum
LESSON 1LEARN THE BASICS OF APP INVENTOR!Today you will learn a little about the Technovation program, explore the basics of MIT App Inventor (AI), and work through some tutorials. (For those of you who participated last year and are familiar with App Inventor 1 already, we recommend trying App Inventor 2. It’s awesome! The instructions in the following tutorials are all designed for App Inventor 2.) !To learn about Technovation, look through the Technovation curriculum, familiarize yourself with the 2014 App Theme, and take a look at the Judging Rubric. Also check out the Technovation Community. It’s an online conversation space where you can post messages to other Technovation participants around the world. You’ll find links to the Technovation Community and other useful resources on the right-hand side of every lesson page.
Update your team profile
Do it now
ACTION
Complete the surveyACTION
TUTORIALS
This tutorial is a basic level introduction into the User Interface of App Inventor (AI). It will teach you how to get started with AI and set up your testing using the AI Companion App from the Google Play Store. You will learn the basics of the AI functions to build an app that talks to you. Printable PDF
Talktome Part 1
Talktome Part 2
Done by Maria Richardson
Beginner
Basic
Advanced
1 / 12
Team Name
4 MEMBERS
Mentor Lori Longman 312-774-7562 email profile
Teacher Mari Wise 425-794-0163 email profile
Student Helen Jones 702-112-2133 email profile
Student Lara Bing 671-213-9300 email profile
invite
Nunc feugiat nulla sed tortor dictum feugiat nulla sed view
NEXT STEPS
NEXT STEPS
!28
▫︎ Final definition of MVP scope; ▫︎ Exploratory wireframing sessions with Technovation together to confirm page flow in defined scope; ▫︎Move intio project planning; ▫︎ Engage ThoughtWorks for support in delivery?
Related Documents
