Communication Skills for IT and IS Professionals
This paper examines the growing importance of communication skills for information technology (IT) and information systems (IS) professionals. Drawing on research from Becker, Insley, and Endres (1997), Schulman (1975), and other scholars, it explores how decentralization of IS functions, the shift from hardware to software, and the rise of teamwork have made listening, writing, presenting, and interpersonal skills essential competencies. The paper also reviews survey data on perceived skill importance across job types, critiques traditional business school curricula for neglecting communication development, and outlines a proposed research timeline for further investigation. Data from Likert-scale surveys illustrate that most IS employees spend the majority of their working time engaged in some form of communication.
- Introduction: Communication as a Core IT Competency: Why communication became essential for technical workers
- Interpersonal Skills and the Teamwork Imperative: Team dynamics and IS employee collaboration requirements
- From Hardware to Software: The Human Element in Programming: Shift to software and human factors in productivity
- Survey Data on Communication Skills by Job Type: Likert-scale survey results across IS job categories
- Curriculum Gaps and Proposed Course Reforms: Business school failures and recommended communication courses
- Research Timeline and Methodology: Step-by-step proposed research schedule and methods
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- It synthesizes multiple scholarly sources to build a cumulative argument rather than relying on a single authority, giving the claim about communication's importance broad evidentiary support.
- The inclusion of quantitative survey tables (Likert-scale data by job type) grounds the argument in empirical evidence, making abstract claims about skill importance concrete and measurable.
- The paper moves logically from identifying a problem (neglect of communication in technical training) to examining causes, presenting data, and proposing curricular remedies.
Key academic technique demonstrated
The paper demonstrates effective use of secondary citation chaining — tracing multiple earlier studies (Finneran, 1994; Leitheiser, 1992; Crockett & Pastore, 1993) through a single synthesizing source (Becker, Insley & Endres, 1997). This technique allows the writer to survey a broad literature economically while maintaining proper attribution at each step.
Structure breakdown
The paper opens by establishing the practical necessity of communication skills in IT contexts, then narrows to interpersonal and team dynamics, followed by a theoretical discussion of the human element in programming. Two data tables anchor the empirical middle section, after which the paper critiques existing curricula and closes with a proposed research plan and timeline. This funnel structure — broad context to specific data to actionable recommendations — is characteristic of applied professional research reports.
Introduction: Communication as a Core IT Competency
Finneran (1994), as cited by Becker, Insley, and Endres (1997), stated that communication has become a necessity even for the most technically oriented personnel. As an example, he mentioned employees who provide user support and who require non-verbal and interpersonal skills in order to tailor their speech to the client's level of knowledge and understanding. The same author stressed the importance of presentation skills, which have become compulsory for technical employees.
Leitheiser's survey (1992) investigated managers' perceptions of technical, interpersonal, programming, and business skills. His research concluded that listening and writing were the most important competencies, and presentation skills also appeared near the top of the hierarchy (Becker, Insley, & Endres, 1997).
Other specialists have argued that communication has become critical for IT employees because of the decentralization of the information systems (IS) function. As a result, the centralized authority coordinating IS functions has disappeared, and IT employees have become responsible for interacting effectively with colleagues across different departments (Becker, Insley, & Endres, 1997).
Interpersonal Skills and the Teamwork Imperative
As Crockett and Pastore (1993) suggest, interpersonal skills have become essential as IS employees have evolved into "effective team players." This trend is clearly illustrated by Edward Schulman (1975), who, referring to the Integrated Semester course he teaches, emphasizes the importance of a socialization week during which students get to know one another and overcome ego and inhibition.
Organizations have recognized the value of synergy as well. To help ensure the success of a project, managers send the employees involved in its completion on activities such as a canoe weekend trip or a retreat to a remote mountain cabin. The rationale behind such initiatives is that by exposing all employees to the same challenging situation, the cohesive force that emerges among them will carry over into the framework of the project they must complete together (Becker, Insley, & Endres, 1997).
Researchers have also identified teaching methods that inadvertently encourage interpersonal hostility. In 1989, Simon observed that business schools did a commendable job of conveying technical information but fell short in developing students' communication skills — a finding that underscores the gap between technical training and professional readiness.
From Hardware to Software: The Human Element in Programming
Edward Schulman (1975) presents a compelling argument for the increased importance of communication skills in the IS field. He emphasizes that contemporary corporations have shifted their focus from hardware to software, the latter now representing the major expenditure of an IT firm. This shift has generated greater concern with program quality and programmer productivity — two goals that managers pursue by recruiting experienced professionals and training recent graduates.
Neither approach, however, has proved sufficiently effective, because managers have tended to overlook the human dimension of programming activity. Recruitment practices often rely on quantitative questions (e.g., "How many projects have you developed?") rather than qualitative ones (e.g., "Were those projects successful?"), leaving the social and interpersonal aspects of the work unexamined. As the Human Sciences and Technology Group (HST) has pointed out, the highest potential can be realized only by "studying and capitalizing on this human element and not trying to eliminate a certainty."
References
Becker, J., Insley, R., & Endres, M. L. (1997). Communication skills of technical professionals: A report for schools of business administration (Vol. 18, pp. 3–19). New York: ACM Press.
Gilberg, D. (2006). A CIO's guide to communication basics. Retrieved February 10, 2007, from
Guinan, P., & Bostrom, R. P. (1986). Development of computer-based information systems: A communication framework (Vol. 17, pp. 3–16). New York: ACM Press.
Nelson, R. R., Kathhan, M. W., & Cheney, P. H. (1991). Training, ability and the acceptance of information technology: An empirical study of IS personnel and end users (Vol. 13, pp. 20–32). New York: ACM Press.
Schulman, E. (1975). Continuing education of systems personnel: Improving communication across functional boundaries (pp. 58–71). New York: ACM Press.
Always verify citation format against your institution’s current style guide requirements.