Speak the same language
Speaking the same language is one of the greatest, and easiest, wins for your teams’ collaboration. All it takes is pointing at things, writing those names down, and agreeing on them.
The process of design
Since I’ve been back from abroad, I’ve written a lot about how designer and developer teams can work together more effectively. I’ve elaborated that it’s more than just making a pattern library. Now, I’ve finally done some work I can actually talk about: I can explain the design process that I’ve been writing around.
I know “What’s Next”
In October 2015, I handed in my resignation at Apple. For the next few months I kept getting the same question. Over and over again. “So, what are you going to do now?” Now I know.
Not just pattern libraries
I made the case that custom tools leads to effective designer and developer collaboration. I also made the point that I’m not talking about just pattern libraries. Let me explain why.
Together
Designers and developers should work together. We know this. They should be partners in production. But they aren’t. Despite us knowing better, our designers and developers fail to work together.
And it isn’t their fault.
What’s Next?
A couple of months into working at Apple it dawned on me that the big question wasn’t whether I could make it at Apple, the big question was “What’s next?”
Using stretch goals to raise funds like Robin Hood
Next to the Register button for the first Gather Workshop for Industry: “Sass: Taking your CSS to the next level” is a bit of text informing you how many tickets we have left until we reach our stretch goal. Our stretch goal being:
