TEST

Step 2 | Test and iterate

Guidelines

After the Kick-Off Meeting, it’s go time! As teams dive into their waves of Test "sprints," here are a few guidelines to help ensure the best possible outcome:

Validation of the prototype is not the point - It should be an artifact that facilitates a new, targeted conversation.

When you test, LET GO of your prototype, physically and emotionally. - Your prototype is NOT PRECIOUS, but the feedback and new insights it draws out are!
Don’t defend your prototype - Instead, watch how people use and misuse it.

Show, don’t tell - Avoid over-explaining, and simply let your users experience the prototype.
Ask users to talk through their experience - “What are you thinking right now as you are doing this?”
Observe - Remember you are testing the prototype, not the user. User mistakes can be valuable lessons learned.
Ask follow up questions - “What do you mean when you say__?”, “How did that make you feel?”, and “Why?”

Sources:

Stanford d.school, An Introduction to Design Thinking - “Wallet” Edition: Facilitator's Guide, 2012
The Interaction Design Foundation (July 2017) by Rikke Dam and Teo Siang

CASE STUDY: SHOW DON'T TELL

Thriving Communities Project - Dalton, GA

Prototype: “The Spot,” a downtown vacant lot turned into a pop-up performance and arts space.

In the Test Sprints phase of the project, the Dalton team had limited time and resources to test their prototype.

Rather than telling people they wanted to create “The Spot,” gauging interest, and polling for feedback, they just did it. The test of concept at “The Spot” in March 2016 attracted 300+ people for arts and music activities.

During the spring, summer and fall 2016, The Spot became a popular site for dozens of scheduled and impromptu arts and culture events.

In December, 2016 a local citizen gave $1 million for the construction of a permanent outdoor performance space at The Spot. The donation included an endowment for ongoing arts programming at the newly renamed Burr Park.

Optional alternative text if image doesn't load

Tools/Methods

Test Teams will have the support of a designated Innovation Coach during testing and will utilize a shared set of testing tools for data capture and learning.

Pre-post survey/ metrics (may be needed depending on prototype)
Weekly Coaching Check-Ins - To be scheduled by coaches with their teams
Test Sprint Log
Feedback Grid
Learning Consolidation Templates

Access Test Tools

Coaching check-ins

Test teams are supported by a weekly or bi-weekly check-in with an Innovation Coach. The purpose of the check-in is to understand what the team is learning and to help them iterate and evolve their test.

Meeting Details:

Who’s leading the meeting? The Innovation Coach leads and facilitates the meeting.
Participants? Test Team Leader(s) and Test Documenter are required. Test Team Members may also be invited to the meeting at the discretion of the Test Team Leader
Where? Virtual or in-person
How long? 30 min - 1 hour

Suggested Meeting Agenda:

Welcome. Reminder, we are testing to learn....
At a high-level, how has testing gone since last check-in? Any questions, any new insights, has anything been surprising, does the team want to modify the test in a future sprint?
Review sprint log - with strong focus on test assumptions and what is being learned. Documenter to add notes as conversation is progressing.
Cover administrative items (e.g., sprint log documentation; time for next call; key upcoming dates)
Closing & Next Steps

Go to step 3