The 'Good Enough' Email That Destroyed BlackBerry: How Mike Lazaridis Watched the iPhone Launch, Called It a Toy — Then Lost 77% of His Company in 4 Years

January 9, 2007. Moscone Center, San Francisco.

Mike Lazaridis, co-CEO of Research In Motion (BlackBerry), sat three rows from the front as Steve Jobs walked onto the Macworld stage. BlackBerry owned 50% of the smartphone market. Their devices were nicknamed "CrackBerries" because executives couldn't stop checking them. President Obama wouldn't give his up. Wall Street ran on BlackBerry Enterprise Server.

Jobs started talking about reinventing the phone.

Lazaridis wasn't worried. He'd seen "iPhone killers" before. They all failed because they didn't understand the one thing that mattered: enterprise email had to be instant, secure, and work everywhere. BlackBerry's push email architecture — where messages arrived in 15 seconds via their proprietary network operations center — was unbeatable. The battery lasted days. The keyboard was physical. IT departments loved the centralized control.

Then Jobs swiped to unlock the screen.

No stylus. No physical keyboard. Just a finger on glass.

Lazaridis leaned over to his colleague and whispered: "How's he going to type on that thing?"

The Architecture That Conquered Wall Street

To understand why Lazaridis was so confident — and why he was so wrong — you need to understand what BlackBerry had built.

In 1999, when everyone else was doing WAP browsers and SMS, RIM invented push email. Not "check every 15 minutes" email. Not "pull to refresh" email. Email that arrived on your device the instant it hit your Exchange server.

The architecture was brilliant:

BlackBerry Enterprise Server (BES) sat inside the corporate firewall, maintaining a persistent encrypted connection to RIM's Network Operations Center (NOC) in Waterloo, Canada. When an email arrived at your Exchange server, BES compressed it (often down to 10% of original size using proprietary algorithms), encrypted it end-to-end with Triple DES, and pushed it through the NOC to your device over a dedicated data channel that bypassed the carrier's network congestion.

The result? 15-second delivery, anywhere in the world, using minimal battery and bandwidth.

Compare that to everyone else in 2007:

• Windows Mobile: Pull-based email that checked every 15 minutes, murdered battery life, and required you to manually sync. Used ActiveSync over HTTP, which meant every poll was a full TCP handshake, TLS negotiation, and HTTP request — even if there were no new messages.
• Palm Treo: Similar pull-based architecture, better UI, same battery death spiral.
• Symbian/Nokia: Didn't even try. Email was an afterthought.

BlackBerry's keyboard was also unmatched. The QWERTY layout had been refined through 14 device iterations. Executives could type 60+ WPM blind in meetings. The tactile feedback, key travel, and layout spacing were obsessively tuned. You could clear your inbox one-handed while walking.

By 2007, BlackBerry had 12 million subscribers, $3 billion in revenue, and a market cap of $70 billion. Fortune 500 companies standardized on BES. Government agencies wouldn't use anything else.

Lazaridis believed the enterprise moat was unbreakable.

The Demo That Changed Everything

But then Jobs kept going.

He showed Safari — a real web browser, not the hobbled mobile browsers that rendered everything as plain text.

He showed Google Maps with multi-touch zoom and real-time traffic.

He showed YouTube. Visual voicemail. iPod integration.

And then he showed email. Not BlackBerry's instant push email. Just... email. That looked like desktop email. With HTML rendering, inline images, and attachments that actually opened.

It took 30 seconds to load. The on-screen keyboard was slow and error-prone. There was no enterprise server integration.

Lazaridis was relieved. "They don't get it," he told colleagues after the keynote. "Enterprise customers need security, speed, and reliability. They don't need YouTube on a phone with 4 hours of battery life."

He was technically correct. And strategically doomed.

The Email That Missed the Point

Three months after the iPhone launch, Lazaridis sent an email to RIM's leadership team that would later become infamous.

The subject line: "iPhone competitive analysis."

The body was a point-by-point takedown:

• Battery life: "4-5 hours talk time vs. our 4+ days standby"
• Keyboard: "On-screen typing is 50% slower than physical QWERTY in our tests"
• Email: "No BES integration, no encryption, consumer-grade push via IMAP IDLE"
• Security: "Can't be centrally managed by IT, no remote wipe, no device policies"
• Enterprise: "No support for VPN, no certificate-based auth, no split work/personal profiles"

His conclusion: "iPhone is a consumer device. Not a threat to enterprise."

Every single point was factually accurate. The first iPhone was terrible for enterprise. IT departments did ban it. Security teams did refuse to support it.

But Lazaridis made the same mistake every incumbent makes: he measured the iPhone against his customers' current needs, not against where the market was going.

The Turning Point: When 'Good Enough' Email Beat Perfect Email

The shift happened quietly, over 18 months.

Apple released the iPhone 3G in July 2008 with Exchange ActiveSync support. Suddenly, you could get corporate email on an iPhone — not via BES with 15-second push, but via Microsoft's ActiveSync protocol with 60-second push.

60 seconds vs. 15 seconds.

To Lazaridis, that was unacceptable. BlackBerry's entire value proposition was instant email.

But to everyone else? 60 seconds was... fine. Because now they had email AND a real web browser AND apps AND a touchscreen AND a camera that didn't suck.

The enterprise moat started cracking. CIOs who had banned the iPhone suddenly faced a new problem: executives were buying iPhones personally and demanding IT support them. The CEO wanted to check email on the same device where he read news and watched video.

RIM's response was the BlackBerry Storm in November 2008 — a touchscreen BlackBerry with a "clickable screen" (the entire display physically pressed down when you touched it, giving tactile feedback).

It was a disaster. The SurePress screen was laggy, the OS wasn't designed for touch, apps crashed constantly, and battery life was abysmal. Reviews were brutal. Verizon, RIM's biggest partner, privately called it "the worst phone we've ever sold."

Meanwhile, Apple released the App Store. By January 2009, there were 15,000 iPhone apps. BlackBerry's App World launched with 2,000 apps — most of which were enterprise productivity tools nobody wanted.

The Architecture That Couldn't Pivot

Here's what killed BlackBerry at a technical level: their entire system was architected for one thing — efficient email delivery — and couldn't evolve.

BlackBerry OS was built on a proprietary microkernel architecture optimized for message routing, not for running third-party apps. The UI rendering was single-threaded. The memory management assumed apps were small, ephemeral tools (calculator, memo pad) not full-featured experiences.

When developers tried to build apps, they hit walls:

• No real multitasking: Apps couldn't run in the background meaningfully. Push notifications didn't exist until 2011.
• Terrible dev tools: Development required Java ME or C/C++ with proprietary APIs. No modern debugging, no simulator that matched device performance.
• Fragmentation hell: BlackBerry OS 4.x, 5.x, 6.x, and 7.x all had different capabilities. An app for the Bold didn't work on the Storm. Screen resolutions were all over the place.
• Memory constraints: Devices shipped with 64-128MB of RAM because RIM's hardware teams optimized for battery life and email, not for running Chrome or Spotify.

Compare to iOS:

• Unix-based architecture designed from day one for third-party apps
• Cocoa Touch framework with rich UI components, Core Animation for smooth 60fps rendering, and Grand Central Dispatch for easy multitasking
• One SDK, one dev environment (Xcode), one App Store distribution model
• Memory management designed for complex apps — 128MB on iPhone 1, 256MB on iPhone 3GS, and developers had access to sophisticated tools (Instruments) to profile and optimize

RIM tried to catch up. They acquired QNX in 2010 — a modern real-time operating system — and started building BlackBerry 10 from scratch.

It launched in January 2013. Six years after the iPhone.

The Legacy: When Perfect Became the Enemy of Good Enough

By the time BlackBerry 10 shipped, it was too late.

RIM's market share had collapsed from 50% in 2007 to 3% in 2013. The stock fell from $230 to $10. Enterprise customers had switched to iPhone and Android with MDM (Mobile Device Management) solutions like MobileIron and AirWatch that gave IT the control they needed.

The killer irony? BlackBerry's email was still better. BES 10 could deliver messages in under 10 seconds. The Z10 had a phenomenal keyboard predictor. The security was unmatched.

But nobody cared anymore.

Because email had become just one app among dozens. And "good enough" email (60-second push via ActiveSync) plus a great browser plus a rich app ecosystem beat "perfect" email with nothing else.

Mike Lazaridis stepped down as co-CEO in January 2012. In his final interview, he was asked what he'd do differently.

His answer: "We'd have moved faster to touchscreen."

But that wasn't the real mistake. The real mistake was believing that enterprise customers valued email perfection over user experience. That IT departments would keep blocking devices users loved. That a 15-second moat could hold back a platform revolution.

Lazaridis was so focused on making email 4x faster that he missed the moment when email stopped being the reason people bought phones.

BlackBerry officially stopped making phones in 2016. The company pivoted to security software and automotive systems. The stock never recovered.

Today, when engineers talk about disruption, they talk about "good enough" technologies that win by being 10x better on a different axis. Cloud storage that's slower than local disk but accessible anywhere. Streaming music with lower quality than CDs but infinite selection. React that's slower than vanilla JS but 100x more productive.

BlackBerry's story is the reminder: being the best at the thing people used to care about is not a strategy. You have to see the pivot before your customers do.

The email that destroyed BlackBerry wasn't Steve Jobs' keynote announcement.

It was Mike Lazaridis' email to his leadership team, three months later, explaining why the iPhone didn't matter.

He was answering the wrong question. And by the time he realized it, the market had moved on.