The Slack notification came through at 10:47 PM on a Tuesday: "Retrospective moved to tomorrow, 9 AM sharp." My partner looked over my shoulder. "You do those every week at work, right? The meetings where you talk about what went well and what didn't?"
"Yeah," I said, already dreading another hour of sticky notes and forced participation.
"We should try that. For us."
I laughed. Then I realized they were serious.
Quick Answer
A couples retrospective is a short, regular check-in borrowed from how teams review their work: you sit down together on a fixed cadence and answer a few simple questions about how the relationship is going. The version that works for us is three questions — what made you feel close this week, what made you feel distant, and one small thing to try differently — done weekly, on the couch, no screens, appreciations before problems. It works as an early-warning system: it surfaces small drifts before they compound into a fight, without turning into therapy or a performance review.
TL;DR
- We run sprint retros at work, so we tried one for our relationship. The first attempt was a laptop-and-bullet-points disaster we abandoned for Thai food.
- The framework is useful; the corporate execution is not. It has to feel human or you'll quit.
- The format that stuck: three questions, weekly, couch and tea, no screens, appreciations first.
- The real payoff isn't big breakthroughs. It's catching "I felt a bit distant this week" before it becomes a month of resentment.
- It's a template, not a script. Change the cadence, the questions, the setting — keep whatever you'll actually do.
The Problem: We Talked About Our Relationship, But Never To Each Other About It
In a long-term relationship, you spend an enormous amount of time coordinating logistics (grocery lists, dinner plans, whose turn it is to take out the recycling) and almost no time actually stepping back to look at how things are going.
We'd have big "state of the union" conversations maybe twice a year, usually triggered by a fight or when one of us felt disconnected. The rest of the time? We just assumed things were fine. Or hoped they were fine. Or avoided thinking about it because we were both too tired.
Sound familiar?
Meanwhile, at work, I was running retrospectives every single week. Fifteen minutes to check in on what's working, what's not, and what we wanted to try differently next sprint. It wasn't rocket science. It was just... structured reflection.
Why wasn't I doing this at home?
Our First Attempt Was a Beautiful Disaster
We decided to try our first couples retrospective on a Sunday evening. I grabbed my laptop, opened a new doc, and even created sections: "What went well," "What could be better," "Action items."
My partner took one look at it and said, "Are you... taking notes on us?"
Fair point. I was treating our relationship like a project kickoff meeting. The whole thing felt immediately weird and corporate. We lasted about four minutes before dissolving into laughter and ordering Thai food instead.
What we learned: You can't just copy-paste your work process into your relationship. The framework is useful, but the execution needs to feel human, not like a performance review.
What a Couples Retrospective Actually Looks Like (After We Debugged It)
It took us three more attempts to figure out what worked. The format we landed on is nothing like what I do at work:
The Setup: Make It Feel Different
We don't sit at our dining table with laptops. We tried that. It felt like a meeting.
Instead, we do our retrospective on Friday evenings, on the couch, with wine or tea. No screens. Just a small notebook that lives on the bookshelf specifically for this. The ritual of pulling out that notebook signals: this is our time to check in.
Time commitment: 20-30 minutes, weekly. Some weeks it's 15 minutes. Some weeks it stretches to 45 if we have a lot to process. The consistency matters more than the duration.
The Three Questions (Our Version of "What Went Well" and "What Needs Work")
We simplified the classic retrospective format to three questions:
1. "What made you feel close to me this week?"
This is our "what went well" section, but framed as appreciation. The goal is to notice and name the small moments that worked.
Examples from our actual retrospectives:
- "When you made coffee without me asking on Tuesday morning"
- "The way you listened when I was stressed about the deadline"
- "That random hug in the kitchen on Wednesday"
Why this works: We're terrible at appreciating each other in the moment. This forces us to look back and acknowledge what's working before we jump into problems.
2. "What made you feel distant from me this week?"
This is the "what could be better" section, but less corporate-sounding. We're not looking for blame here — just honest observation.
Examples:
- "I felt a bit invisible when you were on your phone during dinner twice"
- "We barely talked beyond logistics this week"
- "I was stressed and took it out on you about the dishes"
Why this works: By asking about feeling "distant" instead of "what went wrong," we're focusing on our emotional experience, not creating a list of grievances. It's also okay to say "nothing made me feel distant this week." Some weeks are just good.
3. "What's one thing we want to try differently next week?"
This is our "action items" section. But it's ONE thing, not five. And it's something we both agree to try.
Examples:
- "Let's try having dinner without phones three times this week"
- "Can we do a quick check-in on Wednesday evening? I think we need a mid-week touchpoint"
- "I want to be more intentional about asking how you're doing instead of just 'how was your day'"
Why this works: One small experiment is achievable. A list of action items turns your relationship into a to-do list. We're not trying to optimize ourselves to death here.
The Rules We Added After Repeatedly Messing This Up
Rule 1: No phones We tried doing this while "multitasking." It doesn't work. Twenty minutes of full presence beats an hour of distracted half-listening.
Rule 2: No one is "in charge" I initially tried to facilitate like I do at work. My partner hated it. Now we just take turns starting each question. Some weeks one of us talks more. That's fine.
Rule 3: You can say "I need to think about this" If one of us is caught off guard by a question or doesn't have an answer, we don't force it. Sometimes the most honest answer is "I don't know yet."
Rule 4: The retrospective is not the fight If something comes up that needs a longer conversation, we note it and schedule time to talk about it properly. The retro is for awareness, not resolution.
Rule 5: We're allowed to skip it (but we track why) Life happens. If we skip a week, we ask ourselves why. Are we avoiding something? Are we genuinely too busy? Is the format not working? Missing a week is data.
What Surprised Us: The Retrospective Catches Problems Early
The biggest gift of the couples retrospective isn't the big breakthrough moments. It's the early warning system.
Three weeks ago, during our Friday check-in, my partner said: "I felt a little distant this week. I think we're both really busy and we haven't had much time to just hang out."
That's it. No big fight. No resentment building for months. Just an observation.
We blocked off Saturday morning for a hike. Problem caught, problem solved.
Without the retrospective? That feeling of distance would have compounded. By the time we noticed it consciously, we'd have been in a much worse place.
It's like running tests in production instead of waiting for the whole system to crash.
The Format Is a Template, Not a Script
What works for us might not work for you. Some couples we know do their retrospective over Sunday breakfast. Others do a monthly version instead of weekly because weekly feels like too much.
The core elements that seem to matter:
- Regular cadence (weekly, biweekly, or monthly — whatever you'll actually maintain)
- Structured questions (so you're not just staring at each other saying "so... how are we?")
- Appreciations before problems (always start with what's working)
- One small experiment (not a laundry list of improvements)
We created the Growing Us card deck partially because we wanted prompts that felt less corporate and more human. Some weeks we pull a card instead of using our three questions. Variety helps.
Practical Takeaways: Start Embarrassingly Small
If the idea of a "couples retrospective" makes you cringe (it made us cringe too), here's how to start:
Week 1 — Try it: ask only the first question. "What made you feel close to me this week?" That's it. Five minutes. See what happens. We deliberately did nothing else the first week, because adding structure too fast was what killed our first attempt.
Week 2 — Try it: add the second question — "what made you feel distant?" — only if Week 1 felt okay. Frame it as feelings, not grievances, so it doesn't slide into a list of complaints.
Week 3 — Try it: add one small experiment for the coming week. One, not five. The whole point is that it stays achievable.
You're not signing up for couples therapy. You're just trying a 20-minute check-in to see if it helps you notice patterns before they become problems.
We've been doing this for six months now. We've skipped weeks. We've had retrospectives where we both said "honestly, this week was just fine." We've had ones that surfaced things we needed to talk about more deeply.
But the consistent rhythm of checking in — of pausing to look at our relationship from a slight distance — has changed how we navigate hard things. We catch misunderstandings faster. We appreciate each other more intentionally. We experiment with changes instead of just hoping things improve.
Turns out, the retrospective framework that helps teams ship better products also helps relationships grow stronger.
Just maybe leave the Jira board out of it.
FAQ
What is a couples retrospective?
It's a short, regular check-in adapted from the retrospective meetings teams run to review their work. Instead of reviewing a sprint, you review your relationship: a few simple questions about what's working, what isn't, and one small thing to try next. The aim is structured reflection on a steady cadence, not a deep processing session or a substitute for therapy.
How often should we do a relationship retrospective?
Whatever you'll actually keep. Weekly works well as an early-warning system because small drifts get caught before they compound, but plenty of couples do biweekly or monthly. Consistency matters far more than frequency — a monthly check-in you always do beats a weekly one you abandon after three weeks.
What questions should we ask in a couples check-in?
Keep it to a few. The three that work for us: what made you feel close to me this week, what made you feel distant, and what's one thing we want to try differently next week. Always start with appreciation before problems — naming what's working first makes the harder question much easier to answer honestly.
How is this different from couples therapy?
A retrospective is a lightweight self-guided ritual for awareness and small course-corrections, not clinical work. It's great for catching everyday drift and building the habit of checking in. It is not a replacement for therapy when there's a serious rupture, broken trust, or anything unsafe — if a question surfaces something big, the move is to note it and schedule a proper conversation, or get professional support.
What if we keep skipping it?
Treat the skip as data, not failure. Ask why: genuinely too busy, or quietly avoiding something? Sometimes the answer is "life happened," and sometimes the resistance is the most useful thing the retrospective could have told you that week.
Want more structured check-in questions? We wrote a full guide to weekly relationship check-ins with 30+ prompts to get you started. Or try the Growing Us app — it's basically a retrospective tool that doesn't feel like work. Prefer the physical ritual? Start with the Growing Us card deck.