5 Comments
Jun 13, 2022Liked by Patrick Morgan

Well written Patrick! A lot of companies would be wise to read this and other related articles on this topic to save themselves both time and money (as well as a lot of tears). Having attempted two of these three approaches, I could not agree more that the "big bang / blow-it-up" approach will most likely fail for you every time. In truth, building the design system is in many ways easier than the process of adopting it. This is why a strategy like the "land and expand" works well as it gives you a pre-defined scope within your application that allows you to start establishing a level of trust (and communication) with the various stakeholders of the system while not being burdened with the monumental effort of having to update your entire UI at one time. I really enjoyed this post, keep up the good work!

Expand full comment
author

Thanks for reading and taking the time to comment Noah! Looking forward to working with you again! 🙏🏻

Expand full comment
May 25, 2022Liked by Patrick Morgan

Great post! I've also done "Land and Expand" at prior jobs and found it to be an effective approach. Like you said, it's way easier for design to move quickly with a new design system than it is for engineering/software.

Expand full comment
author

Thanks Valjean! Glad you got some value from it 😀 Really appreciate your support!

Expand full comment
deletedJul 25, 2022Liked by Patrick Morgan
Comment deleted
Expand full comment
author

Definitely! Love that connection. The pilot program approach is so broadly useful when trying to introduce any bigger change to a product or organization. In my experience people are almost always open to trying an idea as "an experiment" (or pilot) while being very hesitant to just wholesale adopt anything new.

Expand full comment