 | 2010 |
| 13 |  | R. Ryan Nelson:
IT Project Retrospectives: Learning from the Past through a Program of Action Research.
AMCIS 2010: 475 |
| 2007 |
| 12 |  | R. Ryan Nelson:
IT Project Management: Infamous Failures, Classic Mistakes, and Best Practices.
MIS Quarterly Executive 6(2): (2007) |
| 2005 |
| 11 |  | R. Ryan Nelson,
Peter A. Todd,
Barbara H. Wixom:
Antecedents of Information and System Quality: An Empirical Examination Within the Context of Data Warehousing.
J. of Management Information Systems 21(4): 199-236 (2005) |
| 10 |  | R. Ryan Nelson:
Project Retrospectives: Evaluating Project Success, Failure, and Everything in Between.
MIS Quarterly Executive 4(3): (2005) |
| 1999 |
| 9 |  | R. Ryan Nelson,
Peter A. Todd:
Strategies for Managing EUC on the Web.
HICSS 1999 |
| 1997 |
| 8 |  | R. Ryan Nelson:
Peopleware: Emerging Roles and Responsibilities (An Interview with John F. Andrews).
DATA BASE 28(4): 16-18 (1997) |
| 1995 |
| 7 |  | R. Ryan Nelson,
Ellen M. Whitener,
Henry H. Philcox:
The Assessment of End-User Training Needs.
Commun. ACM 38(7): 27-39 (1995) |
| 1993 |
| 6 |  | Dennis A. Adams,
Peter A. Todd,
R. Ryan Nelson:
A comparative evaluation of the impact of electronic and voice mail on organizational communication.
Information & Management 24(1): 9-21 (1993) |
| 1992 |
| 5 |  | Dennis A. Adams,
R. Ryan Nelson,
Peter A. Todd:
Perceived Usefulness, Ease of Use, and Usage of Information Technology: A Replication.
MIS Quarterly 16(2): 227-247 (1992) |
| 1991 |
| 4 |  | R. Ryan Nelson:
Educational Needs as Perceived by IS and End-User Personnel: A Survey of Knowledge and Skill Requirements.
MIS Quarterly 15(4): 503-525 (1991) |
| 1988 |
| 3 |  | Paul H. Cheney,
R. Ryan Nelson:
A tool for measuring and analyzing end user computing abilities.
Inf. Process. Manage. 24(2): 199-203 (1988) |
| 1987 |
| 2 |  | R. Ryan Nelson,
Paul H. Cheney:
Educating the CBIS User: A Case Analysis.
DATA BASE 18(2): 11-16 (1987) |
| 1 |  | John A. Ricketts,
R. Ryan Nelson:
Management-by-exception reporting: An empirical investigation.
Information & Management 12(5): 235-246 (1987) |