"Henceforth, a program manager would: 1. DESIGN UI'S 2. Write functional specs 3. Coordinate teams 4. Serve as the customer advocate, and 5. Wear Banana Republic chinos"
@Andrew Joel's description sure sounds to me like he was discounting the UI Designer. Otherwise....wouldn't he have mentioned us somewhere? And if the Program Manager and Developer are peers, than I imagine (if there is a UI Designer somewhere) it is beneath them...which I don't much fancy. On the one hand I take Joel's article as completely ridiculous. on the other, if I cross out "Program Manager" and add "UI Designer" it suddenly looks alot better, and I find myself identifying with the role for the most part and even taking notes... Some of the important points in the upcoming article "How to be a UI Designer" are: - 1 to 4 ratio of UI Designers to Developers - Work together a (IxD and Developers) and as peers - Imperative need for UI Designers to have knowledge of some coding - Making sure IxD isn't left out of the planning process and merely pulled in to gussy up the mess. - Importance of not designing in a box: going to meetings, email communication, and research to find out the needed info to make informed designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=39701 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
