In IT, projects rarely go exactly as planned. Budgets shift, timelines slip, and priorities change. Yet even when a project isn’t delivered 100% successfully, there are still wins — lessons learned, milestones achieved, or processes improved. Recognising these “partial successes” can be just as important as celebrating a flawless project.
Recently, one of our clients shared a video interview question they use for Project Managers:
“Tell us about a project that wasn’t fully successful — how did you approach it, what wins were achieved, and how did you celebrate them?”
The responses were fascinating. PMs highlighted wins such as team learning, improved processes, stakeholder satisfaction with specific deliverables, and maintaining system stability under pressure. Even when the end goal wasn’t fully met, recognising these wins helped to build morale, trust, and a culture of continuous improvement.
Why Partial Wins Matter
Motivation & Morale
In fast-moving IT teams, focus is often on what didn’t go according to plan. Celebrating progress — even if the finish line isn’t fully crossed — shows that effort is valued. This recognition prevents burnout and keeps teams motivated through long or complex projects.
Learning & Growth
Every “almost-success” is a learning opportunity. Highlighting what worked and what didn’t fosters a culture of improvement. Teams feel empowered to experiment and innovate, knowing their contributions are noticed, even if the project outcome isn’t perfect.
Leadership Credibility
Leaders who recognise partial success are seen as fair, pragmatic, and empathetic. They build trust by acknowledging effort, resilience, and creative problem-solving, not just results. Over time, this strengthens the team’s cohesion and willingness to tackle challenging projects.
How IT Leaders Can Apply This
Here are a few practical ways to celebrate partial success in IT teams:
- Post-project reflections: Include a “wins & lessons” section in post-mortems to highlight achievements, not just gaps.
- Celebrate milestones: Even if the final deliverable isn’t complete, recognise small achievements — a successful module rollout, a key bug fix, or meeting a critical internal deadline.
- Recognise individual contributions: Call out team members who went above and beyond, even if the overall project had challenges.
- Share learning across teams: Use partial wins as a way to spread knowledge and best practices, turning setbacks into opportunities for improvement.
The Bottom Line
IT projects are complex, and perfection is rare. But recognising progress — even when a project isn’t fully delivered — builds stronger, more resilient teams. Celebrating partial success improves morale, encourages learning, and helps leaders build credibility with their teams.
Next time you review a project, pause and look for the wins hidden in setbacks. Celebrating them could make the difference between a team that survives and one that thrives.
