2 ms·
The explicit goal of the ribbon design effort was to better manage the complexity. Rather than simplify the underlying products. Such is the conceit of Microso
by specialist 7y ago
The explicit goal of the ribbon design effort was to better manage the complexity. Rather than simplify the underlying products.
Such is the conceit of Microsoft.
I watched the "The Story of the Ribbon". Twice. Just to be sure I properly understood what happened. https://channel9.msdn.com/Events/MIX/MIX08/UX09 https://channel9.msdn.com/Events/MIX/MIX08/UX09
It's a great example of a series of rational decisions yielding a terrible end result.
Because they started with the wrong question.
IIRC, Jensen Harris said Office (or maybe just Word?) had something like 2,000 (or 20,000?) individual operations (commands plus modifiers). Their initial premise was to better organize and present that dizzying number. Create the perfect visual language taxonomy.
Instead of first trying to figure how to reduce that number.
--
It's been a long, long time since I've used Microsoft products. I used to be quite the Word buff. But you'll get the gist of this example:
Embedding an image within a body of text is a common task. With Word, it just fucking sucks. There's an option for every little thing. Dozens of settings to tweak. And predicting where that image lands, especially with reflow, is more launch and pray than anything rational or deterministic.
But really, there's just 4, maybe 6. different ways any sane person would want that image to be anchored. Just show a preview of those options and let the user pick the result.
If someone needs something more fancy, they should opt to use a desktop publishing app, which is actually built for this kind of work.
But no.
Word has to be all things to all people. So consequently becomes nothing for anyone.
--
TLDR: Microsoft hates their customers.
- fowl2 7y agoas simple as possible but no simpler