Bill Gates tries to install MovieMaker (2003)
An internal 2003 email in which Bill Gates struggles to download and install Windows Movie Maker becomes a lens on Microsoft’s longstanding usability problems and organizational dysfunction. Commenters note how executives evade ownership, how siloed teams and perverse incentives produce disjointed user journeys, and how similar patterns still plague modern Microsoft products like Azure and ClipChamp. The thread also contrasts this with more “product-obsessed” leadership styles, arguing that culture and structure at the top ultimately determine whether large software companies can deliver coherent, user-friendly experiences.
Authenticity and Context of the Email
- Several comments focus on whether the Movie Maker email is real; the thread notes it appeared in evidence for a major antitrust/class‑action case and was produced in discovery.
- Some find the tone surprisingly harsh and self‑critical for a founder, but others argue executives talk very differently internally than in public.
Big‑Company Dysfunction and Lack of Ownership
- The email chain is read as a case study in “hot potato”: everyone tries to narrow their responsibility, push it to another group, or start a committee.
- Commenters note that no one clearly owns the “end‑to‑end user journey”; each small part has its own hierarchy.
- People connect this to known management patterns: internal competition, stack ranking, and incentives that reward politics and KPI‑gaming over product quality.
- Several argue that when fixing a problem requires cross‑org coordination, nobody wants to “own” it because they lack authority over all involved teams.
Leadership, Culture, and Responsibility
- Many blame the culture “from the top”: if the CEO/founder doesn’t consistently enforce UX quality and structural accountability, the mess is ultimately on leadership.
- Others respond that at this scale, a founder can realistically only “light fires” and give blunt feedback; solving root causes requires massive reorganization.
- There’s debate over what good leadership communication would look like: some defend the raw rant; others say it should acknowledge leadership responsibility and frame systemic fixes, not just symptoms.
Microsoft UX, Then and Now
- Multiple commenters note that the specific Movie Maker problems (confusing download paths, heavy Windows Update, forced reboots) feel unchanged in spirit: Azure, Windows support flows, captchas, and Clipchamp are cited as modern equivalents.
- Some argue Microsoft thrives financially despite poor UX because of enterprise contracts and deep embedding in organizations, not because of product quality.
Comparisons with Other Tech Cultures
- Apple under a product‑obsessed leader is contrasted with Microsoft; anecdotes describe ruthless but focused product decisions.
- There is pushback that being an “asshole” isn’t necessary for quality and can become outright abuse.
- A number of commenters say this thread explains why they prefer startups, mid‑sized “boring” businesses, or Linux/BSD over Windows.