Operations Review¶
Definition¶
The operations review is a regular (monthly, in Anderson's account), cross-departmental meeting where every manager presents their team's flow metrics — lead time, throughput, defect rates, flow efficiency — to an audience that includes senior management, upstream and downstream value-stream partners, and outside guests. Its purpose is to close the loop between measurement and action: data collected from the kanban system (chapter 12) is made public and discussed openly, rather than filed away, so that both successes and emerging problems become organizational knowledge rather than one manager's private concern.
In the Book¶
Chapter 14 narrates a specific ops review at Corbis, the fourth monthly instance, held at 8:30 a.m. at a downtown Seattle venue with about 80 attendees drawn from Anderson's and a colleague's organizations, plus the CIO and other senior managers. The meeting opens with company financials from a finance analyst — deliberately scheduled after the prior month's books close — "to remind everyone on the team that we are running a business." A guest VP from another department is invited to present, partly to build cross-functional interest and partly (practically) to sponsor the breakfast. Then each manager gets roughly eight minutes to present their team's metrics and take questions. Anderson tracks how the tenor of these meetings changed over four months: initial near-100% turnout and novelty ("I have never seen transparency like this in my career"), then routine appreciation, then by month three some grumbling ("Why do I need to get up so early?"). Month four turned genuinely engaged when the team had to publicly explain a real problem — an oversized, unbroken-down migration ticket for an acquired Australian subsidiary that clogged the kanban system and pushed lead time from 30 to 55 days — and staff were "amazed that we (the management) were willing to talk openly" about the failure.
Why It Matters¶
It shows what makes a metrics dashboard actually change behavior: a recurring, public forum with enough seniority and cross-functional reach in the room that problems can't quietly stay local, paired with genuine tolerance for surfacing bad news rather than only good news. This is the general shape of a functioning feedback loop at the organizational level — measurement alone doesn't produce learning; a standing occasion that forces the measurement to be discussed, and rewards honesty about failure, does.