agile2d ago

How to Use Digital Transformation to Create Effective Team Ceremonies

A family-owned entertainment marketplace running Lean with multiple teams of fifty-plus people has a team ceremonies problem. The company operates a platform connecting independent filmmakers with distribution channels and streaming services. It has been around for nineteen years, employs 340 people, and is still owned by the founding family. (1/33)

Show threadagile2d ago
The product development organization for the company's new content recommendation engine has 62 people across six teams of 10 or 11 each. The team ceremonies are a mess. Each team runs its own ceremonies with no consistency. That inconsistency causes cross-team coordination to fail. Failed coordination delays features that depend on multiple teams. Delayed features mean the content recommendation engine misses launch windows. Missed launch windows let competitors launch first (2/33)
Show threadagile2d ago

. When competitors launch first, filmmakers choose the other platform. That cost the company $162,000 last quarter. That was 36% of the quarterly revenue from the content recommendation engine.

The team ceremonies must be fixed. (3/33)

Show threadagile2d ago
Mukesh Ambani built Reliance on digital transformation. His insight was simple. The biggest problem in transforming a traditional business is the tendency to keep doing things the old way while adding new tools on top. That approach means the new tools don't work. When the tools don't work, the transformation fails. The company stays stuck. That kills it. (4/33)
Show threadagile2d ago
Ambani attacked the tendency to layer new tools on old processes. His transformation was based on one principle: digitize the foundation, then rebuild the structure. Digitizing the foundation meant putting a digital layer under every process. That gave every process data. Data made every process measurable. Measurability made every process improvable. Rebuilding the structure meant redesigning processes from scratch using digital tools. That made processes fast. Speed built Reliance. (5/33)
Show threadagile2d ago
When Ambani launched Jio, he didn't layer digital on top of old telecom infrastructure. He built new digital infrastructure from scratch. That made Jio fast. Speed generated data. Data enabled improvement. Improvement built Reliance. Ambani applied the same thinking to every part of the business, including meetings. He didn't add digital tools on top of the old meeting culture. He digitized the foundation and rebuilt the structure. Meetings became shorter and more focused. (6/33)
Show threadagile2d ago

For this entertainment marketplace, the team ceremonies problem is the same. Each team running its own ceremonies means there is no digital foundation. No foundation means ceremonies aren't measurable. If they aren't measurable, they aren't improvable. If they aren't improvable, cross-team coordination fails. That failure costs $162,000.

Ambani's approach says: digitize the foundation, then rebuild the structure. That fixes the ceremonies. Fixing the ceremonies saves time and money. (7/33)

Show threadagile2d ago
The Core Principle (8/33)
Show threadagile
The best way to create effective team ceremonies across multiple teams is to stop letting each team run ceremonies however they want and hoping coordination works out. Start by digitizing the foundation. Create a shared digital ceremony board that all six teams use to track their ceremonies in real time. Then rebuild the structure. Design a single standardized ceremony format that all six teams follow. That makes ceremonies visible, measurable, and consistent (9/33)
Jun 7 at 10:30amWeb
Show threadagile2d ago
. Cross-team coordination becomes a byproduct of shared ceremony data instead of a constant source of delays. (10/33)
Show threadagile2d ago
Ambani didn't create effective meetings at Reliance by letting each department run its own meetings and hoping for the best. He digitized the foundation by building a shared digital layer under every process. He rebuilt the structure by redesigning processes from scratch using digital tools. Every process had data. Every process was designed for the digital world. That built Reliance. (11/33)
Show threadagile2d ago

For this entertainment marketplace, each team running its own ceremonies costs $162,000. The fix is the same: digitize the foundation, then rebuild the structure.

Four Steps to Apply Digital Transformation to Creating Effective Team Ceremonies

1. Digitize the Foundation by Creating a Shared Digital Ceremony Board (12/33)

Show threadagile2d ago
Ambani digitized the foundation at Reliance so every process had data. Data made every process measurable. Measurability built Reliance. You should do the same by creating a shared digital ceremony board that all six teams use to track their ceremonies in real time. (13/33)
Show threadagile2d ago
The shared digital ceremony board might look like this. The Lean coach creates a shared Kanban board with seven columns. Column one is for team one, the algorithm team that builds the recommendation algorithm. Column two is for team two, the data pipeline team. Column three is for team three, the user interface team. Column four is for team four, the integration team. Column five is for team five, the quality team. Column six is for team six, the deployment team (14/33)
Show threadagile2d ago

. Column seven is for cross-team ceremonies involving multiple teams.

Each column has cards representing ceremonies. Each card has four fields: ceremony name, time, duration, and attendees. The board is visible to all six teams so every team can see what every other team is doing. That visibility improves cross-team coordination. (15/33)

Show threadagile2d ago
Last quarter, creating the shared digital ceremony board took three days. Once it was visible to all six teams, cross-team coordination improved. Cross-team ceremonies got scheduled. Features depending on multiple teams were delivered on time. That saved the company $48,000. (16/33)
Show threadagile2d ago

For a Lean team of fifty-plus, the board should have at least seven columns representing six teams plus cross-team ceremonies. Each card should have at least four fields. The board should be part of the team's visual management system.

2. Rebuild the Structure by Designing a Single Standardized Ceremony Format (17/33)

Show threadagile2d ago
Ambani rebuilt the structure at Reliance so processes were designed for the digital world. That made them fast. Speed built Reliance. You should rebuild the structure by designing a single standardized ceremony format that all six teams follow. Every ceremony should have the same structure, the same timebox, and the same purpose. (18/33)
Show threadagile2d ago
The standardized format might include four ceremonies. First, the daily standup. Fifteen-minute timebox. Three questions: what did I do yesterday, what am I doing today, what blockers do I have. Purpose: synchronize the team. Second, sprint planning. Ninety-minute timebox. Three parts: review the backlog for thirty minutes, select features for forty-five minutes, define acceptance criteria for fifteen minutes. Purpose: plan the sprint. Third, sprint review. Forty-five-minute timebox (19/33)
Show threadagile2d ago

. Two parts: demo features for thirty minutes, collect feedback for fifteen minutes. Purpose: get feedback. Fourth, retrospective. Sixty-minute timebox. Three parts: what went well, what didn't go well, what to improve. Twenty minutes each. Purpose: improve.

When all six teams adopt this format, every ceremony has the same structure, timebox, and purpose. That makes cross-team coordination easy. (20/33)

Show threadagile2d ago

Last quarter, designing the format took one week. Once all six teams adopted it, cross-team coordination became straightforward. Features depending on multiple teams were delivered on time. That saved the company $42,000.

For a Lean team of fifty-plus, the format should include at least four ceremonies. Each should have a timebox, a structure, and a purpose. The format should be part of the team's process design.

3. Digitize Cross-Team Coordination with a Weekly Thirty-Minute Sync (21/33)

Show threadagile2d ago
Ambani digitized coordination at Reliance so dependencies were visible and blockers got resolved. That built Reliance. You should digitize cross-team coordination by creating a weekly thirty-minute cross-team sync that uses the shared digital ceremony board to identify dependencies and resolve blockers before they cause delays. (22/33)
Show threadagile2d ago
The weekly sync has three parts. Part one is reviewing the shared digital ceremony board. Ten minutes. All six teams look at the board and see what every other team is doing. That makes dependencies visible. Part two is identifying dependencies. Ten minutes. Teams say which features depend on other teams. Those dependencies get documented. Part three is resolving blockers. Ten minutes. Teams say what's blocking them. Those blockers get documented and resolved (23/33)
Show threadagile2d ago

. Resolved blockers mean features aren't delayed.

Last quarter, the weekly sync ran twelve times. Dependencies were identified and blockers were resolved every week. Features depending on multiple teams were delivered on time. That saved the company $39,000.

For a Lean team of fifty-plus, the weekly sync should be thirty minutes with three parts. It should use the shared digital ceremony board. It should be part of the team's coordination rhythm. (24/33)

Show threadagile2d ago

4. Iterate with a Biweekly Feedback Loop

Ambani iterated at Reliance. Iteration made Reliance better. Getting better built Reliance. You should iterate by running a feedback loop every two weeks that reviews ceremony effectiveness across all six teams and updates the standardized format based on what's working and what isn't. (25/33)

Show threadagile2d ago
The feedback loop is a thirty-minute meeting every two weeks. Part one is reviewing ceremony effectiveness. Fifteen minutes. All six teams rate each ceremony on a scale of one to five. That shows which ceremonies are working and which aren't. Part two is updating the format. Fifteen minutes. The Lean coach changes the format based on the ratings. That makes ceremonies more effective. (26/33)
Show threadagile2d ago
Last quarter, the feedback loop ran six times. Two problems were found. The daily standup was rated two out of five. It wasn't effective. The fix was reducing it to ten minutes. That made it more focused. The next feedback loop rated it four out of five. The sprint review was rated three out of five. The fix was adding a feedback form so stakeholders could provide written feedback. That made it more effective. The next feedback loop rated it four out of five (27/33)
Show threadagile2d ago

. Fixing those two problems improved ceremonies and cross-team coordination. That saved the company $33,000.

For a Lean team of fifty-plus, the feedback loop should happen every two weeks. It should review at least four ceremonies. It should update at least one ceremony per month. It should be part of the team's process improvement practice.

Closing on Digitizing the Foundation Over Layering Tools on Old Processes (28/33)

Show threadagile2d ago
Mukesh Ambani didn't build Reliance by layering new tools on top of old processes and hoping it would work. He built it by digitizing the foundation and rebuilding the structure. He created a shared digital layer so every process had data. He redesigned processes from scratch so they were fast. He digitized coordination so dependencies were visible and blockers got resolved. He iterated so the organization kept getting better. (29/33)