rituals

What Agile Teams Know About Relationships (That Most Couples Don't)

By Growing Us Team August 10, 2025 8 min read

Every two weeks at work, our teams run retrospectives. We look at what went well, what didn't, and what we'll do differently. It's continuous improvement, baked into the process.

One day it occurred to us: why don't couples do this?

We spend hours optimizing our work. We track sprints, measure velocity, analyze retrospectives. But our relationship? We wing it. We wait until something breaks and then scramble to fix it.

What if we applied the same intentionality to love that we apply to work?

The Relationship Retrospective

We've been running relationship retros for about six months. Here's the format we've landed on:

What went well this week? Celebrate the wins. What moments felt connected? What did we handle well? What made us feel like a team?

What didn't go well? Not blame — observation. What moments felt disconnected? What conflicts arose? What did we struggle with?

What did we learn? Any patterns emerging? Any insights about ourselves or each other?

What will we do differently? One or two concrete changes for next week. Small, specific, actionable.

Parking lot. Bigger topics that need their own time. Acknowledge them, schedule them, don't try to solve everything in one sitting.

Why This Works (When "Let's Talk" Doesn't)

The retro format works because it's structured. "Let's talk about our relationship" is terrifying and vague. "Let's spend 20 minutes on our weekly retro" is contained and specific.

Structure creates safety. You know what's coming. There's an end time. The format guides you through tough topics without getting lost in them.

It also normalizes continuous improvement. You're not retro-ing because something's wrong — you're retro-ing because that's what you do. Regularly. Like changing the oil in a car.

Most importantly, it catches things early. Small friction addressed weekly doesn't become major resentment addressed yearly. The cadence matters as much as the content.

What We've Learned From Our Retros

Patterns become visible. When you track what goes well and what doesn't, patterns emerge. We noticed we kept having friction on Sunday evenings — turns out we were both anxious about the week ahead and taking it out on each other. Once we saw the pattern, we could address it.

Small changes compound. "This week, I'll put my phone in another room during dinner." That's a tiny change. Done for six months, it transformed our evenings.

Naming isn't blaming. The retro format makes it easier to name issues without it feeling like attack. "Something that didn't go well: I felt dismissed during that conversation Tuesday" is different from "You always dismiss me."

Appreciation sets the tone. Starting with what went well isn't just positive-vibes fluff. It genuinely shifts the conversation. By the time you get to "what didn't go well," you're already in a collaborative headspace.

Our Retro Setup

We do ours Sunday evenings. Same time every week. We have a doc where we've been tracking our retros for months now — it's become a weird sort of relationship journal.

Some weeks, everything's fine and it takes ten minutes. Other weeks, something surfaces and we go longer. But we always do it. Skipping feels wrong now, like skipping brushing your teeth.

We don't use a literal Kanban board or anything that formal (though I've seen couples who do). We just have a simple doc with the date and our responses to the prompts.

The Meta-Lesson

Here's the thing about continuous improvement: it assumes you're never done. You don't "fix" the relationship and move on. You keep iterating. Forever.

This sounds exhausting, but it's actually liberating. You don't have to get it perfect. You just have to keep getting better. Small improvements, week after week, year after year.

Agile philosophy says: ship early, learn fast, iterate continuously. Relationships are the same. You're never shipping a final product. You're always in development.

The couples who make it aren't the ones who got it right from the start. They're the ones who kept running the retro.


Related Reading