# How to Use the Authentic Connection Strategy to Create Effective Sprint Retrospectives in Education B2C
An education B2C startup running Lean with over fifty people has a retrospective problem. The company makes a language learning app for consumers. It uses spaced repetition, speech recognition, and personalized lesson plans. The company has been around for three years and has sixty-two employees. Fifty-four of them are in product development. (1/35)
The organization runs Lean with eight cross-functional teams of six to seven people each. The retrospectives are broken. They are stale, repetitive, and useless. A typical retrospective lasts sixty minutes and covers three questions: What went well, what did not go well, and what should we change. The same three questions every iteration for eighteen months. (2/35)
Half the team members do not speak. The other half say the same things every time. Communication was good. We need more testing. The deadline was too tight. The same three answers, every iteration, for eighteen months. Nothing changes. The same problems persist. The same bugs recur. The same deadlines are missed. (3/35)
Last quarter, the team identified the same three problems in every retrospective. Insufficient testing. Unclear requirements. Late code reviews. The three problems were identified across twelve iterations and never solved. (4/35)
Oprah Winfrey built OWN on the authentic connection strategy. The model was simple. She realized the biggest problem in television was disconnection. The host read from a script. The audience watched from a distance. That distance created apathy, and apathy killed ratings. (5/35)
Oprah attacked the disconnection by creating authentic connection. She did not read from a script. She spoke from the heart. That created vulnerability, which created trust, which created connection, which created engagement. The engagement built the show. (6/35)
She applied the same thinking to her interviews. When Oprah interviewed a guest, she did not ask scripted questions. She listened. Active listening created safety. Safety created openness. Openness created honesty. Honesty created the moment. The moment was the interview. The interview was the show. The show was the business. (7/35)
For this education B2C startup, the retrospective problem is the same. The retrospectives are disconnected. Team members do not speak from the heart. They speak from a script. The script is the same three questions. The same three questions create distance. The distance creates apathy. The apathy kills the retrospective. (8/35)
Oprah's authentic connection strategy says: create authentic connection. That creates vulnerability, which creates trust, which creates openness, which creates honesty, which creates change.
## The Core Principle
Oprah's strategy was built on a simple insight. The best way to create effective retrospectives is to replace scripted questions with authentic conversation that makes people feel safe enough to say what they actually think. (9/35)
Oprah did not ask her guests scripted questions. She listened. The listening created safety. The safety created openness. The openness created honesty. The honesty created the moment. (10/35)
This startup's retrospectives use scripted questions. The scripted questions create distance. The distance creates apathy. The apathy kills the retrospective. The fix is to replace scripted questions with authentic conversation. That creates safety, which creates openness, which creates honesty, which creates change.
## Four Steps to Apply the Authentic Connection Strategy
1. Replace the Three Standard Questions with One Open-Ended Prompt That Invites Vulnerability (11/35)
Oprah replaced scripted questions with open-ended prompts. The prompts invited vulnerability, which created authenticity, which created connection, which created engagement.
Replace the three standard questions with one open-ended prompt. For this startup, it might look like this. The scrum master asks: What is one thing that made you feel frustrated or stuck this iteration, and why did it feel that way? (12/35)
The prompt is open-ended. The openness invites vulnerability. Last iteration, the scrum master used the new prompt. One team member said, I felt frustrated when the product owner changed the requirements on day three. It felt like the goalposts moved. I had already built the first version and had to throw it away. Starting over felt wasteful. The waste felt demoralizing. (13/35)
That response was vulnerable and real. The realness created safety, which encouraged others to speak. Another team member said, I felt stuck when I could not get a code review for four days. I was blocked. The block felt like I was invisible. I needed help and no one was there. The invisibility felt isolating. (14/35)
The honesty produced a short list. Requirements changed mid-iteration. Code reviews took four days. Both items were real, specific, and actionable. The product owner agreed to freeze requirements for the first three days of each iteration. The development team agreed to review all pull requests within twenty-four hours. Both changes were implemented. Both problems stopped recurring. (15/35)
For a Lean team of fifty-plus, the prompt replacement should happen in every retrospective. The prompt should be open-ended and invite vulnerability. It should be treated as part of the continuous improvement process.
2. Start Every Retrospective with a Personal Check-In That Builds Psychological Safety
Oprah started every show with a personal check-in. The moment was real. The realness built psychological safety, which created openness, which created honesty, which created the show. (16/35)
Start every retrospective with a personal check-in. For this startup, it might look like this. The scrum master opens with a two-minute check-in using one question: On a scale of one to five, how are you feeling right now, and why? (17/35)
The question is personal. The personal nature builds psychological safety. Last iteration, one team member said, I'm a three. I'm tired. My daughter was sick this week and I did not sleep well. The tiredness affected my focus. I made more mistakes than usual. (18/35)
That response was personal and vulnerable. The vulnerability built psychological safety, which encouraged others to be honest. Another team member said, I'm a four. I'm energized. I solved a hard problem this week, the speech recognition bug. The solution felt good and carried into this week. (19/35)
The positivity also built psychological safety. The safe space made the rest of the retrospective more honest, which created better outcomes. The check-in took two minutes and improved the entire retrospective.
For a Lean team of fifty-plus, the personal check-in should happen at the start of every retrospective. It should take no more than two minutes and use one question. It should be treated as a process activity within the continuous improvement framework. (20/35)
3. Use a Silent Writing Phase Before Discussion So Introverts and Extroverts Contribute Equally
Oprah used a silent writing phase before group discussions. It gave every person time to think. That ensured introverts and extroverts contributed equally. The balance created better outcomes. (21/35)
Introduce a silent writing phase before discussion. For this startup, it might look like this. The scrum master sets aside five minutes of silence. Every person writes one thought on a sticky note in response to the prompt. The introverts write. The extroverts write. The writing is equal. (22/35)
After five minutes, the scrum master collects and groups the sticky notes by theme. Last iteration, the themes were requirements changes (six notes), code review delays (four notes), and testing gaps (three notes). The themes were visible, which created focus, which created structured discussion. (23/35)
The discussion started with requirements changes. The six notes were read aloud, creating context and understanding, which led to solutions. Freeze requirements for the first three days of each iteration. Require a change request form for any mid-iteration requirement change. The solutions were specific, which created action, which created change. (24/35)
The silent writing phase ensured the introverts contributed. They wrote six of the thirteen sticky notes, and those six were the most insightful. The insightfulness created better solutions, which created more change.
For a Lean team of fifty-plus, the silent writing phase should happen before every discussion. It should take no more than five minutes and be silent. It should be treated as a process activity. (25/35)
agile