One of the best ways to learn something is to write about it.
My journey as a developer, designer, founder, and speaker has been impacted tremendously when I've taken the time to write about what I've learned.
There is always someone ahead of you, and there will always be someone a little further behind. I believe it's each person's job to share what they're learning, to help complete that chain of knowledge. Below, you'll find articles, research, notes, and ideas from my journey of learning.
A summary of the deep-dive conversation we had as part of Episode 8 of The Question on design system tooling.
A summary of the deep-dive conversation we had as part of Episode 7 of The Question on multi-platform design systems.
A summary of the deep-dive conversation we had as part of Episode 6 of The Question on fixing design system contribution.
A summary of the deep-dive conversation we had as part of Episode 5 of The Question on breaking the rules of your company.
A summary of the deep-dive conversation we had as part of Episode 4 of The Question on design system communication strategies.
A summary of the deep-dive conversation we had as part of Episode 3 of The Question on design system team makeup.
A summary of the deep-dive conversation we had as part of Episode 2 of The Question on whether you should start your design system from the inside out or from the outside in.
A summary of the deep-dive conversation we had as a part the first episode of The Question on the difference between a Product Designer and a Systems Designer.
It doesn't matter how well you understand the camera if you don't understand the person.
If you're stuck on a specific design system task, sometimes the best option is to pause that work and focus elsewhere.
The core of your design system should be the language you use, not specific instances of patterns. And that language should be derived from the values of the organization. Your job is to make sure the language is spoken fluently and then to trust in the power it offers.
Instead of highlighting what folks have done wrong, be a student of what they've done right. Only then you can establish a system that is true to the context where it must thrive.
A reminder that every situation is an opportunity and that a good part of the work of creating a more systematic design program is educating individuals and teams about the effort.
The most critical skill for any design system leader is the ability to observe what is already working well.
The second most important feature of your design system documentation site is findability.
Good people will try hard to pull you away from the most impactful part of design system work—unity. Don't let them.
Your job is not to track everyone else's success. It's to correlate that success with the adoption of your system.
Connecting some learnings from Rick Rubin and Arthur C. Brooks on how being attentive to what's around us is a key to living a more fulfilling life.
The juxtaposition between the "earthly" and the "unearthly" and a way to integrate nature into our everyday creativity.
An exploration of the undeniable link between an organization's culture and the approach of its design system. The technical and creative aspects of a design system are important, but they are only two parts of a three-part puzzle.
A very simple framework for maturing a design system in a healthy way. Because implementing a design system is asking everyone to change how they work, it's necessary to consider each task you prioritize through this lens.
Why "fluency" combined with "values-alignment" is such an important part of the hiring process. One is teachable, the other is not.
Though they have numerous benefits, design systems are still sometimes seen as design constraints. Understand how creating a culture of trust can bridge this gap between consistency and flexibility in your design system.
A design system can unify different disciplines and lead to improved consistency, efficiency, and much more. Let's define a shared understanding of how systems connect core brand elements with digital interfaces and empower teams to work together effectively.
A model of healthy design system growth based on years of research. Learn the different stages of maturity and where your system fits.
A collection of ideas on how to present the common benefits of design systems to the executives who must support and fund them.
An exploration of ways to make in impact where you are.
A bit about the criticality of accessibility in our work on the Web.
An exploration of how design systems can help to build unity inside your organization.
A framework for investing in your team, leading to greater buy-in and innovation.
A framework for valuable collaboration that considers the diversity of perspectives and the amount of empathy a team demonstrates.
Journeying inward, not upward: this post shares how “Westworld” provides a unique perspective on helping the folks on your team become the best versions of themselves.
Values are the context for your culture. In this piece, I try to demystify “trusting your heart” by sharing that “your heart” is simply the things that matter most to you—your values.
Some ideas on how to shape your project work to create just the right amount of drag.
A few observations from my trip to see the Notre-Dame Cathedral about the immediacy with which we create today, and the speed with which our work decays.
Some thoughts from my reading of Aldo Leopold's A Sand County Almanac about earning your heat and learning from the past.
A few ideas on how to restructure the design process to account for the inherent flexibility of the Web.
To the industry obsessed with process and workflow, I offer this alternative approach to product design and development.
What breakpoints should we use in responsive web design? As commonly as it's asked, this may be the wrong question. Join me as we take a tumble down the rabbit hole, beyond the breakpoint.
A 30,000 foot view of the Web industry's current state as it relates to responsive web design.