Why technical writers should love Microsoft's Inductive User Interface is an overview and tech writer's take on this longer article from MSDN who on this rare occasion appear to be submitting a good user interface paradigm. The principle behind IUI is that most screens in a given application leave far too much un-stated, forcing new users to figure out what they are supposed to do. With IUI each screen has a purpose which is explicitely stated. So rather than having a page that lists all of one's accounts and the actions that can be performed they split it into two pages. The first page is titled "Pick an account to use", the second page would then let you act on that account. It's the same number of clicks but makes each step completely unambigious. And the reason tech writer circles are psyched is that it involves the writer early in the design process. If a page can't be clearly titled then there's a problem with the page and it gets re-worked. It shifts the writer earlier into the process where their skills might actually make a difference. Pretty cool if you ask me.
I've been trying to slide in a jibe at this chick who attempted to do some tech writing at work whom we have dubbed "Talkie" because she talks to much and won't shut up and is replacing someone who is moving to NY and is her superior in every way possible and the only reason that "Talkie" is still around is because someone has some shady deal going on with a recruiting agency, but I couldn't decide where to slip the jibe in, probably because it is such a long and heart-fealt rant that she who is leaving for NY should be replaced by somebody with the mental capacity to be a part of this high-caliber team, so, well, I guess there it is.
No comments:
Post a Comment