Loading...
Loading...
A cultural clash during Microsoft and IBM’s OS/2 collaboration centered on a seemingly trivial UI decision: whether the TAB key should move focus between dialog fields. A Microsoft developer in IBM’s Boca Raton office chose TAB and, when IBM objected, was told by his Redmond manager that these local decisions were his responsibility. IBM escalated through several management layers seeking a like-level confirmation; their VP opposed TAB and wanted an equivalent Microsoft executive to weigh in. Th
A dispute over the TAB key between Microsoft and IBM organizational structures
A former Microsoft programmer recalls a culture clash with IBM during the OS/2 collaboration over a surprisingly mundane UI decision: whether the TAB key should move focus between dialog fields. IBM officials insisted the choice be escalated up their management chain and requested equivalent-level confirmation from Microsoft. The Microsoft engineer’s manager refused to intervene, saying his on-site staff were empowered to decide; when IBM demanded sign-off from a VP-level counterpart, the engineer quipped that "Bill Gates's mother is not interested in the TAB key," which ended the dispute and left TAB as the standard. The anecdote highlights corporate bureaucracy versus engineering autonomy and how small interface choices can become political.
A Microsoft developer assigned to IBM’s Boca Raton office fought a bureaucratic escalation over using the TAB key to move between dialog fields during the OS/2 collaboration. IBM managers repeatedly sought confirmation from Microsoft’s equivalent-level executives to approve the design choice; the Microsoft engineer refused to escalate, saying the local team was empowered to make such decisions. When IBM demanded sign-off from a high-level Microsoft manager, the engineer bluntly replied that Bill Gates’s mother wouldn’t be interested in the TAB key, which ended the debate and left TAB as the standard. The anecdote highlights cultural and organizational clashes between IBM and Microsoft and why decision autonomy matters in product design.
A cultural clash during Microsoft and IBM’s OS/2 collaboration centered on a seemingly trivial UI decision: whether the TAB key should move focus between dialog fields. A Microsoft developer in IBM’s Boca Raton office chose TAB and, when IBM objected, was told by his Redmond manager that these local decisions were his responsibility. IBM escalated through several management layers seeking a like-level confirmation; their VP opposed TAB and wanted an equivalent Microsoft executive to weigh in. The Microsoft reply — that even Bill Gates’s mother had no stake in TAB — ended the dispute, and the TAB key remained. The anecdote illustrates how differing organizational hierarchies and escalation practices can impede joint engineering work.