I'm about to challenge a project team to redefine an open position from
a software developer to an interaction designer. They are currently
looking for a person who can design a GUI and write code -- always a
tough position to fill.
I'm meeting with the team to convince them to go the ID route and not
require coding skills. However, I work in a very engineering-centric
organization where lines of code are *the* basis of productivity. The
team is about to embark on the development of a new version, though, so
the timing is right. Has anyone ever successfully made this case
before? What are your most persuasive arguments?
I look forward to the discussion.
Jay Zipursky | Tel: +01.604.451.2720 ext: 2204 | www.creo.com
Team Leader, Usability | Cel: +01.604.418.2238
Printing Workflow Solutions | Fax: +01.604.437.9891
3755 Willingdon Avenue | jay.zipursky at creo.com
Burnaby, BC V5G 3H3