Top 3 Reasons to Use Boards for Adoption

Transcript

Well howdy folks, it’s Cynthia Boone, your on-demand work front CSM here, and I wanna talk to you today about boards, but not just the features for boards, I wanna talk to you about boards for adoption. Now, if you have not had a chance to check out the boards feature, that is totally okay, I get it. Hopefully by the end of this video, I’ll have convinced you. So, top three reasons to use boards for adoption, let’s get into it. All right, so the number three, the number three reason we always talk about how busy our system admins are, and I know that, I lived that. Sometimes that’s a lot of work to configure new features, but boards is an easier entry level in to work front. It requires minimal configuration. What do I mean by that? Here’s the layout template. All I have to do, a system admin, add boards, click done. Now your users can access board, and it’s all on the users after that. So let’s go to the number two reason, the number two reason to use boards. Users wanna start using boards because they wanna see work in a way that makes sense to them. Do they need to know about Agile or Kanban? Absolutely not. There are boards templates to get them started. So what does that look like? The easiest one, in my opinion, is the retrospective template. They just click it, open it, and then they can just add cards. You can use retrospectives for one-on-one meetings, for post projects, for your team meetings, for looking back in the past year and planning for next year. Retrospectives are great. The next favorite to me is the basic board. It’s easy. You spin that up and people just start typing their to-do list into boards and moving them in a way that makes sense to them. They can also include their actual work within work front if they want. This board is a perfect example of that connected work to work front projects, but also just adding some cards of things that the user wants to track. So the user can do anything that they want to do and visualize it in a way that makes sense to them, which leads me to the number one way to use boards for adoption. As sysadmins, we are responsible for implementing new teams, getting everybody configured, and also tracking users in work front and whether they’re accessing it. Boards provides that fast access. So if you have a bunch of teams like I did that were waiting in the wings for me to get them into work front, this is the way to get them in. Give them boards and then they can wait for the larger implementation later. But what you get to do as a sysadbin, you get to track whether or not users are accessing into work front because that’s one of the things that we have to do. This work front usage dashboard, it’ll show, hey, people are accessing work front, even maybe they’re not fully implemented, I’m still getting users familiar with work front. And then what can I do? I can pin a project on their layout template, give them a little taste of what the project looks like, or I can hit them with a report. Once they start getting access and seeing what work front can do, they’re just gonna want more and we know that. If you want more information, we have a ton of information on Experience League, so many articles to get you started. We also have videos on the Experience League community, event videos, demo videos, anything that you’re gonna need, okay? So top three, I hope I’ve convinced you and I’ll see you next time.