Suggestions
Ken Skistimas
Design Manager at Facebook
Ken Skistimas is a seasoned design professional with a rich background in creating large scale design systems for top tech companies such as Facebook, GE, and Salesforce. Currently, Ken is spearheading the development of the next generation design language for ads and business products at Facebook, with a focus on elevating the quality of deliverables.
Previously, Ken led the Predix Design System team at GE Digital, where he oversaw the creation and maintenance of a scalable design language utilized across numerous applications on GE's Industrial Internet platform. At Salesforce, he held key roles in driving the user experience for Sales Cloud and played a pivotal part in the design and rollout of Lightning Experience, a significant redesign in Salesforce's history.
Ken's expertise lies in distilling design patterns from various sources, leveraging platform-focused design teams to enhance product quality and consistency. He is passionate about tackling complex challenges at scale, all the while enhancing the design culture and craftsmanship within organizations.
With a foundation in graphic design and a collaborative approach, Ken advocates for rapid idea generation, early sharing with cross-functional teams, and data-driven iterations to deliver outstanding user experiences. Ken Skistimas studied Communication Design at the University of North Texas.
At present, Ken serves as the Product Design Manager at Facebook, adding to a distinguished career that includes roles such as Product Designer, Director of User Experience at GE Digital, and various senior and lead design positions at Salesforce, Scribd, Rhapsody International, eBay, Metaweb Technologies, Applied Minds, and his own venture, Ken Skistimas Design.
Highlights
Come join our team! I'm looking for a collaborative, high craft senior designer to join our team to define common design patterns and components used across ServiceNow products. Design system experience preferred.
Several years ago I gave a workshop on design systems. The audience wanted a canonical and finite checklist to create a system and get adoption. My message that there is not one formula to create a design system did not land well. The reality is that checklist is situational and unique for everyone.
I was just chatting with Davy Fung and reflecting the four systems I've been a part of. I strongly believe that the definition, value and operations of a design system needs to mold to what the org needs and how people are working. It has to be a value add, not another ask. That's led to a ton of ambiguity and many moments that have pushed against my instincts and experience. It's been very uncomfortable at times, but I've been more successful when I embraced the ambiguity and was open to redefining things rather than holding things tight (that's a whole other post).
My advice - while there's a ton of valuable insights and tips on design systems out there, don't get lost in the weeds or hung up on how it's supposed to work because it can hinder you. Acknowledge your environment and mold the definition of what the system needs to do and how it works around it.
