Intro to Successful Design Systems with Donna Vitan46:15 with Treehouse
Donna discusses what a design system is and when to use one. She covers how to make a design system work for you, and how it provides the opportunity for creativity. Donna also covers ways to measure the success of your design system.
I am so excited to welcome up Donna Vitan. 0:02 Donna is a user experience interaction and visual designer, committed to inclusive 0:06 design, supporting products, projects, and cross functional teams as the champion for 0:11 best practices, web banners compliance and accessibility. 0:17 But she is passionate about design systems, design tools, 0:21 processes, as the means to express inclusive design at scale. 0:26 As part of the TELUS team designed TELUS Digital she helped support 0:31 the organization, build products quickly and easily, improving the design 0:36 systems tools and processes through collaboration and communication. 0:40 More recently, she's also supporting the unified products and 0:45 commerce team to deliver a global transactional platform. 0:49 Donna continues to express her passion for design systems as the content social 0:53 media [INAUDIBLE] for the design systems community. 0:58 A group helping to bring people together to share ways of working, successes, and 1:01 other learnings to encourage best practices in building, scaling, and 1:06 maintaining design systems. 1:10 We are honored to have are here. 1:12 You all are gonna love learning from her. 1:14 So over to you, Donna. 1:17 Thanks. 1:18 >> Thank you. 1:20 I'm happy to be here. 1:20 Okay, well, hello everybody and welcome. 1:23 My name is Donna Vitan, and I am a digital experience designer. 1:27 So that encompasses user experience, user interface, and design systems designer. 1:33 I am a designer who codes. 1:39 I have been designing websites since I created my first website on Geocities, 1:43 which was a collection of Sailor Moon animated GIFs. 1:48 And yes, I say GIFs. 1:51 Knowing how to code means I'm familiar with the mental models and 1:52 best practices to make meaningful recommendations and user interfaces. 1:57 I'm able to contribute to discussions in how a component should work, 2:02 and it also allows me to think of design as a reusable objects. 2:08 I'm also an advocate for inclusivity and accessibility. 2:13 I wanna make sure we include considerations for the human and 2:16 emotional experience. 2:21 And most importantly, as other people have said in the sessions this morning, 2:23 I'm always learning. 2:28 [LAUGH] You never stop learning. 2:30 There's always something to learn from books, podcasts, tutorials, 2:33 articles, practicing your craft with projects or 2:38 work, and from your fellow designers, sproduct owners and the rest. 2:41 Social media and meetups and conferences like this are great places to learn. 2:46 And learning is a skill, it means keeping your mind open and 2:52 thinking critically, informed by different viewpoints. 2:56 Just because something is done a certain way doesn't mean it should, 3:00 and you should be able to question things to make things better. 3:06 I've worked in the travel and financial industry, 3:13 and I work in the telecommunications industry. 3:17 Working in big organizations have led me to work on design systems. 3:20 And as a designer, 3:25 it affords me the ability to make a big impact on the organization, and 3:26 ultimately help drive inclusivity and accessibility for the customers. 3:31 I'm currently the senior designer for TELUS Digital on their design system and 3:37 digital commerce platform. 3:41 In this session, we'll talk about the answer to these questions. 3:46 What is a design system? 3:49 Why use a design system? 3:51 What makes a design system? 3:53 And what makes a successful design system? 3:55 And hopefully you'll have a better understanding of what design systems 3:58 can do for you, and how it provides the opportunity for creativity. 4:03 So let's get started. 4:08 What is a design system? 4:10 Well, there are various ways to define a design system. 4:13 It can be as simple as a collection of visual and coded components. 4:16 Or it can evolve into ways of thinking, of methodology. 4:20 In the same way that inclusivity is the process and 4:25 accessibility is outcome, so too is a design system 4:30 can provide a way of thinking beyond artifacts. 4:35 So Nathan Curtis says a design system isn't a project, 4:39 it's a product serving products. 4:45 He also says that a design system offers a library of visual style components and 4:49 other concerns documented and released by an individual, 4:56 team or community as code and design tools so 5:01 that adopting products can be more efficient and cohesive. 5:04 A design system, this diagram, this illustration, has four headings. 5:11 There's identity, principles, best practices, and 5:16 they point towards components and patterns. 5:20 And so this is your artifacts, your design and development artifacts, 5:23 but they're informed by the brand identity, 5:28 the brand values, and best practices and accessibility in UX. 5:31 Audrey Hacq describes a design system as a single source of truth, 5:36 which groups all elements that will allow teams to design, 5:41 realize, and develop a product. 5:46 Here we have another [INAUDIBLE] icon that's representing versions and 5:51 they all trickle down to design language, design kit, 5:57 component library, developer sandbox, and documentation. 6:02 So Varun and Catherine from Rangle.IO, they describe a design system as 6:07 a systematic approach to product development complete with guidelines, 6:12 principles, philosophies, and code. 6:18 It shines a spotlight on how a team designs, 6:20 making it a fantastic tool for scaling your design practicing. 6:24 Reducing the need for handoff and promoting more collaboration. 6:30 Jina Anne is a design system advocate well known for 6:37 her work on the Salesforce Lightning Design System. 6:40 Organizer of clarity, a premier design system conference. 6:42 She runs the design system Slack, co-authored the design systems handbook, 6:48 a definitive primer on getting started with design systems. 6:53 Few of her accolades, so she knows a few things about design systems. 6:57 She tweets, I like my title at Salesforce as lead designer design systems. 7:02 People ask but it's just one, why plural? 7:08 A design system or the design system makes people think of a deliverable artifact or 7:12 a library, but it's ongoing design system work, 7:18 process of improvement and workflows. 7:22 Jina Anne continues to explore and surface the intangible work, 7:31 like collaboration and community building within design systems work. 7:36 So here's an image of the typical IKEA catalog. 7:43 It is a living room with a big blue corner sofa with lots of colors, 7:48 and there's a billy bookcase, there's a desk. 7:54 It's very Ikea. 7:59 And Brad Fost once defined a design system as the official story 8:01 of how your organization designs and builds digital products. 8:06 He said, a kit of UI components without accompanying philosophy, 8:12 principles, guidelines, processes, and documentation, is like dumping 8:16 a bunch of IKEA components on the floor and saying, here, build a dresser. 8:22 The guidelines and documentation that accompany the UI components 8:26 serve as the instruction manual that come with Ikea components 8:31 to help the user properly and successfully build furniture. 8:36 So however you define it, a design system is a source of truth for 8:43 your visual design, ready to use coded component library, and ways of working. 8:47 So what's the big deal with design systems? 8:53 Well according to Enterprise UX Industry Report 2017, 2018, 8:57 design systems have been used in some form by roughly 70% of Agile organizations. 9:02 This combination of assets and guidelines have provided organizations 9:08 the roadmap to quickly and easily build digital experiences. 9:14 So here's a word cloud of a few well known design systems, so 9:20 I'm sure you're familiar with it at this point. 9:23 You've used it, you've had it on the app, and 9:26 you've probably visited a lot of websites based on this. 9:30 You've got the human interface guidelines by Apple. 9:36 You've got Material Design by Google, Polaris for Shopify, 9:39 Lightning Design System by Salesforce, and more. 9:42 The mainstream adoption of design systems have inspired the growth of 9:45 communities across the globe. 9:49 There's a slack community with over 16,000 members. 9:51 There's even a channel just talking about naming because naming is hard. 9:55 There's a dedicated conference clarity I mentioned coming up in September. 10:00 Lots of good talks to learn from and, 10:05 even looking at the past ones, it's a great place to get started. 10:09 And also there's a global design system community hosting local, 10:20 now virtual meetups in chapters around the world. 10:23 This is a place for people to share ways of working,, success and other learnings 10:26 to encourage best practices in building, scaling, and maintaining design systems. 10:31 Full disclosure, I contribute to this community as a Content and 10:37 Social Media Manager. 10:41 I must really like design systems. 10:42 So, why use a design system? 10:48 A design system is not just another tool in your toolbox, 10:50 it can be the toolbox, the tool shed, or workshop. 10:55 Use it because you need to solve a problem, 10:59 it can be one really big problem or it can be a really small problem, but repeated. 11:02 A design system can provide the solution or it can provide the decision 11:08 making to find the right solutions for you and your organization. 11:14 I am gonna list a few reasons why you would wanna use a design system. 11:19 And here I'm showing you four pie charts that show the top 11:25 four challenges [LAUGH] on organization in UX design, 11:29 the top one being improving consistency and testing designs within users, 11:34 clarifying requirements, and collaborating between teams. 11:40 One of the most common challenges that a large organization has is, of course, 11:45 the improving design consistency, and why is consistency important? 11:51 Because consistency builds trust, and 11:57 you build trust through recognition and reliability. 12:00 You can use a design system to create a familiar and 12:03 unified experience for all your customers. 12:07 You can eliminate inconsistency by auditing and 12:11 consolidating your visual language and coded components. 12:14 Another challenge is managing design and technical debt. 12:21 So here you'll have the meme of, and, again, 12:24 design tools are so ahead of its time. 12:28 I don't know if you're familiar with this, this is the Photoshop file icon, 12:30 and here it's every designer in this world, at the top left, 12:37 the first icon it says, new.psd and then your next file is newfinal.psd. 12:42 But then there's another one, there's newfinalfinal.psd. 12:48 So it continues because it's never final and you're always iterating and changing, 12:52 and so there's this mantra in the Agile organizations were moving fast and 12:59 break things sounds exciting, but you do end up breaking thingsand that's not fun. 13:04 [LAUGH] So building quickly for the short term means that over time you start to 13:11 collect too many inconsistent and separate experiences. 13:16 Designers end up having their own copies of design files and assets, 13:19 sometimes multiple versions. 13:24 And developers end up having to customize or build their own components to 13:26 meet their own specific need, which can quickly get outdated. 13:31 This leads to inconsistent experiences, so 13:35 use a design system to move fast and not break things. 13:38 You can access a centralized library of design assets and coded components. 13:42 And then you can contribute any updates you make back to the design system, 13:49 which now can be shared with others. 13:54 I have a bullet list of three items here. 13:59 The next few challenges fall under the same sort of bucket, 14:01 you have knowledge gap between time and development, 14:07 lack of collaboration and miscommunication, repeated or wasted work. 14:12 So you can use a design system that's establish a shared language 14:18 between design and development. 14:23 You can document common patterns and interactions. 14:25 You can save time and avoid duplicate or alleviate the burden of decision making. 14:29 As you address these challenges your ability to scale improves. 14:36 Design systems allow for automation in the design process, 14:41 you can build more with less effort and resources. 14:45 By addressing the mundane and tedious work you can focus on the big picture, 14:48 build better user experiences, design creative and delightful interfaces, 14:55 explore more deeply the challenges of your organization and for your customers. 15:01 And here we have the opportunity to scale [INAUDIBLE]. 15:09 This is a screenshot from Tatiana Mac, 15:14 Building Socially Inclusive Design Systems. 15:17 And we have a bunch of input fields that drop down and radio. 15:22 And you can see the label gender and in the drop down, male is first and 15:26 then female is second, male is on the left and on the right on the radio. 15:32 And even a gender label that has more than two [LAUGH] you have male, 15:38 female, unspecified, undisclosed. 15:43 So by looking at this, whether you're aware or not, 15:46 bias is assuming that male is the first and default choice. 15:50 Is there any other way to order these options, alphabetically perhaps? 15:55 So, you see without even realizing it, bias has reached your system. 16:01 Working on and with a design system offers the opportunity to 16:08 embed inclusive principles and accessible components and patterns. 16:13 And by front loading accessibility into your visual language, 16:19 coded components, documentation, content guidelines, 16:23 you're able to make your products usable by people with disabilities. 16:27 So important note, although you can make coded components as accessible 16:32 as possible, it's important to make sure that how it's implemented and 16:37 how it works in the end result is accessible as well. 16:42 And what makes a design system? 16:48 I mentioned a few things, everything and the kitchen sink, just enough. 16:50 I'm going to list a few things you might include in your design system. 16:55 I gotta get a drink because it's a big list now. 17:00 Well, [LAUGH] it's a big list. 17:04 [LAUGH] Design systems may include design principles, 17:07 UX guidelines, development guidelines, coded UI components, 17:12 user flows, designed tools, accessibility guidelines, 17:17 content writing, voice and tone, team structure, resources, 17:22 roadmaps, community meetings, community channels. 17:27 It can be a lot of things. 17:32 So here, we've got a pyramid with four levels, 17:34 the top one being components, the second one being visual design. 17:38 You've got values and principles and then it's the foundation of ethos and culture. 17:43 [COUGH] So, 17:50 this kind of illustrates the hierarchy of your components in the design system. 17:51 It can be as simple as a collection of visual or 17:56 coded assets to something mature as including values and 18:00 principles to define ways of working and simplified decision making. 18:04 As the design system matures, it becomes about building relationships and 18:10 processes that help enable or even define the digital culture of your organization. 18:15 Ultimately, a design system is the distillation of the organization's 18:21 brand and the expression of the promise of expected customer experience. 18:28 So now is the best time to help create a more inclusive culture by 18:34 actively updating and contributing to the systems you have access to. 18:39 So here we have another screenshot from another presentation 18:44 by Tatiana Mac, and I love her, you should really look her up. 18:49 So what we have here is a statement that intent does not erase impact. 18:54 We have the designer label pointing to intent, and 18:59 then we have the user label pointing to impact. 19:03 As a designer, again, be aware of your bias, 19:07 whether you mean to or not, you are making decisions and 19:11 that decision can include or exclude the experience of another person. 19:16 So as you design, code components, write documentation, create ways of working and 19:23 processes, remember, take a step back and understand your own bias. 19:29 System, digital or otherwise, are not inherently inclusive or free from bias. 19:35 What you think is the default and normal isn't for 19:40 everyone because decisions you make within the design system can 19:44 exclude people even when that isn't your intention. 19:49 Tatiana spoke at the clarity conference last year in which she describes 19:54 the social, political and infrastructural systems that affect the parameters, 19:59 limitations and variables of our design systems. 20:05 She shows how broader systems of power and oppression influenced the design 20:08 system and ultimately, the users who use the products defined by them. 20:14 So, if you think about the triangle design system, 20:19 I think about my own privilege and position. 20:24 In a large organization, working on an organizational tool, and 20:28 I know I have the opportunity to advocate for inclusive design. 20:33 This is your opportunity as well, as you become creators of digital experiences and 20:37 products, let's build with humanity. 20:42 Let's build design systems that help build products experiences quickly, 20:45 consistently, and more importantly, inclusively. 20:50 So how do we know when we've done it? 20:54 What makes a design system successful? 20:57 You can try measuring it, you can measure quality. 21:01 Is the user experience consistent across your products? 21:06 You can audit how many reusable components you have versus snowflake components. 21:10 You can measure performance, accessibility, 21:16 the number of components, adoption and contribution. 21:19 You can even measure speed. 21:24 Speed as in are your users able to create their product experiences with 21:26 what is available in the design system? 21:31 And you can experiment by measuring how long someone takes to complete a design 21:34 with or without a design system. 21:39 So, maturity, you can also measure that, 21:41 do you have foundational or complex components? 21:45 Do you have complex code like APIs, design tokens, or even complex components? 21:49 What kind of governance contribution or maintenance model do you have? 21:55 How independently can it maintain itself? 22:00 These are a few ways to measure a design system for yourself. 22:03 So, don't compare yourself to other design systems as well because what works for 22:07 them may not work for you. 22:12 As with anything, the definition of success is a moving goal posts. 22:14 And you really wanna know what makes a design system successful, and it depends. 22:21 Every company has a different need and those can evolve over time. 22:27 Your definition of success depends on what you need. 22:32 From sharing design assets, to creating a limited number of coded components, 22:35 these can go a long way in helping a team build quickly and efficiently. 22:40 A successful design system, honestly, it's the one people use and 22:45 contribute back into. 22:50 It prioritizes communication and collaboration, 22:51 it embraces the process rather than the outcome. 22:55 A successful design system becomes a tool of organizational transformation. 22:58 So, for myself and our team at TELUS Design System, we're still trying to 23:04 figure out how we measure success, both quantitative and qualitative. 23:09 We've tried dashboards to measure the adoption of our components. 23:14 We've interviewed our users to get positive feedback and 23:18 along with new opportunities for improvement. 23:22 While we don't have a definitive answer on what success means, 23:25 we do know that communication and 23:28 collaboration is critical to the health of our design system. 23:30 We have slack channels for support, general design systems discussions and 23:34 announcements. 23:39 We host monthly workshops, we attend design and 23:40 development guild meetings where we also share design system updates. 23:43 And most importantly, we've established a partner to our 23:47 core design system, which is the TDS community. 23:52 It contribution program that empowers our team 23:56 members to contribute to the design system. 24:01 We've actually gamified the contribution model, so 24:05 here we've got your first level, you get stickers, as you contribute, 24:09 you get more points and you power level to get land yards, you can get socks, mugs. 24:15 And then the big one as you get a big t-shirt. 24:21 [LAUGH] So, when we first launched the community, it was a great draw and 24:25 well, thoughts were nice to have. 24:30 We still saw great success with support, attendance, and 24:32 contribution through the community program. 24:36 However, within the year we began to see the challenges of creating a community 24:39 that was still at arm's length from autonomy and speech production. 24:43 We started to explore how we can maintain quality 24:48 of design without becoming blockers for our own teams. 24:52 We reached a point where teams must be empowered to 24:56 create unique components with less blockers. 24:59 And this is something we're trying to figure out. 25:01 One thing for sure, communication and collaboration is key. 25:04 We have to remember that the design system can only succeed if people use it, 25:08 otherwise, it's as good as a PDF brand guide, save it and forget it, [LAUGH]. 25:14 A design system is a product serving products. 25:20 And a design system is even better when you have a variety of components with 25:25 different features functionality to create vibrant and flexible digital experiences. 25:29 And here we're back to IKEA catalog. 25:35 What I love about Brad's comparison of design systems with 25:40 IKEA is that you have this collection of basic furniture. 25:44 But every once in a while, they add a new basic, and 25:48 they always have seasonal additions, and they all work together. 25:51 And IKEA provides so many basic and versatile pieces. 25:55 You can have the same piece in every room and it could still look different. 25:59 I think the best design systems are the ones that allow you to be creative, 26:04 while creating a cohesive look for 26:09 the rest of your organization to deliver a unified customer experience. 26:11 So, that's your intro to design systems, 26:17 [LAUGH] I hope you like it and let's get questions. 26:20 .Okay, so we got what was your path? 26:29 Yeah, so I started with GeoCities websites, I actually, 26:35 after, I don't know if you remember if still exists. 26:41 But I did go to a technical school Internal Academy of Design which 26:46 is pretty much kind of like the boot camps, the tree house that we have today. 26:51 And after that, I got into a small agency, and it was so small that literally I 26:57 was doing graphic design and then I was doing websites for the company. 27:03 So, that kind of kicked me off and then I joined Scotiabank, 27:09 which is the financial industry that I talked about. 27:13 And then, so I also want to Flight Center which was the travel industry, 27:17 and now I'm in TELUS Digital which is a telecom now working on design system. 27:24 So I'm pretty lucky and happy about that. 27:32 I have some knowledge and programming just not confident. 27:34 But then how do I know if I'm ready or not? 27:39 I think you're gonna realize a lot of the advice that people even 27:43 I get from other people, is you gotta start somewhere and 27:49 you just have to get started because there's no right time. 27:54 [LAUGH] You learn as you go, I'm still learning. 28:00 That's why I said in the beginning, you learn from your peers, you learn from 28:04 your managers, you learn from the organization, so you should continue that. 28:09 I've been designing and developing since the days, 28:14 [LAUGH] that is, but he took break for me, and now I'm coming back. 28:18 I've noticed everything has changed, it used to be web design and 28:23 now it's UI/UX design or design system. 28:27 So I don't know what my role even is anymore, 28:30 but what would you suggest I start to jump back into it? 28:33 That's right, so UI/UX is this big cloud very next, 28:36 cuz sometimes you could be more UI, more UX. 28:42 And I think beauty of it is that you're 28:46 not pigeon holed into a specific role. 28:50 And even if you start off at more in the UI, which is the user interface, and 28:55 you're just specifically pixel pushing, 29:00 eventually you're gonna get pushed into UX. 29:03 Because you need to push your boundaries and you need to deliver. 29:06 So, again, with the question of how do you know when you're ready? 29:09 I think you kinda have to start where you wanna work, 29:15 what kind of work you wanna be doing? 29:19 And then let design is such a broad term, let that passion find you. 29:22 And so, there's another question from 29:29 Christian, is UI/UX graphic design? 29:34 [LAUGH] I think I kinda touched on that, so 29:38 it's almost like if you took graphic design times 100 on. 29:43 An added experience to it. 29:50 So graphic design is just very visual, very pixel. 29:53 But you need to add interaction to it, 29:57 you need to add the why and the rationale of those things. 30:00 And that will bring you to [LAUGH] I don't know if I said that properly. 30:05 We've got a question from Roberts. 30:11 Do you recommend Adobe XD or Photoshop for web design? 30:14 So I specifically did not include talking about design tools or 30:19 the languages because those depends on your organization. 30:25 It depends, even now we do use Sketch, 30:31 we use Envision VSM to manage our design system. 30:34 But your organization is continually looking at 30:39 tools to make it more efficient. 30:43 Is this serving our needs? 30:46 And it doesn't matter what tool you start with, 30:48 it has to be, again, it has to be a tool that everybody uses. 30:52 Everybody has to be on the same page because if one team is 30:57 using a different tool or software and 31:02 you're using something different then your files don't much and 31:05 you're not able to share components. 31:11 And here we have a question from Hannah. 31:15 Do you have a part in the research aspect of figuring out what 31:17 the product needs in terms of accessibility? 31:22 If so, how do you source your audience? 31:25 [COUGH] 31:28 So part of the design system is we do 31:38 reach out to different groups in our organization. 31:41 In our community of practice of designers we have user researchers, 31:47 we have accessibility experts, and so we try to go through this matrix and 31:53 try and help ourselves create accessible and inclusive products. 31:59 But anytime when we have any questions or if we need to reach out, 32:04 we do reach out to the appropriate people and 32:09 then they can help us determine what are the right questions to ask. 32:11 They're not necessarily gonna be like, here's the solution, 32:16 but they can help you find the right answer. 32:20 Okay, and then here's a question from Jason. 32:26 When applying for a role to work on design systems, 32:29 would you recommend creating a design system from scratch for a portfolio piece? 32:33 That is a great question. 32:39 So that's great if you really wanna get into it, 32:41 it'll show you that you're capable of doing that design of building it yourself. 32:46 And to be honest with you, I haven't been in the process of hiring so 32:53 I'm not quite familiar with what people are looking for. 32:58 But from my experience, the way I was hired, 33:03 I didn't have design systems 33:10 the way it is today experience. 33:15 I did have a lot of work with brand guidelines, so 33:20 there there was that aspect that helped contribute to getting me where I am. 33:24 And I think if I look back at the way I was interviewed, 33:30 it was more of my systematic thinking, 33:37 my ability to see the creative potential of 33:42 something boring as working on bonds and cards. 33:47 So it really I think it's about your passion for 33:53 it and how you express the way you think so 33:59 that it helps build the design system. 34:04 What is the best way to manage versioning of components in design systems? 34:09 So I think this is something that I can tell you a few things that we have today, 34:15 and that's not to say that this is the best way. 34:22 It's one of those things where you kind of start one way, 34:26 realize you gotta pivot, and then you go another way. 34:30 And so in the beginning TELUS did have one one repo for 34:34 all the components, and that means anytime 34:40 a component is updated you need to download 34:44 the whole package again because it all goes as one. 34:49 And that's basically how Sketch is today as well. 34:54 Did some versioning, so if you were to only update a component, 34:58 the whole library has to go up and people have to download the whole library. 35:02 But the way our code repos work now is that each 35:08 component is its own file, its own package. 35:13 And that way when I update the button, when we update the button, 35:17 you don't need to download the entire thing, so it has its own version. 35:22 I hope that answers, if not you can always reach me on the social. 35:27 [LAUGH] What boot camps would you recommend one 35:31 should look to study UIUX Designer for 35:36 someone who's totally a beginner? 35:40 So, I'm not familiar with a lot of boot camps, [LAUGH] but 35:44 I know Treehouse has lots, you should probably check it out, 35:48 especially if they have a trial. 35:53 I think it's one of those things, right, are you ever ready? 35:59 You just gotta dive in. 36:03 And I think if the course is in your budget, if it's in your realm 36:04 of actually going for that, that's what you need to look for. 36:09 Because, like I'm trying to explain here, 36:14 it's about how you yourself approached learning and how you teach yourself. 36:18 Yes, boot camps do give you commodification gives you 36:25 that certificate, it gives you a stamp of approval, but 36:30 at the end of the day it's about you and how you learn and 36:35 how you express that in your projects. 36:39 And I think it's regardless of where you go, 36:43 it's how you create your projects. 36:47 What devices are you using for graphic design? 36:52 I have a Mac Book for work, I also have a Mac Book for home. 36:55 I used to be a PC person because I used to game a lot, but Macs, 37:01 the reason why I use Macs now is just I don't have to worry 37:06 about building my own PC and kind of tearing it apart. 37:11 It's just like, I'm going to turn off my computer at the end of the day and 37:16 go watch Netflix with my kids. 37:21 [LAUGH] Can a web developer UX designer 37:22 get his first job as a remote job? 37:27 Why not? 37:32 Why not? 37:33 Yes, you should. 37:34 There are a lot of remote jobs. 37:35 I haven't had a remote job, although technically I kind of have 37:38 a remote job now now that we're working from home. 37:42 [LAUGH] The concept and importance of design systems is clear enough, 37:45 but how do you actually start building one? 37:53 One of the slides these three things like colors, fonts, images, but 37:59 what is the practical way to start building? 38:03 So I did go through, like here are all 38:06 the components of a design system. 38:11 And what I wanted to be specific about is you 38:16 really only need to build just enough to build whatever your product is. 38:21 So it's not like I'm gonna go look at Shopify's design system and be like, 38:30 okay, those are all components I need to build and I will have a design system. 38:36 No, if your website or your app is only three pages, you probably 38:42 only need to start with typography and colors and maybe some sizing, 38:47 and those are the pretty foundational stuff to get started with. 38:52 And then obviously a design system is not really a design system until 38:57 somebody else starts using it with you. 39:02 Hackman protocol IO for screen designs. 39:09 To be honest with you I don't remember using it, so I cannot give you an opinion. 39:13 And Caleb says, how long are you expected to master UXUI design system? 39:19 So if you're talking about actually mastering it, 39:26 is that more you need a formal education for it? 39:30 Because I think this is the attitude of being a lifelong 39:35 learner is I never feel like I'm the master of something. 39:40 If it's, [LAUGH] you don't know what you don't know, so 39:45 I feel like this this part of me is like, 39:49 I can't call myself The know it all of UX UI design. 39:52 And we have a question here. 39:57 How has COVID impacted your current work and 40:01 how do you see it impacting the future of your work industry? 40:05 [COUGH] So I think we answered a lot of questions. 40:10 So How is Covid? 40:15 Yes, definitely, so Covid has impacted my work. 40:19 I'm pretty lucky that our work in the the digital part of Telus, 40:23 the telecom communications because we also sell products in store. 40:31 So it's pretty lucky that I get to work from home. 40:38 But what the challenge is, is that we need to 40:43 continue providing service to our customers. 40:48 And that means making sure that our digital 40:54 experiences are at a level where we're not 40:58 letting down people because if we don't have 41:03 in store people anymore then, well, we do. 41:08 It's just we need to keep the lights on, we need to make sure 41:13 that our customers are getting the same level of quality experience. 41:18 And so that's kind of the challenge that we're all working on. 41:25 And design systems luckily is I think very critical to that kind of work. 41:30 Because if you're trying to create new pages, 41:36 new experiences you need to be able to do that really quickly. 41:39 And the only way to do that and without a lot of repeat work based on leave in work, 41:44 certificate of work is to use the design system. 41:51 Well, and I hope that answers that. 41:55 And what's your desk setup for remote work? 41:58 I live in a very small place. 42:03 [LAUGH] So right now, I'm in the kids room. 42:08 I'm in like the Tiny Corner, I'm all squeezed in. 42:12 But as long as I got my desk, I got my monitors and 42:15 got my music and my lights, I'm all good. 42:19 [LAUGH] I'm okay with the tiny corner. 42:23 Okay, and I think we have a question from Jonathan. 42:28 I have a UI UX interview this week. 42:33 Yet, I don't technically have measurable experience as a UI UX designer developer. 42:36 I do have experience in graphic and web design, 42:43 as well as some front end web development experience. 42:46 What skill should I highlight? 42:49 [COUGH] Yeah, I think, so you're saying you don't have measurable experience, 42:51 but you have experience in graphic web design and 42:57 you have front end web development, whatever. 43:01 That's literally the definition of UI UX designer developer. 43:04 So I think you're gonna be okay. 43:09 I think maybe when you first start out, 43:11 you kind of really wanna show flashy graphics, 43:16 flashy animations. 43:22 And really, I think the best way to really make 43:25 yourself stand out is really explain your 43:30 rationale behind the choices that you make. 43:35 Why did you make it? 43:39 This color, is it accessible? 43:41 Usually totally highlight like, more of the benefits of 43:44 what you're designing like the problem you're trying to solve, 43:49 like those again, assets that you create, those are those are nice. 43:55 But at the end of the day there's a person that is gonna use that, 44:01 and there's a reason why they're gonna use that. 44:07 So I think it's very important whether you're creating a project for yourself or 44:11 you're working on your portfolio. 44:16 It's like be very clear why you're creating this and 44:18 hopefully that shows through in your in your projects. 44:21 Do you have any advice for people looking to make a complete career 44:30 transition to UX design when battling with impostor syndrome? 44:35 So [COUGH] impostor syndrome doesn't go away. 44:40 So can I think have that all the time. 44:45 That's why learning is so important that you have 44:47 this fear that you don't know what you don't know. 44:53 But I've met so many people that have transitioned into UX design, 44:59 that is not from graphic design. 45:04 They used to be a nurse, they used to be a musician, they used to be like, 45:07 there are different ways to transition into UX design. 45:13 And ultimately, it's not about pixels, so 45:19 you get into UX design because you get to the heart of what that, 45:23 so there's the user experience but think about it is like 45:29 what is the human experience that you're designing for, 45:34 it doesn't take a great artist or create like creative person. 45:39 Creative in like very visual 45:45 person to get into UX design. 45:51 It's again, getting to understanding what the problem is, 45:57 getting to understand how you can help the customer, 46:02 how you can help the person at the end of your experience. 46:06
You need to sign up for Treehouse in order to download course files.Sign up