'Good design' is sooo much more than the world view laid out in the article. For an organisation like MS, 50% of the job is defending a proposal against 'design by committee' and navigating group politics.
Don't get me wrong, it's a good article but only half the battle, if that!
One note has promise but it's clear that a lot of the design intent got ambushed as the product made it's way out the door.
Anyway "intuitive" is not a top priority if you're designing for power users.
But when you're designing for power users, sometimes it's more worthwhile to trade intuitive design for deeper functionality.
But intuitive design should always be the top priority, IMO - making something less intuitive in order to achieve power-user goals should be the exception, not the rule.
Just my $0.02, and you're free to tell me why I'm wrong. I'm not a designer, I just like using well-designed tools; and more often than not, the best tools behave exactly as you'd expect them to, and communicate intent pretty clearly and intuitively.
Looking at you, systemd folk.