Design Overflow, №3

The most interesting things the Stack Overflow Design team shared for the week of February 20th, 2017


“Design research at Dropbox”

by Cristen Torrey

We’ve identified three key points of leverage: connecting to the organization by embedding in product teams, collaborating closely with stakeholders through facilitation techniques, and systematically bringing researchers from different product areas together to address key strategic questions.

Image-to-Image Demo: edges2cats

The team had some fun creating some truly freaky—and hilarious—images.


“How to construct a design system”

by Colm Tuite

A design system (as it pertains to tech products) is more than a framework, UI toolkit or component library. It’s more than a style guide or set of code guidelines. It’s even more than the sum of those parts. A design system is an evolving ruleset governing the composition of a product.

“Tips for Becoming a Design Leader”

by Andrew Lucas-Walsh

If you’re looking to grow as a leader, don’t wait for someone to promote you into that position.Uncover the areas where you can lead and just start doing it.

Andrew lays out seven great suggestions for how you can personally grow your career. This article especially resonated with some design team members. We’re a medium-sized design team with a flat organizational structure. We aren’t dramatically growing our team. Our challenge is helping people feel that they’re growing in their career even if they aren’t moving into more management roles.

Thanks to Andrew for sharing his thoughts!


“Why Less Choice is a Better Choice”

by Paul van Oijen

Rather than informing me of all the available options and forcing me to make a decision on whether or not I’d actually like to use these services, Google made this decision for me. And the experience ended up being delightful. Less choice, or no choice in this case, ended up being the better choice.

Anticipatory design is increasingly become an area we find ourselves discussing as a team. How can we think ahead for our users? How can we help them achieve their goals faster and better? Paul shares the merits of anticipatory design and why you should be considering it more.