Streamlining Creative Workflows with Workfront + Adobe Experience Manager

Transcript

Hey everyone, I’m Adam Fertz from Latepoint. I’m thrilled to be here today to walk you through how integrating Adobe Workfront and AM assets can power a more efficient, governed, and scalable content operation. Today’s session is all about moving from request to reuse and how we can streamline that journey.

Here’s what we’re going to cover today. We’ll start with a quick look at why this integration matters, and then we’re going to walk through the key benefits, the Adobe Gen Studio vision, and what it takes to prepare for a successful rollout. I’ll show a live demo of the connector in action, and we’ll even get extra nerdy and walk through the configuration steps. Lastly, we’ll wrap with a real-world case study and some key takeaways. As a content supply chain leader at LeadPoint, I work with some of the world’s biggest brands to solve real-world marketing operations challenges using the Adobe ecosystem. I live in Salt Lake City, and when I’m not geeking out over metadata, Workfront, or any of the other Adobe tools, you’ll likely find me outside rock climbing, snowboarding, gardening, or camping. For those of you that have been with Workfront since the days of AppTask, you’ll know LeadPoint has the OG implementation partner for Workfront. LeadPoint has been helping customers leverage the full power of Workfront from the very beginning. At LeadPoint, we see Workfront as the central nervous system for Adobe, connecting operational data and strategy to and providing a unified platform for managing a work across the entire organization.

Let’s start with the reality many marketers and creative teams face. Creative capacity is limited, campaign visibility is fragmented, and content reuse is more difficult than it should be. God knows how hard it was for me this morning trying to find that PowerPoint slide I created last week. There’s a lot of demand, but not enough structure to meet it efficiently. This is what Adobe refers to as the content supply chain challenge.

In today’s presentation, I won’t be covering the full set of solution aimed at solving the content supply chain challenge, but I will be focused on what I believe to be the foundational solutions, Workfront and AEM assets. By connecting Workfront with AEM, we start solving these pain points. Requesting campaign data caption Workfront can drive asset metadata, folder structures, and even automated workflows in AEM. It becomes easier to search, reuse, and govern assets when you have structured data flowing between the tools.

With structured data and taxonomy flowing between Workfront and AEM, you can now begin connecting this data to other parts of the larger of the ecosystem. For example, connecting operational data, like how much does it cost to produce a piece of content, to performance data like conversion rates from experiences in your web channels. This is the stuff I get really excited about. Finally, some hard data tell us that the content we’re producing is actually worth the time, money, and effort. The benefits of the native integration between Workfront and AEM assets are not just theoretical. They’re tangible and immediate. First, you’re going to see faster time to market. When requests, reviews, and approvals are all managed within Workfront and assets automatically flow into AEM, your teams can move significantly faster. You also eliminate a lot of manual steps. No more copy and pasting metadata, manually uploading files, or digging through folders to find the right version. We all know how it goes with version 1, version 2. No, really, this is the final version. With the integration, everything is mapped out and automated. On top of that, you’re getting more consistent metadata, which improves asset findability, enables better governance, and fuels personalization at scale. Speaking of governance, the integration supports stronger oversight and compliance by enforcing naming conventions, folder structures, and approval workflows. All of this contributes to something bigger. A true content supply chain or strategy, work, and assets are connected, giving teams the visibility, control, and scalability they need to deliver great content at scale. From improved team collaboration to stronger reporting and asset governance, these outcomes are what make the native integration so powerful.

This is how we help teams scale content without scaling chaos. Teams are no longer stuck managing approval workflows via e-mail or tracking asset progress and disconnected spreadsheets. What you’ll get is automated folder creation in AEM based on project data from Workfront. Teams aren’t wasting time organizing folders manually. Streamline approvals that move faster and leave an audit trail. Improve brand consistency because metadata and usage policies travel with the asset from the moment it’s requested. Better reporting and insights on how content is created, approved, and activated. Security and governance baked in, which is critical when scaling content production. Ultimately, this integration helps organizations move faster, while staying in control, controlling more content with less chaos. Adobe’s Gen Studio vision brings together planning, production, activation, and measurement across multiple tools. It’s designed to power the full content supply chain, from campaign brief to cross-channel delivery, under a unified model. At the foundation, you have tools like Workfront and AEM. Workfront manages your intake, workflows, and approvals, while AEM handles asset production, and activation. On top of that, you have creative tools like Creative Cloud, Express, Firefly, Frame.io, feeding all of that content into the system. Finally, you’re able to measure impact through insights from Adobe Analytics and Experience Platform.

Gen Studio helps unify these disconnected tools, and teams, and data across your entire enterprise. The native Workfront and AEM integration plays a crucial role in this architecture by aligning work management with asset management, bringing structure, traceability, and efficiency to every stage of the content life cycle. But to make this successful, preparation is key. It’s not just about the tech. You need a metadata strategy, a governance plan, a clear rollout strategy for change management, training, and ongoing maintenance. This work ensures the integration is scalable and sustainable. If you haven’t already reached out to Adobe to ensure your Workfront environment is migrated to the Adobe Admin Console for user access and provisioning, reach out as soon as possible. Define user provisioning and access strategies early, ensuring the right people have the right access, avoiding delays later on in the process. Document your governance model, who owns the metadata, who updates it, and the workflow configurations, who’s responsible for those. This clarity supports long-term stability, establish clear business requirements, align across teams on what success looks like, and how Workfront custom forms will map to AEM metadata. Design a scalable folder structure that aligns with your campaigns, teams, and business units, so that content can be organized and retrieved intuitively. Plan your metadata and taxonomy mapping. This ensures that what gets captured in Workfront lives on in AEM in a meaningful way. Test thoroughly and train regularly. A thoughtful rollout and change management strategy will keep your integration on track and your teams confident. Now that we’ve covered the why and the benefits, let’s get to the fun stuff. I’m going to walk you through what this actually looks like in action. In this demo, I’m going to show you an end-to-end flow for a simple creative request. Something really simple like creating a campaign image for your social channels. We’ll start with the request being submitted in Workfront, using a custom form in a request queue, then follow that project through key tasks and approvals. Once the asset is ready, we’ll publish it directly to AEM assets via the link folder with all of the metadata intact, thanks to the native connector.

The goal here is to show you how teams can move from request to reuse with fewer handoffs, stronger governance, and total visibility. Without relying on swivel chair work or custom code, let’s take a look now.

We’re going to start with the creative request submitted in Workfront. All of you are going to be familiar with the request queue. I’m not going to spend much time here. But here, we’re going to go through and just open a simple marketing request. We’re just going to stick with a single asset request now rather than a larger integrated campaign. I’ll fill out some of the details in the form, like the subject. I’m going to put in a brief description of the image that I’m going to be creating. This is actually an image of my dog using Adobe Firefly.

We’re going to actually select an image asset and what regions we’re going to publish the social posts to. Then we’ll go through and select our audiences, add some details around the request of delivery date, languages, and channels. I’m doing all of this to illustrate that the metadata that we capture here in the request is metadata that we can collect in AM assets as metadata. Think of this as a snowball effect, whereas I’m gathering metadata from the request, it’s then moving along into the project once the request has been converted. Then once the creative uploads their final approved assets into AM, we’ll then have that asset available with all the relevant metadata that we’ve collected all the way from request down to delivery into AM. Here I’m going to go and convert this request into a project playing the role of the project manager or traffic coordinator. I’m going to select a campaign template for this specific project. This template is actually going to contain some additional configuration details for how the folder structure should get created. We’ll actually walk through that in a later demonstration on how to configure the connector. But here I’m just verifying that we have all the relevant information that I have a portfolio and program selected, because that’s what I’m going to use to build my folder structure automatically in AM when the project gets converted.

Here we go, we have a converted project. I’m going to go through and just basic task list, I’ll assign myself even though I’m no creative to the creative task, and then we’ll move this project to active.

You’ll have to pretend with me for a moment. You-all are familiar with these steps. We’re going to go from a active project and then I’m going to go and upload some already final approved assets directly into the link folder that got created. Again, based on that native connector, when the project was created, folder automatically got created. We actually use the portfolio name, the program name, and the project name to create that folder structure. Then I created a subfolders underneath that as well. We’ll actually walk through in a later demonstration how we can define what folders are created.

Here as I upload these assets into the linked folder, I’m actually pushing these assets directly into AM assets. While these assets are being pushed to AM, they’re actually collecting those metadata fields that we defined in the request form that then flowed down into the project once we converted it. All of that data that we used to have to pass over using spreadsheets or we have the digital asset manager in AM, go and add that metadata manually. We now actually can collect all that metadata automatically through the connector and push it into AM. Here, we’re going to see if the assets have all uploaded. One thing to note here is that this is designed to handle lots of assets at once. We drag many assets at a single time and those will be safely pushed to AM along with any of the relevant metadata. Next, we’re going to jump into AM. What you see on my screen here is AM assets. As I go through the folder structure, you’ll actually see that portfolio, the project year, the program, and that structure that we defined in Workfront. Then we can go and look at the final files folder and see all the assets that were uploaded. Here’s all those assets that I pushed from AM and now I actually can look at the metadata that we were pushing over as well. I have some Workfront project metadata, including the project ID and the project name, as well as some asset level metadata that I collected. We gathered that information at the request level.

Again, it’s important to keep all this metadata because once the assets in AM, we now have all these metadata properties that we collected from the Workfront custom forms as searchable data points within making a lot easier to find the assets that we’re looking for and even activating those assets across other channels. You’ll see here in Workfront that I can also keep these metadata properties in sync. If I go into Workfront and make a change to say, will the region filled or any of the other fields, I can then ensure that those changes are being updated in AM assets as well. There’s a configuration that we’ll walk through in the next demonstration about how we can ensure that the metadata properties are kept in the two systems. Again, a really powerful, flexible, and intuitive tool to be able to standardize and streamline the integration between Workfront and AM and ensure that all of our assets and folders are structured accordingly.

Now that we’ve seen how the flow works from a user’s perspective, let’s go behind the scenes and look at how easy it is to set up this integration using the native connector. We’re going to start with the setup menu in Workfront. Specifically, the document section where the AM native connector lives. From there, I’ll walk you through how to select the appropriate AM environment to connect with your AM assets instance, then how to map metadata fields for your Workfront custom forums directly into AM asset metadata properties. Then we’ll configure link folders that automatically create just like we saw in the previous demonstration in AM. Then we’ll assign this configuration to a Workfront project template. It runs seamlessly in the background every time you use to convert a request to a project. I’m also going to show you how to modify the configuration on the fly to support new use cases. Set up conditional logic to create multiple link folders based on metadata or the project type, and even rename folders dynamically to match naming conventions or brand requirements.

The beauty of this native integration is that it’s both powerful and accessible. No code, no middleware, just smart configuration that aligns with your governance model.

Let’s jump in. Here’s a quick look at the actual configuration behind the scenes. Again, we’re going to go to that setup menu first. If you’re a Workfront system admin, you’ll be familiar with.

Then we’re going to go down to that document section over in the left panel. In the document section, we’re going to see that experience manager assets menu. This is where the native integration actually lives. I can go and create a new integration. Assuming that I am also a system administrator within the AEM assets environment, I’ll have it as an option to select in my drop-down. You’ll see here I have a Leap Point AEM assets environment that I can select. This connects Workfront to the AEM assets repository. Next, I’m going through and I’m actually going to map the metadata properties in AEM as well. Here I can actually go and search any of Workfront’s custom form fields across any of Workfront’s object types, and then map those to specific AEM metadata properties, and keep those data fields in sync. Again, you’ll need to make sure that any Workfront fields that you have, there’s a corresponding field in your AEM assets metadata schemas as well. You won’t be able to link these unless you’re both a system admin in AEM and Workfront. As we set up these different fields here, these fields then can be set up to have an automatic sync. After I add these last two fields, we’re actually going to go in and we’re going to set up the object sync and this allows any updates that happen in Workfront to actually see down into AEM as well. If I change a custom form field in Workfront, then that metadata schema in AEM will automatically get updated.

Next, I’m going to do the create project link folder. These link folders, that’s what you saw in the previous demonstration when I created the project and went to the document section, and there was an AEM folder that automatically was created. Here I can define my parent or my root folder. Once I’ve defined my root folder, here I’m going to do the project year.

Then I can go through and define those child folders underneath the root folder. Then I can select the year, and then let’s say we’ll create the portfolio name. Whatever portfolio this project exists under, we’ll have a portfolio folder. Then underneath that folder, we can create a program folder. We can map this again automatically to that object data. Then we can actually do a project folder. It’s going to create a folder based on the project name.

Then underneath all of that, we can add as many folders as we like. I’m just going to use static folders using text and say, a final assets or a final files folder, and then we can do a source files folder. This becomes helpful for creatives that need to upload any supporting assets or source files to go along those final files as well. Those will be done just with the text field.

Once I’ve added that here, I have some options where I could either publish the assets automatically, either to a brand portal instance or even to an AEM site or asset share common instance.

Once I’ve saved the integration, the next step is going to go into the templates. That’s the global configuration that is required before I can do any automated link folder creation in the templates themselves. Now I’m going to go and find a template that I’ve already created for this demonstration. Then we’ll go into the experience manager configuration and set up those automated rules that allow that project link folder to get created automatically, allowing the creatives to upload their assets, their approved assets into AEM. Here I can select the global integration that we just configured. Again, I’m in the project template. Then I can go through and I can actually modify the rules for the linked folders and how they should get created over here. I can look at specific work front fields and create statements to say, create this folder structure if work front object data equals X. A lot of flexibility here and I find this really useful when working with multiple business lines or multiple marketing teams that may want to have a slightly different folder structure created in the dam. This allows you to actually set up those rules within the project templates themselves. Again, really intuitive solution here to define those folders and to set those up on different project templates. You may have the need to create multiple project templates in order to support this as well. Again, really flexible, intuitive solution to set up, again, without any code or middleware in between.

I hope you found those useful. But again, I want to point out that the technical side of this isn’t going to get you all the way.

What you need is alignment across people, process, and technology. That means bringing in cross-functional teams, standardizing intake and workflows, and building your metadata and a folder strategy with long-term scale in mind. I’m going to apologize ahead of time for the secrecy here, but it was important that we predicted our client’s name. I really hope all of you can appreciate that. Let’s just say that you’ll probably figure out who I’m talking about in this case study with three guesses or less. This organization was able to reduce request time by 65 percent, and eliminated 80 percent of spreadsheet-based tracking by integrating Workfront and AM. They saved over 16,000 hours of work and drastically improved visibility. This is what success looks like when people, process, and platforms align. Gone are the days of passing manual spreadsheets across to your digital asset managers to ensure that metadata in the dam is robust. Now we can do that automatically all the way from requests, to project, to final approved assets in AM. We can even keep that data in sync using the sync object function within the native connector. I knew I threw a lot of information at you in today’s presentation, but I really hope you found it useful. If there’s four things I hope you remember as you go back and share with your teammates, this is it. Measure twice and cut once. Don’t rush into configuration. Take time to align on taxonomy, naming conventions, workflows, and those business rules so that what you build is scalable and sustainable.

Align your people, process, and governance early. The integration only works when everyone is on the same page. Ensure clear ownership, process consistency, get stakeholder buy-in, and plan for ongoing support. Successful roll-outs require champions across departments. Engage early and often to make sure all voices are heard and needs are addressed.

Launch is just the beginning. Plan for training, documentation, and regular optimization to keep your integration running smoothly and delivering long-term value. When you get these fundamentals right, the native integration becomes a game changer for scaling content operations.

Thanks for sticking with me today. I’d love to hear your questions and what challenges you’re facing in your work for an environment today. We can get into some of the technical questions, talk more about the integration, or where to begin. Let’s dig in. Adam, way to bring the GrowTrack home. So excited to have you here.

Excited to be here. Thanks, Cynthia. Yeah. You’ve been around the block a few times with all the different iterations of Workfront plus AEM.

But one of the things we were talking about is you know that these integrations are more than just connecting systems. I’d like to start with sharing your experiences, recommendations, all of that on building relationships with stakeholders for success.

Yes. Fantastic. I love that question. I appreciate you asking it because I think this is critical. I mean, when we talk about connecting Workfront with AEM assets, I think obviously as many teams can imagine, this means talking with teams across different functions. You have creatives, you’re working with project management teams, you may be working with development teams to develop digital experiences for the website. There’s so many pieces to this. So I think it’s really important that when we’re thinking about connecting these two tools, it’s much more than just a technical integration, like we saw in the demo, but a lot of this is trying to help stakeholders understand the value of the tool in order to get their buy-in so that they’re sold on that vision. So a big part of the work that we do with customers when we’re integrating is help show that vision end-to-end, similar to what we did in the demo today, and help them understand that value. So whenever I’m looking to get buy-in from creative stakeholders, let’s say where they may have not used a project management tool before and they may be stuck in their old ways of sending assets via e-mail, or via Teams, or Slack, and to get review and approvals, actually showing how it can save them time so that they can focus on the work that they want to do. I’m going to steal a quote from Richard Whitehead who often says, I want you to work in a work front, but I think that’s the value that we want to show all our stakeholders is that this is not a tool that we’re looking to add complexity and make your everyday harder and harder. It’s really a matter of, can we show you the things that you need to work on so that you can do your work more efficiently, and that we have all the details that we need and all the data in the system that we’re creating that operational system of record and giving all of those data points back. I think that’s the biggest part is that whenever I’m discussing this with stakeholders, most people understand that and that resonates with a lot of people is showing them the value and then getting them to be your champions. Then they can help you and as you gain more people who understand that value, change becomes a lot easier and adoption becomes a lot easier in the organization.

That’s amazing advice.

I want to talk about just time back. I actually love project templates.

I just want to talk about what are your best practices. I know something that you talk about for setting up those project templates to take advantage of the integration in the best way. That goes to a lot of the questions that are in the chat. So I think that’s going to get us a good start. Yeah, absolutely. In fact, this is one of the evolutions of the tool that I’ve become a really big fan of is the fact that the ability to take a project template as you saw, and then add some additional condition statements for the connection to AM assets. Obviously, I imagine most folks on the call that are familiar with Workfront, know the value of the core features of a project template. Being able to standardize those task list for common repeatable tasks and how important that can be. Setting up from a resourcing standpoint and from plant work, and just being able to quickly execute any of the work that comes in through the RQs. I think project templates are invaluable. But being able to think about how that integrates with AM, one of the things that I found really useful is that let’s say you’re working in an organization with multiple brands. You may have project templates for a specific deliverable type. When you have the ability to customize the connector at that project template level, that now gives you more flexibility to maintain a more organized and streamlined folder structure within your AM assets environment. So as you saw in the demonstration, I can have a project template, let’s say created for a specific brand, not only a specific asset type. If I’m creating content for a digital display ad, I can have that template assigned to a specific brand, and then that can drive where the folder gets created in my AM. Again, I think one thing to highlight here is not only this ability with the project templates to provide that flexibility, I think it points out this goal of really having a strong taxonomy, and really thinking about not only how your portfolios, programs, and project templates are being used in Workfront, but thinking about how that will actually translate into folder structures in AM, and the flexibility you have around that. So on top of being able to use that project template to define where the folder gets created in AM, and then also going as far as in some more complex use cases, assigning a specific custom form to create subfolders, and being able to go in there and say based on a value selected in this project custom form, create X subfolder. So I think it’s important with all of this before implementation to really think about how that is tied to your global taxonomy across, all the way from planning workflow into pushing final approved assets into the dam and where those templates come into play.

You just set me up perfectly for the next question. I know you just talked about taxonomy structures, but what metadata fields, most valuable, where do you go to when you sync between Workfront and AM? Well, that’s a fantastic question. I’m glad you asked me today too, because I just came out of a workshop with a client around Workfront planning. I’m sure some of you have seen Workfront planning. If you haven’t, I highly recommend looking into it. But as we start thinking about taxonomies, it’s really important to think about all those different stages of the life cycle of creative assets or campaign assets that you’re developing. When I think of what are the most important ones, it really goes back to that initial stage of campaign planning. What are the key attributes that we need to begin collecting to tell that full story end to end? The reason I say this is that there is data at every stage of the life cycle that I see very valuable for that particular stage. On the execution side, there may be things like, what was the time from start date to finish? How long did it take us to build the assets? That can be incredibly helpful for the execution teams that are developing content within Workfront.

On the planning side, if you’re thinking more high-level top of funnel planning, there’s things like what brand and brand voice, and what channel are we going to be targeting, and what is our messaging and our strategy at that level? I think it really requires that you actually look at those specific fields. Just to throw out a couple of examples here, depending on your industry or depending on your products and your services offering and what your organization does, it’s really thinking about those core fields at each stage, from planning, workflow, execution into even activation and measurement.

I’ll often see things like the campaign start date, being able to know that because I think that’s important as assets are going from campaign start date and campaign end date. I think that’s important as assets are flowing from Workfront into AM, because then that can trigger further automation on AM to say, publish an asset from your brand library so that users aren’t using an asset that’s no longer approved for campaign, to be used in a current campaign. I think those start and end dates for campaigns are critical, and then alignment to your brands becomes really helpful in terms of storing and organizing your assets and making those easy to find in your repositories. Those are just a couple of fields, but again, I could list a lot of my favorites, but I think the important thing is to think about the key fields at each of those different stages. I think you’re leading me down this, like the larger question. We have a bunch of questions, and I’m going to give you the example and then it’ll open up a larger conversation. But how do you handle, what are your tips for assigning more complex items? They gave examples of terms of use, talent usage rights, brand portal groups. But to me, what you’re talking about is this opening up your mind to what is possible with it, and what are the things that you love? There’s so many options. I’m going to let you. Right. Yeah. No, I think that’s great. I think you’ve caught on to what I’m getting at here is that I think there’s always a simple technical answer to a lot of these questions. I encourage anybody that’s looking at integrating these tools and understanding what’s possible within the product and what you can do natively within the product as you saw in my demonstration, I think it’s important for everybody to think more philosophically about how and why should we do this. Or a lot of the answers to these questions, I’m going to tend to give that spin to them because things like terms of use or digital rights management that would typically reside within a AM assets within your DM, it’s understanding which of each of these systems should be the source of truth for that data. We often talk about source of truth and how important a centralized repository is for assets. It’s not necessarily always the case that all of the metadata that ends up in AM alongside the AM is the source of truth for that asset. For example, if I’m collecting operational data, the time that it takes to develop assets within Workfront, who worked on it, any of those fields that you can capture in Workfront that are being populated in the request and then flow down to the project and then along into the asset in AM, Workfront is the source of truth there. But some of the fields that you mentioned as it relates to AM assets, terms of use, digital rights management, those are more traditionally sources of truth that should reside in AM. So I think it’s really important to understand each data point and where it should reside. That can help inform the bidirectionality of metadata and where is the metadata originating, where is the source of truth. So I wouldn’t recommend anybody if it’s determined that your digital asset manager is going to own the rights management in AM directly that we’re updating that in Workfront. So it becomes AM is the source of truth and then there are methods in which we can send that data back if that’s not through the native connector, through Workfront Fusion or more complex integrations. So yeah, I think that there is an ability to do that with some fields, but more importantly, it’s understanding where should the data reside and which system has control or ownership of said data. And we do have some technical questions and I think they’re all along the same theme, literally what you just said, but I just want to address them. So it’s basically like if something is changed in Workfront, will it be reflected in AM? If I update a custom form field in Workfront, will it be updated? We’re getting a lot of those questions and again, I’m going to let you address it. I know you just did. I mean, the short answer is yes. What’s fantastic about the native connector is that ability to synchronize data from Workfront to AM is available through the platform, right? If I wanted to map those at the document level and Workfront to the asset, we can do that with the native connector, but then it becomes more of this broader conversation around what data should we, right? Just because it’s possible, is that something that we should be doing? I think that’s probably the more important thing to think about, but yes, technically, absolutely. I think I’ll make one distinction here because when it comes to some of the data that is being synchronized from Workfront into AM assets, there’s one thing to just keep in mind. The folder creation piece that I showed in the demonstration, there are certain fields in AM where let’s say that the folder gets created upon project creation and Workfront in AM. Then you go and update the name. There may, it may require some custom integration work or custom development to update the name of that folder after it’s been changed, but there’s also workarounds that allow you to map, say, the project name field in the custom form to that document, right? Although the folder may not change in AM, we can keep the name of the folder in AM in sync through other means. But there’s some nuances and things to just be aware of as you’re thinking about that. In your, when you’re implementing the tool today. But yeah, I think generally speaking, all those questions that you asked, completely technical possible.

Okay. So the last sort of big question, and I know we’re running, we’re getting close to time. Tell me your best, your favorite best ways to prepare for integration. Yeah. Yeah.

Well, I mean, it’s probably not going to surprise you based on everything that I just talked about today, right? So I think that technically speaking, there’s some simple things that you want to make sure you’re doing. So I’ll start with that. Technically with the native integration, you need to be on AM assets as a cloud service and you need to have your work front migrated into the Adobe admin console. I imagine most organizations have done that. If you haven’t, or if you don’t know what that means, I’m, I’m, you know, I would reach out to your Adobe rep and find out if that’s the case. If they’re both in the same Adobe admin console instance, then setting up the integration is possible. So I think that’s the first step technically.

And then when it comes down to, okay, well now how do we set this up? Obviously based on every other answer I’ve provided so far, you’re going to, you’re not going to be surprised when I say global taxonomy strategy and development, because I think that the value in the connector resides in that streamlined taxonomy from planning to workflow into, you know, the dam for activation in whatever channel, right? So the value in this tool is to be able to tie that full end to end life cycle together in order to do that, that requires a really good global taxonomy strategy. Your folder structure strategy, I think I bucket all of that into this global taxonomy work and the shared language across the systems, because it’s one thing to send all that data, but are you thinking about how it ends up in your reporting tools, right? What are the data that you’re collecting that will tell you how the assets performing and all these great things around, you know, ROI on your marketing content? So I think that’s the biggest step. So that comes into sort of my measure twice cut once recommendation is that it’s really important that you look at that data holistically.

Oh my God, this is like, we could probably talk for an hour, but we don’t have much time. Okay. So everyone, they watched your presentation, they did the Q&A, what do you want them to do? They’re going to go back to work. What do you want them to do? Yeah. If there’s one thing that I would ask you to go do to look at is to look at your taxonomies, look how your metadata is being used today, not only in Workfront in your custom forms, but also look at AM assets and then start raising that with more people on your team. How are we thinking about data? How are we thinking about these systems of records? Are we using Workfront merely as a project management tool? Are we looking at it more as this operational system of record? So I think that would be one thing I would recommend. Go back and talk to your teams, share these ideas with them, start thinking broader. Because I think you’re doing Workfront a disservice when you merely think of it as just this project management tool. It’s much more than that. Now you’re speaking my language. Adam, thank you so much for closing out the GrowTrack. You have inspired us to take advantage of Workfront integrations and think through those larger processes. So thank you so much for joining us today. Absolutely. Thank you so much for having me.