accelerating product delivery with design sprints

Post on 02-Dec-2014

457 Views

Category:

Design

3 Downloads

Preview:

Click to see full reader

DESCRIPTION

Technology teams both big and small alike are under tremendous pressure to ship innovative and compelling products day-after-day and week-after-week. Industry concepts such as “agile software development” have arisen to help, but only addressed a piece of the technology organization, engineering. However, as we all know, it takes more than Engineering to build a great product, quickly. With the emergence of Design Sprints via Google Ventures, we finally have playbook that brings agility beyond engineering and into the Product Management, and User Experience teams. Design Sprints allow technology organizations holistic acceleration with their learning/prototyping and thus their product delivery. In this talk I’ll explain how Fooda’s technology organization has adopted this emerging playbook into our technology organization, and our lessons learned thus far.

TRANSCRIPT

Design Sprints

anthony broad-crawford@broadcrawford

cto, @fooda

cto, ceo, cpo

the intersection of product, user experience,

and engineering

Product Metabolism

first, what is metabolism?

it's the set of life-sustaining chemical

transformations within the cells of living organisms

what is product metabolism?

it's the set of life-sustaning transformations of key-

learnings and opportunity into released product

changes

you want a high metabolism

that means your organization can quickly take an opportunity and have a solution in your

customers hands, quickly

this should be no more than 2 or 3 weeks

but this is really tough given our current product

development methodologies

So What's Wrong With Our Existing

Methods?

waterfall

scrum

kanban

free for all

none of these make the organization agile

enter design sprints

What's A Design Sprint?

5 day process to go from an idea, problem, or opportunity, to a user

tested high fidelity prototype

Understand > Diverge > Converge > Prototype > Test

Understand1. Review the opportunity

2. Conduct lightning demo's

3. Layout existing user flows

4. Define success

5. Review existing research

6. Interview internal stakeholders

7. Review existing analytics

Diverge1. Mind map

2. Crazy eights (sketching excercise)

3. Story board

4. Silent critique

5. 3 minute critiques

6. Super votes

7. Repeat

Converge1. Search for conflict

2. Best shot or battle royale

3. Identify assumptions to test

4. Whiteboard your user story(ies)

Prototype1. Make it minimally real

2. Write real copy

3. Divide and conquer

4. Lightning critiques

5. Review with an outsider

Test1. Review your assumptions

2. Identify your key questions

3. Setup observation room

4. Test any A/V in advance

5. Conduct your tests

6. Assess your findings

So What Do We Think?

love it, love it, love it

we've conducted 5 design sprints

across our web products, mobile products, and even a visual rebrand

What Have We Learned?

A Lot

setup a product war room

don't walk in with a solution

don't skimp on the prep : data

don't skimp on the prep : design brief

don't skimp on the prep : external involvement

don't skimp on the prep : sizing

don't skimp on the prep : day 1 interviews

assign a sprint lead

assign someone to start recruiting day 5 testers, on

day 1

invest in tools like silverback

invest in codifying your findings

prioritize your sprints against your roadmap

allow sprints to beget sprints

allow sprints to inform your roadmap

involve engineering

involve the executives on day 1

involve key stakeholders on day 1

conduct retrospectives just like engineering

Big Shout Outs To ...

andrea de almeidaproduct designer @fooda

@andreaalmeida

cameron garrettproduct designer @fooda

@camgrt

Jimmy Skurosproduct manager @fooda

@jskuros

fooda, for having a culture that empowers an organization to try

something like design sprints

Questions?

top related