Bill Gates tries to install MovieMaker (2003)
436 points
• 7 days ago
• Article
Link
在 2003 年 1 月发给 Microsoft 高管的一封电子邮件中，Bill Gates 对 Windows 及公司网络基础设施日益恶化的可用性表达了强烈不满。他详述了一次下载 Windows Movie Maker 的失败尝试，把整个过程形容为长达一小时的折磨：网站响应缓慢、导航混乱、安装步骤难以理解。他批评系统要求不必要的重启，并在程序列表中出现一些莫名其妙的测试文件，称整个体验一团糟，反映出公司在关注用户需求方面存在系统性疏忽。
领导层迅速回应并承认这些投诉是合理的。 Will Poole 指出 Gates 的挫败感有其道理，强调必须明确责任人来修复公司网站、 Windows Update 以及操作系统本身。包括 Amir Majidimehr 和 Dave Fester 在内的其他高管开始协调，商定谁将负责解决这些反复出现的可用性问题，并认为这些问题应成为未来产品发布时的正式验收项目。
内部讨论揭示了更深层的结构性问题，比如通常掌控网站发布的营销团队与工程团队之间存在摩擦。 John Martin 指出，下载流程的混乱在很大程度上源于营销方面的疏忽，他主张公司应优先提供无缝统一的客户体验，将下载和安装视为一个直观连贯的过程，而不是一系列支离破碎的技术障碍。
来自 Ian Mercer 等团队成员的反馈还指出了 Windows Update 的具体不足，例如它无法有效向最终用户推广新功能，也无法提供简洁、非侵入性的软件更新路径。讨论凸显出公司内部各团队各自为政，导致用户体验不一致。最终，这次交流反映了 Microsoft 内部的一次自我反思，领导者们开始探讨如何重新组织工作，以确保连下载软件这样简单的任务也不会成为用户体验的败笔。
In a January 2003 email to senior Microsoft executives, Bill Gates expressed intense frustration regarding the deteriorating usability of Windows and the company's web infrastructure. Gates detailed a failed attempt to download Windows Movie Maker, describing the process as an hour-long ordeal characterized by slow website performance, confusing navigation, and an incomprehensible installation sequence. He criticized the system for requiring unnecessary reboots and cluttering his program list with obscure test files, labeling the entire experience an absolute mess that reflected a systemic lack of attention to user needs.
The response from leadership was swift and acknowledged the validity of his complaints. Will Poole noted that Gates's frustration was reasonable and emphasized the need to identify owners for fixing the company's websites, Windows Update, and the operating system itself. Other executives, including Amir Majidimehr and Dave Fester, began coordinating to determine who would be responsible for resolving these recurring usability issues, which they agreed needed to become a formal sign-off item for future product releases.
Internal discussions among the staff highlighted deeper structural challenges, such as the friction between marketing teams, who often controlled web releases, and engineering teams. John Martin pointed out that the chaotic state of downloads was largely due to marketing oversight, arguing that the company should prioritize a seamless, unified experience for customers. He suggested that downloading and setup should be treated as a single, intuitive process rather than a fragmented series of technical hurdles.
Further feedback from team members like Ian Mercer identified specific shortcomings in Windows Update, such as its inability to effectively promote new features to end-users or provide a streamlined, non-intrusive path for software updates. The conversation underscored a broader consensus that the company's internal teams were siloed, leading to inconsistent user experiences. Ultimately, the exchange reflected a moment of self-reflection within Microsoft, as leaders debated how to reorganize their efforts to ensure that even simple tasks like downloading software did not result in a failure of user experience.
295 comments • Comments Link
• 大型组织中的高层管理者常通过把问题推给委员会或把责任推给其他部门来逃避问责，导致问题永远无法从根本上解决的文化形成。
• 在大型公司中，组织失调很常见；各部门为争夺资源和权力互相竞争，造成孤岛化的环境，没有单一负责人拥有管理端到端用户体验的权力。
• 缺乏责任感往往导致表面化的修补，例如"篡改关键绩效指标"或掩盖症状，而不去解决导致问题的结构性或文化性失败。
• 当一位高层领导表达不满时，下级管理者往往会表现出一种表演式的狂热，急于修复特定症状以安抚领导，而不是对底层流程进行系统性审查。
• 当管理哲学鼓励内部竞争并实行排名时，大公司的文化可能适得其反，使有才能的员工专注于自我保护和地位争夺，而非产品质量。
• 有效的产品开发往往需要一位"直接负责的人"（Directly Responsible Individual），拥有弥合壁垒并强制执行统一用户体验的权力，但在臃肿的公司结构中这种角色常常缺失。
• 从简单的独立可执行程序向依赖大量依赖项的复杂软件交付转变，加剧了用户体验问题，使用户难以维护甚至理解其系统的状态。
• 不亲自使用自家产品的领导人往往失去识别明显缺陷的能力，这种脱节会一直存在，直到这些缺陷严重到威胁到组织为止。
• 虽然"暴君式"领导有时能强制推行高标准和清晰愿景，但这种风格通常会导致高流动率和有毒的工作环境，使那些重视协作与非对抗性工作氛围的人才感到沮丧。
• 公司功能失调并不限于大型企业；一旦形成了糟糕的管理习惯和缺乏问责制，中型企业和初创公司也会出现同样的问题。
反复出现的主题是，大范围的公司失败往往源于责任的系统性扩散，在这种情况下，组织结构把自我保全和部门政治置于用户需求之上。管理层经常诉诸官僚层级化，而不是解决根本原因，这强化了"学会无助"的文化，使得有意义的进展几乎不可能。虽然一些成功的公司靠市场垄断或惯性维持其统治地位，但长期代价是创新被内部摩擦与对终端用户彻底缺乏同理心所扼杀。 • Executives at large organizations often avoid accountability by delegating problems to committees or attempting to shift blame to other departments, creating a culture where issues are never fundamentally resolved.
• Organizational dysfunction is common in large firms where departments compete for resources and power, leading to siloed environments where no single leader possesses the authority to manage the end-to-end user experience.
• The lack of ownership often results in superficial fixes, such as "KPI hacking" or masking symptoms, rather than addressing the structural or cultural failures that caused the issues in the first place.
• When a high-ranking leader voices frustration, lower-level executives often react with a performative frenzy to fix specific symptoms to appease the leader, rather than conducting a systematic audit of the underlying processes.
• Large company cultures can become self-defeating when management philosophies incentivize internal competition and stack ranking, causing talented staff to focus on self-preservation and status rather than product quality.
• Effective product development often requires a "Directly Responsible Individual" with the authority to bridge silos and enforce a cohesive user experience, a role often lacking in bloated corporate structures.
• The shift from simple, standalone executables to complex, dependency-heavy software delivery has exacerbated user experience problems, making it difficult for users to maintain or even understand the state of their systems.
• Leaders who do not dogfood their own products often lose the ability to identify obvious flaws, creating a disconnect that persists until those flaws become so severe they threaten the organization.
• While a "tyrant" leader can sometimes enforce high standards and clear vision, this style often leads to high turnover and a toxic environment that discourages talent who value collaborative, non-adversarial workplaces.
• Corporate dysfunction is not limited to mega-corporations; it can manifest in medium-sized businesses and startups as soon as bad management habits and lack of accountability are established.
The recurring theme is that large-scale corporate failure often stems from a systemic diffusion of responsibility, where organizational structures prioritize self-preservation and departmental politics over user needs. Rather than addressing root causes, management frequently resorts to bureaucratic layering, which reinforces the culture of learned helplessness and makes meaningful progress nearly impossible. While some successful companies maintain their dominance through market monopolies or sheer inertia, the long-term cost is an environment where innovation is stifled by internal friction and a total lack of empathy for the end user.