reflecting on technology acceptance: lessons from commercial creative processes oasis 2004,...

5
Reflecting on Technology Acceptance: Lessons from Commercial Creative Processes OASIS 2004, Washington DC Oded Nov Polytechnic University, New York, USA [email protected] Rachel McCalla Henley Management College, UK E-mail: [email protected]

Upload: amice-warren

Post on 26-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Reflecting on Technology Acceptance: Lessons from Commercial Creative Processes OASIS 2004, Washington DC Oded Nov Polytechnic University, New York, USA

Reflecting on Technology Acceptance:

Lessons from Commercial Creative Processes

OASIS 2004, Washington DC

Oded Nov

Polytechnic University, New York, USA

[email protected]

Rachel McCalla

Henley Management College, UK

E-mail: [email protected]

Page 2: Reflecting on Technology Acceptance: Lessons from Commercial Creative Processes OASIS 2004, Washington DC Oded Nov Polytechnic University, New York, USA

Motivation

- Technology acceptance research dominated by the

Technology Acceptance Model (TAM).

- UTAM (Unified Technology Acceptance Model) - consolidates

key theories into one parsimonious model.

- Examine usefulness of TAM/UTAM in the context of industrial

creative processes.

- Four case studies of companies in the advertising industry

that use technology to support creative processes.

Page 3: Reflecting on Technology Acceptance: Lessons from Commercial Creative Processes OASIS 2004, Washington DC Oded Nov Polytechnic University, New York, USA

The advertising creative process

Page 4: Reflecting on Technology Acceptance: Lessons from Commercial Creative Processes OASIS 2004, Washington DC Oded Nov Polytechnic University, New York, USA

IS in the creative process

Page 5: Reflecting on Technology Acceptance: Lessons from Commercial Creative Processes OASIS 2004, Washington DC Oded Nov Polytechnic University, New York, USA

Discussion

- System functionality – rather than technology as one

homogenous factor.

- Functionality Acceptance - more appropriate than Technology

Acceptance?

- Look at functionality acceptance from two different

perspectives: direct ideation support vs. indirect ideation

support.