New Year, New Possibilities: Using Agile Retrospectives to Set Resolutions That Truly Matter

January is here, and with it comes the promise of a fresh start—a chance to reflect, reset, and reimagine what’s possible. As individuals, many of us embrace this opportunity through New Year’s resolutions, setting intentions to improve aspects of our lives. But how often do those intentions stick? And how often do they genuinely help us thrive?

For software development teams, the new year offers a similar opportunity to reflect on the past and set intentions for improvement. Agile retrospectives—a cornerstone of Agile and DevOps practices—provide the perfect framework for this kind of reflection. However, instead of simply focusing on what more your team can do, this year, let’s challenge the norm. Let’s explore how we can simplify, streamline, and remove friction to create a healthier, more energized environment for your team to thrive.

Resolutions: Doing More vs. Doing Less

Traditionally, resolutions focus on “doing more”: more productivity, more efficiency, more goals. But often, the key to genuine improvement lies not in adding more, but in stopping something or simplifying processes that no longer serve us. For teams, this could mean identifying practices, habits, or tools that create unnecessary friction or drain energy.

What would happen if your team approached this year’s resolutions not by asking, “What more can we do?” but by asking, “What can we stop doing to make room for what truly matters?”

Retrospectives as a Resolution Tool

Agile retrospectives already encourage teams to pause and reflect. By combining this practice with the philosophy behind New Year’s resolutions, teams can:

1. Identify what’s not working: Take an honest look at workflows, meetings, tools, or habits that slow your team down or create frustration.

2. Simplify and declutter: Ask, “What can we stop doing?” Eliminating redundancies can create space for more impactful work.

3. Set meaningful intentions: Instead of piling on more initiatives, focus on a few key changes that will yield the greatest impact.

4. Commit to sustainable growth: Resolutions aren’t about quick wins but about fostering long-term improvement. Align intentions with your team’s capacity and goals.

Using Data to Drive Change

Resolutions and retrospectives are only effective if they’re grounded in reality. To truly improve developer experience and team performance, teams need to consider both quantitative and qualitative data points:

• Quantitative data: Metrics like cycle time, deployment frequency, and defect rates provide a factual foundation for identifying areas of improvement.

• Qualitative data: Surveys, team feedback, and one-on-one conversations capture the human side of the equation, offering insights into morale, engagement, and areas of friction.

By combining these perspectives, teams can paint a comprehensive picture of their current state and identify the most impactful opportunities for change.

Building a Thriving DevEx Team Environment

The ultimate goal of any resolution or retrospective should be to create an environment where teams thrive. This means fostering a culture where:

• Teams feel valued and supported: Developers should feel excited about contributing to broader company goals.

• Workflows are optimized for energy, not just output: Simplifying processes can reduce burnout and increase focus.

• Continuous improvement is celebrated: Small, meaningful changes build momentum and contribute to long-term success.

Start Your Year With Purpose

As your team embarks on a new year, take a moment to reflect not just on what you can achieve, but on how you can achieve it. Use retrospectives to pause, learn, and take action. Let go of what no longer serves you. Simplify where you can. And focus on creating an environment where your team can bring their best selves to work every day.

Here’s to a year of clarity, focus, and meaningful progress. Let’s make it count!

And if you'd like to dive deeper into how to improve your Retro practices, tune into this episode of The Ojo Effect as a refresher to what they are, why they matter and how they accelerate your team's performance to learn faster, grow faster and go faster!