Collaborate on Figma Invoice Template for Non-profit Organizations with Ease Using airSlate SignNow

Figma invoice template for non-profit organizations

there's a lot of different ways to go about building out Design Systems right A lot of people think it's just about building out the components and building out the right design pieces and making sure everything's connected and functioning and seamless automation all the way through while that is true really a lot of the work is about connecting our team and getting that team alignment and these resources are really focused about getting that team alignment the next resource that we're going to talk about is the governance model or contribution model so this is a super beneficial template when we are thinking about how do we contribute or how do we manage contributions to our design system and how do we even make the decisions about what needs to be added and what doesn't need to be added so we use this throughout the entire design system creation not just at the end if you save documentation and things like that to the end it's probably not going to get done so it's good to just be thinking about it the whole time and this is super helpful for educating new team members on building out their individual process and understanding the design system and how they can contribute and how the different rules and maybe guidelines and definitions are set up so we're going to jump into here like I said before same thing we've got a little Knowledge Center kind of how to unpack this and kind of talking about sort of the way we think about this and the way we think about uh the governance model is it's really a framework of four categories and we broke it up into four um based on different models that we've looked at and different governance uh and contribution models we've seen and and kind of unpacked and this is a boilerplate so it's framed up with different questions so you can go in there and ask yourself some questions as you're going through this and make those adjustments as you're kind of working through so but like I said before we broke it up into these four specific categories we have our decision area so what is the decision tree or the flow that I go through to make an actual decision so for example if I zoom in here it's like does this component already exist yes or no if it does does it meet all requirements no then we're going to unpack the needed requirements and present them to the team does this component is it a new component or a modification if it's new does this component scale across different products or screens right so like what are some of the things that we can go through as designers as we're asking the design system team or the design system uh or as we're acting asking everyone who's contributing to the design system do we need this component or not so that's part of the decision area the next one is the design area and we've unpacked the design as sort of separate because one of the things that we see in a lot of teams is design is in charge of building out a component and is in charge of thinking about of all the elements first before development gets involved right so uh we broke this out here design might be building this in their UI kit they're mocking it up with all the different states they're going to review the component with the development team and they're going to then see if it is uh sort of approved by the development team and then it'll go over to the development side which is the next category that we think about is the development side of that and then in here this is might be where we're creating that branch and figma or building that final component here we're conceptually working through what it might look like what it needs what are the different states and then here we're actually building that that final piece and development is building their component in the sandbox things like that we're testing it and then we're documenting the component the properties usage guidelines animations different things that we might want to document then we're going to get sign off and then we go to the last part which is delivery and delivery is like publishing it to the design kit publishing it live components out to our sandbox environment or to our live coded library and then communicating with the team to the com uh the different links and components and documentation making sure that the team's aware of that right so this is a really simple breakdown of a governance flow but it's built so that you can customize it for your team and what does your team actually need so for example what we've noticed with a lot of our clients and a lot of design system builds is the design team is a lot more involved here with the early stage of a component than they are when it gets into develop development so honestly like this actually can get removed from here because what design is going to do is they are going to create a branch in figma and they are going to build that component right figma has branching so we notice this with a lot of organizations so the creative Branch with figma and what we might put in here is uh follow branching guidelines um and those branching guidelines branching guidelines uh might have a link somewhere so then we would add that length and we'll just do google.com for now right so we're going to do that there and we'll make sure that we have that and so what our design team is going to do is they're going to mock up the component in all the states they're going to review the component maybe with the development team but instead of mocking up the component in all the states in sort of isolation we're just going to do this in the branch that we've created so this is actually going to get moved over here and we're going to delete some of these connectors and this is based on like a specific client that we've worked with and kind of how they function in their design system Team Works after discussion so we're going to move this connector down here to this so design team is going to create a branch of figma they're going to follow the branching guidelines then we're going to mock up all the components and the states and then in this specific instance and I'll just duplicate this because for simplicity's sake once the component is done the design team will review with design um Team group and then we'll move this are there any changes down here I'll delete this little line here right and we'll start to ask these questions and unpack this flow and if there are changes we'll move it back up here and then we'll add a yes and actually that's not going to go to the branch it's going to go up here to the mock-up so we'll move this out here and then if there aren't any changes it's going to move on and so then we'll go through and kind of clean this up and this is our new our new Contra our new design process and this might change right so like the idea of updating this as we go is that this might change because different needs might happen right when we get into the decision area there might be Parts where we now have to uh we have to think about multi-tier design system right so then we have to ask more questions and things like that so this might evolve and you might have different models depending on how big your design system is or how big your design system team is so like I said this is a super beneficial diagram to go through and really unpack with your team and using that design system interview that we talked about earlier you're going to find a bunch of things that you might impart in here based on the questions you're asking you might know you might not know things about your process that are currently in place that you can start to map out and put that and put that in here as well we like to link to all of our documentation too so that's really nice little nice way to link back out to specific documentation so for example if we have branching rules written in a notion document or in the um design area we might have an accessibility check so we might go hey link to all of our accessibility uh question or documentation or we might have a documentation hosted in something like zero height things like that we might have those links in here as well as we go through because this is a good resource for someone to understand the whole process and really understand where all the documentation is for that process this is part of our Design Systems in figma course so you don't need to have used the course to use these resources they're all free in the community but if you really want to unpack how we build out Design Systems in figma from like a designer's point of view the whole design team here at Headway put a really great course together it's available at shipwright.design so definitely feel free to check that out we've got some other resources out there as well like ux audit templates building customer Journey Maps a brand guideline template and then of course our free UI kit and design system starter kit and we use these in everything that we do and if you do use any of these or download them I'm definitely looking forward to any feedback that you might have of adjustments or things that that work best for you or didn't work for you as we're trying to build really the best resources that we can for Design Systems and for designers working to do their their different product designs