Get a seat at the table and build the design career you want. This podcast is for designers looking to break in, level up, and take control of their careers—whether you're freelancing, climbing the corporate ladder, or just trying to get noticed. Every two weeks, we dive into career fundamentals, design best practices, and the hottest topics in the design community.
People are a bit modest. I talked to so many designers where they are very calm and easy and, you know, we did this and, you know, I'm able to do this kind of thing, you know. And I always have to tell them, no, you should be more in people's faces. Not not tell them about, you know, I I am able to do this thing. No.
Nick:I do this thing. It's just what I do. Way way stronger. That applies here too. You want people to come to you.
Nick:You know, when you're new at the company, nobody knows you exist and they don't know what you do. The ones you give them a little bit of... And
Tyler:you're officially live.
Nick:We're officially live exactly. I mean, this is just an experiment. Hello. Hello over there.
Tyler:Nice to be back with you again.
Nick:Mhmm. Again and again. How are you today?
Tyler:I'm pretty good. Really, can't complain. The sun is shining, but it's getting colder. So it's it's that transition period where I knew winter is coming.
Nick:Yeah. It's a favorite time of the year for me that... Just after summer. It's it's kinda warm still, but it's also dark out early, and the leaves are changing color. The the scenery is very good to to walk through, which makes me sound like an old man a bit, I think.
Nick:But but still, you know, I... Yeah. My favorite time was I appreciate that.
Tyler:I appreciate that too. It's also right before they change the time. Then after they change the time, it's dark in the morning and dark at night. But Yeah. This period where it's a bit a bit warmer during today, a bit cooler at night, I think it's the perfect mix.
Nick:Let's let's just discontinue the whole changing of the time thing, by the way. I mean, the the user experience of that whole moment is just terrible.
Tyler:Yeah. No. It is. We we
Nick:can all agree on that, I think.
Tyler:In Ontario, my my... The the province, so our left is actually... They voted... Half the province voted for... To have it, and the other half doesn't.
Tyler:So it's a weird it's a weird thing where you don't know what time it is depending on where you are located in the Ontario region. So that one's gonna be an interesting one.
Nick:Yeah. Well, if the first one goes, hopefully, more will follow. You know, they're all pointing at each other, looking at each other, like, who's going to go first? And should it be wintertime or summertime? You know?
Nick:They're just stuck. So maybe the Ontario people will unlock it for all of us.
Tyler:Hopefully. Hopefully. Because I'm I'm Yeah. I'm okay with never having to go back and forth. It's fine.
Tyler:Yeah. Same. Same. Let's stick with it.
Nick:Same. Same. Maybe we should just keep things simple. I think that's a good lesson for any... Anyone, not not just designers, but anyone.
Nick:Let's, you know, let's let's talk about the main topic today. Don't want to make it too ominous, but we're going to talk about signs that you're about to be replaced Okay. At work. You can almost hear our audience now shout at us, you know, by AI. Well, yes, maybe by AI, but also by another designer or maybe even someone in a different role just just in general.
Nick:And then, of course, how to, you know, save yourself, how to prevent it from happening. Mhmm.
Tyler:Yeah. I think we have some good tricks... Tips and tricks for today. I'm excited to dive in.
Nick:Yeah. Yeah. Maybe maybe we should start with, well, the the literal designs. I I have two in mind. Just going to mention that the first one is when you're being asked to develop a design system.
Nick:Think that's the first one.
Tyler:Why do you say that?
Nick:Well, you know, if if everything is in a system and you have rules when to use certain components and when not to use certain components and then, you know, the the best practices and all all the good stuff that comes with the design system, it's way easier for a nondesigner or a nonhuman to to do it for you. And then especially at a lower UX maturity company where they think, well, UX is just pooping out screens and then UI, especially then, you know, the risk is quite high that they will think, well, you know, we have a design system. We can just use AI now to to do to do this whole UX thing, quote unquote, which is wrong as we all know, but they don't know. And that's why there's a low level UX maturity at the company like that.
Tyler:Yeah. That's fair. Yeah. I I see where you're coming from there on that one. It's like they...
Tyler:Like, the output that they see from a design typically, and depending on its size and its maturity to your point, it's like this this UI or this design deliverable. But, like, if there was some kind of system in place to kind of dictate, hey. This is how we... This screen works. This is how this component works.
Tyler:Then potentially, someone... An engineer or someone else can just put things together. But... Yeah. That's fair.
Tyler:But I guess it's it's up to the designer in that case to set the bar or, like, increase the maturity of that company. Like, as we just speed up our process with creating things like design systems, I think the the goal is there. We've now created a system to create UI. Now this unlocks time for us to do other UX work And then communicate to the to the org what that work is so that we're not just setting ourself up in that case. Oh, well, we did this thing.
Tyler:Now this is my deliverable. This can be Yeah. Automated away by AI or another team.
Nick:So is is that your recommendation for someone who's listening to this now and they're like, wait a minute. They've just asked me to do the same thing, and they're in panic mode now? So that's your advice for them?
Tyler:Yeah. I think it's always about... So, like, you as the individual on on... Or the UX designer on the team, like, if you're in that environment where it's, like, low design maturity... And that's, like, part of startup world.
Tyler:Right? So, like, someone's some founder or CEO or CTO starts a company. The first hire is probably like an engineer. Yeah. Because they wanna build the thing.
Tyler:And it's like like long days, long nights turning over a thing. The perception is that designers dragging, like, the the velocity in terms of, like, in in the spirit of, like, quality and and targeting the the correct experience for the specific user, etcetera. I think the goal there is to overly communicate the value that you're delivering outside of, like, the aesthetic deliverable. It's like, here are all the seven things that we do, and this is the one part that you get to visually see. The same thing with engineering teams.
Tyler:It was like, you see the end product, but there's a bunch of things that engineering team has to do as individuals to ship and launch, like, the the product or feature that you're working on.
Nick:Do do you think it would help if you became really strict on the the the way of working around the design system? For example, whenever a new component... There's a need for new components, it has to go through testing and reviewing to be done by an actual designer before it's being approved to be added to the design system?
Tyler:I think so.
Nick:Or... Yeah. Or can a... Like a manager just decide to skip all of that?
Tyler:I think you can... I think that's ideal. I think a designer should be involved in, like, the creation of a new of a new component, and then also coding it if if possible. Just making sure that there is more... It's more one to one to, like, the desired kind of outcome.
Tyler:I I think that's I think that's idea... Ideal.
Nick:Yeah. Yeah. True. And because of the the the most serious design systems I've been involved with, they all had a dedicated design system team, like a core team containing at least one designer, but also a development guy and a more, like, let's call it politics guy, you know, an an an outside facing, like, team leads, product owner type character. Yeah.
Nick:Because the design system is more than just design. A real mature design system for each component, they also have the code ready for you to copy out. You know? So I think, you know, if the company isn't all about speed and then they they they think they can then can discard everything, they should probably have a dedicated design system team, and you would probably want to be a part of it because then your job is way safer.
Tyler:Yeah. I think... Yeah. A 100% agree. I think the desired state is a design system team because, like, that is, like, the core of what, like, gives license to the entire product.
Tyler:I think this... The interim strategy could be done, like, if you don't wanna do testing for each individual component to kind of upgrade it to the design system. You can also, like, QA it or, like, user test it within the feature that you're shipping it with. So, like, you have this new feature. It does...
Tyler:It requires this additional component. We're gonna stress test the entire experience, but also this component as well. If it passes, then we're able to upgrade it to the design system. Yeah. But I've seen too many...
Tyler:Like, there's two... I think I prefer that strategy until you have, like, a actual design system team versus teams creating a design or designers creating a design system in Figma that's, like, complete, but only 30 or 40% of it is actually implemented in code. Then it's like this this never ending catch up game. I prefer the... If there's a new update, it's part of a shippable feature or deliverable.
Tyler:And then that gets merged into the design system. So that for the next feature, that's... That can... New components that's already. So you're iterating as you're building the product versus we've designed this thing.
Tyler:How are we gonna inject this into the product over, like, two or three different quarters Yeah. For example.
Nick:But I think your chances of success in that I mentioned is, you know, it it really falls or stands with alignment with your stakeholders. You know, I... In in our course, you talk about those 11 questions you have to ask. Yeah. It applies here too.
Nick:Like, when is this design system ready? You know, what should a component look like? Why are we building this this? Where can people, even nondesigners, access this design system? You know, Figma doesn't sound like the best place to keep a design system, if you were asking me.
Nick:A marketing colleague would probably struggle to find a component in in a design system. Yeah. So so... I mean, and that would probably strengthen your position as well. You know, ask a lot of questions back.
Nick:Make sure that your stakeholders are also scratching their heads like, you know, maybe this guy is right. Maybe we need to do this and this and this too. Yeah. Yeah. That makes you more involved and and much harder to replace.
Tyler:Yeah. It's all... It's always about over... Especially if you're working remotely, I think always about over communicating your value and, like, what you're Yeah. The thing you're delivering is.
Tyler:If it's just like I delivered the screen and that's what I do Yeah. Then it's essentially, like, someone can create, like, a wireframe or a quick prototype and then just about, okay. Just implement this versus the thought... Like, all the discovery work that's been done ahead of that final UI thing that you're delivering.
Nick:Yeah. It is challenging, though, because the delivering screens on a surface level, it's what we do. You know? Just like in a restaurant, a chef delivers you a plate of food, you know, but nobody really sees, like, all the thought that's been put into, you know, the thing ultimately ending up on your plate. You know, there's so much thinking there, and the same goes for for a designer.
Nick:So lots of companies that think we just deliver screens, and I also think... This might sound a bit harsh, but I also think lots of designers are only able to deliver screens. Like, nobody's taught them anything about the strategy and the business side of of being a designer. You know? It's not part of boot camps to think about stakeholder management and ROI and conversion rates and that kind of stuff.
Tyler:Yeah. It's like the... It's the tension where the the craft and and the the screens that you... The the ability to create these screens is, like, the first thing that you really need to nail. And then it's the balance of when...
Tyler:How once I've achieved whatever threshold, when do I move on to, like, strengthening the other, like, pieces of my equipment, like, my other swords and and my shelf there. Like, that's the tension. And also the the craft part, it's like, it's so deep in kind of... It's a never ending quest of of perfection.
Nick:Yeah.
Tyler:But it's really understanding that, like, that is that is the bar, but, like, the rest is really important as well. So it's like the business case. Because what you're delivering, yes, is the aesthetic. Here's the screen that we're delivering. But what you're really delivering is, like, the dis...
Tyler:Like, the seven decisions that are made ahead of it. It's like, what we're not building, What are we building? What are we measuring? What's the ROI of this thing that we're crafting? Like Yeah.
Tyler:That is that is packaged with the final screen because that's the thing that people are gonna experience at the end of
Nick:the day. I imagine that's something you you would you would have to tell people because they cannot just... If if you deliver a screen, they cannot connect adults from... To go from screen to business value. You have to be very specific, almost annoyingly so about selling yourself.
Tyler:Did... That's the name of the game. That's politics one zero one. Whether you're you're in house or, like, they're, like, overcommunicate what you're doing. And that's why I think Yeah.
Tyler:Like, documentation is number... Is is super important. Like, with... Any feature or thing that you're delivering, documenting the reason. Like, what is the baseline?
Tyler:What is the problem we're solving? What is the current state? What's the desired state? What are we measuring? How are we measuring success?
Tyler:And then when you ship it, document those wins so that you have essentially a collection of case studies regardless if it's gonna go into your portfolio or not. And then you have that thing documented for someone to refer back to. Like, we're going... Let's say you've developed feature x. You delivered, shipped it, cool.
Tyler:Now there's feedback that we need another iteration, a v two of this thing. You can go back to that same document with those success stories so that people are seeing that incremental improvement and success, and then you have the receipts of why you built this thing. And then the value that you've brought because you've... Now you've over documented, over communicated all these things.
Nick:Yeah. Yeah. People are a bit modest. I talked to so many designers where they are very calm and easy and, you know, we did this and, you know, I'm able to do this kind of thing, you know. And I always have to tell them, no, you should be more in people's faces.
Nick:Not tell them about, you know, I I am able to do this thing. No. I do this thing. It's just what I do way way stronger. That applies here too.
Nick:You want people to come to you. Know, when you're new at the company, nobody knows you exist and they don't know what you do. But once you give them a little bit of value, you know, at some point you will get notifications where people have been talking in Slack and they say, oh, you know, we should ask Tyler for this. You know, you have to build that name for yourself where people just know that, oh, he's our design guy. You know, it makes you much harder to to replace.
Nick:And the way to get to it is to be very visible. So, yeah, it's a long answer of a long way of me saying that I agree with you, basically. Before we continue, if you're feeling stuck in your design career or if you feel like you're doing solid work while no one really notices, we've got a bunch of extra stuff on our website.
Tyler:We're building a community for product designers to actually learn, grow, and get hired, not just scroll and collect more inspiration.
Nick:There's also articles, checklists, and courses.
Tyler:All based on real world experience from both of us. No fluff, just what actually works.
Nick:Check out designtablepodcast.com. The link is in the description.
Tyler:Yeah. Yeah. A good advice I got like a year ago from a mentor was that half the job is doing the work. The other job is communicate... Is Yeah.
Tyler:Just ex... Like, being your own cheerleader. I think that's a better term, like, being your own cheerleader. Yeah. It's not about being arrogant and, like, showboating.
Tyler:It's just, like, celebrating your... Or communicating your wins or the things that you do. Like, especially if you're remote, like, another... This probably ties into another sign that you're gonna be replaced. If you're not vocal...
Tyler:If you're in a remote environment and you're not vocal or active, like, on Slack or email, whatever it is, people are gonna forget that you exist. So it's just about having that paper trail, like, in those Slack or conversations. And to your point, if there's a situation that, hey. We should bring Nick into this conversation.
Nick:I I I really hate that. I think you're I think you're right. But, I mean, I can be quite introverted. I work remotely. I work remote almost exclusively.
Nick:I'm constantly selling, you know, and and it's it's going well, but it's also exhausting. And also, last time I had an office job, still in house also, I was denied a promotion because I did everything great except the internal visibility. And they they didn't think I did enough of, you know, hosting a workshop for colleagues or doing knowledge sharing events on top of a full time job, you know. So I was very annoyed to not have that. But I've come to realize that it's very important.
Nick:So now I'm I'm not as angry as I was before, you know. It's a downside that comes with the game, I think.
Tyler:You know, you have to be I'll tell you a trick probably that'll be very useful. And also, it's it's it's using the word we instead of I a lot. You can communicate your value and still use the word we because the work you did is still... Is inferred based on what you're trying to communicate. So, like, for example Yeah.
Tyler:Like, we just... We deliver this feature. And and in that example, you've probably did most of the... Probably the research, probably, like, the stakeholder management, etcetera, and then there was some development involved, some project management involved as well. But if you're constantly saying we, you're Mhmm.
Tyler:Everyone being vocal about, like, the work that we've done as a team, but also it's inferred or it's assumed. Yes. You you were part of the the recipe that was the ROI of that thing. And, also, it's about leveling up the team, making sure everyone's included. So, like, you're...
Tyler:The the most successful people at a company or in in general don't just level up themselves. They're leveling up. Like, they're multipliers. They're leveling up the team around them. So if you're seen as that, like, that multiplier and if you have that we kind of methodology or, that that verbiage, it, like, it it really it really goes far.
Tyler:And you don't... It doesn't sound like you're bragging because you're using
Nick:Mhmm.
Tyler:That we work.
Nick:What does that mean in this case, leveling up?
Tyler:It just... Well, with anything. Right? So if you're at a company in jet... Or, like, you're trying to you're trying to hone in on your craft.
Tyler:You're trying to be a better designer. You... Or trying to level up on your design skills, your coding skills, your user research skills. Like, you're trying to every day just be a a bit of a better than the person you were yesterday or year ago. Right.
Tyler:Right. But in the same... In that same frame, you should be also leveling up the team around you. Reminds me of back... I think one of my first jobs, I had a very...
Tyler:Which I think is a great thing. I had really healthy competition with one of my colleagues. Mhmm. It's like we we we both wanted to kind of beat each other. Like, who's the best designer in who's the best designer in the company?
Tyler:But we did it in such a, like, a... In a healthy way. Meaning, if I was more proficient at a thing and he wasn't, I would teach him how to be my thing that I'm really good at so that we're both level... Trying to equal the playing field, but I'm still gonna beat you. So I'm gonna I'm gonna teach you what I know, and I'm still gonna beat you.
Tyler:And you're gonna do the same thing for me. So we're... But it's it's this it's this... We're rising the ties, but also, like, I'm still I'm still gonna be number one. I think that's a healthy way to kind
Nick:of... To see that. Yeah. Yeah. Competition brings the best out of us, or mostly.
Nick:Yeah. I I mean, I can see that. I think a sign really closely related to this is you not getting invited to meetings anymore.
Tyler:Yep. A 100%. Which
Nick:is... It's a sign, and I I think it's it's close to being too late at that stage. It was still fixable. Probably same advice as before. You you you being visible, delivering value, selling yourself well.
Nick:Right? I'm I'm just thinking that right now, I I don't... I'm not sure if there's anything else to recommend in that case. Maybe ask why. Be open, potentially.
Tyler:I I think a good strategy there is just finding the gap that was left by not including you. It's like in a in a... Not a disagreeable way. So, like, you were in a meeting about maybe some research findings that was happening or a decision is gonna be made about, like, what we're gonna be doing in the next quarter or, like, an item that's gonna be added to the road map.
Nick:Right.
Tyler:Don't take it as a shot. Just, like, be proactive. It's like, hey. Take a look at what was happening and what decision wasn't made where that would be, like, your responsibility. So, like, a design Right.
Tyler:Decision was made, validate it if it was good. If it wasn't, raise it up like, hey. You guys might have forgotten something. I think this will be helpful. So, like, you're you're you're wedging yourself in with value versus being disagreeable or being that annoying person in the room.
Tyler:Like, hey. What about me?
Nick:Kind of thing. Yeah. Because that... That's the the reflex, the, like, the gut reaction many people have at that point to be like, yeah. You know, whatever.
Nick:You're all wrong. Blah blah blah. This company sucks. Blah blah blah. Understandable, but not the best thing to do at that stage.
Nick:You know, it's true. Which is very challenging. I I I know that from experience. Yeah. That's that's true.
Nick:What else? For this recording, I had a few more signs, but I I I only remembered the first two, I have to admit.
Tyler:I think, like, in that... Like, if you're not if you're not in the room, but, like, when you're in the room, making sure... Like, if you go back to, like, visibility, make sure that you're engaged and you're active in those conversations and not just like a fly in the wall that... Or like this checkbox that you... We just need to include this person in the room so that they hear it, that they have context.
Tyler:It's like when we invite this person to the room, they're adding they're adding value too. Like, this is like Yeah. It's, again, it's that overly communicative thing, like making sure that that you're seen and heard.
Nick:Yeah. I think value is probably the key sentence here. As long as you are of value to someone, they'll probably not send you away except for crazy scenarios, of course. But if your main way of delivering value is something they're currently automating, it would make sense to to have you, you know, get fired, which is... It's very harsh maybe.
Nick:But then when you see it coming, you should probably find another way to to provide a value potentially using the ways we just described. But still, you know, that's maybe a question you should ask yourself monthly. Like, am I still valuable? Am I providing value to stakeholders or to users?
Tyler:Yeah. And also, maybe as a quick tip there, I think just taking notes or not with... Not scrapbooking. Like, having a journal of, like, what you're doing. I think it's a very low level thing you can do, but, like, effective.
Tyler:Like, if you document what did I do, what are the three things that I did this week, have it in, like, the Notion document. And then six months down the line, you have these receipts. Like, oh, what did I do? Well, let let me go through what I've done. Yeah.
Tyler:And it's beneficial not just like, here's what I've contributed, but, like, some things, some opportunities to, like, that I could have done better. What... Let... Let's see what I can do better in the next six months.
Nick:Right. Yeah. You know, I use a Trello board for that because I always feel like there's more I need to do, you know, in a in a in a healthy way. So I have my Trello board every... At the end, when I finish something, I drag it to this done column.
Nick:It's just just like your your typical agile scrum board. But then it helps me at the end of the week when I feel like I've only been in meetings all day. You know, I can look at my done column and see like, oh, I I finished six things this week. It makes me feel better. But in our case of signs of you being let go, you should probably make that Trello board public.
Nick:Right? So that's what everyone can see, or you should make a summary that you share once a week.
Tyler:One... Something that our engineering team does, which is very good, is that they have weekly confluence wrap up of the week, like things we delivered, bugs we've killed. And it's just like a... It's it's almost like an internal blog that, like, people can kinda dive into. But it's in public...
Tyler:It's in, like, the public Slack channel, the the build department Slack channel. Like, if you wanna... This is what we did through this week. And it's... Even if you don't actually click in and read the Confluence document, you're still getting these notifications of, like, the t...
Tyler:This act... This team delivered something, which is, like, it it... At us... At that first glance, even at that parent level, like, they're delivering value, and it's and it's it's documented, and it's out in the open.
Nick:Yeah. Yeah. That's that's smart. You know? It's almost spammy, but it's it's a good thing.
Nick:We should all do that. Alright. Anything anything else? I'm I'm not sure if I know a few more.
Tyler:If they're if they're engaging with a design agency while you're still working there, that's a good sign that you might be replaced.
Nick:Yeah. Because they're already prepping your replacement
Tyler:Yeah.
Nick:With you still being there.
Tyler:But that that one's aggressive.
Nick:Yeah. I I I frankly remember that happening to you. Right?
Tyler:Yes. Yes. Yes. I I discovered that my manager was engaging with talks with agencies while I was running there. You had to think in Google Meet, you have...
Tyler:When you're trying to book a meeting with with someone, you get to see what their calendar looks like. And depending on what privacy setting, you get to see who their meeting is with. And I noticed that they there's... There are a couple sessions with agencies that I recognize from the local area.
Nick:Right. Okay. Yeah. Yeah. Yeah.
Nick:And then you were... You you stormed into the manager's office, and you were like, explain yourself. What's going on?
Tyler:Yeah. There's a lot of yelling and and wagging my finger.
Nick:Yeah. Yeah. Yeah. Yeah. Mean, and and along those lines, you have also have signs like not only you not being part of a meeting, but also the way of working you all agreed on and not being executed.
Nick:You know? People are skipping steps. Yes. Nondesigners are making prototypes. At some point, they will probably get good enough at prototyping that they're like, well, you know, I'm not going to ask Tyler anymore.
Nick:You know, it takes a day until he sends something back. I'm just going to prompt this thing myself, and I'm done in in an hour. You know, it's not a direct sign that you are being replaced, but it it does give the the person responsible for your your job, for your employment a sign. Like, hey. They're doing quite well with this design stuff.
Nick:They're not designers. Do I need Tyler? Do I need Nick? You know? So it's it's an early sign where, hopefully, you have some some time left to to prep and to prevent even.
Tyler:Yeah. And in that case, if they're doing that and they think they're winning, they're not measuring anything.
Nick:Oh, it's true. Yeah. You and I, we both know that an AI driven design system without any human help, you know, it it will just degrade over time because of maintenance not being done well, new components not being added well. Those new components, meaning the older components need to be updated for consistency and and way of use. It's probably not being done.
Nick:Yeah. So I'm still hopeful that all of this this AI job taking in design, at least, that it's it's it's a wave. Hopefully, there will be a return where they all realize, like, this is crap. Let's let's get a real designer.
Tyler:Yeah. I think I said it before. This is just... Like, history repeats itself. This is just another evolution of a engineering led organization.
Tyler:So if they're... Like, oh, let's replace Designer's AI, then it's... They're gonna be in the same shape where it was engineering led, where there wasn't a designer present, and then they're gonna have to play catch up, hire an agency to fix the work. And then it's
Nick:like Yeah.
Tyler:The cycle continues. So it's just it's just being aware that, like, this is this is nothing new. It's just it has... It's wearing a different mask.
Nick:Yeah. People always wanted to skip design. You can see it from the ratio of designers to engineers. It's, like, one to six. Maybe, like, one designer can handle a team of 60 developers easily.
Nick:Mhmm. It's just now with AI, those who don't value or think they need design, they now have the tools to prove it to themselves. You know? A few years back, they were just angry. You know?
Nick:A stupid design. Don't need design. Blah blah blah. Now the... Now they will prototype something and just go over your head to a developer and tell them, like, hey.
Nick:This is great. It works. We've done the UX. Build this thing, please.
Tyler:Yeah. Say it. I would do the likewise then. Yeah. I I coded a prototype.
Tyler:I did the development work. Ship it.
Nick:Yeah. Yeah.
Tyler:The world that goes over. Yeah.
Nick:Yeah. Yeah. Yeah. If it... If it's really coming for our jobs, it's probably coming for all of us.
Nick:You know? Yeah. But I I don't think it will go that way. Yeah. I mean, it's pretty...
Nick:A pretty good list. Right? I think we have Yeah. You know, the I think at least the big ones we have are
Tyler:I think the main takeaways here, probably the the one takeaway is communication at all levels. Being your own cheerleader, being active in meetings and in Slack so that you're... They hear you in the bushes, and then always communicating the ROI of your work, not just handing over a screen to be built. It's like bring with you the receipts or the decision that that deliverable is wrapped in, I guess.
Nick:Yeah. Yeah. You know, it's all about the value. You being useful. Yeah.
Nick:I think that's a good finisher. Right? Yeah. Alright. Well, to to all of you building design systems, good luck.
Tyler:Good luck. That's another episode in the bag.
Nick:Yeah. Great episode. By the way, if you're stuck second guessing your work or trying to figure out your next move, drop a question in the comments or leave a review. We might actually feature you in one of our future episodes.
Tyler:And if you got any value from this episode, hit subscribe wherever you're listening. It helps more than you think.
Nick:You can can find everything else, resources, articles, and more at designtablepodcast.com.
Tyler:Thanks for being here.
Nick:See you next time.