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. It is also standard practice in agile: the Agile Manifesto asks teams to reflect at regular intervals on how to become more effective, and the Scrum Guide makes the sprint retrospective a regular event.
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?
Quick Answer
A relationship retrospective is a short, regular conversation where a couple reviews what went well, what didn't, and one thing to change next week, borrowed straight from the agile sprint retro. It works because "let's talk about our relationship" is vague and scary, while "20 minutes on our weekly retro" is contained and specific. The format catches small friction early, before it compounds into resentment. It is free, and setup is a shared doc or a notebook with the date and the prompts; a weekly retro takes about 15 to 20 minutes.
TL;DR
- A relationship retro is a sprint retrospective applied to your relationship: what went well, what didn't, what we learned, what we'll change.
- The structure is the point — it makes hard topics safe by giving them a start, an end, and a shape.
- Start with what went well. It's not fluff; it shifts the whole conversation into a collaborative mood before you reach the hard part.
- One small change per week, done for months, beats one big talk per year.
- You don't need a Kanban board. A shared doc with the date and the prompts is enough.
What Does a Relationship Retrospective Look Like?
We've been running relationship retros for about six months. 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.
Try it: run a 15-minute version of this once this week. Set a timer, go through the four prompts in order, and stop when it dings. What made it stick for us was protecting the same slot every Sunday so it stopped being a decision and became a default. If four prompts and a parking lot feel like a lot to start with, our couples retrospective guide has a simpler three-question version.
Why Does a Retro Work 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. It is the same logic as a weekly relationship check-in, with the retro adding a "what did we learn" step.
What Have We 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. The Gottman Institute reports that stable, happy couples have five or more positive interactions for every negative one during conflict, which is the same instinct at a smaller scale.
Try it: at your next retro, name one concrete thing that went well before you touch anything that didn't — specific, not "this week was nice." We found the more specific the appreciation ("you handled the daycare call when I was underwater Thursday"), the more it actually landed.
How Do We Set Up Our Retro?
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. If you'd like a ready-made page to copy, try our relationship check-in template.
Why Do the Couples Who Make It Keep Running the Retro?
Continuous improvement 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.
When Is a Retro Not Enough?
A retro is a lightweight habit for catching everyday friction. It will not hold a serious rupture, broken trust, or anything that feels unsafe, and for those a professional is the right call (our list of things to try before, or instead of, couples therapy covers what sits in between).
If a retro keeps turning into an argument, put the topic in the parking lot and give it its own conversation, the way we describe in how to resolve conflict without hating each other.
FAQ
How is a relationship retrospective different from a check-in?
They overlap a lot — a retro is essentially a check-in with the agile vocabulary kept in. The retro framing adds two things: an explicit "what did we learn" step, and a parking lot for topics too big for the session. If "check-in" feels too soft and your brain likes process, the retro framing tends to land better. If your partner finds the work metaphor cold, just call it a check-in.
How often should couples run a retro?
Weekly is the sweet spot for us, same as a sprint cadence. Weekly catches friction while it's still small; monthly lets too much pile up between sessions. Some weeks ours takes ten minutes because nothing's surfacing, and that's a healthy week, not a wasted one.
Won't treating your relationship like a work project make it feel transactional?
It can if you import the cold parts — KPIs, scoring each other, performance language. The trick is borrowing only the structure (regular cadence, start with wins, one small change) and leaving the corporate tone at the office. Done right it feels less transactional, not more, because small things get heard before they curdle into resentment.
Related Reading
- Couples Retrospective Guide — Our complete guide to running relationship retrospectives
- Relationship Check-In Template — A ready-to-use template for your weekly reviews
- Weekly Relationship Check-In Guide — Building the check-in habit that supports continuous improvement