Start Fast, Scale Smart: Activating Team-Level Success with Workfront Planning

Transcript

All right. Hello, hello.

Good morning, good afternoon, good evening. Welcome, welcome. We are going to give it just a second. We had a lot of people sign up for today, so let’s just give it another minute or so. But if you’ve been to our events, say hey in the chat if you want.

Let’s say hello myself.

Where’s my favorite GIF? We can just get in a site in the chat about is it GIF or is it GIF? That could take us all day.

Yes. There we go.

We have people from everywhere.

Welcome everybody. See, I started something. I don’t know if you saw that Andy, but I did in the chat. We got a GIF happening. You’re welcome.

Welcome everybody. This is going to be our start fast scale smart about work front planning.

Just so you know, we are recording this in two ways actually.

But there will be a recording and then we’ll have the presentation slide deck, we’ll have all the good things. Don’t worry about that. Right now, we have the Q&A pod is available.

We have a did start something with the chat. We do have Andrea Fernandez will be helping out along with Andy Watanabe, who is our presenter and our special guest, Jazz Hands star today.

If you have a question while he’s doing the presentation, if you don’t mind just popping it into the Q&A pod, chat is still open for conversation, networking, doing all the good stuff. But if you have questions on the presentation, if you pop it in there, and we’re hoping that there’s going to be plenty of time at the end, so that when the presentation is over, then we’ll just turn everybody’s mics back on, and you can come off mute and ask your question. With that, Andy, welcome. Welcome to our event today. We are so glad that you’re here.

Thank you, Cynthia. Thanks everybody for coming. Appreciate you taking the time out of your day to come and hear about this story we’re going to tell today about how you can start fast and scale smart with work front planning.

And this is a response to like a pretty specific, I guess, ask from a lot of folks who have been looking at work front planning, and I hope you get a lot of value out of it today.

So to get started, I’ll just kind of introduce you to myself. I’m Andy. I’ve been a product manager with Adobe for about seven and a half years. This is a picture from a long time ago. I tell my wife, I think I still look the same, and she tells me I do not.

And this is a photo of my workshop. And I like this as an intro just to kind of highlight this idea that I love tools. I love the idea of what you can do when the tool works well, whether it’s climbing equipment, you know, the sort of life-saving equipment when you’re rock climbing, whether it’s table saw sled to help you make a straight cut. I really love tools. And it’s part of why I am so excited. And I’ve been really happy to be part of the build out of work front planning. Because what we think is we’ve built this tool that can really help you as marketers and system administrators and you know, all the different roles within an organization plan and orchestrate your operations better. And so that’s just a little bit about me. Today’s goal, though, is that we’re going to talk about a path to help you get to value fast with work front planning. And we think that this path can even help you improve your system design outcomes through what we sometimes refer to as a federal and state model. And we’ll explain more about what that model is in just a moment. But let’s start by talking about what reality is like today, especially as it relates to governance. If you didn’t catch from the federal and state metaphor there, we’re going to talk a lot about governance today. And we’re going to speak in many regards specifically to folks who are system administrators or group admins who are trying to curate this experience inside of work front for a group of marketers that you’re trying to help have success.

And so we start by thinking of admins or group, yeah, sysadmins or group admins as the guardians of order. And in some scenarios, over governance can lead to confused users who might feel like this system that they just got dropped into is really complex.

It can sometimes lead to low adoption, which creates this high support burden as teams are really working hard to drive adoption of a tool. And in the worst cases, it can lead to abandoned tools. And I know we’ve got a lot of shadow IT in organizations. And if that term is not familiar, it’s basically when you use a tool that the company didn’t sanction, because you just felt like it was going to help you out better for use cases A, B or C.

And that can happen when there is over governance. We’re not saying that that is always the result of governance. Governance is good and right, but that can sometimes be the result of over governance.

And there’s a new opportunity here with work front planning. Work front planning is a new product. And we want to like talk about how we can think differently about governing work front planning to create success.

And so start by asking this question, what if you could deliver a governance model that reduced resistance instead of sometimes creating resistance? What if teams loved the system that was there for them so much that they were signing up to get in, you might have even had a backlog of teams, you know, waiting to support them, because they’re all trying to get in the door and get access to the tool? What if autonomy among those teams actually made the operation team, the ops team’s job easier? What if giving them autonomy actually made it easier to administer the system? And we think we have a response to these three opportunities with this model for how to adopt and get to value with work front planning.

So work from planning is a new product. And that new product comes with new expectations. This is a new module as part of the work front family. But again, it is a different product. It’s a different and connected product. And so one of the first expectations here is that work from planning is designed primarily for agility, and not necessarily for rigidity.

It’s built for users who are trying to get clarity about their operations are trying to get visibility to see what’s happening. And it’s not necessarily built for highly, highly complex, really rigid workflows that have to operate exactly the same every single day, day in and day out. There’s a lot of need for clarity, which also sometimes means flexibility.

Work from planning is built in a way that it’s sort of safe and separate from the rest of what we call, some people refer to it as core work front, we call it the workflow module. So it’s safe and separate from the workflow module in the sense that things that you do, while you’re setting up or governing work from planning, don’t necessarily have adverse impacts on what’s happening in what you’ve already built in work front.

One sort of simple proof point of this idea of safe and separate here is that our beta testers were able to test in production with work from planning because it wasn’t, that there was no tie in for it to again, adversely impact what they had already built.

Work from planning comes with a mindset shift from enforcing structure to enabling flexibility. You will have structure and that will be important to it. But again, the mindset now is about how do I enable teams to have flexibility in the ways that they operate in this system, so that they develop a sort of buy-in, a feeling of ownership over participating in the new system design.

And this new product comes with entirely new object types. In work front workflow module, we’ve had, you know, portfolios, programs, projects, tasks, issues, and so forth. But in work from planning, we have new objects, we have workspaces, we have record types, we have records, and we have views. And those new objects come with new behaviors, they come with new relationships with each other. Again, new ways of thinking about how to govern them. And so with all that newness comes a risk of applying old habits. So if we treat planning like the workflow module, that could result in an implementation that might be over complicated. If we do that, you know, admins may unintentionally block value by over governing a system that’s intended to be more flexible. And that over design could sort of kill exploration, it could slow learning, it could slow adoption of the tool, which also has like this idea of fueling some resistance. So there is some risk in applying old habits of how to administer a tool, you know, the workflow module to a different tool, a new tool. And so again, that’s why we’ve come up with this idea of the federal versus state model. And so in the federal versus state model, we have this notion of the federal government here, which we’ll think of as the enterprise. The federal model says, hey, we bought this tool because we wanted to create an enterprise-wide, centrally governed marketing system of record, this like, which is a really great vision, and we totally support that. And getting there can have really long implementation timelines, because it is not easy to shift the way that an organization at enterprise scale plans and operates marketing. That’s a big ask. We think it’s worthwhile, and we highly recommend you do it in time. But we acknowledge that that is that comes with long implementation timelines, takes high coordination, there’s low short term value, which can result in negative sentiment towards the new system. And so we want to avoid that. And that’s where the state model comes in. State model is this idea of more decentralized team-led adoption as a precursor to implementing the enterprise model. It’s fast, it’s modular, meaning each team can adopt and sort of you can run pilots with teams. And it’s very scalable. And this model for state or team level adoption drives early wins, which creates momentum, which creates enterprise use cases, and helps the enterprise as a whole understand what kind of design considerations actually work well by collaborating with teams. And now these teams who have been part of the system, they have a lot more buy-in because they understand how to use it. And you come with it, you get a built-in evangelist system through this. And there’s a part of this slide that’s actually kind of wrong. And I wanted to highlight this specifically. The reality is it’s not federal versus state, but it’s federal and state. It’s working together. So, this is about guided autonomy and not chaos. This is about partnership, not opponents. So, we want to think in terms of providing the states here or the teams with lanes on a road. It’s not open fields. They don’t get to go do whatever they want. But we give them lanes within which to operate. And we can call those lanes workspaces. And those workspaces come with permissions and permissions models. They come with some restrictions.

So, it’s about giving teams workspaces, lanes on a road. Admins can define the lanes. And when teams get into those lanes or workspaces, they can choose, you know, they can choose like sort of like how to drive, how to navigate within their lanes. So, it is a bit like a choose your own adventure at the team level, but there’s still structure to it. And you as admins can provide that structure. You just don’t have to do it all at once. You don’t have to provide the entire structure, an entire redefinition of how marketing operates. You can just support teams and maybe migrating from say a spreadsheet to a governed tool that will help them buy into this idea of a centralized marketing system of record and time. So, why does this work? Why does StateFirst really support driving adoption and fast value? Well, I just mentioned this a second ago. The first thing is that teams are already operating in kind of a StateFirst model. In other words, a lot of what a team does is already outside of Workfront. It’s in Excel. It’s in a PowerPoint. It’s in a SharePoint site. It’s in a wiki. You know, it’s any number of places where they’re tracking objects or artifacts that are relevant to their operations. They’re managing trackers. They’re putting together briefs and that might all be happening before work ever gets into the workflow module, you know, core Workfront. So, teams are already operating with that kind of autonomy outside of the constraints of Workfront. When teams get have like relevant spaces to work, clarity about how to do it, and they can do it fast, well that drives adoption and they get that already or rather they can get that if you give them a space within which to operate inside of Workfront planning. Give them that space that’s relevant to them. It’s clear how they can manage it and they can do it fast and they can manage their operations quickly in there. That’s going to support adoption. And if users have autonomy, if your marketing teams have autonomy to get into a workspace and kind of make it their own, then it means that they’ll understand it. They understand how it was built. They understand its constraints. They understand why these design decisions were made, why the form has this data but not that data, and that means that they can more easily adopt it because they can’t understand or can’t use or what keeps putting up roadblocks for them. But if they design the system with your guidance, then that’s going to help them a lot. Smaller teams also adopt faster.

It’s much easier to drive adoption with a small group than it is to drive adoption across a giant enterprise with thousands of marketers. And faster adoption equals faster feedback. So, as you are trying to support admin, sorry, support your marketers in driving adoption of this new system, what you’re going to want is a really fast feedback loop. And when you give teams the space within which to operate in a governed sanctions tool, well, now you can get their feedback in these rapid feedback loops which will help you as you go out and design the enterprise scale marketing system of record together with them now. That fast feedback loop is super helpful, especially when you’re trying to define what your global taxonomy should be. You know, how do you globally want to define a concept of a campaign? Well, if you have a bunch of small teams that are already sort of working towards that idea, well, you can work with them, see how they’re modeling those objects in their own workspace, and you can start crafting from that a centralized taxonomy plan from all that feedback that you’re getting from the ways that they actually operate.

And this means that you can start laying a foundation for that enterprise scale system of record while generating your return on your investment, getting value out of the tool.

So, in short, early wins build momentum, momentum builds trust in the system, and that trust in the system earns this idea of governance. So, when people trust the system, they’re going to be more willing to participate in a governed system than they would if they were left out of the design process or didn’t have any sort of autonomy in that system design. And so, all of this is going to support driving adoption.

And there’s benefits for the admins as well. We think this results in a lower support burden because you have more champions who can do the support with you at the team level. Fewer complaints about complexity because teams are participating in the design. And even if the team is a result, it will be their design. And so, you know, fewer complaints about that. You get real-world examples of how teams operate that you can then codify into more streamlined centralized structures. You have more visible success stories to help shape future rollouts to other teams and start to garner more interest in participating in this centrally governed system. And now we’re encouraging bottoms-up advocacy instead of these top-down mandates to adopt. So, that’s really, again, useful to support admins.

So, I know I’ve talked a lot about this. And some of you may not be very familiar with what Workfront planning looks like. I know some of you work in organizations that have purchased the product already and you’re looking for more info about how to get value fast. Others work in organizations that haven’t purchased this product and so you may not have really seen it yet. So, I just wanted to spend some time showing you what a successful implementation can look like.

To start, we’ll take a look at the workspaces that could exist inside of an implementation that’s doing the team-level adoption paradigm.

In this case, we’ve got team-specific workspaces. For example, a global events workspace or a PR and global comms workspace. Each of these teams have very different operational paradigms. An events team tracks a lot of things that are relevant to events. Maybe they want to track a list of speakers or venues and those could be objects or artifacts that they create and manage inside of Workfront planning. So, they could have a table of speakers, a table of venues, and a table of other things that are relevant to their operations and they can manage those and then construct plans that draw on those artifacts that they’ve created and added into planning. So, now you can tie a plan for an event to a specific venue that you’ve tracked or a specific set of speakers who are going to be there at that event and they can start to tie their operations together in their own workspace. Or you could have a PR or global comms workspace, a team that’s trying to work with media outlets or news reporters to spread the word about how great your company is and how great the new product offerings you have are and so they can have their own team-specific workspace. And at the same time, you can start early and start building a global metadata workspace, a workspace that stores records that you want to use consistently across all teams. So, maybe you want a consistent set of brands or products or regions or countries that you do business in or languages that you localize marketing into. You can store all of those inside of a unified global metadata taxonomy workspace and then share them out to the teams. And you can do this again at an early stage without having to design the entire system of record and this will support a successful early team implementation.

If we take a look at the Fresco PR and global comms workspace, you can see that there’s these four rectangles here that represent the types of things that this team tracks.

The PR and global comms team may want to track that list of reporters that they are working with, say at outlets like a Wall Street Journal or a TechCrunch or The Verge or something like that, you know, depending on whatever industry you’re in, it could be a list of reporters for that industry. And those reporters may work for some media outlets that Fresco also wants to track and they may have specific media interactions that the PR team wants to track. Every time they have a conversation with a reporter, they may want to track that so they have this detailed record of their operations and all of that can be tied together to support their delivery of comms into the marketplace or PR moments into the marketplace. And with a work front planning workspace, they can track all these things, tie them together and have a space that really details their operating model.

And when we talk about new products, new expectations, this is really what we’re talking about. We’re not here talking about projects and tasks just yet. We’re not talking about form-based intake just yet, although we will in a minute. We’re talking about a space where teams can now plan. They can plan their work. They can plan out all the sort of artifacts that live in their solar system of work, like reporters, media outlets and media interactions, in order to then deliver the core value of their work, in this case a PR moment. And so these, we would call these like team-specific planning records. An email team doesn’t really care necessarily about the media team’s PR moments. A social team may not care about these PR moments and likewise the PR team may not care about specific elements of social channels because they may not be doing a lot of work in those channels. So teams that operate differently can have different workspaces where they reflect those operations and model them in these record types. And so these artifacts keep teams aligned by centralizing what they do into more codified structures. So rather than a loose Excel spreadsheet that tracks a few media outlets, another spreadsheet somewhere that somebody put in their own personal OneDrive tracks reporters, now you’ve got a centralized location for the team to meet together and operate and collaborate together. And those teams can enter into these record types like a list of media interactions and they can create shared views that help the team improve visibility, improve collaboration. So here I have a view of interactions that the media team has had with different media outlets and you could click on each of these and you could review sort of a brief of the interaction and how it went. We do have form-based intake so a successful team implementation can consider how to take in records using forms on these planning records. So here we have an intake form to submit an idea or a plan for a PR moment or a request that the team wants to deliver. We’ve got required fields, you can submit that request and you can then have it land in a queue where it gets triaged or you can make it land directly into your comms table. And that simplifies and creates consistency in record keeping for teams.

One of the last things I’ll call out here is that we also have an ability to connect to global taxonomies from within a record type. So here we have our comms and PR moments and we’re connecting to a global concept of brands. In this field for brands the idea of connecting this moment to say cafe luxor or fresco organic as a brand that’s all part of this idea of connecting multiple workspaces together. So brands actually comes from our unified metadata workspace and we’re using it at the team level. So this team is using this this workspace is using brands. The events workspace could also use the same concept of brands and so you can have team adoption while still introducing this sort of consistency in taxonomy use which will aid you in reporting down the road. We also have this notion of automated project creation. So when a team like this media and PR team has planned a moment they have thought through it they decide that it’s time to execute it. Well now we can make that bridge from the work front planning module into the work front workflow module using automation. So here if you just select this you can easily go execute that plan which will create a connected project that lives in within the workflow module.

And part of what’s cool about that is that those connected projects can deliver real-time info about any information that lives on the project object whether it’s from a custom form on the project or the native fields. So in this scenario I’ve pulled out the actual cost from the connected project and I’ve referenced it here so that folks who are planning the work can get a real-time view of the cost from the context of their plan. You can see the percent complete of the project from the context of the plan and if you had multiple levels of planning hierarchy you could roll this data up and aggregate it so leaders or other stakeholders could get aggregations of costs or percent complete or again any other data from your execution work in the workflow module with projects tasks and issues. All right with that I trust that the chat pod if there are questions in there that folks have been answering those questions. Cynthia is there anything I got applause on before we jump into a demo? I don’t think there’s any like the questions are being answered but I do want to point out some things that you said I just don’t want them to get lost and Annie and I talked y’all before the session. One of the things that I think about with Workfront Planning is I was this sole system admin for years. A lot of us if you’re super lucky you might have two but it’s really just it was just me. So I had like a stack of departments trying to get into Workfront and that the sentiment of Workfront what it did or how easy or difficult depending on who you talk to like that sort of flowed through that adoption challenge that Andy was talking about and so I just want to like just reiterate like to me having something that I could get users in quickly where they could and I you know I hate to say these words but they’re already using spreadsheets just like Andy like they are using those spreadsheets outside of Workfront you know they’re doing it so skip get them into planning if you can so that they can start using it. So I just wanted didn’t want that to get lost. We’re about to do the demo but that those sort of strategic and and really higher level messaging of what it could do for your teams. So I just want to throw that in there Andy and we’re going to hope that the demo is going to go like we’re not going to have any issues. You know I feel like the product manager can say as much as they want but when when you when you speak from experience Cynthia I think that carries a lot of weight so I appreciate you adding adding that in. All right so I’m going to swipe over here into our demo and I’m not going to take a long time to demo because I want to make sure we have time for Q&A. We’ve got about 20 minutes left and so anyway I don’t want to take too much time in the demo. Cynthia and others do feel free to pause me if folks are wanting to spend more time in a particular area and we can do that we can sort of maybe even field some questions while we’re here in the demo because I think that this is this tends to be where where ideas get sparked and you wonder oh could I do that could I do that so anyway yeah please feel free to pause me when you need to. All right so this is the set of workspaces that you were seeing in my screenshots from before. I took all those screenshots right here from this workspace. This is a production instance of Workfront Planning so any feature you see here is available in your version of Workfront Planning right now. I don’t have anything sort of like special or unique to this instance and maybe the first thing I’ll do is I’m going to go into this unified global metadata. We talked about this as a way to store metadata that’s relevant to all the different teams operating within Workfront Planning and what I’ve done here is I’ve created just a few taxonomies to illustrate how this might work. One of those is a set of regions. I’ve created a list of regions that the business is interested in doing business within. This format here in Workfront Planning gives me the ability to add columns that further define what a region means to Frescopa, our fictional sort of CPG multinational company here and so they’ve defined this as having a region code, a description, a status, and a connection to another record, countries. So here we have a list of countries and this gives them a connected way to tell the story of their operations. They do business in these countries and these regions and so countries has its own schema, its own set of columns that’s different than the regions object or record type.

Countries has a connection to brands. Brands is another record type that’s one of my global metadata taxonomies and I can show you the brands record type here as well. Because Frescopa is this large multinational sort of conglomerate as a CPG company, consumer packaged goods, they’ve got many different brands and this is a space where those brands can be tracked. So we’ve got Frescopa Espresso, Brewmaster Pro, which is you know professional coffee machines, many different brands here and I have this table view where I’ve grouped them. I’ve controlled field visibility. For now I hit the thumbnails but I can show them if I want and I’ve added row colors to help highlight brands that have been end of life like Frescopa Barista and you can use these row colors to you know apply conditional rules on how you color things. Again that’s maybe not part of the start fast scale start uh start fast uh what did I call it? I can’t even remember the title of my webinar right now. Start good. Thanks Cynthia. So anyway it may not be part of that narrative directly but I think it’s an important just call out so you are aware of features that you have access to and planning and all that helps you construct the views that guide your users, your marketers to having success in their own operations. So I’ve got some geos as taxonomies and then I have business taxonomies. You saw brands. I’ll show you products. I have this whole table of products and this is useful because it’s going to help me have a record of objects that I can tie into my plans for different sort of channel or team level deliverables later.

And then last I have a record type for audience segments. I can track audiences like international espresso lovers, global coffee bloggers, global fair trade advocates. You know as a brand you’re going to have a notion of who your audiences are. This is more of a business notion of audiences and not necessarily like a technical notion that we have in other Adobe tools like Adobe Experience Platform. So this is sort of useful from a planning construct to say who am I planning my marketing for? Oh yeah it’s for our global coffee enthusiasts. Now storing all these in work front planning gives you now the opportunity to connect those into your team level operations. And if we look at this workspace for Frescopa’s PR and global comms that we were you know sort of I was showing you in the PowerPoint slides before you’ll see how that starts to work. So I can start with my comms and PR more moments. Here I have six different moments that I’ve planned. Again the columns are very different for these moments than they were for regions or channels because planning gives you that flexibility to model exactly the way you want to capture the data for the operational plans that are relevant to your teams. And this is where I’ve got that connection to brands. And so this as a special field type is a connection field. It allows me to reach across to a different workspace, grab a record from within that workspace, and make it available to folks who are building a PR moment here. And so what I’m going to do is I’m just going to quickly submit a request for a new PR moment and I won’t spend a lot of time you know getting it just so. We’ll just call this test moment and here I have a selector for brands. So this allows me to reach into that brands table that existed in the other workspace and now I can select a brand from a set of governed unified brands. So this one will be for let’s say this is for Chill Brew and we’ll just say this test PR release for Chill Brew. I can give it a status. Status is development. Expected go live is going to be July 30th and if I have had any interactions with media folks that I want to tie into this I can here. So I might know that I recently spoke with Daniel Brown and he was helping me out to plan out this moment through his particular media outlet. So I’m connecting to records from other workspaces. I’m connecting to records in this workspace and I’ve set this one up so that I don’t have to triage it. It’s going to land straight here in the table where I’m going to see it. So here’s our test moment. I get a notification and I can see all the data that’s related to this. And what’s cool is that when I connected to this media interaction I was able to other data from that connected record. For example, the date of the media interaction. I now know when that took place. I’m also pulling the media outlet. This one’s this the Daniels with ARS Technica. And by the way, some of these media outlets are these are like real outlets but the the reporters are fake. So the names are the names are fake here. But anyway, I’m getting this data from my connected ecosystem of records. And that’s one of the things that helps teams sort of light up with the ideas of what could be done. When they realize that they can manage a connected ecosystem of artifacts and tie them all together into their plans, they see this idea that they can begin to fill out their plans using lookup data across those connected artifacts without having to fill out quite as many fields in their briefs. So this can actually help them write their briefs faster or manage their plans with more simplicity, less manual data entry. Now I might be ready to activate this and execute this as a plan. And so I can use an automation that I set up and manage right here in Workfront Planning to say I’m ready to execute this. Let’s go ahead and create the project. So I’m going to click that execute plan button, which is a custom button that I added through the automation. And it just created this project object called test moment. I can see that I’m already pulling in the actual cost and the percent complete. And I’m just going to go over here as well. I’m going to update this from development to planning. Since I’ve decided I’m ready to execute, I’m now planning it out in an execution way. And I can click here to open up the planning object. And part of what’s cool is you could create this project from a project template. I didn’t fill out my templates for the demo today, but you could have a full set of templated tasks that are automatically populated because you created that project from a template. It’s already got a reference of its connection back to the planning object. So you can click here and you can see the brief of the plan that spawned it. And you can see a history of changes on that to get full context between the execution of the work and the planning of the work.

And as I make updates to this, for example, maybe I’ll just quickly add an expense here, test expense. I can, I’ll say this was planned at 10,000 actual is 9,000. We came in under budget. That’s great. So now I’m going to come back over here to planning. And that’s already updated in real time to show the actual cost from the project. This is another case where when teams get into planning, they start to see how much easier it can be to actually use the rest of the workflow module, how that can tie into their management of operations. This is so much better than trying to tie it into a spreadsheet, or a PowerPoint file. Now their briefs and their trackers and artifacts can all be in one place. And when you give those teams the freedom to set up their own record types to manage the artifacts that are relevant to them, it makes them so much more willing and interested to then take the next step and engage in the structured execution workflows that you’ve come to appreciate in the workflow module today. And of course, you can do this across many different workspaces, whether it’s a global events workspace, where we have totally different record types like accommodations, you know, venues, event types, speakers, etc. And you can connect it all together. So anyway, this is, this is sort of the the vision of what could be done in a team level adoption plan. All right, so I have a couple more slides, but I’ve taken longer than I wanted to. So I think what I’m going to do is I’m just going to go through these very fast and then turn it over for Q&A. So what’s the admin’s role in a state world? It’s not about surrendering control, it’s about scaling it intelligently. We have tools and techniques that we’d offer for scaling support. For example, we recommend having monthly office hours, brown bag lunches, or drop-in Q&A sessions with teams to help them in their process of getting onboarded into planning. And all that leads on a path to enterprise scale. So we think about this as a two sort of like a subway map or a metro map. There’s these two paths. There’s this path to team workflow and configuration, which can be parallel path next to the enterprise workflow and configuration. And once you do both of these, that’s your like scalable, fast path to value and enterprise scale marketing system of record. So the road to enterprise is state first, we think, but not state only. We think it helps teams succeed and help you design better at scale. And then the real win, and we’ve seen this internally at Adobe where we’ve rolled out work front planning, is that we have teams leaning in and asking to try and adopt it and they want to join because they see the flexibility that they can have.

Okay. So with that, work from planning, it’s about clarity, not control. It’s about finding your initial team champions to get yourself started. It’s not about losing control. It’s about gaining champions and letting teams find value fast and early. With that, we’ll pause and turn it over for Q&A. Thank you so much, Andy. This was amazing. And we do have questions in the chat pod that are pending, but also really quickly, Andrea, thank you. You’ve been a champ in the Q&A pod, so appreciate you. Okay. So I’m just going to kind of go in order, kind of back, like what hasn’t necessarily been asked, but Kim asked if she wanted to see everything happening for the Chillbrew brand, can I have it pull records from this PR moment table into a brand table? I don’t know if we need more information or if you’re good on that question. Yeah. Would you mind stating that one more time and then I can try to show an example here how that might work? Yeah. And what I’ll do super fast, I’m actually going to change the settings really quickly to on everybody’s mic. So give me one second. Mic for attendees, camera for attendees. Look at us.

All right. So, and Kim, if you’re able to, I’m going to let you come off mute, but I just want to repeat that. If I want to see everything happening for the Chillbrew brand, can I pull the records from the PR moment table into a brand table? Okay. Thank you. The answer is yes. You can, because you’ve connected them now, there’s this tie between the Chillbrew brand and anything that’s part of its connected ecosystem. And sometimes that connected ecosystem could be sort of like multiple layers deep, but you can both see everything that Chillbrew is connected to. In this case, it’s connected to specific products and countries as well as, and you can also see them here in this brief view of Chillbrew. So you can do that. You can bring in data about any connected object. And so what I may need to do, like do some remodeling here of the structure of the brand, but that is generally as simple as adding a new field.

And you have a field type called the connection. And so I could connect brands to objects that are in the rest of the work front planning ecosystem.

So this is a similar question Chris Lou asked that, could we compare records from one workspace with another? It seems like that’s a yes, or you want to compare the budget of several PR line items with several event line items. The answer is yes, you could make that happen. You could make it happen through again that through that connection system. Maybe what I’ll do is I’ll set up, we’ll show you this one as well. Okay, so it’s often the case that teams are operating and then they have to contribute their value units to some higher level planning construct. And we didn’t talk about that in the demo yet, but I have a workspace where Frescopa is tracking its sort of like top level, its core marketing records, campaigns, tactics, and deliverables. So it might be that you want to ladder up that PR moment to a campaign and maybe you want to ladder up an event to the same campaign.

Again, this is going to take a little change in the way that this has been modeled to do that. And there’s different ways to approach it. Short answer is yes, you can do it. There are solutions that would involve fusion to sort of map those together into a different object model like you have here at the campaign level. There are other solutions that would rely on some features that we’re building that would actually be a subject of our next webinar. And those features would allow for better cross-workspace connectivity. So again, features that we could be talking about in the next June webinar, we’d love for you to tune in and come join that one. Again, I know we have limited time, but yeah, we have these cross-workspace connectivity features that are rolling out soon to help you with that. Amazing. And yeah, Andy already plugged it. So the event in June, which is available and you’ll get the link to it, is definitely going to spend a lot of time on the new features that are coming out in the release. Also, spoiler alert, we are, I would say, pretty close to getting you in to join us if you know you and you love you. And for the July event, for five ways that you can use Fusion with planning. So for those of you that are asking like how can I do all that, so we’re trying to get all of that. And with any luck, I’ll just hold your, everyone, I might get a customer to join us in August and say this is how we use planning. So this is what we’re trying to do in terms of upcoming. Okay, so I know we’re going to have about five more minutes for our questions. I don’t know if anyone wants to raise their hand, but I’m just going to keep going with the Q&A pod. And I think there’s always questions about how to either export data out of planning or how to use reporting. Do you want to talk a little bit about that, Andy? Yeah, so in terms of data export, that’s a feature that’s available in preview today. It’s not quite yet rolled out to production, but it’s coming out soon. And what you’d be able to do is come in here and then export these records. Let’s see, actually if I switch here to my preview environment, and let’s come here. Now I have the ability to export to file or CSV. So we’re really excited about this one coming out. We know that customers have been waiting for this for quite some time. And this is a very highly requested feature. So that is coming out. And part of what’s cool is that we also have the ability to create from create a new record type by uploading from a file like a CSV. So if you wanted to take all the goodness that a particular team had put together in their workspace and make it easier to sort of translate that to another team, the export and then the upload, the create a record type from uploading a CSV can help you with that process. That’s another thing that we’ve heard a lot about is like how do I duplicate the success of one team and translate that to another team? So that there’s a model there that helps make that simpler. I do want to touch on, there was a question in the pod earlier and I gave my two cents. So I’m just going to share with everybody, just as a reminder, when you’re selecting the team that you want to start fast and scale smart, obviously the business processes are really important, but I would also argue that choose wisely your team, a team that already communicates well, one that perhaps isn’t dysfunctional. I’m going to go ahead and use that because remember if you’re first getting started with planning with a team, you’re going to want that team that already knows how to kind of communicate back and forth of like, oh we need to try this or we need to try that or hey have you all looked at this. So you need that team that’s already sort of working well and collaborating that wants to jump in because they will also be the voice and the champion hopefully, hopefully the champion as you move forward. And I would argue that for workflow as well, like choose wisely that first team, but especially with this. So I just wanted to throw that out there as well. Just to add one little proof point to that one, Cynthia, internally at Adobe we had a team as you know, we are on our own adoption journey here as the product is still new and one of the early teams that raised their hands here to say hey we’re going to jump in there was our social team. Meanwhile, marketing operations was trying to figure out hey how do we go enterprise scale with this new product. So this is like the exact model that we ran internally. We had a team that adopted and they were able to get to value rapidly and that team started evangelizing what they were doing to the other teams in our marketing organization and those teams were like oh that’s interesting and they started leaving tools that were disconnected from the overall marketing operational ecosystem like again spreadsheets or powerpoints and coming in and bringing their operations into planning and they started to see oh now that we’re here we can start to use these early central metadata’s and taxonomies and now they are in a position where it’s going to be much easier to drive them into the next step which is blowing those plans down to the execution stage.

Amazing, I love it. I mean we all have experienced this of like teams gonna go I’m gonna go we’re gonna find our own thing so bringing them back is that’s just amazing to me. Okay so I’m gonna ask sort of there are two questions in here I’m gonna ask them together and then what we’ll do at the very end there’ll be a survey popped into the chat but also I’m gonna share with you all the upcoming events so that you’ll have that information as well. So the last question I kind of want to hit upon is when you’re creating the actual like the automation right I’m creating the actual project what does that handoff look like because you said you know obviously and folks he’s in the demo environment but if you were using a project template it’s just gonna you’re gonna create this project it’s gonna show up in workflow like it would always you know show up depending on what that template is what those tasks are right so it would end up in basically a connected record and planning and in workflow right. That’s right yes so let’s see let me let me walk through I’m gonna try to think if I ought to do another one maybe I’ll do Fresco global events and maybe you want to set up an automation to to trigger the events to be created oh actually sorry there’s this there’s a weird thing that happens when you transition from preview here back into production it’s how has it helped out live demos work isn’t it that’s that’s how they work okay so now this will work okay great so I was wondering where my manage automations button went if any of you encounter that when you’re using it it might be because you transitioned from preview to production okay so there is a button here that says manage automations and you click on that and now you can create new automation and you get to name your automation and then what you can do is you can choose to trigger actions based on things like button clicks and then you get to choose the action that will take place now actually I think like this isn’t working right now because I haven’t modeled that record out fully enough but if I come back to this one I can show you how this one oh you know what I’m getting a bug sorry about that and that’s okay because we can send out the documentation after I just like I knew that it was possible so I just wanted to so the answer’s yes I think someone else asked when are some of the new things like the exporting coming out and Andy that’s coming out with the key three release right that’s right so if you’re on the fast release schedule you’ll get it the next at the next monthly release which I think another one of our team members may have to remind me when that is and then if you’re on the quarterly release cadence then yeah it’s the key three release and that’s July 17th everybody we’re going to be doing a webinar on the 10th of July but yeah mark your calendars q3 release is July 17th this this time yeah Andy thank you so much I’m going to share I’m going to share my screen for a second if you don’t mind I’m gonna just give everybody some resources and what’s coming up the survey is pinned so please let us know let me tell you all while I’m waiting to bring this up what’s going to happen so I’m going to work on getting your follow-up email with the recording and the slide deck this afternoon and there’ll also be a post to experience Lee so I just want to let you know that’ll be this afternoon it’s just because there’s some meetings but we’ll get it we’ll get the survey link in the chat we have so many upcoming events including tomorrow is work front data connect so those of you that have been asking us questions in terms of reporting and canvas dashboards and all that stuff that is tomorrow so we also have a partner in product Matt Mitchell everybody should know Matt so that’s tomorrow and then down here you can see summoning success unlocking the latest work front planning and that’s here so it’s out on experience league you’re going to get the link please come back in June we’re going to talk about all these new features and we’ll have a host of different folks sharing some best practices on that and these are the resources there’s a lot of resources we posted them in the chat I think we posted them in the QA pod but we’ll also send them out in the follow-up email so please go check them out and I mean again as a standalone system admin having something an offering to my users like hey go in there and figure out your processes and then actually be able to use them as my test use case in office hours that would have been amazing amazing for me to have so I’m just gonna stop that and stop sharing and yeah thank you again Andy thank you all of my co-workers that are on you that joined out with the chat pod we appreciate y’all and Andy you’re gonna join us in June right June 26th you’re gonna be there with us yay all right this is fabulous thanks everybody and we want you to have a great rest of your week and we’ll see you next time thank you all everybody thanks bye bye