 Thank you so much everyone for being here for this very incredibly damn important talk about digital asset management in the remote age. I'm Adam Good. I'm a senior strategist at Parsons TKO. I'm happy to be talking with you about this today. A few just orders of point of points of order microphones have been turned off and cameras have been turned off as well. If you have questions, comments, anything's unclear you want to talk about stuff. Feel free to post it in chat and we'll go through that and respond either during the presentation or in Q&A at the end. And also want to let you know that the webinar is being recorded and will be distributed after the session along with the presentation deck. And also there will be a few polls that will pop up throughout the conversation as well. So really happy to have everyone here with us today. All right, so it's about damn time. We are talking about improving digital file management in the remote age. So with the pandemic forcing many organizations to go either partially or fully remote, managing your assets, managing in particular your digital files across the organization in a coherent and structured and transparent way is really important. I want to talk through some frameworks and perspectives on what digital asset management really is and what it takes to effectively get asset management rolling or improved in your organization. So a quick note about Parsons TKO and about how we see the possibilities of your organization. This will inform how I'm talking about digital asset management. This is a kind of philosophy called engagement architecture, which really treats your outreach platform as a holistic ecosystem. So it's not just a piece of technology here that does one thing and you know people that are doing their, their own things and content that you have over here. Everything is connected and those things need to be understood and improved together to help advance your mission. So we're always talking about, you know, what is the, what are the key engagements you're trying to drive with your audiences, and how do you have strategy that supports that. And then that lets us focus on the people and processes and platforms that are critical to actually succeeding in that strategy and driving engagement. So even though this talk is about dam, which often refers to digital asset management as a product or a platform, we really see it as a capability asset management as a capability that connects your people and the platforms they use and your processes to advance your work. All right, so what's the damn idea. I'm going to make a lot of damn jokes throughout throughout the talk so please excuse me I can never resist a good plan. I really wanted such an obvious one. So what's the, what's the damn idea. So it's not, we're not talking about this kind of damn. We're not talking about a damn that you just sort of put in place and it pools all of your resources and then they sit there. We're talking about digital asset management. And my good friend, Lizzo, just, we were talking about this and she wrote a song inspired inspired by this talk called it's about damn time. Because I think organizations, organizations know that they have problems organizing their, their digital assets and need to get them more coordinated and consolidated. So, what do we mean by damn. We're talking about the ability to organize assets so they can be found and used throughout your organization. Again, we're not just talking about the technology that helps make this possible. We're talking about an overall ability or capability to organize your assets and anything that you use, particularly images, files, video, content, pictures, reports, anything that people need to be able to find and use throughout the organization can be considered an asset. Many of you probably are coming from communications background so you might be familiar with doing some degree of asset management, maybe in your CMS so if you're working with a website like WordPress to really most modern websites, you can upload images into your website CMS and use them on the website. So, one kind of use of assets in your organization. We're talking about taking a step back and saying, hey, where do we store all of our assets, so that people from different parts of the organization can find them at different times. And there's a lot of benefits to this. So, probably you have some degree if you're like most organizations that we work with, you have some ad hoc damning. So, maybe some of your important files can be in any one or any all of these locations so maybe some of your important files are in a Google Drive or on SharePoint or something called a Q drive. Maybe they're in Dropbox maybe you've been experimenting with Dropbox maybe some parts of your organization use Dropbox and the other uses Google Drive. A lot of files are in people's emails. Maybe so maybe you have a hard drive from five years ago that you always have to dig up if you're looking for that one perfect image, or maybe they're print pieces, they're in a folder on an interns desk. So we see this all the time with with organizations particularly as they grow that assets are everywhere. And the fact that they're everywhere and in different systems with no kind of clear consistent vision and governance about where things go leads to a big mess, and a lot of frustrations, wasted effort, inefficiencies, etc. So we're going to start with the first poll, as you know, this quick survey of everyone who's here I want to know what your damn situation is what's your damn situation. We have no formal dam and we desperately need one. We have a dam but we don't use it well and we have an awesome dam and we're just here for the puns. So, in this sense we are talking about kind of a more specific digital asset management platform, like maybe using binder maybe you're using Google Drive, maybe you're using Dropbox. So, you know, the degree of which you have something formal in place. I see a couple people have awesome dams and they're here for the puns that's fantastic. Oh, wow, great. People are so fast. Thank you. All right, so the looks like we've got about 58% have a dam but don't use it well. I'm going to share the results. Okay, so kind of a good mix of people who don't have a formal dam and need one and others who have a dam but don't use it well. And that that's great this is for you, because a lot of the principles we're talking about can help you improve the use of a given dam. Again, with any technology platform it's really only as good as the clarity of your vision for using it and then how you execute on that vision. There are some ways that you can get clarity on how to use dams more effectively, as well as just, you know, what dams are and how we can more effectively use them. So great, thank you for that. All right, quickly, why should I give a dam about dams. I've never done dams before but basically if you're like most organizations you might be kind of a hot mess in terms of where your assets are. If you have scattered files online and off time offline, no system or too many systems. No process or too many processes for images from public relations go here and videos from media go here, and they have their own processes in their own places. So when things takes a long time, you might have random requests that take a long time to fill, and increasingly, our teams are distributed. So dam is, I like to think of dam is a new way and I put this scene from one of my favorite movies wet hot American summer, when they do this training montage about learning a new way. It's kind of like this mystical experience of, you know, leveling up and really focusing on dam lets you kind of increase your organization efficiency and realize things you never thought were possible. So it helps you get organized it helps you get more efficient. It helps you get much more consistent so that you know your images you're always showing the images that you want to show. And you're not showing ones that you know maybe fell out of favor two years ago and are still just kind of floating around. It also improves your institutional memory, especially with turnover being an issue now with a lot of organizations. If, if you don't have a comprehensive system and governance and process around it. When one person goes they take all of that knowledge with them. It makes it easier to collaborate if people can be looking at the same resources together. And then it's easier to get inspired by materials that people haven't seen. We've worked with organizations. A lot of times one one group will have a lot of interesting content that another group just doesn't even know about and when they come together to the table and say here let's get it all in one system. People start getting inspired about oh we could do this we could use this we could create this new campaign, you know featuring this these these images of this video. So this is, you know, truly kind of a secret sauce capability for organizations. So this is just a quote from one of our one of our clients at American Forest who we help them choose and implement a dam. And again, going from being disorganized over lots of different systems to really clarify the answer. How do you want to search it what do you want to look for how do you want to find those materials, and then creating not only a system but also a process for getting there. So this is the time that you're going to be using from finding things, sending requests, just gathering the materials to really doing more good with the materials that you have. Alright, so everyone I'm sure is very excited, and it's like, okay, dammy, give me a damn, I'm ready to go. I give it damn, give me a damn. Not so fast. So again, we want to focus on the critical elements of really any, any organizational initiative or organizational capability you need to talk about your people and your processes and the governance that you have in place around a particular asset or capability. Again, dam is a capability. It's not just software. It's the people who use and access your assets like your staff contractors, other external users who all needs to relate or use the system in question in this case dam, who needs to use it. What do they need to do with it. How do they like to work. What are the requirements right so for contractors you might want them to see some specific pieces of content and not others. So really understanding all the people who are going to be involved in your asset management or touch it in any way is critical process so really figuring out what the process currently is and where you want the process to go. Where are the steps that it takes to find edit and deploy your digital assets, you know, in any use case. So a lot of times what we do when we come in this where we start is with people and process, you know, what is your organization, do we now to find to find assets and how are they using them. How do they want to be able to find assets, what kinds of things that are what do they want to do with it are and getting those people together to paint kind of a holistic picture of what ultimately the capability of asset management needs to look like. Then we really focus on the technology. Where is it stored currently, what works what doesn't do we need a one size fits all kind of one dam for everything or can some assets still live in one place and some assets live in another and they're just tightly integrated. So the technology is really an enabling piece for your people to use your processes. And then finally governance is the overlay of all of these that provides rules and guidelines for for using assets. So, all too often, you know, organizations will get a new technology. They'll get the training or onboarding from from the vendor, and then it's kind of off to the races. Okay, great now we have a system. So there isn't clear maintained documentation and governance about how the system is set up. Who needs to use the system. What are the processes to go through. So these are all tightly interlocking parts that will really enable you to, to make the most of asset management. So just to pull the pull back a little bit and say, you know, when we talk about digital asset management. It's not just a matter of finding stuff putting all these things in a location and then finding it. You really need to tease apart the process of where, you know, from left to right here sourcing your assets where all where's your stuff coming from. And with remote teams, and people using contractors and external vendors, your, your assets can come from lots of different places. Where are those coming from. How do you ingest them how do you get them into the system, and then refine and edit them. So our how do how are you adding metadata how are you organizing them into two folders are using tags that are kind of agreed upon to to help the people in the organization on the right over here, use the assets. So that flow of getting things, putting them in the system, refining them so that they're kind of clearly, you know, labeled and set up to your systems and structures and then using them. Layer underneath that is really the idea of collection management and system administration. These can be large complex systems. Even if the end user experience is seamless and straightforward it still takes a fair amount of management on the back end and system administration so when one of the key pieces we talk about is, you know who is going to own this system, who's going to be responsible for the maintenance of the system. And, you know, sometimes that's in the comms department sometimes that's in brand sometimes that's in it. And that's part of the process of, you know, who are the people involved in dam. And then finally that underlying layer of governance again that documentation, you know, how do we use the system who's able to do what what type of approvals do we need. And this is all stuff that again happens in an ad hoc fashion in most organizations, it's informal, maybe there are some guidelines that someone wrote up in a Google Drive for themselves and one colleague, and it's sitting there and they know about it, but really having clear consistent and understood and accessible documentation is really critical. So we have another poll. So we talked about in the last one about, you know, do you have a dam are you looking for a dam. This one we want to ask about your governance. So, you know, the how is your, what is the state of your of your dam governance is it non existent. So you don't really have any clear processes documented around asset management. Is it okay. Great. And then you get a gold star and get to leave early, if you have amazing governance. Right, I'm going to share the results here. Excellent. Okay, yeah, so we have kind of a similar split. So there are two people said they have great clear governance that's consistently followed I'm going to call on you during a question and answer and ask who you are and what you're doing, because that that's awesome. Yeah, so, you know, again, we see a lot of organizations that don't have clear processes documented and often that's the first step that that we can do with you or that you can do on your own is just writing down. You know, even if you don't have a document yet, go ahead and write it down. You know, something that we have to do frequently is find headshots of staff to send to media outlets. Write that down and then, oh, here's how we find them. Here's how we find those things. Even if it's not documented, you can start documenting it at any time really, or collecting the ad hoc documentation that you have. Or, you know, it looks like about 60%, have a system that there are many gaps and ad hoc processes. For those in that situation. A lot of times what's good is to do kind of a documentation audit and say, here's the documents we have here other processes that we know are going on, or other systems that we think are going on or know we're going on and have those cataloged so that you have kind of a big picture of the knowns and the known unknowns. Yeah, the known unknowns or the known maybes. So, again, this is all just the stress that governance is really important understanding the processes that are in place, either formal or informal is key to making the most of Dan as a capability. Another reason I really want to emphasize this piece of it is that, you know, a lot of times organizations say okay well we need a platform, we need a tool, there's these great tools let's just get one. But if you don't have the process to support it, you know clearly going into selecting a dam or implementing it, you're going to end up with a better tool but in somewhat of a similar situation that you currently are. How to dam your org so let's get into this. So, you can dam your org in three easy steps and I'll go through this fairly quickly and talk about some of the ways that you can use these ideas even if you already have a dam in place. But really it's about getting clear on the requirements and again this is something that you can consistently do, especially as you're using the system you can continue to clarify exactly how you want to use it what you want to do with it. If you want to have a dam selection stage, then you definitely want to evaluate different vendors, and then ultimately you want to implement and you want to have a clear plan for implementing. So we'll go through a couple of these so with gathering requirements you really want to understand your users and processes I've touched on this a lot but who's using the system. What do they need to use it for really getting granular with your use cases storage space and file types, how many, how much stuff you have. What are the files you need to manage is it just digital files do you want some some degree of physical archiving to happen. Do you do audio do you do video. Are there financial records that you want in this asset management system that would only be available to some part of the organization or do you want grant reports. So again, anything that can be a thing can be an asset. And a lot of times, we think about dam from a communications context, but there are also robust systems that, you know, allow and encourage you to organize other files as well. Search use cases and taxonomy will get into that a little bit more but again, really getting specific with the people using the dam. What are you looking for. What terms do you want to find. How do you want to find things what do you want to use things for really getting granular helps you select and then. implement a system features and integrations. What are the kind of the core features that you need. What does it need to integrate with, do you need one place that can feed content into a website. Do you need to pull in content from a content pool, etc. So there's a lot of you know if you have other systems in your engagement architecture. Now's the time to kind of document them. So evaluating vendors. There's a you know a lot of vendors are kind of have similar features and functionality. And that's why we have features at the bottom, you know, once you once you get a sense of your requirements, a lot of the, a lot of systems will have similar features that what you want to do is get demo meaningful demos that let you assess the usability of the platform because it's something you know you are many people in your organization are going to be using regularly. It's got to feel good. It's got to feel usable. Of course cost is a factor you need to think of how many users you have how much space you're going to need. One thing that we really recommend that organizations look for is onboarding and support, you know, to what degree. You need really in depth onboarding and support to get the system up and running and then do what degree does the vendor provide that because there are some solutions that just say, great you're installed and you're ready to go. And there are others that will really set you up with a representative who will help you set up the system really to your to your liking and provide in depth training to make sure you're really set up for success. Know what type of organization you are like if you have someone who is like knows the stuff pretty well and is you know has the time on their plate to do the implementation work themselves you might not need a solution that provides is robust of a non boarding experience. So that gets the third stage which is implementation. You know, so, so many initiatives and organizations rise and fall on how well they're rolled out in the organization. So you want to be planning from the beginning of how you are going to start using this new platform start evolving this new capability. So that includes who's using it, you know maybe you train a core group of users first, and then a wider group and then a wider group. And that actually gets my next point starting small, you know, who are the core users using it most regularly, who have the most, you know, kind of solid use cases and start there. And then you can use that to solidify your processes again, along the way you were saying here's how we're going to do this here's how we're going to do this. But then as that small core group of users is starting to use it they go oh actually it's more effective if we do x instead of why great update the documentation and now that's changed. So you're making it heard of enhancements along the way, you know, one of the pieces I really like to recommend in those projects as you identify your, you know, your project ambassadors or project champions or people who are really going to who are eager to get the benefit from a new capability and involve them early on make sure that their needs are heard. And then as you're planning your rollout, find ways to help them be ambassadors to others. So that could be, you know, a lunch and learn hey we've got this great new dam here's how I used it to, you know, speed up the time for creating emails for a campaign. And these are some things that I've learned. So socializing the capability is really important. Which dam should I get I'm not going to spend a ton of time on this. Again, at various price points a lot of the feature sets are fairly similar for a lot of organizations. You know we, we recommend something kind of in the middle tier, where you have a dedicated robust dam platform that can handle multiple file types. So if you're missioning specific so you can say hey this person sees these assets but this person doesn't really great for if you have contractors doing work for you, like how they can provide assets. The three examples in the middle, kind of get to that like it's a it's a dedicated platform it's robust it has good support. It has good onboarding is what a lot of organizations that we work with kind of need. The other direction to the left would be something that's more minimal and and also cheaper. So some people use box or Google Drive I'm sure many organizations on or many folks in this fall probably use Google Drive to some extent. And again that can be fine, depending on again who's using the system what you need it for. I'm not sure what your budget is maybe you can't afford a dedicated dam and you just need to know how to, you know, optimize Google Drive as a dam so there are minimal solutions. I would say that the more minimal you go the more the you know the fewer kind of advanced search features you're going to be able to have, and the more work your processes and governance are going to have to do. The the mid tier and above have a lot of things about managing all of your users and managing their permission levels and version control and and taxonomy being able to find things in lots of different ways that a minimal systems just not going to let you do and enterprise really gets into, do you have a lot of different technical platforms with a lot of assets that you need to integrate really well so again a lot of these are primarily used by businesses that are, you know, have offices around the world and are dealing with tons of you know millions of assets and connecting them in a really tightly in a really tight way. And again, it, it'll, it'll vary based on the organization and what your needs are, but this is kind of a spectrum of what you can look at. All right. Where's the dam JPEG searching and taxonomy so I really love to focus on this part of the conversation because it gets to the heart of what the, what the dam is for what what's the damn point what's, what's all this damn talk about. It's about finding things, finding stuff that your organization has so that you can do things with it, and a key part of, you know, selecting and then organizing your assets and writing processes around them is really understanding what people are looking for. So I am reminded of this, the scene from the first matrix movie, where they're about to go into battle and they say we need guns, we need lots of guns, and then just this, you get the swoosh of racks and racks and racks of guns which is I guess America these days but whatever. The point is, you need things right and then you get a lot of things and you want to find that the import and taxonomy is the thing that allows you to do that. So what we mean by a dam taxonomy here is a classification system that lets you categorize and organize your assets so that they can be found and use through searching and filtering. So what do we mean by that. Okay, another, another way of thinking about this is, you know, taxonomy is kind of a technical term. Other terms for it can be categories or groups or labels or tags or lists, basically how how things are organized. So one of the things you can do to find taxonomies is you look through your website information architecture. Probably that is based on some sort of taxonomy maybe you focus on different issues and each of those issues is a term in a taxonomy. So there are a lot of ways that you can identify what taxonomies you're using. And a great way to do that is to really, really get in there with again the people that are looking for assets in your system in the first place and asking them what they're looking for. So this is an exercise that that you can do. And I think we'll take just a second you can do this on your own. But again thinking through, you know, the, the whole point of a NASA management platforming process is to be able to find things so you can do things. So think about your, your use cases your direct use cases and fill this out. So in order to create blank. Right, so think of the what you would use a damn for in order to create a particular thing I need to find what I need to find an image I need to find a video. Okay. You're probably going to want to be more specific than that, or you'd like to be. You want your system to help you be more specific. So maybe in order to create a new campaign landing page about climate change. You want to find video that includes one of our partners and is sponsored by a particular partner that is about climate change and is recent. So it's, you know, was made within the past year. So I'll pause there for just a second. So you can think of a use case for yourself. Exercise is something that you can do yourself and that you can do with your teams that people who are going to be using the dam and this is really at the core of making sure that your assets are well structured, because they should be well structured so people can use them. So I'll pause there for just a second. And if anyone wants to put their use case in chat. That would be awesome. We can see what people are wanting to use a dam for. And also if there are any questions about that exercise, feel free to ask in chat. All right, does anyone have any examples of searching use cases. So you can put them in chat and if not feel free to put in chat as well that there's just the types of things that you are frequently looking for in your dam. Or in the absence of a dam, the types of things you're looking for regularly that you think a dam could help with. Awesome. Great. So I see some, I see some good examples coming in. Thank you. Kelly Davis has one in order to create a case to report I need to find relevant images and approved content. That's great. That's a that's a great case use case, because it's, you know, I'm going to create a particular type of content. I need to find relevant images. And so the relevant piece is where we would dig in and say okay what what is relevant. So it's relevant maybe because of, you know, the person who sponsored the report, or it's relevant because of the location of the case study, or it's relevant because it covers one of our main topic areas, or it covers a particular grant management area. So that that I'm honing in on that keyword of relevance, because that really helps you unpack your taxonomy. So I'm looking for to create a report on a case study. What are the types of images that I need to need to be relevant, what is relevant within your organization. And then the other piece of that approved content is great. And that's another thing that would be considered kind of metadata around an asset, you know, is this approved yes or no, or what part of the approval process is it in doesn't need to be reviewed. So those pieces about kind of actually managing the assets, proving them reviewing them putting them into kind of periodic review cycle so you can say hey is this logo updated is this deck updated doesn't need to be updated. Those are types of things that you're that should be handled partly through your governance and documentation, but the better your dam is the more it'll help you do those things. Google Drive and box don't have as many capabilities about saying hey this asset is approved for this asset needs to be reviewed. A good dam will let you do those those kinds of things. Someone says that they need to manage legal arrangements across the board across the organization. Great. We like legal agreements that's fantastic. That's another use case where again maybe that's a very small sliver of your organization needs to see that. So it's not something that is ever going to go up on the website, or even to even to the communications or marketing team, but it's in one, one place for the legal team that then they can reference and allow some others to see. So again, it's not just, you know, it's not just digital assets. So, so, yeah, more about organizing all assets, not just digital images, all of these concepts apply. So again, thinking through, you know, what are people trying to look for and what are what are the terms, how do they think about the types of things they're looking for is the place to start. And, you know, a lot of the same principles apply so a legal agreement, you have that tagged as for review, you know, or what what is the, what is the stage of a process that the particular asset is in. Who should be able to see it and when and how and under what conditions, you know, maybe you have, you know, people that you want their permissions to expire after a certain amount of time. Particularly when you're dealing with stuff that's, you know, of a sensitive nature, you want to be able to have visibility and control over who sees what and when. There's another example create polling reports need to find our infographics from previous reports for comparison. Absolutely so basically being able to say hey I want infographics, and that's a type right and that's a taxonomy so we have a type of images their infographics that's the type. When was the last used, or we have here a possible taxonomy number of uses or date. So these are all things that you can then put in the system to make sure that it tracks so you can look up an infographic and say hey, we've used this three times in in our last three reports. And then you can say do we want to use it again do we want to update it. So you can have a lot of that rich context around your assets. And I think that that phrase rich context is really what you're getting more of what that kind of mid tier and above dam solution you're getting a lot more context around the asset that is either baked into the system or you can easily add to the system. You know, where was it created, who created it, what's the orientation, you know for for visual assets this is often really important hey for for a particular section of a web page we need a horizontal asset that is a certain size. Right, that is, that is valuable taxonomy and metadata information that that you can put in the system so that people can find those things faster, and they're not having to go through a font folder that says website images. Okay, another example in order to build a social calendar I need to identify specific images to support posts. Some are internal some come from partners and some are bought obtained online and the proper attribution. Awesome. Thank you. Thank you Judy that is a fantastically rich use case. So that's sort of the, the, the end goal and what are all the posts that are going to go into the social calendar, and then figuring out what the images are. So, being able to look at particular images and say, Okay, we have images from people in internal teams we have some images that are coming from partners, we have somewhere that we bought and need attribution. So that's all things that you can bake into your asset management platform so you can have as part of any asset, you can say is from a partner, yes or no. If so, what, which partner is it from. So then you can say, Hey, I just want to see images that are from a particular partner, or that are from, you know, from a particular, you know, particular source for example. And from it you can kind of what we're getting to is like the more of this you bake into the system, the more you can do really advanced searches and filters and say hey I want to find all images that are in a square aspect ratio that were taken within the last year that have been approved for use. And boom, then you have your list and then you can clearly see okay, these are ones that need attribution, right because they will say, you know, associate with the asset needs attribution. You know, partner consult with partner before reusing something like that. So the more specific you can get with those use cases, the more you can, you can start to build out that that taxonomy model, again, which is all, it's all ultimately built to help you do your work better, and more efficiently. I think that there. All right, so I'm going to go to. All right, we have a questionnaire. Answer the damn questionnaire. This is something that we have put together that you can fill out on your own you don't need to send this back to us, you can if you like. But as you are thinking about your journey with asset management where you are. These are some of the key questions you need to be considering. So what do you what are you ultimately trying to achieve with with asset management in the organization. You know, then get into the nitty gritty is like, where's everything stored, a huge part of it is just figuring out where everything is or might be storage. That's that's important maybe you already know like we've got this much space on a roll drive we need this much. That's something you can figure out. How many users need to manage the dam and be able to search. That's a key part because a lot of work, a lot of vendors will need to have a number of users. So some combination of storage space and number of users. You might have, if you're a smaller team you might have one or two people that actually need to have a user seat in order to manage the system, but you need to be able to say, Hey, we have 30 people that just need to be able to come in and search for assets, and those can be teared out differently depending on depending on the platform. So that's a big degree to you already have governance. We've talked about that and again, even if you say hey we don't have much governance, just documenting what you think you know, or where where things might be can be a really good start. Oh yes and thank you Mickey we also have a, if you wanted to fill out the questionnaire in an online survey we've got that up as well there's a link and chat. I'll provide additional links as well. Thinking about again that taxonomy and any kind of advanced features that you might have. So I think with that, I'm going to pause and see if there are any questions. Okay, Bridget says I think my team has an issue waiting through all the docs that are often titled similarly. Yep, especially when many are years old and or have updated versions, as well we recently keep coming up needing to know who took photos that we have stored. All, all kind of very common and very frustrating issues that they dam a dam again combined with good governance can help you solve. You know so I talked to before about like Google Drive versus some of these other systems. Google Drive you can do some degree of this if you say, here's the naming convention, everyone has to follow it. Like if you are naming a document title it this way. That is governance. That kind of governance can be hard to enforce, you know, or you have to really make a habit of enforcing the governance. I mean it's good practice anyway but that's, that's a common challenge. Then Google you can kind of like sort by date, last edited owned etc. Everyone seems to have their own system. Absolutely. And that that's the perennial struggle within organizations and systems. But that is, again, when you when you go to something like a dedicated dam you can say, you know, who took the photo, like that's a part of your taxonomy, and then you have a list of 10 staff members in the dam. And you can say, Oh, Adam took these 20 photos, and Adam as an object in the taxonomy as a user can be staff or consultant or former staff, or partner. So you can really get granular and say hey we want to find, you know, any asset that Adam produced. So, even if I leave in five years if your dam set up and you say hey, remember that really awesome guy Adam he took this great picture of a chicken. If you want to find it, you can go back in the dam and say, Okay, Adam, you know, pictures, pictures from Adam or pictures of chickens. That dam enables you to do that. So one issue we have is having the waiver. Yep, to use the photos organized to match the photos we want to use. Yeah, absolutely. So that's something where when you have a structure dam, this would be really hard to do I think in Google Drive. Again, could do it, but it becomes much easier if you have something that says, you know, like for a particular photo or an asset type you can say requires waiver yes or no. And then maybe a sub thing would be has waiver, yes or no, or waiver needs to update. And then those files can link together and so that you can then you can run a search and say, you know, for, yeah, photos, photos without waivers. And then you can go okay, these are we know we need waivers for these photos so let's go ahead and get them proactively. You know, if you've gone out in the field or you've had a vendor that's gone field and taken a bunch of photos as part of their upload process, you can define really clear processes to say, when you upload photos, put them in this folder with this naming convention, put the waiver with them, or put the waiver in a separate folder and then you can have automations that when they upload those those will sync up together. There are a lot of different ways to do that based on or depending on the vendor in question, but that is definitely a frequent use case of assets with some sort of waiver or permission or release or something that, yeah, there are tools in place and a lot of the dams that can do that. Okay. Well I think with that I'm going to go to my right screen. Thank you so much for for for joining us. I just want to throw this up there for folks who might be needing to be heading out. I can answer a few more questions but you know generally you can go to our website person cco.com. We have a lot of great content that can help you with this and other challenges related to your engagement architecture. You know, pretty much if it touches us on how organizations interact with your audiences. We can talk with you about it and help you with it. We have a lot of content articles videos, a fantastic podcast and events like these. So, please don't be hesitant about reaching out. And I thank you for your time.