In this episode, I'll be talking to Michael Shumaker from Eversend. We talk about his influence on how Eversend developed their design system, Stakeholder Influence to make it happen, and what he has learned from the experience. We'll also touched into how he names files within the design system you know more in depth things all about design systems, covering aspects of design systems specific to small teams and a few large corporations.

Timestamp:
00:52 - Why was the Blueprint started?
01:35 - Broader explanation on the objectives of the Blueprint series: The Blueprint series was created because of his love for design and wanting the African community to be open with their works for anyone to access.
02:40 - More information on the Blueprint series: It’s a two-part series: one on Twitter Space, sharing insights on design systems and some technical aspects; one on YouTube, offering a deeper dive into conversations with top African designers, as a monthly session.
04:04 - Introducing and welcoming guest Michael, who is also a designer and the first guest on the series
04:50 - Michael’s appearance
05:06 - Getting to meet Michael: Michael tells us who he is, where he works, and what he does.
05:32 - Brief intro about EverSend from the guest speaker, including what they are and what they do
05:48 - Discussion on what EverSend does, the goal of EverSend, and how long he has been with them
06:54 - How long they’ve worked within a design system
07:04 - Overview of what went on with their design system
07:37 - More details on the design system
08:02 - Deciding factors for their design choices
08:11 - Explanation of the deciding factors
08:58 - Further questions about the deciding factors and their origins
09:11 - Responses to these questions
13:20 - Encouragement to keep pushing despite setbacks
13:34 - Duration and process of building a design system
18:43 - Challenges in getting developers and designers to effectively use the design system
20:09 - Short break about whatspodcasting
21:14 - Discussion on the design system EverSend uses and their development end
21:43 - Whether EverSend has a documented library or end code on Figma
22:58 - EverSend’s future vision for using documentation
24:18 - Tracking metrics with the design system
26:55 - Number of designers at EverSend and how they manage their design system
27:12 - Challenges and lessons learned as a manager at EverSend
29:38 - Onboarding new designers for the design system
32:36 - Introducing a controversial topic to the guest speaker
35:37 - Lessons from this episode: Design systems don't limit creativity; they test it. A design system is a collaborative product for you and your designers.
37:02 - Guest speaker's favorite design system apart from EverSend's
38:23 - Thanks to the guest speaker
38:36 - Importance of having a design system
39:22 - Follow-ups on YouTube and Twitter Spaces
40:06 - Who manages the podcast (WhatsPodcasting)
42:00 - Explanation about the Question Center and how to use it
43:09 - Questions to the guest speaker: When did he start talking about design systems to his company? Would he recommend design systems to a company that is not mature?
43:51 - Convincing stakeholders and the team to build a design system
44:00 - Guest speaker addresses these questions
47:21 - Thanks to the second speaker for her questions
47:35 - Opening the chat for further questions
47:45 - Closure and highlights
48:20 - Appreciation to everyone for joining
48:40 - Goodbyes

🛠️ This podcast was powered by ⁠PLLUGG⁠ —Free AI powered content creation and repurposing tool.

To contact me(Host): @KingFayemi

This podcast is managed by whatspodcasting.Subscribe to the ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠whatspodcasting⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ newsletter for podcast recommendations. contact @D_rounz