Ideation at Sprint Pace

AMY DITTMAR | DESIGNER | ATLASSIAN

Introducing the design sprint

Agenda

Design sprint planning

Journey mapping

Disrupt

Wrap up

Sprint team The right team is key. Include the core product people, experts in other areas, a facilitator, and stakeholders.

Pre reading Pre reading ensures everyone has shared knowledge, and team members get in the head space ahead of time.

Preparations

Recruit users Recruit users the weeks before the sprint. You won't have time

or capacity to manage this during the sprint.

Clear calendar The core team members and

facilitator must be in the room M-Th, experts should

be there as much as possible.

Materials White boards are key! Post-its, pens, paper, timer too.

The sprint space

No devices Commit to being off your devices during working

sessions. Leave the room otherwise.

Book a room Book the same large room for

the week. Off-sites are perfect too.

STRUCTURE THE DAY

9:30 / 10am

Break

Work Work

Lunch Break

Work Work

4:30 / 5pm

STRUCTURE OF THE WEEK

Define the problem

MONDAY

Ideation

TUESDAY

Story boarding

WEDNESDAY

Prototyping

THURSDAY

Testing

FRIDAY

Agenda

Design sprint planning

Journey mapping

Disrupt

Wrap up

Why take the journey? Journey mapping helps you visualize how customers experience your product, define pain points, and opportunity areas.

Journey Mapping

Mapping

Pro tips

Pain points

Sentiment line

Mapping

Define scope - specific persona in a certain scenario with a defined goal.

Start mapping with 1st action the persona would take, and go from there! One action/touchpoint per postit.

Explore the journey and mine it for opportunities to improve the experience, NOT adhoc solutions.

Note the communication of the action/touchpoint. Messaging app, video conference, email, face-to-face, social media, homing pigeonAnalyze

•

•

•

•

Atlassians Journey mapping Sydney office

Journey Mapping

Mapping

Pro tips

Pain points

Sentiment line

Pro tips

Color code your postits!! Example color categories: actions, feelings, pain points, time sinks, comm channels

Save time, divide and conquer. Break up journey into sections, assign diff team members to sections.

"On-stage" (what the customer experiences) versus "back-stage" (what systems and processes are active in the background)

If the journey branches based on the answers or choices, have one participant map out each path.Analyze

•

•

•

•

Journey Mapping

Mapping

Pro tips

Pain points

Sentiment line

Pain points

"Ok, show me where it hurts." This is the therapy session for your persona!

Take 2nd pass over the journey, placing pain point postits on journey map near the painful touchpoint.

What’s the severity/impact of each pain point? Trivial, blocker, abandonment?

Analyze

•

•

•

Journey Mapping

Pro tips

Pain points

Sentiment line

Sentiment line

Each touchpoint of journey map gets a sentiment point below. Connect the dots and you’ve got a sentiment line.

Visualizes persona sentiment of the journey.

Analyze

•

•

Mapping

Rapid drops Indicates large gaps in expectations, and frustration.

Troughs Indicate opportunities for lifting overall sentiments.

Positive peaks Can you design an experience that lifts them even higher?

Journey Mapping

Pro tips

Pain points

Sentiment line

Analyze

Discuss trends and patterns in the experience. Ask probing questions such as:

Analyze

MappingWhere are the areas of greatest confusion/frustration?

Where is the journey falling short of expectations?

Are there any new un-met needs that have come up for the user type?

Are there areas in the process being needlessly complicated or duplicated?

•

•

•

•

AgendaAgenda

Design sprint planning

Journey mapping

Disrupt

Wrap up

Disrupt

Pro tips

Capture

Structure

Structure

Break up group into 2 groups

Each group needs a lead that will be the source of truth for all the ideas. They will not rotate

Each Disrupt loop is 10 min. The session is 60 min, aim for 5 loops.

First loop has no constraint. Each loop after introduce new disrupt card, removing the old one.

•

•

•

•

Disrupt

Pro tips

Capture

Pro tips

Structure

Start the session after lunch or break time so everyone’s fresh coming into it. Maybe even kick it off with meditation or yoga!

Have fun, stay focused

More the merrier, there’s no stupid ideas just write them down.

And then when culling ideas, be ruthless. Most teams end up with 10% of their idea at the end.

•

•

•

•

Disrupt

Pro tips

Capture

Capture

Structure

Snap! Aka, group similar ideas into clusters to reveal themes across the last 10%. Agree on an owner for each idea.

If too many ideas remain, dot vote or severity/frequency table to cull down further.

Organize and document the top ideas. Be sure to capture everyone's brilliant thoughts.

•

•

•

AgendaAgenda

Design sprint planning

Journey mapping

Disrupt

Wrap up

Not enough time When the pressure is on generate good ideas fast

When design sprints are good idea

Stuck Break free of the same old

solutions

High stakes Go for the big win, don't play

it safe

Benefits of design sprints

Low risk / high reward

Only 1 week

Team Collab

Start at the end See if your solution will succeed or fail before ever building an MVP version with a fake finished product, aka a prototype.

Fake it ‘till you make it Prototypes are perfect for communicating / testing your ideas early and often.

Be shallow, keep it surface level Prototypes are only the shell of a finished product. There’s no issues with implementation, dev resources, or legal :)

Only 1 week

Team Collab

Return on investment Identifying critical flaws in one week of work is the height of efficiency. It’s taking the risk out of risky ideas.

Benefits of design sprints

Bypass meeting-creep Shortcut months of meetings with a structured uninterrupted week of focused team collab.

Low risk / high reward

Low risk / high reward

Only 1 week

Team Collab

Team Collab Design sprints brings teams together and builds trust.

Buy in There’s shared understanding and buy in since the whole team was fully invested in the ideas, prototype, and user testing results generated.

The lucky 7 Shoot for 7 or fewer members. Have the core people plus some experts from elsewhere in the business. Choose a skilled facilitator to keep things on track.

Benefits of design sprints

Atlassian Playbook www.atlassian.com/team-playbook/plays

Sprint Jake Knapp

Check these out :)

Go forth and ideate The next game changer idea is a design sprint away!

Thank you!

AMY DITTMAR | DESIGNER | ATLASSIAN