Activating Field Teams - How to Run Decentralized Content Capture Without Bottlenecks

Hey. What's going on, team? It's Daniel Litwin, voice of b two b. I've got some tips here on how to ensure that when you decentralize content creation to your field teams, that you actually get decentralization to work for you. Something that we see often when we're working with customers and they say, hey. We wanna get our field teams creating content. This could be a sales team. It could be installers. It could be engineers. Right? It could be a field offices with their own, you know, small marketing team or small operations team. What we often see is that even though these are desired communities to bring to the content table, there's still a disconnect on what decentralization actually looks like in practice. And things tend to get bottlenecked around one main person, one HQ contact, one field creator rather than a whole team of five, ten, or a dozen. Right? So what ends up happening is that if one person owns all that video capture for a field team, whether it's the the capture itself or the uploading and processing of it, what happens when they get busy? What happens if they're out for a week? Well, your videos stop and decentralization stops. Right? Because it wasn't actually decentralization. It was one to one asks. So you need to distribute ownership if you really want field teams to keep content moving across all the locations where they work, and you can rely on MarketScale Studio as a platform to handle that. People can, be different user roles depending on how how much visibility they need in the platform. They can filter their channel media feed, based on, you know, their actual content, leveraging groups, right, if we build out groups for each of the field teams. So there are small ways, including folders, right, tagging content into different folders to make sure it's visible for the right team. These things help decentralize ownership without creating clutter and chaos, but you gotta start at the point of true decentralization. So let me give you some tips, and you guys can kind of follow along and take some notes here on how to run distributed capture without a single point of failure. Right? So again, the common mistake we see a lot is that we've got, you know, field teams being activated, but field capture requests run through one person. Right? Or like there's one coordinator or one creator that actually is gonna do it or something. Right? So nothing moves, and content stops scaling because it's living still with one person. We are centralizing responsibility. So my top tips are number one, make sure you've got at least one capture lead per field location. Right? This is not so that you have a central coordinator who's gonna assume all the responsibility. Rather, it's to create a social lead on the ground who's going to champion decentralization across your people. So you need that content champion, the creator you can rely on, the innovator who needs content for their day to day, and so you know they're gonna champion this. Again, this is not to centralize. It's to create a peer leader amongst a decentralized community. Right? That alone will begin to spread the good word of distributing ownership so that no one person ends up becoming the bottleneck. But you do need some of those champions. Now once you start asking field teams to send you content, if you create friction points, if you say, hey. Just capture what you can and upload it, the friction there is vagueness. It's too many options. Analysis paralysis. Right? So you wanna have location specific requests built out in MarketScale Studio so that the briefs, right, the prompts that you're posing to these creators are specific and targeted, and make it so that you could realistically get all ten or twelve or fifty, you know, sales reps in that region to actually send you install videos. Right? And this can look, again, very simple. You have the request tool in MarketScale Studio that lets you build out these requests. You can even templatize them and then just, you know, make small tweaks based on regional needs. Right? Templates over here, Or you could build out templates like these for regional activation, or you even have a template per region that you constantly deploy for different on-site projects. So let's create a new request here, right? You can title it something. So let's say, you know, Southeast region submissions, and this would be, you know, content for the Southeast region. We'll just kinda fill that in with Laura Mipsum. Check this out. You can add specific prompts here. Right? So let's say this is all for uploading, cause that's usually what we're looking for from field teams. Film something on your phone, send it to me. Right? So this could be as simple as upload your videos from today's install here. Easy. Required. Right? Well, click that. Now let's say we wanna get even more granular. We want this to also be an upload prompt, but this is asking, you know, something specific from them. Answer in ninety seconds or less. Right? What was the scope of today's installation? What problem did we solve for customers? Nice. Right? So you can both give kinda generic but frictionless direction on where to get you the content you need so that you can get this to a dozen different creators and everyone have the same logical simple experience. You can also add these kinds of more specific prompts that get your people creating content, and you get that prewritten direction for them without leaving so much to kind of vague confusion or reinterpretation or as we really know, in the moment reasons not to do this. Right? Lay it out clear for them. So, you can build these out, save them as a template, or just launch them to your team. Right? Now another thing here is that you should be setting deadlines and publishing cadences. Right? This helps make it so that even if you do decentralize across a lot of people, you are building the standards for the operational environment where this content is being created. Some of this is just gonna be you setting these best practices with your people. That's kind of inevitable. Right? However, you can also build some of this infrastructure in MarketScale Studio leveraging the same survey tool as well as tasks in the platform. Right? So you can set a close date for your request. That is gonna make it pretty clear when folks have to get their content in by. So let's say Saturday the fourth. Right? Or you could be using the task manager tool in the platform up here, right, to set specific tasks and responsibilities for different people. You could even build out a playbook specifically for, you know, on-site regional content capture. You know, let's say it's I'm going to do this, field engineering. Right? Okay. Well, this playbook already exists, and check it out. It's got all these checklist subtasks already built out. So if you're deploying the same kind of strategy, the same kind of content capture asks, If the workflow's gonna basically look the same every time you tell a field team, I need you to send me some content, leverage these templates to make the responsibilities clear and the timelines clear so that nothing is left to confusion and that confusion doesn't become a reason or the kind of decentralized chaos of everyone kind of having their own layer of ownership and responsibility, that being the reason things don't get done. Centralization, again, is attractive. It's all, you know, in your hands. You can control the variables. But what happens if the person holding all those variables drops the ball or can't handle all those variables? Then everything stops in its tracks. So those are my, pieces of advice for y'all here. Right? If you really wanna get your field teams creating, make sure you're running a true decentralized campaign of content creation and submission. And, again, you can get all your people added right here. Invite your users as standard or guest users, depending on what kind of field team they are. Get their emails in here. Get them in Studio, and take advantage of all the tools you have here to orchestrate decentralized content creation. There you have it, folks. That's what I've got for y'all today. Good luck out there, and let's get those field teams creating. Can't wait to see what you cook up.