[SYMBOL] [A] [B] [C] [D] [E] [F] [G] [H] [I] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W] [X] [Z] Sagent Technology SAP as customer-driven company ScanMan [See Logitech ScanMan case study] scarcity thinking 2nd scenarios 2nd breadth versus depth constructing daily use 2nd necessary use 2nd 3rd 4th scheduling programs usability problems 2nd 3rd self-confidence in software 2nd self-referenctial design versus interaction design service companies 2nd 3rd Shared Healthcare Systems project "clinical vortex" 2nd personas Shared Heathcare Systems project personas programmers unification of system shipping products late 2nd short-term versus long-term thinking (managers) 2nd Silicon Valley, California skill levels 2nd [See also euphemism pyramid]3rd perpetual intermediates 2nd 3rd 4th 5th software bridging hardware to 2nd 3rd browser-based 2nd forgetfulness inflexibility 2nd installation 2nd lack of responsibility 2nd 3rd laziness user blame 2nd witholding information 2nd software apartheid 2nd 3rd 4th software design [See design] usability problems alarm clock 2nd ATMs 2nd causes 2nd 3rd costs digital cameras 2nd 3rd 4th file systems 2nd 3rd 4th IFEs 2nd 3rd navigational computers (airlines) 2nd Porsche Boxster 2nd Windows NT (USS Yorktown) 2nd software development process changing 2nd 3rd software engineers [See programmers] Sony Trans Com's P@ssport case study 2nd original interface 2nd personas 2nd 3rd 4th designing interface for 2nd 3rd 4th 5th source code versus vocabulary special cases specifying personas 2nd stereotyping personas sticky notes style guides 2nd Apple 2nd conflicts of interest 2nd Microsoft 2nd survivors 2nd Swiss Army knife cognitive friction of 2nd |