Yach

"Brenner was unwilling to give up part of his responsibilities and didn’t get along with Tobin. It took them months to negotiate the transfer of responsibilities and executives; Tobin wanted to control project management and set the road map for what services and apps would be developed, but the two never reached an agreement and that role largely stayed with Brenner. “I think Alan assumed that my job was to market and sell whatever [apps and services] he wanted to build, and my instructions were that he needed to build to what I required,” says Tobin. “Because the roles and responsibilities weren’t clear, it created some conflict. Alan felt he was capable of handling the business side as well as the technology side.” Balsillie didn’t agree—he felt Brenner should stick to technology—and Lazaridis didn’t care; when Tobin tried to escalate the issue to both Balsillie and Martin, he was redirected to Yach, Brenner’s boss, who sent him back to work things out with Brenner. To many it made no sense to split the responsibilities between two people; it just caused confusion and gridlock. “Those two jobs aren’t really separate,” said McDowell. “Tobin wasn’t looking for Brenner to tell him what to do, and Brenner wasn’t looking for Tobin to tell him what to do.… The net result is a stalemate.”"

"Balsillie and Lazaridis never called each other out in the Tuesday meetings as relations between their organizations deteriorated. “They were mindful of how they were being perceived” and kept any disputes behind closed doors, says Patrick Spence, who by now was one of three sales vice presidents and Balsillie’s most trusted lieutenant. But tensions between the two CEOs were evident to others. Balsillie encouraged his salespeople to press on quality issues and would chime in, “Did you get that, Mike?” to which his co-CEO would tersely reply, “I got it.” The Tuesday noon grillings rattled Lazaridis. He felt blindsided and thought the salespeople were grandstanding. He would stop meetings when they raised quality issues and ask for more information. “What is it? Can you send me details? I need to understand,” he’d say. Lazaridis would leave the meetings steaming, then walk into a meeting with his direct reports and Morrison at 1:00 p.m. where he would let loose and demand answers. By early 2010, Lazaridis’s chiefs were telling their assistants to clear their Tuesday afternoon schedules in anticipation of long, difficult meetings with their boss. “I got the worst of it,” says Yach, an assessment shared by others. “After hearing about an issue for the first time at the Tuesday noon meeting, I’d immediately e-mail folks to get me background and updates in time for the one o’clock meeting. My most common thought [during the Tuesday meetings] was, ‘I miss Larry.’” Sometimes, Lazaridis says, his direct reports would tell him they were already well aware of an issue raised by Balsillie’s side of the house and dealing with it. “It bothered me that I was hearing about stuff [from salespeople] that I should have heard from the team that reports to me every week,” says Lazaridis. Morrison says, “It became evident [Lazaridis] was losing control of some of these problems and he wasn’t getting straight answers … [or] support from people he needed.”"

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