Conlee Vacuum and Decision Drift
Books Teaching This Pattern
Evidence

Losing the Signal
Jacquie McNish and Sean Silcoff · 2 highlights
“Conlee’s responsibilities and title were split between handset chief Thorsten Heins and manufacturing head Jim Rowan, both of whom he had groomed, leaving Lazaridis with two chief operating officers; a third, Morrison, still reported to Balsillie. Lazaridis’s direct reports, including software head David Yach and chief information officer Robin Bienfait, met regularly with Morrison to ensure they were on the same page, “but nobody could stand up and say ‘Okay, all opinions heard, this is the decision’” as Conlee had done, says a former senior executive. “It slowed the company down. It was not that people didn’t perform in their roles; it was just purely the structure that was established did not lead to good, sound, and convergent decision making.” With Conlee gone, inertia and frustration set in at the senior levels. “There wasn’t the individual accountability that we needed,” says Morrison. “It was too splayed because it was across three different organizations. Now, all of a sudden, Mike is trying to manage something, but he doesn’t have the genetic code Larry has.””
“Yach charged his software teams to work on alternative plans. Two possible solutions emerged, neither of them ideal: Yach favored running the existing Java BlackBerry platform on top of QNX’s core technology in order to support existing apps. But many developers, including Alan Brenner, championed a different approach: tacking the BlackBerry interface on top of an Android operating system with QNX at its core. Android offered ready-made technology that would enable RIM to push out a new device to market quickly, with a running start in consumer apps, where Android was a significant player. But it would also mean apps developed for BlackBerry wouldn’t work anymore. By late 2010, Yach embraced a third option: combining RIM’s Java operating system with Android’s. Lazaridis wanted no Java on future BlackBerrys and was troubled by Android: he felt an Android BlackBerry would be less distinguishable from countless other smartphones and would be far less secure than the QNX or existing BlackBerry operating systems because Android was written using publicly available open-source code. Businesses were sure to reject it. Nevertheless, Lazaridis allowed the debate to play out for months. “There was no right answer,” says one engineer involved in the discussions. “You just needed to pick an option and run with it. There was more and more discussion about looking at options than making a decision. And making the decision wasn’t easy because ownership wasn’t there. I think the decision was clear in Mike’s mind: there was going to be a rewrite, done by brand-new people. It was probably the right decision. But the execution of that decision,” in the engineer’s view, “was done poorly.””