Skip to content
thebifule

Learning to Reflect Together

How a fortnightly retrospective grew from hesitation into a ritual the team came to own.

FOCUS
Team Culture
TIMELINE
2023 — 2026
PRACTICE
Retrospectives
OUTCOME
Psychological Safety
Illustration of a dense school of blue fish with a single orange fish swimming among them.

01 — THE BEGINNING

It began with hesitation

Our first retrospective didn’t begin with a conversation. It began with hesitation. As everyone gathered around the board, the room filled with questions instead of ideas — “What am I supposed to write?”, “Does this count?”, “I honestly can’t think of anything.” People picked up a sticky note, put it back down, and started over. It wasn’t that they had nothing to say; they were trying to find the “right” answer to a question that had no right answer. Looking back, they weren’t struggling to reflect — they were learning, perhaps for the first time, that reflection didn’t need to be perfect. It only needed to be honest.

WHY NOT ANOTHER MEETING

At the time, retrospectives were common in Scrum teams but not within our design team. We already had critiques, weekly syncs, project updates, and one-on-ones. What we rarely discussed was ourselves — how we were feeling, what made collaboration hard, what we had quietly learned, what frustrations kept repeating but were never spoken aloud. The problem wasn’t communication. It was that we had no shared space to reflect. So we decided to create one.

THE FIRST RETROSPECTIVE

A retrospective board covered in sticky notes.
A retrospective board covered in sticky notes.

02 — BUILDING THE RITUAL

Borrowing a ritual

We started with a retrospective every two weeks. The first few sessions were messy. Questions were met with long pauses; people picked up a pen, hesitated, then put it down again. It wasn’t that they didn’t care — they simply weren’t used to reflecting on their work this way. Sharing successes felt awkward, and talking about struggles felt even harder, especially in a room where everyone worked together every day.

SOMEONE HAD TO GO FIRST

As the facilitator, I realized that if I wanted honesty from the team, I couldn’t wait for someone else to create it. I had to go first — naming the uncomfortable things everyone could see but nobody wanted to say out loud: burnout, communication gaps, confidence quietly slipping away from someone who had been struggling for weeks. These conversations weren’t easy to start. But once they began, something changed. People realized retrospectives weren’t a place to judge each other. They were a place to understand each other.

BUILDING THE HABIT

A retrospective session in progress around a shared board.
A retrospective session in progress.

03 — TRUST GROWS QUIETLY

Trust grows quietly

Change didn’t happen overnight. It happened one sticky note at a time. The conversations grew a little longer. People started replying to each other instead of only answering me. Someone admitted a mistake. Someone thanked a teammate for helping them through a difficult sprint. Someone finally voiced a concern they’d been carrying for weeks. None of it felt dramatic — yet together, these moments slowly changed how we worked. Without anyone announcing it, psychological safety was quietly taking root.

THE RITUAL STARTED EVOLVING

After several months, retrospectives no longer felt like something I was running — they became something the team owned. People volunteered to facilitate and explored different formats depending on what the team needed. Around Christmas we focused on appreciation; at year-end we reflected on growth. When someone joined, we made space to get to know them; when someone left, we used a simple format — One Wish for You, One Wish for the Team. We rarely reused the same template. The purpose never changed. Only the conversation did.

ONE NOTE AT A TIME

A quiet, attentive moment during a team discussion.
A quiet moment during a team discussion.

04 — WHEN IT WAS WORKING

The moment I knew it was working

There wasn’t one big breakthrough — there were many small moments. People began seeing beyond their own work, noticing each other’s energy, confidence, and wellbeing. One retrospective, the team seemed to sense I wasn’t doing well before I ever mentioned it. Another time, someone raised a concern about a teammate — not to criticize, but because they genuinely cared. That was the moment I realized retrospectives had become something much bigger than a meeting. They had become part of our culture — not because I designed the perfect process, but because the team had learned to take care of one another.

WHEN THE TEAM TOOK OVER

As our retrospectives became more natural, we moved the cadence from every two weeks to once a month — not because they mattered less, but because they no longer needed constant nurturing. Eventually I wasn’t always the facilitator. Different teammates hosted the sessions, chose the activities, guided the discussions, and adapted the format to whatever the team needed. Watching that happen was surprisingly emotional. The ritual no longer belonged to me. It belonged to them.

THEY TOOK IT ON

A teammate facilitating a retrospective session for the group.
A teammate facilitating a retrospective session.

05 — REFLECTIONS

Reflections

People often think leadership means standing at the front and leading every conversation. I’ve learned that the best outcome is the opposite.

CARRYING THE LANTERN

For a while, I carried the lantern — I showed the path, started the difficult conversations, and kept the ritual alive while it still felt unfamiliar. But once the room was bright enough, it no longer mattered who held the light. The team found their own way. And that, I think, is what culture really is: not something a leader owns, but something a team chooses to keep alive together.

CHEERS, MAGIC

A closing, celebratory moment from the team’s retrospective journey.
A closing moment from the team’s retrospective journey.
“Leadership is creating something that continues even when you’re no longer the one holding it together.”
— on leadership