1.
Beyond
the Waterfall
RETHINKING HOW WE WORK
// mbruck@etsy.com // @mayabruck

2.
I working collaboratively.

3.
SERIOUSLY?

4.
The Epic Waterfall Fail.

5.
RESEARCH
UX
DESIGN
DEVELOPMENT
QA

6.
Photo via Brad Frost

7.
#WATERFALLFAIL

8.
#WATERFALLFAIL

9.
ABOUT TO
#WATERFALLFAIL

10.
If it was with my dying breath, I would caution
anyone against attempting the feat...
ANNIE EDS ON TAYLOR

11.
I would sooner walk up to the mouth of a cannon,
knowing it was going to blow me to pieces than
make another trip over the Fall.
ANNIE EDS ON TAYLOR

12.
#NEVERAGAIN

13.
The post waterfall workflow.

14.
Icon by Austin Condiff from the Noun Project

15.
Being involved from the beginning gives me a
greater sense of ownership over a project. I'm not
just implementing a drawing someone hands
me, I'm helping real people solve real problems…
MAT T WON DR A , SENIOR DE VE LOPER, APARTMENT THERAPY

16.
…This not only makes me happier in my work, it
also motivates me to make sure every detail is
done just right.
MAT T WON DR A , SENIOR DE VE LOPER, APARTMENT THERAPY

17.
SKETCH STUDIO
TECHNIQUE

18.
Include the full team.

19.
UX
DESIGN DEV

20.
Keep it focused.

21.
Come prepared.

22.
FEATURE BRIEF

23.
A Feature Brief establishes the
sketch studio’s priorities
FACT

24.
Sketch. Erase. Repeat.

25.
Capture decisions.

26.
SKETCH
STUDIO
• Iterate & test ideas in real-time
• Build a shared understanding
• Create a sense of ownership

27.
CRITIQUE, OFTEN
TECHNIQUE

28.
Team-wide critiques.

29.
Review your designs early and
often with a broad team
TIP

30.
“Wow, this design looks really
nice. You obviously spent a lot
of time on this. Unfortunately,
we can’t build it.”

31.
When the developer is involved in the process, they
can warn about parts that are harder to implement.
BRIAN WALTERS, FRONT-END DEVELOPER, PIXO

32.
Informal critiques.

33.
Design critiques.

34.
CRITIQUE,
OFTEN
• Get feedback from a broad audience
• Make sure our designs can be built
• Push ourselves to innovate

35.
And now, a story.

36.
WORK IN PARALLEL
TECHNIQUE

37.
RESEARCH
UX
DESIGN
DEVELOPMENT
QA

38.
RESEARCH
UX
DESIGN
DEVELOPMENT
QA

39.
RESEARCH
UX
DESIGN
DEVELOPMENT
QA

40.
RESEARCH
UX
DESIGN
DEVELOPMENT
QA

41.
RESEARCH
UX
DESIGN
DEVELOPMENT
QA

42.
WORK IN
PARALLEL
• Gives time to deal with complications
• Allows you to respond to project needs
• Encourages communication
• Creates a sense of ownership

43.
TASK BOARDS
TECHNIQUE

44.
TO DO IN PROGRESS BLOCKED DONE
Task
Task
Task
Task Task
Task
Task
Task

45.
Ticket for task

46.
Backlog of tasks

47.
Tasks added to board

48.
TASK
BOARDS
• Provide transparency
• Capture, organize, and prioritize the
project’s tasks/issues
• Help address bottlenecks immediately

49.
TWEAK CODE
TECHNIQUE
IT’S OK! YOU CAN DO IT!

50.
TWEAK ALL
THE CODE!

51.
I love when designers actively help implement
their vision.
LEONID GRINBERG, DEVE LOP E R, THE NEW YORK TIME S

52.
1. The right tools

53.
2. Version control

54.
designer + developer = awesome

55.
TWEAK
CODE
• Iterating a design in code can be
hugely valuable
• So. much. more. satisfying.
• Creates a stronger relationship
with developers

56.
The secret sauce.

57.
Without empathy, it doesn’t matter what you
do with computers. Engineering success
doesn’t come from technical means. It comes
from understanding humans.
JO HN ALLSPAW, CTO, ETSY

58.
Beyond the waterfall.

59.
Whatever tool or method you
use, let it be one that empowers
your team and allows them to
be true partners.

60.
Thank you!
// mbruck@etsy.com // @mayabruck