Conlee

"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.”"

"One thing Morrison didn’t get was Balsillie’s objections to talking about the company’s stock price, a ritual in most executive suites. Anyone caught talking about RIM’s share value was penalized. Balsillie didn’t want staff becoming complacent or distracted about company or personal fortunes. When Morrison sent Balsillie a congratulatory e-mail about RIM’s soaring stock price, he had to buy hundreds of donuts for RIM employees. Stock prices and quarterly results were precisely what Conlee believed needed more attention. He’d been hired to expand RIM “from millions to billions.” The company wasn’t going to get there unless it paid more respect to commercial details. That, the Texan knew, called for “a different culture.” Conlee invited RIM’s engineers to the Waterloo Inn to explain new marching orders. He introduced a detailed schedule of product milestones for Project Tachyon’s 5820 BlackBerrys, goals that would be enforced by a new product management office. Going forward, deadlines would be short and inflexible. All software features on the 5820 had to be completed within two weeks; for hardware design and beta-testing, the deadline was six weeks."