How to Foster Team Buy-In for New Project Management Frameworks

I've seen PMOs designed in a way where teams & stakeholders ignore them. Not because the frameworks were bad. Because no one had involved them in building it. The typical approach: Build the framework. Roll it out. Then figure out how to get people to use it. Perfect PMO processes get created this way all the time. Beautiful templates. Clear governance. Everything documented. Then teams ignore them. The problem isn't that people resist change. It's that adoption gets treated like an afterthought. Most PMO teams spend 90% of their time designing the process. Then scramble to "sell" it to teams in the final 10%. By then, it's too late. Here's what actually works: Adoption isn't what happens after you build something. It's what you design for from the beginning. The most effective PMOs flip the entire approach: Start with the people who'll use it. Instead of asking questions and then disappearing to build, bring them into the design room. Build together from day one: ↳ They show you their current workflow, messy parts and all ↳ You bring lightweight structure options, not finished templates ↳ You prototype together, test with their real work, iterate fast The key shift? They're not giving feedback on what you built. They're co-creating what you're building. Not a comprehensive framework. Not a polished playbook. Just the minimum viable structure that solves their actual problem. The result? Frameworks that don't need training sessions to explain. Tools that people ask for instead of avoid. Processes that feel helpful, not bureaucratic. PMOs don't fail because people won't adopt them. They fail because they weren't designed to be adoptable. Want a PMO that actually gets used? Stop building first and hoping for adoption. Start designing for adoption from day one.

Part 3 of 3 — How to bring your team and stakeholders along for the ride (without sounding like you’re empire-building) In Part 1, I shared how to earn executive trust. In Part 2, I broke down how to bring peers into the vision. Now let’s talk about the most important group of all: Your team. Because if the people doing the work don’t believe in the vision — it won’t matter who else does. You can have the perfect strategy. Executive alignment. Cross-functional support. But if your team doesn’t feel ownership — it’s just another “thing from the top.” So I focused on turning passive agreement into real buy-in. Here’s what worked: 🔹 1. Co-create the narrative Before we agreed on a charter, we opened a conversation. We asked: • What’s working? • What’s missing? • What would you be proud to build? • What could we create 1 year from that you would be proud of? People engaged because they were shaping it — not just receiving it. They saw themselves in the story. 🔹 2. Make learning visible We didn’t just launch a strategy. We built capability. We brought in: • Experts on post-sale programs • Customers that experienced what it was like to be part of a real community • Operators who’d run adoption and success models • Coaches who guided our team through real problem-solving This made the strategy a career builder, not just a directive. 🔹 3. Spotlight early wins We celebrated the moments that showed the vision in action: - Wins on how we communicated effectively to GTM leaders - Celebrated team launches and rollouts - Every action that resulted in a positive outcome. - A Slack thread where someone said “This actually feels different” We created momentum. These weren’t vanity metrics. They were culture signals. The kind that tell people: “This isn’t just a shift in what we do — it’s a shift in how we show up.” 💡 The unlock? Your team doesn’t just want a mission statement. They want clarity, momentum, and a reason to care and feel valued towards a bigger purpose. You don’t get buy-in through compliance. You get it through contribution and storytelling. #Leadership #TeamBuyIn #StakeholderAlignment #ChangeManagement #TeamCulture #EmployeeEngagement #OrganizationalChange #PeopleFirst #StrategyExecution #ModernLeadership #customermarketing #customerengagement

Why most new systems fail, and how to get your team to actually use them... You can build the most detailed, foolproof process, but if your team doesn’t buy in, it’s all just paperwork gathering dust. I’ve seen it too many times: leaders roll out new systems hoping for instant adoption… And end up frustrated when nothing changes. Here’s what I coach my clients to do instead: ↳ Involve your team early. Before finalizing a system, ask your people how they currently do the work and what pain points they face. Systems built WITH your team, not FOR your team, get more commitment. ↳ Make the benefits clear. Don’t just say, “This is the new system.” Explain WHY it matters - how it will reduce their daily headaches, save time, or help the whole company grow. ↳ Start small and iterate. Roll out changes in bite-sized pieces. Get feedback quickly and adjust. When people see their input shape the system, they feel ownership. ↳ Train and support consistently. Don’t assume everyone “gets it” after one explanation. Provide ongoing support, coaching, and reminders, it’s how habits form. Getting your team to adopt new processes isn’t about enforcing rules…. It’s about creating a culture where systems are tools they want to use. What’s one system you’ve struggled to get your team to use? What happened? Share your problem in the comment section below, and I’ll help you solve it with a LinkedIn Systems Jam Session. This is exactly what I do; helping small business owners create systems their teams actually use, making work smoother and growth easier. #systems #leadership #business #strategy #ProcessImprovement

Getting buy-in is one of the most underrated UX skills and ironically, it’s the one thing most juniors avoid because it feels like selling. But here’s the shift: Buy-in isn’t persuasion. It’s alignment. And you can do it without being pushy, political, or manipulative. Here’s the simple blueprint I teach my mentees (and use myself): 1️⃣ Start with their goal, not your idea Instead of leading with “I think we should redesign…” start with: “What’s the outcome we’re trying to drive?” When someone feels heard first, they’re far more open to the solution second. 2️⃣ Show the problem, not your preference Skip the “I like / I don’t like.” Lead with evidence: A user quote A friction point Data that signals a drop-off A pattern you observed in testing This shifts the conversation from opinion vs. opinion → shared problem vs. solution. 3️⃣ Present options not ultimatums People resist when they feel cornered. Try: “Here are two paths we can take. Want to walk through the trade-offs?” Giving choice = giving ownership. And ownership = buy-in. 4️⃣ Connect your idea to business impact The fastest way to lose buy-in is to stay in “design land.” Make it practical: “This reduces onboarding time.” “This lowers support tickets.” “This helps us hit the Q3 activation goal.” Speak their language and the conversation changes instantly. 5️⃣ Invite pushback early Nothing kills momentum like a surprise objection at the finish line. Instead: “Before we run with this, what concerns do you see?” This transforms critics into collaborators. 6️⃣ Close with clarity Always end with one crystal-clear next step: “Do we feel aligned on path A?” “Is this the direction you’d like me to move forward with?” “What’s the priority for this sprint?” Buy-in without a next step is just a nice conversation. This is how you get buy-in naturally not through pressure, but through partnership.

Your VP said yes, and the budget's approved. So why is nothing happening? Because executive buy-in is not organizational buy-in. Your VP approved it, but their directors don't understand the why. Their managers don't know how to talk about it.  And the teams doing the actual work think this is another initiative that'll fall through in six months. Most leaders think their job is done after the approval meeting. But that's just the beginning. Because the people who need to change their behavior weren't in that room. They didn't hear your rationale or your data.  And without that context, they'll choose to wait it out rather than make a change. What you need is a Message Cascade System. Here's how it works: 💬 Step 1: Build your core message Get clear on three things before you talk to anyone else 👇 - What's changing and why it matters to them - What's in it for each stakeholder group - What you're specifically asking them to do 🕊️ Step 2: Identify your message carriers You can't be the only voice in every room. Find the leaders at each level who have credibility with the teams that need to change.  Ask: who will they actually listen to? ⚒️ Step 3: Equip them Don't assume they'll "just get it." Give them the talking points and answers to commonly-asked questions. Give them stories, not just data. Then permit them to say it in their own words. ✅ Step 4: Get their commitment Have individual conversations before you go broad. Ask for their commitment to reinforce it in their own team meetings.  Surface their concerns now, not in front of their teams. 🏁 Step 5: Run the roadshow as a listening tour Present the core message, then spend twice as long listening. Document everything you're hearing.  Adjust your talking points based on what's landing and what's not. 🔁 Step 6: Close the loop After the roadshow, go back to your message carriers. Share what you heard and update the language accordingly.  Give them what they need to handle the new objections that came up. This is the step most leaders skip entirely. If your change initiative isn't moving, ask yourself: who besides you is talking about this? If the answer is no one, you have a message cascade problem. Change happens when leaders at every level can explain it, defend it, and reinforce it in rooms you'll never enter. What's the hardest part of getting change to stick in your organization? Let's talk it through in the comments! ♻️ Repost to help a leader trying to implement change across their organization. And follow me, Cicely Simpson, for leadership systems that help you create organizational movement, not just executive approval. P.S. In LeaderOS, I help leaders navigate the art of persuading people even when they're not in the same room. Sign up here 👉 https://bit.ly/TheLeaderOS

Why 73% of Projects Fail and How I Stopped Losing Stakeholder Support Let me tell you a quick story. Years ago, I was leading an ops overhaul that was supposed to streamline internal reporting. Everything looked good on paper, timelines, budget, resource allocation. I checked every box… Except one: I didn’t fully engage the stakeholders who would actually use the system every day. 🚨Big mistake. Within 3 weeks of launch, adoption lagged, teams worked around it, and leadership questioned the ROI. That’s when it hit me—involvement doesn’t equal alignment. Just because stakeholders are informed doesn’t mean they’re invested. So I changed my approach. Here’s what I did: • Identified key influencers across departments, not just top execs, but daily users and frontline managers. • Used long-form discovery sessions to understand their actual pain points (not just the ones listed on a dashboard). • Built a feedback loop into every sprint cycle. Small changes. Real-time validation. • Created internal linkages between project goals and departmental KPIs (this one’s huge). The result? 🎯 41% faster implementation. ✅ 3X higher adoption in the first 30 days. 💬 Consistent stakeholder engagement from kickoff to post-launch. Why does this matter for you? If you’re a project manager, ops lead, or department head, especially in finance, tech, or healthcare, here’s your reality: 📌 You’re juggling timelines, compliance, and team bandwidth. 📌 You’re expected to “drive transformation” and still “not disrupt the day-to-day.” 📌 You’re measured by results but those results start with buy-in. So ask yourself: Are you just updating stakeholders or are you empowering them to shape outcomes? That’s the difference between a delivered project and a sustained solution. If you’re tired of rework, delays, or lukewarm adoption, start by rethinking how you engage your stakeholders. Involve early. Involve meaningfully. Involve often. ✅ Start with a 30-minute alignment session before you build your next project charter. ✅ Don’t just collect feedback—co-create the solution with the people who live it. You’ll thank yourself later. Let’s stop managing projects and start leading with people who matter. #ProjectManagement #StakeholderEngagement #LeadershipInAction

Struggling to Get Team Buy-In? Here’s What Worked for Me Getting buy-in on major projects isn’t easy; misalignment can delay timelines, lower quality, and create frustration across teams. I’ve been there, starting procurement from scratch in organizations where it was seen as a roadblock rather than a partner. But here’s the thing, buy-in isn’t about convincing people to follow; it’s about showing them the value you bring to the table. When done right, alignment isn’t just possible; it’s transformative. A Real Example: Starting Procurement From Scratch When I started building a procurement process from the ground up, I knew one thing, getting buy-in wasn’t optional; it was essential. The challenge? Many team members saw procurement as a barrier rather than a partner. My solution? Transparency, inclusion, and relentless focus on quality and timelines. Here’s what I did: 1️⃣ Invited Everyone Into the Process I made sure every stakeholder, from technical teams to leadership, was included in every key discussion. They saw firsthand how procurement could not only handle the commercial side but also support them in achieving their goals. 2️⃣ Aligned Goals Across Teams I showed how procurement wasn’t about taking over; it was about enabling them to focus on what they did best. For technical teams, it meant being in control of specifications and quality, while procurement ensured cost-efficiency, timelines, and compliance. 3️⃣ Kept Deliverables on Track Collaboration didn’t slow things down—it sped them up. By staying transparent about the progress and involving the right voices, we not only delivered on time but maintained high quality across every deliverable. The Lesson Building buy-in isn’t about convincing; it’s about creating alignment. When people feel heard, involved, and respected, they’re more likely to support the process and contribute to its success. Collaboration drives trust, and trust drives results. How do you build team alignment and buy-in on major projects? I’d love to hear your strategies and experiences. If you’re facing challenges with team alignment or building streamlined procurement processes, follow me for actionable insights or reach out to Rath Management Solutions, LLC. Let’s work together to achieve exceptional results. Who I Am I’m Melissa Rath, founder of Rath Management Solutions, LLC, with over 17 years of experience in procurement, contracts management, and project leadership. I specialize in creating collaborative environments that drive results, even on the most complex projects. Let’s connect and discuss how I can help your team thrive. #ProcurementLeadership #TeamAlignment #Collaboration #RathManagementSolutions #ProjectSuccess

Everyone talks about “getting buy-in.” But no one talks about what that actually looks like. You can’t force it. You can’t fake it. And you definitely can’t skip it. If you’re rolling out change and hitting resistance, ask yourself this: Have I earned their trust? Or just shared the plan? Here are 5 practical steps that helped me build real buy-in.  No begging.  No pressure. No performative alignment. 1️⃣ Listen First 2️⃣ Build Psychological Safety 3️⃣ Make It Theirs 4️⃣ Translate the Why 5️⃣ Celebrate Small Wins This is what it actually looks like to lead change. Strategically. Sustainably. Respectfully. Because if your team doesn’t trust the process, they won’t follow it. No matter how “strategic” it looks on paper. Save this. Share it. Steal the process if it helps. ➕ Follow me for more on project management. I break down how to lead with strategy, empathy, and a COO mindset (no matter your title).

Ever launch a “better system” at your nonprofit organization that somehow made everything harder? Let’s say your strategic plan includes this goal: “Improve our grant management process to increase efficiency and reporting accuracy.” Sounds clear enough. But if you jump straight into choosing platforms or rewriting workflows, you risk missing the real-world barriers that trip up your team. I’m building a service for first-time Executive Directors, and this strategy-to-action process was one of the places I stumbled hardest. Here's an approach I now follow, using three mental models to move from strategic intent to operational clarity, without wasting time, energy, or staff goodwill. 1. 𝗔𝗽𝗽𝗿𝗲𝗰𝗶𝗮𝘁𝗶𝘃𝗲 𝗜𝗻𝗾𝘂𝗶𝗿𝘆 (Start with what already works)    “Where in our organization do we already track, document, or follow up well, and what’s making that successful?”     You might find that your program team already uses a clear structure for reporting outcomes, or that finance has a reliable monthly review rhythm. Borrow those strengths. Avoid unnecessary reinvention. Build on what your team already trusts. 2. 𝗜𝗻𝘃𝗲𝗿𝘀𝗶𝗼𝗻 (Then flip the problem)    “If we wanted our new grant system to create more confusion, what would we do?”     Answers might include: • Use yet another platform • Assume everyone understands how to use it • Skip training and just send a login    Now you’ve surfaced hidden assumptions. You’re thinking like a realist, not just an optimist. And you’ve flagged areas where staff may get stuck. 3. 𝗣𝗿𝗲-𝗠𝗼𝗿𝘁𝗲𝗺 (End with specifics)    “It’s six months from now. The new grant process still isn’t being used as intended. What went wrong?”     Teams might say: • No one owned the data entry • The system didn’t integrate with our program calendar • There was no clear deadline structure    Now you’ve got actionable risks to address. You can clarify roles, timelines, and communication before rollout. You’re moving from concept to reality. 𝗣𝗿𝗼 𝘁𝗶𝗽: This works best as a team exercise. Give each model 15 minutes. Ask the question. Listen to the patterns. You’ll gain sharper insight and stronger buy-in. Strategic plans don’t fail for lack of intention. They fail when implementation skips the thinking. 𝗣𝗦: If you’re a first-time Executive Director (or supporting one) and would like to be added to my interest list (service launches July 15), reply or send me a message.

The mistake I made that tanked my programs early in my career: I built customer advocacy & marketing programs for stakeholders, not with them. I’d roll out something I thought was brilliant… only to watch teams ignore it and keep doing things their own way. It wasn’t that they didn’t care. It was that I hadn’t taken the time to understand their goals, their pain points, or the way they actually liked to work. Eventually, it clicked: buy-in comes from co-creation. If people help shape the process, they’re invested in making it work. Now, my “design with, not for” approach looks like this: → Start with conversations: polls, surveys, or 1:1 chats to uncover goals and friction points. → Gather feedback early: share the plan, get reactions, adjust. → Co-create the process: refine together so rollout feels collaborative, not imposed. → Pilot and champion: involve a small group early—when they believe in it, others follow. That shift changed everything. Instead of pushing uphill, my programs now launch with buy-in already baked in.