Measuring What Matters - How Schneider Electric Drives Workfront Efficiency with Fusion

Transcript

Welcome to our session. It’s Measuring What Matters, How Schneider Electric Drives Workfront Efficiency with Fusion. I’ve been talking about this session for a really long time. I’m very excited.

It’s a brilliant approach and I hope it inspires everybody. The question that you’re going to ask and you’re going to want to know, is this session being recorded? It absolutely is. We’ve got it recording two ways because you’re probably going to want to rewatch it. So we will get that out later today. I will say something about the slides and I know some people may come a little bit later, so I’ll just repeat it. Kimberly needs to get approval on those slides and once she does that, we will send those out. So I’ll send the recording. As soon as we get that, I’ll do a follow up. OK. Today’s agenda, we’re just doing the welcomes. Then we’re going to go through Kimberly’s presentation and then she said she’s willing to do a little bit of Q&A. So super stoked for that. Your scale team. This is your skill team. You’re not here for us. But if you ever need us, the easiest, fastest way to get us is CS at scale at Adobe dot com. Just send us an email and hey, if you’ve got a great story to tell, we would also love for you to do your own scale event. So just email. With that, our speaker, Kimberly Ray. Hello, welcome. I know we’ve been talking a while. Hello. Yes. I’m just going to take the ball here and I’ll share my screens. So let me know if you see everything OK here.

I do. It looks beautiful. OK, perfect. All right. So hello. I am Kimberly Ray. I am with Schneider Electric and a little about me. So I am originally from Massachusetts, but I’ve lived in Rhode Island now for 20 years.

I were just talking to Nicole and I were just talking about this. So I graduated from Salve Regina University, which is in Newport, Rhode Island, with a degree in interactive design. And I did a minor in photography and I did so I have an art degree. So this always surprises people sometimes because I didn’t have a full technical coding background as I go through this. I am a mom of two girls. I have a 10 year old daughter and I have an eight just turned eight on Sunday daughter here. And I basically live at the soccer field with them. The two of them are on two different travel club teams. And then they also do two other teams in the spring and the fall. And then they do additional guest spots on different teams. So if you can’t find me or I’m messaging you late at night, I’m probably at a soccer field with them and watching going there. The beach, living by the ocean. This is my happy place. And I absolutely love being able to drive within a few minutes to go to the beach here. And I am a big New England sports fan. So the Patriots are in season right now. We have the Celtics and then we also have the Bruins. But we also love the Red Sox. And I used to work at Fenway and it’s such a great stadium and historical place. So my work front application. So just a little history of how we’re using the tool and how long we’ve been using it. So we actually purchased at task that long ago in February of 2009. We deployed SSO in 2014 and then fusion was first purchased in April of 2020 with this very specific project in mind. And then shortly after we purchased fusion, that project went on hold due to life events in 2020. So our first fusion scenario did not launch until October of 2021. So over a year later. And then in 2023, we launched our first integration of fusion with another tool, our dam solution to pass data back and forth. And then from January 2022 to 2024, we I specifically launched 19 different scenarios with fusion and going back and forth here. We then ran into a roadblock of only having 20 solutions. So we kind of froze everything and we couldn’t really move forward. So that in February of 2024, we upgraded to the unlimited licenses so that we could have unlimited fusion scenarios and the ability to really just explode what we were working on and clear the queue of items here. And then this December, we started our pilot and our initial proof of concept of integrating with Airtable for some of our planning purposes here and going through. So we’ve started to integrate with other tools. And just so you don’t think I do this all by myself, because I wish I could.

I am the person within Schneider. So I’m the application manager within the creative studios. But then I also have a WSA package. So I have Sarah Myers is our work front system admin that helps me deploy and make the changes and was a huge part of this reporting area. And then I also have Steve Watts as an integration consultant who helps me with the fusion and helps me get through those pieces that I have here. And when I get stuck, I just kind of send to him and go through. We have 378 standard licenses in our instance, 150 light and we have just shy of 9000 contributor licenses that are in here today through single sign on that we’re managing in this process within here.

So let me go into a little bit of a deep dive on how we’re using fusion and I’m focusing solely on our creative studio process. They’re one of our more robust processes within here, but they’re not the only ones using work front.

So the green are our standard creative process, right? So we plan quarterly in advance. And we have a prioritization manager who takes all that information in this very robust Excel file, which is in the past, and fills in everything that we’re going to do for next quarter for our planned work. And we look at an 80% planned rate within here. We go through and get that information. And then we have our creative brief approval. We do our discovery meetings, we do concepting, we do pitching, then we go through and do our kind of design and share. And then at the very end, we have asset management into our damn solution.

So what we’ve been able to do is plug in how confusion work to make this process faster and seamless and going through. So we actually took in 2023 when we started to go through and launch, we took that quarterly planned process and we automated that in. And I’m going to go through the case study here shortly. We automate the quarterly plan process. We rename all of our projects with a specific unique part number, which is coincidentally the project reference number. And then we send out automatic reminders that those briefs are due. So today is December 3rd, and we actually just put in all of the projects for Q1 into the system. So we have projects that are scheduled to start all the way through March now of next year that will start to get reminders that your brief is due. We also automate when a brief is uploaded and notify our traffic managers. We have automations with how the project status has changed. So as tasks get closed out, the status changes on the project as it goes through.

And we also send automatic reminders to our stakeholders. We send an automated message of here’s the metadata that’s going to go with your asset when it goes into the damn solution. And then we take all this data and we export it into a CSV file that Tableau then consumes for some other larger items.

So this has taken a couple of years to get to this point for this group. But based off of this, the challenges that I had to solve were how can I show the value behind all these automations? Because these are really cool. But how do I show the value of what they’re actually doing? Because I know what they’re doing, but leadership doesn’t. And then how can I get budget for additional consulting hours? And how did I get budget for the unlimited fusion scenarios? Because that was an increase for us.

So I was able to put total hours saved associated with those different integrations or different automations. So specifically, the automatic reminder notification. So when we have our projects into the system for a quarter in advance, we have a date that they need to be briefing it into us for in order to keep on schedule.

And I’m going to go through the case study here shortly. But we were able to save 70 hours in 2023 when we launched it towards the end of 2023. For the full calendar year of 2024, we saved 148 hours of manual work for sending those reminder messages. And I was able to get some data around this and show, OK, well, this is something that we’re no longer manually having to send. It’s just automatically going. And we can spend our time on actually planning or actually looking at the capacity, looking at this information. So some are usually higher volume time savings than others. But then there’s smaller ones that are just little inconvenient things that we can save time for our designers or our writers and really help with them to be better engaged with the system itself and the tool itself. So how did I do this? Every single fusion scenario that I have running has the same two items within it. The first is I have a set variable and I set the scenario ID. The scenario ID is available in the URL of fusion when you’re in there. And I set that as a variable. Then at the very end of everything, I have a fusion data input that I put and I set the variable. I set the scenario ID. I put the execution ID and I put today’s timestamp. And where this goes is into the project and work front. So every single time fusion runs, those three data points are captured wherever they’re doing that within the system. And what that looks like is I have four different fields for each individual scenario that runs on one custom form here within and that’s on every project. Now, this custom form is not visible outside of the admin group. So it just kind of runs silently on the background for everybody. So I go through and I put here a I set the scenario ID. I set the execution ID. I put the last date. And then I also put it populates how many times this runs. So if this runs multiple times for me, this same one could run two, three, four times. This last item here is going to start counting up for me and it’s going to give me a count of every single time something touches there. And what this looks like. Is this. So we have, I think, eight different awaiting brief reminder notifications that we give out to our users and every single one. It’s part of the same exact scenario. As you can see here, the scenario ID is the same. But the execution ID changes and the date changes and then I’m counting up here how many times this touched. So I can start to see and then here on the bottom, I can see total briefing touch points on this specific project. And I can see that my project was seven times that this touch. So that would have been seven different times that our prioritization manager would have had to search for the project. Look at the date, post the message, tag the stakeholder and hit submit on here that she saved within this. And that to me is invaluable time. So finding that and having that same static message and sending that out within here. The best part of this is this runs automatically no matter what time zone you’re in. So we’ll go through that here.

What does this look like? So this is an example of a program that we did and we break all of our individual records down by specific items within here. So we can see how many presentations we had, the banners, the web banners, the social matrix, etc. And you can start to see total fusion touch points across those. So for this entire campaign or this entire program, we had 89 different fusion touch points for this program that a human didn’t have to manually go in and do something. And the totals don’t add up here because there are some other ones I’m mainly looking at here. Briefing and with stakeholder ones that we send out because those are the biggest and most time consuming items. We have some other smaller ones that run for this. We’re able to see here if this briefing touch points took us three minutes per project to go through and do this, you can then multiply that by how many times that touched the project and how many hours you would have spent going through here.

So this is our case study for the quarterly planned projects. So the objective for this specific scenario in fusion was we need to reduce time manually entering our projects. So we would create a project, we would attach a template, enter all the custom data, and then we would rename the project with our very specific naming convention, which is 998 dash and then the reference number for that specific project record.

The before really was that the business was entering plans into an Excel file with standard data, and then the prioritization manager was manually copying that information and creating the project records in Workfront.

We do this quarterly and it was taking her about 24 hours to actually enter in the records, anywhere from 150 to 200 projects for the quarter. And these are for full campaigns. Then she was spending about eight hours a week going through and checking all those projects on the quarterly to see when their due date was due and send out the reminder emails.

So the results here for us were decreased manual time entering of those. So it’s a global team effort. Our prioritization manager is in Australia.

I’m in the US, so she finishes and gets that CSV file all set. She drops it into a project for me and she goes to sleep. I go through, I run the automation, and then when she wakes up the next morning, all the projects are in there for her to start resourcing.

And we have these, we call them Miranda bot because it’s really running as Miranda posting these in. It sends it out at 9 a.m. every morning, whether she’s working or not. So the best part of this is she could go out on holiday for two weeks and her Miranda bot messages are still running in the back end and it’s still happening and we don’t actually have to have coverage for her on this.

So for Q3 2025, we uploaded 178 projects in nine minutes using Fusion. And I was able to quantify that by looking at how many times that went in. You also can see that in 2025 through the first half of the year, so through July, the Miranda bot automated messages sent out 4,344 messages that just went on the back end and she didn’t have to do. So if you look at that and you say, well, it took her two to three minutes to find the project, check the date, send the reminder, and type that in, that’s where I’m able to get those time savings here.

The next case study is our brief upload. So when we have our projects awaiting brief, we go through and we want the brief. We want it to be put into this brief folder on our project so that we can start to understand specifically what we’re working on. So the objective was to reduce the time for our traffic managers to go in and check to see every morning if a brief was uploaded in the project and then close out that brief do task. And change the project status from awaiting brief to now resourcing. That was taking about 15 minutes a morning for our traffic manager to look at all projects that are awaiting brief, which could be anywhere from 30 to 50 projects that are in the queue, and see if that was available. And the brief was in there and ready to kick off. So what we’ve done is we’ve automated that. We have a customized notification that is watching for the file in Fusion for the document to be uploaded to the brief upload folder. Once that happens, the brief do task is marked completed, a note is sent to the traffic manager, and the project status is changed to resourcing.

And here’s the time savings because we’re documenting that happening on the custom forms. We were able to see that when we first launched it and tested it with our North America studio, there was 19 hours saved just for Q4 2023. But all of 2024, we had 240 hours saved of our traffic managers checking and looking for that data point, looking to see if the brief was entered there.

And the final case study here is going through the automated stakeholder reminders. So when we send something out for proofing and we add it for a proof, we’re looking to see, is this due back? OK, this is due back for first draft review by Friday. So our project managers are now checking and we’re looking to see, did feedback come back? We’re looking at this. We’re adjusting due dates. We’re reminding them everything. So we set out automatic stakeholder reminders based off of the task due date and manually reminding them this. And the best part of this is if they don’t get back, it automatically changes the project status to with stakeholder in delay. And it notifies them that the status is in delay now and it’s with stakeholder. And then it goes through and it automatically will. If we don’t hear anything back in two to three weeks, the project just gets closed out automatically. And we found that it was about eight hours a week. They were spending, checking and looking our project managers. And then based off of how many notification reminders went out and looking at that custom data information, we saw that in 2024, we had four hundred and sixteen hours saved across four studios and four main project managers across the board here.

So looking at the data points and having that scenario ID, the date now and having that in here and having it start to tally up, the information has really been able to give us the ability to pull those data points and really show, hey, we automated this small piece of looking for a brief, going into a project and looking to see if a document was uploaded. And what that actually did was save two hundred and forty hours last year, over nine hundred and sixty two different projects that they were looking for, because we’re capturing that that scenario ran and touched that project on this date specifically here.

And what I do have in the appendix when we do send it out is specifically what those look like for the calculations, for those custom calculations to be able to pull in that information and populate it here as you’re looking through stuff here.

So that is all that I have to present and go through, but I’m ready to take some questions if they have. And I can see that the chat’s going off, but I haven’t seen it. That’s OK. This is amazing. Lots of reactions. Yes. There are some questions. The first and I do want to thanks for I just want to talk about the recording again. Once since we joined a little bit late. Yes. The recording shows that it was like longer because Kimberly and I were working on basically my microphone issues. So that’s why it showed it different. You will get the recording after, though. OK. So the first question on our list was, does your team also pull in projects manually outside of your automate automated processes? How does that work? Yes. So we have. So the planned process goes through quarterly. So we just closed planned for Q1. So the queue is closed. Plus, we have some ad hoc work that comes in through the request queue in work front and that ad hoc work will come in and based off of what we’re we have capacity for. It’ll either bump something off the plan or we’ll fit it in when we can fit it in or maybe it goes to an agency for our direction. So the key with this and the planning and having that coming in and going through is we only have so many hours available by resources.

We don’t want to over allocate them because we would like to retain our users.

So we really stick to the plan and we really don’t take on more than we have for resources. So you either need to have a vendor come in and support it. You need to bump something off of your plan or you need to help deprioritize something else here.

I love that. First of all, I love that you are able to do that because that was the dream. I just want to take a look at that. Yeah, definitely. The timeline on that one. OK, so the next question really quickly. OK, which one is the best module to use watch events or webhook as the starting trigger? I think it depends. I think it depends on what you’re trying to do.

I usually defer to Steve for some of those questions, so I don’t do this all myself. I just want everybody to know, like I really leverage Sarah. Sarah actually did all of those calculations for me. And Steve helps for that. So I do the watch events, but Steve would say do webhook.

Yeah, OK. I mean, yeah, I think that’s fair. I do. And I’m not the only person that is interested. Like, what is your leadership response generally? I know, like the question is in response to like, it’s delayed because it’s your fault. Definitely interested in the response to that. But like generally speaking, like now that you have. All this data in this messaging, like what are their thoughts on Workfront Fusion, like all of that? Yeah, so so Workfront certified in our tool landscape. So we are trying to push more people to use that in that case. And I will say, Cynthia and I had a conversation earlier that I don’t actually pitch this tool around the company. And a lot of people hear the ease of use and the automation and this and we go through and they’re like, hey, can I use it? Yeah, sure. Let’s go through it. Let’s start building. What’s your use case? Let’s go through that. And then we prioritize that. I will say that a lot of our teams in our studios kind of go back and say, listen, if it’s not in the tool, it doesn’t exist. We’re not working on it. And that’s a hard thing to get. But it really works. And it really helps our team know what they’re working on. Know what’s coming next. What are their due dates? What is their deliverable by? And really making it and customizing the tool with layout templates to make it easy for them. But then being able to come back and say, look, I had this crazy idea. Let’s automate this piece. What’s your biggest pain point? And let’s see how long it takes. And let’s automate this piece here. And then I can come back and say, well, look at how much time we saved just by this one little thing.

And it seems so small when you’re like, oh, well, it only takes 15 minutes in the morning to go look and see if the briefs were uploaded. But I think once it’s automated, all of a sudden they’re looking and they’re saying, oh, my God, I can’t believe that I actually did that for 15 minutes every morning now and I got that time back to go do something else. That’s more valuable than the time.

So for me, we said, yeah, go ahead. Go ahead. So for me, a lot of these a lot of these scenarios and a lot of these things that we’ve deployed in these efficiencies are things that I saw their pain points and I just.

Solved it for them a little bit. So, like, I don’t think people know what’s even possible when it comes to fusion and automating. There’s so many possibilities in here. But looking at what takes the most time each day and then start to record that and start small. We started small with that the piece of, well, let’s automate getting the projects in. And then we saw how much time that saved. We were like, well, what’s next? What can we do next? And then how can we show this value? And it’s really that custom form piece there. And documenting every time fusion touches a project that a human didn’t have to do something really goes back and shows here’s the value of this. We saved all these hours and now they can actually work on something else. And how many times do people say I’m so busy, I can’t do this or. Yeah, we just save that time. And it’s a lot of it is the admin work of time within here. And it was the thing I was going to comment on that I just want everyone to also think about is even if it’s 15 or 30 minutes, which is significant, but it’s the switching between the tasks. There’s also a bit of time that you know, you trying to like change gears. Right. And I just think that’s also important to be like have that thought process of like, yeah, it’s 15 or 30 minutes. But at least for me, and I know it’s for a lot of people, like I’m focused on that. I’m like, OK, it takes me a few minutes even like let me get into the other thing that I was supposed to be doing instead of the admin work. So it just saves so much.

That and having those four fields and then having kind of the totals at the bottom really shows look at all these times that we didn’t have to do something on this project, but it actually kept moving the process along. And it kept going. And being able to document that and being able to show back, because if you go and say, hey, listen, I need more few scenarios or maybe I need to move to the ultimate license so that I have an unlimited amount that I can work with. Well, this is the value. We’re saving this many hours, which ties to user effort. And we’re able to free up and say, OK, we’re not doing this much work. Let’s readjust and we can actually take on more projects because we’ve already canceled this one out of the pipeline because nobody responded to it and we don’t have to spend time going through and doing it. So I think that’s the value of documenting it on the back end. And just again, I have a custom form that’s hidden from everybody, but I think like five of us in the whole system as admins that is just tracking this on the back end for us.

And I see Marie Claire, just give me one second. The only thing the other the other thing I was going to say was, I just want to talk one second about those abandoned projects, because we talk about that so much in all of these events. And I don’t want it to get sort of glazed over. Think about if you were able to show like, yeah, we can show projects that sort of like fizzled out. But if you show how many times things were needed to be touched and go, look at the work that went into that and just went away. Yeah, it’s work that’s being completed, but also that. So I just wanted to throw that out there for everyone’s mind to also flow for that. OK, sorry. Marie Claire, what question do you have? And I will get to the ones in the chat, I promise. Yeah, sorry. I don’t have the chat. That’s why I’m raising my hand. And thank you so much, Kimberly, for sharing with us, you know, your use case.

I’m working on quite similar use cases as well. So I’m curious. OK, my scenario is based on the approval process that’s used on a task. Fusion will be triggered and we’ll send like a reminder every two days. And so I was kind of wondering if it would be possible for you or your team to share like the functions that were used inside of Fusion.

Or maybe it’s on the custom forms, like custom fields. I don’t know. So I’m really curious because right now I’m kind of eating like a hiccups.

Yes. So I actually so. So I just have to give shout out to to Sarah Meyers, our WSA, because she actually did this for me with my idea. Can we do this? So this is the actual formulas and I’m going to send these out with it of what are on those three fields that are calculating. So the SID is the scenario ID that is that is populated for this.

The EID is the execution ID. And this always helps me sometimes, because if there’s an error message, I can always go back and try to look in the last 30 days what this is. And then I also have just a date field where I capture the date that it happens. And then this one actually, this date history field is what captures if it goes through multiple times. And I think I saw Sarah in the chat at some point here, but she’s the one that kind of built these. But I will send these out. These are the specific formulas that we use on the forms to calculate this. Thank you so much. I appreciate it. Yeah, I’ll definitely send those out because I’m not it’s not not hanging on to it. I didn’t do it. Sarah just said, hey, that’s me. Shameless bug. So the WSA and the WSAF, which is including like ours, we have Steve Watts as our fusion consultant. I would not be able to do any of this stuff without having those hours available to me because I come up with these like crazy ideas of stuff. And then I go to Sarah and I say, OK, I’ve gotten it 80 percent. Where’s that last bit that I’m missing? Or she’ll come back and say, hey, I’ve already learned this new piece here. Let’s do it this way. And I’ve seen another customer do it and we’ll go through and bounce some ideas off.

So having that has been invaluable for me to be able to do this. Plus, I’m one person and we have a large instance. We work well together. But I will send these calculations out. And this is what is populated onto here. So we have for each one of those messages that you send. I have my own. So I have a message for four weeks, a message for two weeks, one week, brief due date, one week delay. And I kind of go through here. So each one of those has its own record place to capture. And then at the end of those, each one of those scenarios, I have a fusion data input that inputs on that specific message. So if it’s the four week message, I’ll have fusion data input for that four week message. I’ll have one for the two week message, one for the due date message.

Amazing. Thank you so much.

Thank you for that question. We have a lot in the chat. So are you ready? I can just grab one here. Yeah, I’ll just go ahead. I know that.

So how did I ultimately prioritize where I would focus the effort for automations? Was it a small group? Or was it a broader user survey to determine where even the smallest amount of times could help? So to start, it’s been me just kind of knowing what the process is, and I really focused on our creative teams and our creative studios. They’re the largest use case in here for us and the most robust process in here. And they’re actually the best advocates of the tool for us. And they’re really big champions of mine, which I really help and really support here. So I went through and I just created a project and I started listing out everything that I thought could happen. And then I go to my traffic managers in each studio and I say, what else do you need? What else can we do? And I start putting it on the list and then I start to look at, well, what would either one, what is a quick win, low hanging fruit that I could just knock out and be done with? What is a larger one? What would actually have the most impact? And that with stakeholder was a huge impact. And it took me a while. And then what I did for that with stakeholder one was I actually started with just our NAM group. And I tested with them for three months and just from a proximity standpoint as well. And then I started to roll it out to our AMIA team and then to Hong Kong and then to our India studio and kind of went through there. So I use Workfront to manage my projects. I prioritize everything in there and I track everything. And I go through and I assign Steve and I assign Sarah tasks right in my projects and they go through and we help work together on that.

That’s amazing.

There’s some questions around work planning. And I did not I don’t believe we’re going to be at this time. I believe we’re going to be because other areas of our business are using Airtable. So we’re we’re kind of going into that. So that’s why I’m actually integrating the data from Airtable and pushing it into Workfront. And then I’m actually pushing Workfront back to Airtable. So it’s a bi-directional integration here. And then also tracking how many things came through from the Airtable planning into Workfront so we can start to see how that works.

So unfortunately, that one’s not my decision, but I am going to integrate the tools so that we can talk to them together and that our teams are still executing in Airtable. I’m planning in Airtable and executing in Workfront. Yeah. I mean, to me, that’s the magic of Workfront. It’s a plug and play. Yes. And Fusion makes it so simple with the connectors. It was do a search in Airtable and here’s all the information. And then I mapped it right into Workfront. And we just did our first pilot through it. And I saw that it took I think it took like five minutes to move everything across total for all projects, which is even less than the nine minutes it took last quarter. So we’re getting faster. That’s pretty good. That’s amazing.

We want to get out of Excel. We want to get out of Excel completely. That’s not that’s not my idea.

There was an earlier question regarding capacity and prioritization of resources. This is how do you currently estimate planning capacity? Are you doing that in Excel? No. So the planning capacity is done in Workfront using the Workload Balancer.

So we use schedules. We put in our you use the PTO functionality. So our designers, our writers, our producers, they go in and mark time off. We use the schedule and then we also bump every DIT buddy down to an FTE of 0.7 as their full time capacity. So that’s why we’re trying to get all the work in and we see which group it would go to. And then we look and see what resources we have available. So all of our planned capacity and everything is through the Workload Balancer.

So as a tech writer, this is like definitely for me to like, how do you build and document your fusion use cases? Like what are you using? And my PowerPoint.

Yeah, yeah. I’m putting together. So Sarah has provided me an excellent documentation for new build ups and how that comes in. And then Steve is and I have been working on a similar format for the fusion setup. So documenting what is your process? What are the data points that we want to connect? What is this? We have two types of fusion scenarios. Is it a work front to work front? So is it we’re pulling data out, we’re automating it and we’re pushing it back in. That’s one scenario. And we can really run with that at the capacity that I have available. But if it’s work front to another tool in Schneider, then we have to take a step back and we have to go through the proper channels to make sure that we’re not violating any data privacy policies. And we go through the proper channels and we document and we document through a PowerPoint template and we go through what’s the today use case. Here’s the users involved. Here’s the steps they take. And here’s how long it takes. And then I go through and I start to play around with, well, what if we did this? And then I document it on the steps. And then at the very end, what I do and I probably should have put this in, I’ll add some slides here. What I do at the very end is I export a blueprint once the fusion scenario is live and I store that in our OneDrive as a backup of everything.

And then I document into our master documents area. This is the scenario. These are the triggers. These are the data points so that if anything changes in and I communicate that with Sarah, because if anything changes in work front in a certain capacity, it’ll impact the trigger and it’ll impact the data point. So it’s really communicating to the governance and working with your WSA and having that trust back and forth of Sarah is aware of the field that we can’t touch in the system because we’re communicating. This is the trigger for this fusion scenario or when this moves this impacts here so we can’t change that data point because it’ll impact in fusion.

And then what we also do for fusion and documentation is, and this is kicking off in January, is we do our one referential governance across the entire company. And I have a project plan and we update fusion, we update work front, we update our dam solution, we’ll update air table, we’ll update all the different pieces at the same time so all our data aligns across and that we don’t have issues with not matching.

I feel like I want to be you when I grow up. I just, like this all seems amazing.

I just want to address one of the questions. I know you already answered it, but I just want to address it in the chat.

You know, they’re talking about the processes and how they planned and unplanned. When starting to use fusion, what automations were the most helpful? Where did you decide? And I know you said to start small, but I didn’t know if you wanted to address that a little bit more. Yeah. So the very first fusion scenario we did was the project input. And it’s because I took that fusion class to understand how to use fusion. And the very first exercise in the class was, let’s take this CSV file, let’s parse the data and create projects for it. And it was like a light bulb went off on me of, oh my God, we could do this and it could make things better.

Some of the other smaller scenarios that I quickly was able to do were user accounts. So I send an automatic message based off of my profile if they’ve been inactive for 90 days to check and see if they still need the license. So those are some smaller things from the governance perspective. And then I started to look at, well, what are the actions that take the most time for our studios and what makes the most sense? And then my colleagues all started to come to me with some ideas. And then I was like, well, I need to prioritize these now. We need to create a list. And what can I go through and what can I leverage from others from there? I love that. Okay, so there’s questions about both Airtable and the DAM, but I just want to start with the DAM. So can you talk about your integration? How does it work? How do you set it up, etc.? Yeah, so we do not have the Adobe DAM. We use a Primo DAM. The first integration we did was actually not with Fusion, but we passed all of the metadata for the assets in Workfront.

And so we used the integration layer within our company to pull that data out and pass it and automatically fill it in with the information, which is where you start. I think I’m still sharing.

So that’s where you’re seeing these hours here. This integration was actually through an integration layer where it’s taking the metadata from Workfront and it’s pushing it into the DAM solution. So we don’t have to copy and paste it in both because we are capturing all of that information in Workfront. The second integration that we did was the other direction. And this was fully done in Fusion with Steve’s help, where you’re in our Primo DAM, you’re in our DAM solution, and you can right click on the asset and say, I need changes to this asset. And it opens a ticket in Workfront with all of the metadata filled in within there. So that was the second one that we did. So it goes both ways and it pulls all the information so they don’t have to refill it in again.

And so you’re not having the assets in Workfront. The assets live in the DAM. Yeah, the assets live in the DAM. Workfront is not our repository for assets whatsoever. Which, yeah, I agree with. Anyway, because in my past life, they’re like, we have a DAM, it’s called Workfront. I’m like, no, no, no, that’s not supposed to be that. Oh, no, it’s not. It’s not the search. It’s not that. So the question for the Fusion is I took the bootcamp in 2021. It was like a three day bootcamp that I took.

And we can, I will put the Adobe Digital Learning Service link if anybody wants to. It is a paid bootcamp. But again, like we’ve talked about making the case for all these things, like definitely trying to make the case for the bootcamp as well. So I’ll put that link in the follow up as well. So I also see Ivana’s question here about the stakeholders response. What stops it from going to the next gate? So we use digital proofing and we use the approval. So when they hit approve, it notifies the traffic manager or the traffic manager and project manager can see it. And then they close out that task for stakeholder review, which I’m working on automating that whole piece there. But once that stakeholder review task is completed, the milestone changes and the project status changes and it’s no longer with stakeholder. It’s back with Studio automatically for us. And that pulls it out of that initial search.

Well, I love that. But just again, it sounds magical to me. Did I miss any? So, I mean, again, like people are asking about the Airtable integration and that’s through Fusion, right? You’re not using the open API, right? Yeah.

I know that there’s other people that have done the Airtable integration. So if there’s any questions, I think you could probably post on the community as well. Yeah, I’m still going through. We just did our proof of concept for that. So where there was a lot of unexpected challenges that came out with the proof of concept, which is why you always do a small proof of concept before you launch live. So we have to go back and rework a few things for this that we weren’t expecting.

I mean, yeah, like that totally makes sense. And I will just say, like, again, I know we talked about the plug and play, but learn from at least my mistakes. Like I used to try to strong arm people into work front. But if there’s other systems that they want to use, you can do the proof of concept, you can do the integration and sometimes just show show and tell works a lot better than the strong. So just yeah. Yeah.

So anyone have any other questions? I was going to run through some quick updates.

OK, I’m going to do that real fast. And then, like I said, you’re going to get the recording because I know everybody’s going to be like, I want to see this again. And then probably tomorrow we’re thinking if Kimberly gets approval to share those slides, I’m just going to post it on the experience post, which will also be in the follow up email. Just repeating a little bit of that just in case you missed it. OK, so first things first, let me do this. OK, I want to talk about like this slide has tons of fusion events like on demand events. And we were talking about Steve Watts, which right here he presented this one. And I just love like it’s music related. Like he came up with the title. It just I don’t know. It was amazing. But that’s his event. So you’ll have a link to that. And then we literally just had, you know, five tips for automating naming conventions like before Thanksgiving. So there’s a bunch of stuff there. If you are interested in more events, we do have several for the rest of the year, including more pro tips. So that’ll be tomorrow. We have the admin chat for Marketing Creative and then we have a planning event. And I just want to throw out there. Oh, yeah, this I need to cancel this one. This AMA, it’s not canceled, but it’s been pushed out to January the 28th. So it’s Kelly, Skye and Nathan going to be doing your demystifying text mode. But you know, you’re going to want to attend that and ask questions. So we’ve got that coming up. And I did want to put the summit information out there just because there’s early bird summit deals. So if you’re trying to make the case for stuff, there’s like I know people did the labs last year. They did the fusion labs last year. They did certifications at summit last year. Like there’s a bunch of cool things that happen at summit. So if you want to make that case, go ahead and grab that information. And then last thing, there are two like there’s a there’s four user groups out there and a lot of them talk about fusion and automation and all the stuff. So just don’t miss out on these opportunities. But there is a new work front champion office hours. There’s a content supply chain user group that’s been started. There’s a bunch here. And I know more being open. We’re trying to get a Dallas Fort Worth one open. So I might crash that one if that ever happens.

And then last thing, there’s a virtual one. So there’s a virtual chapter. So, you know, I know I’ve got a bunch of champions on the chat. I know I’ve got user group leaders on this chat. So please go out and connect with your other work fronters because the questions that you’re asking. You know, it’s the question. These are the questions we’re all asking and we can work shop them and work through them together.

And I think that was it. Oh, yeah. And then survey. So we’ll pop the survey in. Oh, thank you so much, Nicole.

So, yeah, this this was it. Kimberly, oh, my gosh. I’m going to stop sharing.

I told you everyone would be excited.

So thank you so much. She did all this. She did this over the holidays. I’m so grateful for your time and you sharing this with us. And maybe maybe we’ll come back and talk to us. I hope so. We appreciate you. Thank you. Yeah. Thanks, everybody, for tuning in. Like I said, we get this follow up out to you in the next hour at the latest. And then tomorrow, hopefully get those other slides. Thanks, everybody. You have a great week. Bye.