Ways to Boost Morale During Long Tech Projects

Morale doesn’t collapse. It erodes. You don’t wake up to mutiny. You wake up to silence. No chatter in standup. No questions in training. No banter in Slack. Just reps going through the motions...quiet, compliant, and clocking out mentally by 2pm. This is what mid-quarter rot looks like. The deals aren’t dead. The team isn’t checked out. But something’s.....off. The engine is still running, but it’s out of torque. And lots of managers respond the only way they’ve been taught: - “Trust the process.” - “Pick up the phone.” - “Back to basics.” The problem there is that morale is much more of a momentum problem than a motivation problem. If you want to reset the team mid-quarter, stop yelling louder, and maybe just try to change the frequency a bit. Some ideas: 1. Take the emotional temperature. Before you fix the system, check the weather. Ask: - “What’s starting to feel pointless?” - “Where are we wasting time?” - “What do you wish we’d change...even if it’s minor?” You’re not looking for therapy, but you are trying to find friction. Morale doesn’t tank when things get hard, but it DOES tank when effort stops translating into progress. 2. Zoom in on the sparks. Forget the scoreboard. Find the bright spots. - One reply. - One call that turned into a thread. - One CMO who said, “Not now...but this is interesting.” Then break it down like game tape: - What channel? - What message? - What timing? Show the team there’s still signal in the system if they know where to look. 3. Change the scoreboard. “Meetings booked” works when reps are winning. When they’re not, it becomes a weekly reminder that they suck. So change the metric. - Conversations started. - Positive replies. - New contacts added to flows. Give them a scoreboard they can control. Not as a crutch, mind you. As a catalyst. 4. Inject constraint-based creativity. Monotony is the silent killer of sales teams. If every day looks the same, morale flatlines. So throw in constraints: - “Book a meeting using only LinkedIn voice notes” - “Re-pitch the same prospect in 10 words or less” - “Send a follow-up without a CTA” Why? You’re reminding reps that creativity matters. 5. Get in the trench. No one follows a manager who’s only seen the battle from a dashboard. So jump in. - Co-write an email. - Jump on a cold call. - Build a flow live on screen. When reps see you sweating with them, they start believing again. You don’t fix a mid-quarter slump with Slack gifs and a Starbucks card. You fix it by restoring a sense of cause and effect. Effort -> Feedback -> Progress. It's really, really not the grind that burns people out. They burn out when the grind feels meaningless. Inject meaning. Show movement. And make it fun again...even if just for a day. That’s how you turn a ghost-town sales floor back into a team.

If you’re not hitting pause, you’re failing your team. Momentum doesn’t come from endless forward motion. It comes from taking a breath, looking around, and saying, “Damn, we did that. Even when a project doesn't go so well...pause, celebrate, recalibrate... Here’s the play: 1. Call Out The Wins Be specific to one person at a time. Make eye contact. They need to know you saw them. “Your creativity turned this around when we hit the wall.” “You carried the emotional load no one saw but everyone felt.” “You kept us moving when things got messy.” 2. Mentor This is your shot to coach. To build. To lead. “The strength I see in you is…” “You’ve grown in ways that make this team better. Here’s how…” “One encouragement I have for you is…” 3. Make It a Moment Stop rushing. Hold space. Let the team soak in what they’ve done. “What’s one lesson you’ll carry forward?” “How has this project changed you?” 4. Set the vision for what’s next. But only after you’ve taken the time to recognize what got you here. Celebration isn’t fluff. It’s fuel. If you skip it, you’re leaving your team running on empty. Pull up a chair. Because a team that feels seen will run through walls for you.

If your team is underperforming, stop trying to fix them. Start building them up instead. I recently spoke with a Director who inherited an underperforming team with low morale and execution gaps. She had newer team members to develop, not deploy. But how do you invest in growth when the team is struggling? A pattern I've noticed: leaders think they choose between fixing problems and developing people. They don't. Developing people IS how you fix the problems. When morale is low, everything feels urgent. The instinct is to jump in and solve it yourself. But that keeps your team dependent and keeps you stuck doing their work. Building morale while developing capability means shifting from "I have to fix this" to "I'm going to build them up to fix this." Here's how: 1️⃣ Stop protecting them from reality. → Be honest about where the team is and why. Honesty builds trust. 2️⃣ Give them agency in the solution. → Involve them in identifying what's broken. When people feel heard, they're invested. 3️⃣ Celebrate small wins relentlessly. → When morale is low, people miss progress. You have to notice it for them. 4️⃣ Create clarity on what success looks like. → Be crystal clear about what good looks like and what you're measuring. 5️⃣ Give feedback in real time, not in reviews. → Say it immediately when someone does well or needs adjustment. Real-time feedback shows investment. 6️⃣ Make development visible, not separate. → Develop them in real work. It shifts from "they're not ready" to "they're getting ready." 7️⃣ Be the first to admit your learning curve. → You're new too. Model vulnerability. It gives permission for others to be imperfect. 8️⃣ Create psychological safety by asking before telling. → Before fixing something, ask: "What's your thinking?" Being asked signals you trust them. 9️⃣ Connect their work to something bigger. → Why does their work matter? How does it connect to customer outcomes or business strategy? 🔟 Give them room to fail in low-stakes ways. → If you're always catching them, they never build confidence. Let them make smaller mistakes and learn. Morale doesn't come back because you fixed all the problems. It comes back because people feel trusted, seen, and capable. When you shift from fixing the team to building up the team, morale follows. Your job isn't to do the work. It's to make them better at it.

A VP of Engineering told me a few months ago: "I'm thinking about quitting leadership and going back to being a senior engineer." Fifteen years of experience. Ready to walk away. Not because he was failing. Because he couldn't see himself succeeding anymore. Here's what he said: "Every day is fixing what's broken. Mediating conflicts. Explaining delays to executives. Watching my team struggle. I don't remember the last time I felt good about what I'm building." I asked him: "What went right this week?" Long pause. "I... don't know. Nothing major. The usual fires." "Okay, what small thing worked?" Another pause. "Jennifer caught a security flaw in code review before it hit production. Saved us from what could've been a nightmare." "Did you tell her?" "No. It's her job." That's the trap. Tech leadership without gratitude isn't just exhausting. It's invisible progress wrapped in constant crisis. You're solving complex problems. Managing people solving complex problems. Every win gets buried under the next fire. Here's what changed for him: I gave him one practice: Every Friday, document three moments that almost went unnoticed but mattered. Week 1: Junior dev caught logic flaw that would've broken invoicing Team shipped hotfix in 20 minutes (used to take 2 hours) Week 2: Engineers pushed back on impossible timeline. He backed them. Project got realistic scope. 2 AM production incident—three timezones collaborated, fixed it fast, nobody panicked Customer emailed: "Your API change saved us hours of manual work daily" Week 3: He texted me: "I'm not quitting. I was measuring the wrong things." The shift: He stopped counting problems solved. Started counting capabilities built. Gratitude isn't forced positivity. It's recognizing what's working before burnout blinds you to it. Three practices that kept him from walking away: - Catch micro-wins in real time. Screenshot that Slack thread where your team solved something impossible. Save the customer email. Take a photo of the whiteboard after a breakthrough. You'll need proof that progress is happening during weeks when everything feels broken. - Tell people when you feel it, not when you schedule it. Don't wait for quarterly reviews. Someone saves the deployment? Tell them now. Peer covers your meeting during an outage? Acknowledge it immediately. Gratitude expires. Don't let it spoil in your head. - Turn complaints into capability gaps worth solving. Tech leadership without this becomes a grind that burns out good leaders and fragments good teams. With it? You stay clear-headed enough to see what's working while fixing what isn't. That VP? Still leading. Team growing. Hasn't mentioned quitting again. Not because the fires stopped. Because he can finally see the progress between them. ♻️ Share this post if it reminded you of something worth appreciating ➕ Follow me (Phillip R. Kennedy) for more on succeeding in tech leadership without losing yourself in the process.

❌ Pizza won't motivate your developers. ❌ Beers won't motivate your developers. ❌ Unlimited snacks won't motivate your developers. ❌ Ping-pong tables won't motivate your developers. ❌ Fancy office spaces won't motivate your developers. Yet companies spend thousands on these things every year. And then wonder why their best engineers quietly quit. A great developer doesn't stay at a company because of free snacks. They stay because the work feels worth doing. So what actually motivates developers? 🎯 𝗔𝘂𝘁𝗼𝗻𝗼𝗺𝘆 → Let them make real decisions. → Stop micromanaging them. → Developers do their best work when they own what they build. 📈 𝗚𝗿𝗼𝘄𝘁𝗵 → Give them time to learn new things. → Let them use new tech in their projects. → Sponsor courses, books, conferences. → People stay where they feel like they're getting better. 💡 𝗣𝘂𝗿𝗽𝗼𝘀𝗲 → Show them why their work matters. → Connect their code to the real people it helps. → Nobody wants to spend years building something that feels pointless. When developers understand the impact of their work, they care more about the quality of it. 🤝 𝗧𝗿𝘂𝘀𝘁 → Stop tracking every hour. → Stop demanding daily status updates. → When you trust people, they want to do a great job. Trust is the foundation of a high-performing team. 🛠️ 𝗠𝗼𝗱𝗲𝗿𝗻 𝗧𝗼𝗼𝗹𝘀 → Give them fast machines and up-to-date software. → AI tools like GitHub Copilot or Claude remove friction. → Slow tools don't just waste time — they frustrate people every single day. 📌 Instead: → Remove micromanagement → Remove everything that slows them down → Focus on developer experience The goal is to build an environment that doesn't actively demotivate them. If your developers have no autonomy, no growth, and no trust, a pizza party won't make them stay. But when the foundation is solid? Perks amplify motivation that's already there. A team that feels trusted, challenged, and purposeful will genuinely enjoy the team dinner. Fix the environment first. Motivation will follow. Then the perks will actually mean something. What's the one thing that demotivated you the most at work? —— ♻️ Repost to help others build better developer teams ➕ Follow me ( Anton Martyniuk ) to improve your .NET and Architecture Skills

9 things I learned about motivating engineering teams & keeping morale high By making consistent mistakes over the last decade as a Principal Engineer Manager. 0. Protect focus time like production data. 1. Ask for input early; silence kills ownership. 2. Your mood sets the weather; show calm, earn calm. 3. Celebrate small wins; they stack into big momentum. 4. Feedback loses value if you delay it longer than a sprint. 5. Public praise, private course-correction, every single time. 6. Clarity beats charisma, explain why before you explain how. 7. Constraints inspire creativity; micromanagement smothers it. 8. Burnout isn’t a badge; enforce PTO the way you enforce code reviews. Still learning. Still iterating. But these ten keep my teams shipping, smiling, and sticking around.

As a Project or Program Manager, we are often the unofficial CMO — Chief Motivation Officer — for our teams. When it comes to motivation, one thing that truly boosts morale is  CELEBRATING WINS We often rush from one milestone to the next, chasing the bigger delivery. Sometimes, we are so busy that we forget the Wins. And here’s the truth: wins—big or small—deserve to be celebrated. And wins aren’t just about achieving a milestone or closing a project. They can take many forms:  -> Quantitative Wins – measurable outcomes (budget saved, timeline shortened, revenue impact, % efficiency improved)  -> Qualitative Wins – less tangible but equally powerful (stakeholder trust, client feedback, enhanced reputation)  -> Collaborative Wins – fostering cross-team alignment, breaking silos, creating synergy  -> Strategic Wins – aligning projects with organizational vision & long-term goals  -> Process & Innovation Wins – streamlining workflows, introducing automation, raising PM maturity  -> People & Growth Wins – mentoring, upskilling, and growing leadership within the team  -> Customer/End-User Wins – delivering solutions that delight, improve usability, and solve real pain points Celebrating these moments is not just about recognition. It’s about:  - Keeping team motivated  - Reinforcing great communication  - Building resilience during challenges  - Creating a culture of gratitude and belonging  As PMs, let’s not just deliver projects—let’s also celebrate the journey. Because it’s in those celebrations that teams feel valued, connected, and inspired to do even better.  Every win matters.  Every win motivates us!!!

11 Strategies To Boost Your Team's Morale This isn’t about perks but about trust and purpose. Burnout spreads faster than gossip. Quiet quitting starts with invisible neglect. Your team’s loyalty is earned, not bought. Fix the cracks before they break your culture: 1. Celebrate Small Wins Publicly ➜ Ignored progress fuels burnout. ➜ Start meetings with a “win wall.” 2. Offer Flexibility Without Strings ➜ Rigid schedules scream distrust. ➜ Implement “core hours,” then step back. 3. Invest in Growth (Even If They Leave) ➜ Stagnant roles = silent resignations. ➜ Fund courses, certs, or passion projects. 4. Ditch Micromanagement ➜ Hovering kills creativity. ➜ Swap daily check-ins for weekly goals. 5. Prioritize Mental Health ➜ “Unlimited PTO” means nothing if unused. ➜ Enforce “no-meeting Fridays” and model it. 6. Share the “Why” Behind Work ➜ Tasks without purpose = resentment. ➜ Start projects with a “purpose pitch.” 7. Gamify Mundane Tasks ➜ Tedium drains energy. ➜ Turn KPIs into team challenges. 8. Rotate Leadership Roles ➜ Junior voices = fresh perspectives. ➜ Assign a “meeting captain” weekly. 9. Be Transparent About Challenges ➜ Secrets erode trust. ➜ Host monthly AMAs with leadership. 10. Create Fun Rituals ➜ Forced fun backfires. ➜ Try trivia or “desk decor” contests. 11. Listen (Then Act) ➜ Surveys without action = morale poison. ➜ Share “You spoke, we did” updates. Morale isn’t a pizza party. Tag a leader who needs this. Culture is built daily; or eroded silently. ♻️ Repost this and spread the word. P.S. What team activity do you think is never needed?

𝗪𝗵𝘆 𝗮 𝗦𝗵𝗮𝗿𝗲𝗱 𝗦𝗲𝗻𝘀𝗲 𝗼𝗳 𝗣𝘂𝗿𝗽𝗼𝘀𝗲 𝗶𝘀 𝗘𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹 𝗳𝗼𝗿 𝗗𝗶𝗴𝗶𝘁𝗮𝗹 𝗧𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝗷𝗲𝗰𝘁𝘀 Truly successful ERP, CRM, HR, Payroll implementations don't just go live “𝙩𝙝𝙚𝙮 𝙨𝙩𝙖𝙣𝙙 𝙩𝙝𝙚 𝙩𝙚𝙨𝙩 𝙤𝙛 𝙩𝙞𝙢𝙚”. Successful projects usually have a team that is united by shared sense of purpose. However, this collective vision requires constant nurturing. As projects evolve, team composition changes and business priorities shift. There are many moving parts, which is why it is critical for the leadership team to always be communicating the reality of the situation and what the "win" will look like when you get there. And, most importantly, what everyone's role is in helping to achieve that goal. 𝗣𝗲𝗼𝗽𝗹𝗲 𝗙𝗼𝗰𝘂𝘀𝗲𝗱 𝗘𝗹𝗲𝗺𝗲𝗻𝘁𝘀 𝗼𝗳 𝗦𝘂𝗰𝗰𝗲𝘀𝘀𝗳𝘂𝗹 𝗣𝗿𝗼𝗷𝗲𝗰𝘁𝘀 Combined Management Consultants has extensive experience with complex, multi-month (and sometimes multi-year) implementations and we focused on the following elements: 1️⃣ Creating achievable milestones that allow for regular celebration of progress. 2️⃣ Limiting customization to strategic necessities, ensuring faster implementation and clearer focus. 3️⃣ Cultivating adaptability among staff, encouraging embrace of the system's native processes. 4️⃣ Proactively address resistance and cultural barriers before they jeopardize progress. 5️⃣ Identifying and mitigating risks early, meeting governance requirements while protecting the project. 6️⃣ Establishing psychological safety so team members feel supported and heard throughout. 7️⃣ Communicating relentlessly to build awareness and desire for change among all stakeholders. 8️⃣ Fostering collaborative relationships between vendors, staff, and consultants to maintain unified direction. 𝗠𝗮𝗶𝗻𝘁𝗮𝗶𝗻𝗶𝗻𝗴 𝗘𝗺𝗼𝘁𝗶𝗼𝗻𝗮𝗹 𝗠𝗼𝗺𝗲𝗻𝘁𝘂𝗺 The emotional trajectory of ERP and CRM projects often follows a predictable pattern. Users commence a project with initial enthusiasm followed by declining energy as challenges emerge. The projects that succeed maintain emotional momentum until completion. Leadership must therefore constantly monitor not just technical progress but team morale and engagement. Knowing when the project is veering off track and where to apply corrective effort is essential to bringing your implementation across the finish line with the benefits originally envisioned. What other techniques have you found successful?

Technology in distribution is moving at a blistering pace. We're constantly revving the RPMs into the red, pushing for continuous progress. Customers, partners, and employees depend on us, and there are always fires to put out. If you're not careful, you can find yourself like my car last week, with the gas light on, and with an empty tank. In that moment, you're not thinking about going the distance or doing anything fast, you're just worried about getting to a gas station (in my case, it's always Wawa). So, how do we go both FAST and FAR in what we're trying to accomplish? Yes, I'm a big fan of what technology is doing and will do - and AI a crucial part of the equation. But equally important? The human element. Here's how I work with my teams and clients to keep our tanks full so we can continue moving FAST while focusing on going FAR: 🎸Fostering a Culture of Riffing I love brainstorming sessions where team members share and build on new ideas. Insist on the "yes and" mindset - you'll be amazed at how it transforms your next meeting. 🏁Regular Strategic Pit Stops Pit stops might feel like slowing down, but they're key to maintaining speed and distance. Open talks, plan adjustments, and alignment checks prevent small issues from becoming big problems. 🏆Celebrating Wins and Learning from Losses Boost morale by acknowledging achievements, but don't shy away from analyzing setbacks - together, as a team. Turn failures into valuable learning experiences. 🗺️Maintaining a Clear Vision and Roadmap Keep your goals front and center. When everyone understands the direction and their role, it's easier to stay aligned and motivated for the long haul. In technology projects in distribution, you can keep making significant progress to stay ahead - without necessarily revving into red or feeling like you're driving on empty. This balance - between speed and endurance, between technological advancement and human ingenuity - is at the heart of what I call "Building Better Work." ---- If we haven't met yet, I'm glad you're here - I'm Nick 👋 I work at the crossroads of digital, distribution, and emerging leadership. I'm fueled by an insatiable curiosity to learn, share, and drive progress in everything I do. If you found this interesting, let's connect 👉🔗 for more of these discussions!