Hey there. Welcome back to Elevated. I'm Brandy Lawson, and in this episode we're working through what might be the trickiest part of any software implementation, getting your team excited instead of terrified. When you're announced we're changing our systems. I've seen some software rollouts that looked more like mutiny than improvements, the hard truth that most business owners miss. Software implementation. Isn't a technical challenge, it's a human one. Your team isn't resisting the software they're resisting. The uncertainty, disruption and fear of looking incompetent during the transition and no fancy features or efficiency gains will overcome those very real emotional barriers. So to overcome that very real hurdle to a better life, through software, we're creating a team communication plan that transforms resistant team members. Into enthusiastic champions because the difference between software that gathers digital dust and software that transforms your business isn't the features. It's in how you bring your people along for the ride. Getting your team on board requires a strategic approach across five key areas. First, timing and messaging. When and how you announce a software change dramatically impacts initial reception. Avoid the mistake of announcing a complete system overhaul right before your busy season. That kind of timing can create immediate resistance because everyone's already stressed out about deadlines. Yes, your communication plan should carefully consider when to introduce the change and how to frame it. The most successful implementations I've seen start with the why, the specific problems. This change will solve for your team, not just for the business. Don't say, this will improve our efficiency By 20% say this will eliminate those specification reports that keep you working late on Friday. Second, identify and leverage champions within your team. Every workspace has influencers who have opinions, carry weight with the colleagues. These aren't necessarily managers. They're often the go-to people. Others ask for help if possible, identify that person. Everyone naturally gravitates towards with software questions. There's usually one in every office. Then bring them into the software selection process early to help build natural internal advocacy. That way when the change is announced, there is someone on the team who's already familiar with the system. Excited about its potential and ready to be that go-to resource for their colleagues. This kind of strategy might seem obvious in hindsight, but is so often overlooked in the planning stages, and it's usually a win-win. The tech savvy team member gets to shine in the leadership role while their colleagues get the support from someone who truly understands their day-to-day challenges. Third, acknowledge and plan for the changing gears where the team is less productive as they adopt the new software. Performance and morale will temporarily decrease during the transition that's inevitable. Your communication plan needs to normalize this experience rather than treating it like a failure. Okay. One idea here would be to create a mistake of the week share during team meetings where everyone, even the owner can talk about their software blenders. This creates psychological safety during the learning curve. Fourth, create a personalized what's in it for me for different team roles. Your designers. Project managers and administrative staff will each have different concerns and potential benefits. An option here is to create a role specific one pager, highlighting how the new system solves specific pain points for each position. Finally, establish clear expectations and support mechanisms. Beg directives, like start using the new system are implementation killers. Your communication plan should outline exactly what's expected from each person. Buy when, and most importantly, where they can get help when they struggle. Let's explore how a kitchen design firm might structure their communication strategy when rolling out new project management software. Here's what a 30 day pre-launch communication plan could look like. So day one, opening the conversation. Consider starting with small group discussions, uh, skipping that impersonal email blast. Next, gathering team wishlist for improvements and acknowledging what's working well in current system. Then day seven, introduce your solution. The team might demo features that address top pain points. Share a potential timeline, introduce key players and peer champions. Day 14, make it personal, possibly organize role specific sessions, some hands-on previews, tailored to each department and have open forums for questions and concerns. Day 21. Setting learning expectations. This could include proposing training schedules, introducing potential support resources, and having honest conversations about learning curves, creating a no silly questions culture. Day 28, mapping the journey. The outline here might include a proposed timeline for phasing out old systems, suggested adoption milestones, ideas for celebrating wins along the way, because throughout this process, maintaining an open communication channel is critical. Team adoption hinges on addressing all questions, honestly, even the tough ones like, what if I struggle with the new system? With this kind of thoughtful approach, a team might not just adopt the new software. They could become enthusiastic advocates for it. Who knows? It might even become a selling point when recruiting new talent. This week, you can outline your team communication plan ahead of the next software change. Head to fiery effects.com/choose and download the worksheet. Start by answering these critical questions. Who are the key influencers on your team? Regardless of title, what specific pain points does this software solve for each role? What is your plan for the inevitable implementation dip? How will you create safety for questions and mistakes? And what does success look like at 30, 60, and 90 days? Remember, your team doesn't resist change. They resist being changed. When people feel ownership in the process and clarity about the benefits, they become partners instead of obstacles. Next week, we'll complete the implementation discussion by talking about training and support strategies that set everyone up for success beyond the initial launch phase. If this episode helped you rethink your approach to team communication around technology changes, share it with another design professional who might be struggling with team adoption.