An Animation Story
A love story between a girl named Design and a boy named Animation. Adam created, narrated, and presented this story to a group of 20 developers at Solstice in order to talk about the importance of having a "design-gineering" mindset and the value of the relationship between designers and engineers.
Postface
So, what was that all about? And what ever happened to Engineering? Well, this story highlights the Design-Engineering mindset, or rather the lack of. Too often do I see us breaking designers' hearts. It seems implementing a design exactly as it was created often presents a problem. But instead of solving the problem, we find ways to avoid it. "Oh this increases technical complexity, let's simplify". "Oh this skyrockets our scope, let's do this later" (aka never). Implementing animations is a common trigger to these excuses.
Why is it so important to not break out designers hearts? In my opinion, a great design tells a story. It evokes emotions and brings character to the product. Animation is a tool in a designer's toolbelt that brings life to a design. It is a story in of itself - the change of values over time from one point to another. You see, when we find reasons to not fulfill a designer's creation, to not implement their animations, or any other design element for that matter, we are taking the life out of the design. We are stripping it of character and emotion.
What ever happened to Engineering? Perhaps he makes an epic return in Chapter 2. Perhaps not. It is our job as engineers to create Chapter 2...to not break our designers hearts. And, so, honestly I don't see the value in sitting here and showing you how to implement animations. Because, I believe that without a "design-gineering" mindset, we will continue to find excuses not to meet design face to face. I don't think you all need to be as passionate about design or animation as I am, but I think we all have to at least appreciate what it is a designer does, and the impact their designs have on a product.
I encourage everyone to work very closely with your designers. Understand what it is they do everyday, what problems they think about, and what tools they use to solve those problems. The best way to understand a designer is to become one. This, in my opinion, is what the "design-gineering" mindset is all about.