In 2003, Bill Gates—the founder, CEO, and richest man in the world—sat down at his computer to install Microsoft MovieMaker. He failed. Spectacularly.
You’ve probably felt this exact frustration. You try to update an app, it forces a reboot, you lose your workflow, and you wonder if you’re just bad with technology. You’re not. If the most powerful man in tech couldn’t install his own company’s software, the problem isn’t you. It’s the system.
The recently surfaced email thread from Gates is a masterclass in corporate absurdity. Gates tried to download Microsoft MovieMaker. Instead of a simple install, he was bounced around, forced to download unwanted garbage, and faced multiple reboots. When he fired off an angry email, the response from the team was legendary: “So they told me that using the download page to download something was not something they anticipated.”
Read that again. The team that built the download page didn’t expect users to use it to download things.
When the person with absolute authority can’t bend a download page to their will, the problem isn’t the page. It’s the company. Gates possessed god-like power inside Microsoft, yet he was powerless against the organizational silos that built the install flow.
The deeper issue here isn’t bad engineering. It’s the complete failure of “dogfooding”—the practice of using your own product. The install process mirrored internal team handoffs, not user outcomes. One team built the downloader, another built the installer, and nobody actually tested the end-to-end experience.
Look at the corporate deflection in the email thread. A guy named Mike Beckerman (who, ironically, went on to become a VP at TikTok) gave Gates a rambling, grammatically painful response that explained nothing and fixed less. Power without a working feedback loop is just a fancy title. Gates could fire anyone he wanted, but an executive tantrum couldn’t fix a system built around untested assumptions.
We see this everywhere today. Software updates that break your logins. Apps that force you into a labyrinth of settings just to delete your account. We’ve normalized software that hates its users because the people building it never have to feel the friction they create.
The next time you spend an hour fighting a login screen or a forced update, remember Bill Gates. Remember that he couldn’t install his own software. And remember that until executives are forced to feel the friction they create, nothing will change.
FAQ
Q: Wasn't this just a one-off mistake in 2003?
A: No. The thread reveals a systemic issue. The download team didn't anticipate downloads. That's not a bug; it's a broken organizational structure where teams build in silos and no one owns the end-to-end user experience.
Q: What's the practical implication for tech companies today?
A: Executives must dogfood. If the CEO can't use the product, the product is broken. Stop relying on focus groups and start forcing your leadership to use your software like a normal, everyday user.
Q: Isn't it just a funny story about Gates losing his temper?
A: It's funny, yes, but it's a terrifying indictment of corporate bureaucracy. Gates had absolute power and still couldn't fix a broken download page. If he couldn't, what hope do normal users have?