A few weeks ago I had the opportunity to deliver a talk at Shift in Split, Croatia.
Shift is a developer conference, so initially, I thought it would be entertaining to talk about what it’s like to work with an engineer, from a designers perspective. The working title of the talk was Things Engineers Hate About Working With (Me) a Designer.
I was going to share the mistakes I’ve made, and learned from, along the way. A manifesto of what not to do when working with an engineer. However, feedback included phrases like “it’s a bit tongue & cheek” and the best talks are ones that are “raw, honest and vulnerable.”
You don’t write code, but you’ve been successful in spite of it. The lines are blurring between design & engineering. Why not talk about how tools have helped bridge that gap?
There was something more interesting to talk about. I realized that I didn’t write code because I didn’t need to. For years I’d been spoiled, and to some extent enabled, by a handful of incredibly talented iOS engineers. The realization didn’t sit well with me.
I scrapped everything and went back to the drawing board.
Tools were my first introduction to a hobby that turned into a passion that has become an obsession
They have been steadily influencing and shaping me as a designer from the first time I sat in front of a computer in elementary school. I would not realize how much they’d impact my life until much much later.
Tools have had a massive influence on me and my work, but had they on others?
53. OVERCOME WITH COMPLACENCY
Just a decade ago, competition among the tools for digital
designers was muted, at best. Today new applications and
utilities debut seemingly every other week.
-Khoi Vinh, Subtraction
62. THE DEVIL IS IN THE DETAILS
Details are not the details.
They make the design.
-Charles Eames
63. FOR MANY YEARS WE DESIGNED
{primarily} static experiences with an
extremely limited tool set
64.
65. EXPECTATIONS HAVE CHANGED
Scope has grown enormously. Many
years ago, you could make a fancy
design and call it a day – after you had
exported some assets, perhaps.
-Pieter Omvlee
Founder Bohemian Coding
66. TODAY WE ARE DESIGNING & BUILDING
Highly interactive experiences with a
plethora, and at times intimidating,
sets of tools that work seamlessly
across platforms & devices.
70. THE PROCESS HAS CHANGED
The days of designing, building and
shipping in a vacuum are gone
71. DATA DRIVEN, CROSS FUNCTIONAL COLLABORATION
Today, teams rapidly design,
prototype, test and iterate before
shipping to customers
72. THE DESIGN SPRINT
Understand the Problem
Sketch a variety of solutions
Vote for the best idea
Build a prototype
Test with customers
73. PROTOTYPING & TESTING
The adoption of prototyping & user
testing has produced radically better
outcomes for teams and stakeholders
74. THEY CAN ATTEST TO IT
Interactive prototypes allowed me to express micro-
interactions and workflows in a way that made sense
to stakeholders, which improved my ability to
communicate design tremendously.
Additionally, it allowed me to bring user research into
the core of my practice.
75. THEY CAN ATTEST TO IT
Because prototyping allows me to simulate the actual
intent of the experience much closer than static
comps, I get to observe customers interacting with my
concept or flow.
I get to learn whether my design is resonating with
customers much quicker.
76. WHAT DOES IT MEAN?
We’re learning earlier in
the process what does &
does not work. Saving
time, money & resources
77.
78. BICYCLE 🚀 FOR THE MIND
...the computer is the most remarkable
tool that we've ever come up with. It's
the equivalent of a bicycle for our
minds.
-Steve Jobs
79.
80. BICYCLE 🚀 FOR THE MIND
Today’s tools feel more like a
self driving car than a bicycle
81. BICYCLE 🚀 FOR THE MIND
Newer tools have provided more specialized solutions
for designing for specific platforms.
This specialization has cut design time significantly. It
has also armed me with a way to communicate my
ideas better and more effectively.
96. A SHIFTING MINDSET
The easier and faster it is to prototype, the more I'll do it.
If I know building a prototype is going to take a really
long time, I'll be more hesitant to prototype something I
probably should because I fear it'll keep me from the
other things I need to get done.
104. LEVERAGING CODE
The new wave of tools do not {easily} support
building out micro-interactions & animations like
typing indicators.
Sometimes code is just easier & faster.
107. BUT, WHY PROTOTYPE?
Gain clarity faster
Design holistic solutions
Clear & efficient communication
108. FEWER MEETINGS 🎉
A prototype is worth a
thousand meetings.-Paul Stamatiou
-Paul Stamatiou
109. FROM A PRINT DESIGNER
Being a print designer who moved to digital, tools like
Flinto, Invision & Atomic helped get my head around
flows and interactions that I didn't have a full
appreciation for when I was designing logos & posters.
110. THOUGHTFUL DESIGN
It's made me think more thoughtfully of the
construction of pages/screens/objects/interactions.
It's also allowed me to communicate my ideas in a
way I couldn't before.
118. I HAVE A PHILOSOPHY
…when responding to a question
from Operator {reactive} I believed
the affordances should live inside the
channel, not the keyboard…
138. SHAPING THEM
It {tools} has made me think more thoughtfully of the
construction of pages, screens, objects & interactions.
It's also allowed me to communicate my ideas in a way
I couldn't before.
139. A SHIFT
We’re seeing change that
goes beyond the desired
skill set of a designer