ideation - meetupfiles.meetup.com/17394812/dux - ideation.pdf · 2015-09-15 · the ideation to...

From an idea to proven concept in five days.

Ideation

The ideation to implementation process.

Design Thinking

• 5 day design sprints.

• Get away from v2 and focus on iterative design.

• Prove a solution without developing based on assumptions.

• Answer critical business questions

• Design, prototyping, and testing ideas with customers.

• Use KPI’s and benchmarks to ensure success of our decisions.

Five Day Sprints

DAY 1 DAY 2 DAY 3 DAY 4 DAY 5

Kick-off Meeting Sketch Day Decision Prototype Test

Kick-off meeting, we get as many people involved as possible and identify the problem we will solve.

Day One

How Can We Do This?

• CEO explains the business restraints and how we got to our current solution

• Allow each department to explain what they know about the problem

• People write down “How might we” questions based on the discussions

• We can look into how competitors are solving similar problems

• Pull together analytics, current KPI’s, and market analysis

• Print out pages from the app/site and walk through the current solution

We Must Set Our Benchmarks and Define Our KPI’s Today

Experience Mapping• Experience Mapping depicts the way a user moves through the task

• It highlights the order of actions and pain points along the way

• This visual map grounds the conversation and keeps use on the same pageWhy?

Experience Mapping

• Loosely map out the flow a user takes to complete the task

• Don’t reference UI elements, just focus on the experience of the user

• Consider the value proposition

• Clarify how the user encountered the problem

• As a group everyone writes down each step in the process on sticky notes

• Each person sticks their flow on the wall right to left

• From here we can group common steps and divide the flow into tasks

• Everyone dot votes on the biggest pain points to identify what we focus on

How?

the Experience Map

Sketch, we get as many ideas down as possible and look for creative solutions.

Day Two

• Spend 5-10min taking notes and reviewing the “How might we” notes from the day before

• Each designer develops their own list of assumptions on how to approach the problemSTEP 1

• Run 4min rounds of sketch sprints

• We run multiple rounds coming up with different variations of the solution

• The idea is to get as many creative ideas out as possible

• This method is commonly referred to as crazy 8’s

STEP 2

Crazy 8’s

• Now each person involved takes 20min to build 1 or 2 storyboards from their best ideas.

• Designers redraw their ideas on sticky notes and stick them to a sheet of paper

• We then write a description of the action to the right of each sticky note

• Storyboards shouldn’t need to be explained

• Storyboards need to be anonymous as possible to ensure there is no favoritism

STEP 3

Storyboards

Deciding

Storyboards• Hang all the storyboards on the wall gallery style

• Everyone gets 10mins to vote on what they feel is the best solution

• You can vote on a storyboard or just a single step

• After voting everyone gets a few minutes to explain their ideas to the group

You should be able to run through this entire process 3-4 times

Our goal today is to concentrate everything down to a handful of designs to test.

Day Three

• We start by looking for conflicts in the storyboards

• Group the conflicts and discuss as a group the best solutions for the prototypes

• Thinking like this allows us to explore multiple ideas as appose to committing to one idea

STEP 1

• List all the assumptions that were made and find a way to test as many as possible

• This could be behavior, Messaging, or calls to actionSTEP 2

• Now we write out detailed storyboards on whiteboard of what we will prototype

• We map out every single interaction from opening an email to entering text

• This needs to be clear enough for the designers to design against

• This is done as a group and we all discuss the steps, business needs, and user needs

• At the end of the day we should have multiple storyboards and be ready to prototype tomorrow

STEP 3

Test Prep

• Create a form asking for the credentials you are looking for

• Post for interviewers on Craigslist, Facebook, Twitter

• Make it clear where testing will be and how much they will be compensated

• If this method is to pricey you could opt for un-monitored testing

Lets build this Mutha

Day Four

The Product Team Must Know Front-End Design HTML5, CSS3, SASS, JavaScript, jQuery, Handlebars, JSON

How We Work

• Prototypes are built from a living style guide

• We use a sub-set of CSS variables to work from

• We build in a middle-man app in a staging area

• We do this because we can test in the browser on any device

• The code is a jumping of point for developers (minimizing how much we through away)

• We can skip over high-res mockups

• Styles can be updated across all prototypes

• Everyone works in parallel, one building, one stitching, one writing copy in a JSON file

Test Prep• Start contacting people to make sure they can test tomorrow

• Test 5-8 people per design

It’s time to put our money where our mouth is with some user testing.

Day Five

One Way To Do This

Testing

• Try to lockdown to conference rooms for test day

• Conduct the test in one room with a facilitator and note taker

• Webex/Skype the test to the other room for anyone who wants to see the testing

• This helps everyone understand the users needs and pain points

• Once testing is complete look over all your notes and decide on one or two designs

• A/B test them at launch for 2 weeks to a month and adjust down to a final solution

Thank You