From my talk at BigDesign 17 in Dallas where I shared how Atlassian designers collaborate with their product teams, other designers as well as across the organisation.
23. Triads are responsible for
making sure that we look at
problems from all three
sides
ROSS CHALDECOTT
24. Designers
Other designers, IXers and
researchers in the team
Collaboration
Cross-organisation
Temporary teams that span
across the organisation
Cross-functional
A product team that includes
PM, dev & design
28. I recognise that the Council has
made a decision. But given that
it’s a stupid-ass decision, I’ve
elected to ignore it.
NICK FURY, THE AVENGERS
29. Different perspectives
Different backgrounds will help you explore
paths that you wouldn’t have considered.
Shared understanding
Working closely together on the same problem
will help the team be aligned.
Better solutions
Different skillsets and strengths will lead you to
better ways to solve a particular problem.
Why is it
important to
collaborate?
30. Different perspectives
Different backgrounds will help you explore
paths that you wouldn’t have considered.
Shared understanding
Working closely together on the same problem
will help the team be aligned.
Better solutions
Different skillsets and strengths will lead you to
better ways to solve a particular problem.
Why is it
important to
collaborate?
31. Different perspectives
Different backgrounds will help you explore
paths that you wouldn’t have considered.
Shared understanding
Working closely together on the same problem
will help the team be aligned.
Better solutions
Different skillsets and strengths will lead you to
better ways to solve a particular problem.
Why is it
important to
collaborate?
33. Lack of focus
Collaboration occurs randomly with no clear
purpose and is often derailed by interruptions.
No agenda
Sessions that don’t have a structure or goal tend
to yield underwhelming results.
Too busy
We’re all too busy with our work and between
meetings there is no time to collaborate.
Challenges
to be able to
collaborate
34. Lack of focus
Collaboration occurs randomly with no clear
purpose and is often derailed by interruptions.
No agenda
Sessions that don’t have a structure or goal tend
to yield underwhelming results.
Too busy
We’re all too busy with our work and between
meetings there is no time to collaborate.
Challenges
to be able to
collaborate
35. Lack of focus
Collaboration occurs randomly with no clear
purpose and is often derailed by interruptions.
No agenda
Sessions that don’t have a structure or goal tend
to yield underwhelming results.
Too busy
We’re all too busy with our work and between
meetings there is no time to collaborate.
Challenges
to be able to
collaborate
37. Design detention
Concentrated time,
designers only.
Design plays
Design spikes
Adapted design sprints that
fit into Atlassian’s culture.
Disrupt play
Rapid brainstorming session
to come up with lots of ideas.
41. What if there was a way to
come up with brilliant ideas
faster?
DISRUPT PLAY
42.
43. What’s a disrupt play?
A session where teams brainstorm on
a theme, while constraints get
introduced at intervals to push their
ideas in a new direction.
44. Quality ideas
Everyone can come up with an idea, but coming
up with good ideas is hard. Really hard.
New ideas
Themes & constraints constantly push teams
into new directions with fresh ideas.
Innovate, innovate
We're constantly being pushed to innovate, but
it’s much easier said than done.
Value of the
disrupt play
45. Quality ideas
Everyone can come up with an idea, but coming
up with good ideas is hard. Really hard.
New ideas
Themes & constraints constantly push teams
into new directions with fresh ideas.
Innovate, innovate
We're constantly being pushed to innovate, but
it’s much easier said than done.
Value of the
disrupt play
46. Quality ideas
Everyone can come up with an idea, but coming
up with good ideas is hard. Really hard.
New ideas
Themes & constraints constantly push teams
into new directions with fresh ideas.
Innovate, innovate
We're constantly being pushed to innovate, but
it’s much easier said than done.
Value of the
disrupt play
49. Disrupt cards
Download “Disrupt cards”
from the Atlassian playbook.
You’re going to need
Themes
Choose specific themes that
the team need to ideate on.
Timer
It’s fast-paced; you’re going
to need to be strict on time.
50.
51. Warm up, go broad
Choose a theme and generate as
many ideas as possible, with no
constraints. The idea is to go broad.
52. Silent culling
In silence, each team goes to the
other team’s board and remove any
ideas they don’t support. Don’t be shy.
53. Add constraints
Gradually add constraints as
the loops progress.
Disrupt loops
Move team member
Swop team members at
every second loop.
10 minutes
Loops are fast paced and
rapid - 10 mins each.
54.
55.
56.
57.
58.
59.
60. Don’t be precious
Remove any ideas that are
not feasible/desirable.
Culling
Keep ~10% of ideas
Get rid of 90% of the ideas
on the walls.
Be ruthless
There’s gonna be a tonne of
ideas. Be ruthless.
61.
62. Document ideas
Group any similar ideas into themes
and assign an owner to each idea.
Organise the brilliant ideas by
capturing everyone’s thoughts.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72. Your biggest risk isn’t
occasional failure it’s
sustained mediocrity.
LUKE W
73. It often takes many bad
ideas to get to the good
ones.
MARIE-CLAIRE DEAN
74. Disrupt play / recap
Constraints
Use constraint cards and themes to
help teams zoom their focus.
Disrupt loops
In 10min loops, use constraints and
swop members to get many ideas.
Warm up
Get the team to warm up by going
broad without any constraints.
Culling
Be ruthless and remove ideas that
aren’t feasible or desirable.
Silent culling
In silence, teams remove each other’s
ideas that they don’t support.
Document ideas
Group similar ideas together and
assign owners to each idea.
78. Find a group of people who
challenge and inspire you,
spend a lot of time with them,
and it will change your life.
AMY POEHLER
79.
80. What is design
detention
A partial or full day where designers
comes together to spend time
working individually, or together as a
team without any interruptions.
81. Pair strengths
Designers can lean on each others
complimentary skills to tackle hard problems.
Relationships
Sitting together and working on problems
creates strong bonds between designers.
Focused work
Dedicated time without interruptions such as
email, meetings or 1:1s to focus on deep work.
Value of
design
detention
82. Pair strengths
Designers can lean on each others
complimentary skills to tackle hard problems.
Relationships
Sitting together and working on problems
creates strong bonds between designers.
Focused work
Dedicated time without interruptions such as
email, meetings or 1:1s to focus on deep work.
Value of
design
detention
83. Pair strengths
Designers can lean on each others
complimentary skills to tackle hard problems.
Relationships
Sitting together and working on problems
creates strong bonds between designers.
Focused work
Dedicated time without interruptions such as
email, meetings or 1:1s to focus on deep work.
Value of
design
detention
85. Colocated space
Ensure that you’ve booked a big
enough space where the team can
work during that time. It helps if it is
not a meeting or board room.
86. No interruptions
Get buy-in from the bigger team to
ensure that there are no interruptions
and set the expectation that the team
is inaccessible during that time.
87. Flexible
Let the team self organise,
encourage pairing skills.
Structured
Choose a specific theme that
the group needs to work on.
Flexible or structured
88. Playback to team
Set up a way for the group to
playback the work they did to the rest
of the team through sparring sessions
or blog posts.
89. Socialise
Encourage the team to do coffee runs
together or organise a lunch to get out
of the office together to talk outside
work. This builds bonds and trust.
94. Design detention / recap
Colocated space
Set up a pleasant environment where
the team can work during that time.
Structured
Set specific goals for the team with a
desired outcome.
No interruptions
Give the bigger teams a heads up to
avoid unplanned meetings.
Playback
A milestone helps the team focus
towards achieving something.
Flexible
Let the teams self-organise, but
encourage collaboration.
Coffee and lunch
An opportunity to let the team bond
and know each other better.
96. You can shortcut the
endless-debate cycle and
compress months of time
into a single week
GOOGLE VENTURES
97.
98. What’s a design
spike?
A sharp concentrated period where a
team with complimentary skills try to
solve a specific problem in three days.
99. Rapid & quick
The constraint of time during a spike drives
teams towards making quicker decisions.
Better solution
Different perspectives and strengths will lead to
better ways of solving the right problem.
Shared understanding
Having a cross-functional group working on the
same problem gets everyone on the same page.
Value of
design
spikes
100. Rapid & quick
The constraint of time during a spike drives
teams towards making quicker decisions.
Better solution
Different perspectives and strengths will lead to
better ways of solving the right problem.
Shared understanding
Having a cross-functional group working on the
same problem gets everyone on the same page.
Value of
design
spikes
101. Rapid & quick
The constraint of time during a spike drives
teams towards making quicker decisions.
Better solutions
Different perspectives and strengths will lead to
better ways of solving the right problem.
Shared understanding
Having a cross-functional group working on the
same problem gets everyone on the same page.
Value of
design
spikes
103. Complimentary skills
In order to have a successful design
spike, make sure that the skills of
individuals in the team compliment
each other (usually cross-functional).
104. Timer
Keeping track of
time is essential to
keep moving.
Agenda
A structured agenda
will keep the group
focused on the task.
Whiteboards
Sketching on
whiteboards, post-its
& paper is essential.
Playbacks
Regular check-ins
with sponsors will
drive motivation.
You’re going to need
105.
106. Structured agenda
A clear agenda is vital, which will help
the team stay focused towards
specific outcomes for each day.
107. STRUCTURED AGENDA
Outcomes
Make sure that not only the
goal for the spike is defined,
but as well as for each day.
Activities
Break down each day into the
specific activities that need to
get done - remember breaks!
Flexible
Keep in mind that even though
the agenda provides structure,
adapt when required based on
the team.
108. Day 2: Ideate
Go broad on ideas through
lots of sketching.
Three days
Day 3: Prototype
Create an end-to-end flow
that captures the solution.
Day1: Immerse
Understand existing research
and requirements.
109. Day 1: Immerse
Its challenging to build a shared
understanding in one day, so creating
a journey map helps distill the
research, data and requirements.
110. Post-it #allthethings
Ask the group to capture any
questions, comments or insights on
post-its throughout the day in leading
up to the journey mapping activity.
111. Data
Analyse and review any
existing usage data.
Immerse
Requirements
Walk through the business
requirements and goals.
Research
Discuss existing research and
look at your competitors.
112. Tasks
Map tasks into the
different phases of
the journey.
Pain points
Highlight any pain
points that might
occur.
Opportunities
Define possible
opportunities that
may come up.
Sentiment
Draw a customer
sentiment line across
the journey map.
Journey mapping
113.
114. Day 2: Ideate
It’s important that the group explores
many ideas before converging onto a
single solution. 6-up sketching allows
the team to do this effectively.
115. Diverge
Go broad and sketch ideas
using 6-up’s / crazy-8’s.
Ideate
Converge
Select potential ideas that
best match the goals.
Define
From the journey map, define
the specific problem areas.
116.
117. Day 3: Prototype
Getting everyone to understand the
end-to-end experience is vital to
making better decisions. A clickable
prototype can achieves this.
118. PROTOTYPE
Solution
Show how you are solving the
problem.
Flow
Capture the end-to-end flow of
the specific problem.
Interaction
How the experience unfolds is
an important factor that
compliments the solution.
126. Design spikes / recap
Structured agenda
Invest the time to come up with a
structured agenda.
Immerse
Build a journey map to understand
the research, data and requirements.
Complimentary skills
Make sure that individuals’ skills
compliment each other in the group.
Ideate
Go broad first and then refine ideas
by sketching the whole day.
Playbacks
Hold regular playbacks at the end of
each day to motivate the team.
Prototype
Create a tangible end-to-end
experience to show the solution.
128. Ice breakers
Loosen the group up by
running an ice breaker.
More things
Health monitors
Highlight improvement areas
that teams can work on.
Meditation
Group meditation help teams
think and focus together.
129.
130.
131. Coming together is a
beginning, staying together
is progress, and working
together is success.
HENRY FORD