We make a pile of nearly fifty cards proposing changes to the Rainbow, Saturn, and Taser applications, and also changes to the network and certain shared databases, which could impact a significant portion, or even all, of the business. "Even looking at those cards makes my heart palpitate," Wes says. "These are some of the dangerous changes we make around here." He's right. I say, "Okay, let's mark all of these as 'fragile.' These are high risk and must be authorized by the cab. Patty, changes like this should be at the top of the pile during our meetings." Patty nods, taking notes saying, "Got it. We're predefining high-risk categories of change that not only must have change requests submitted, but must have authorization before being scheduled and implemented."