Académique Documents
Professionnel Documents
Culture Documents
IT Adoption,
Implementation and Use
Malabrigo, Evangerica C.
Stages Theory of IT Adoption
The stages theory, a set of concepts for understanding the assimilation of IT in
business organizations, was first proposed in the early 1970s.
In the early 1970s, most firms used computers for data processing.
As the next few decades unfolded, new IT and applications–MIS, minicomputers,
DSS, personal computers, expert systems, CAD/CAM, videoconferencing, and
others–were introduced to organizations.
As organizations “learn” how to utilize IT, they spend more and more money to
develop this capability. Expenditures accelerate into a growth period, then
decelerate and mature into slow-paced steady growth.
Stages Theory of IT Adoption
Stage I – Initiation
• Data-processing technologies are first introduced into an organization’s
administrative operations for automation of systems such as payroll or
accounts receivable
Stages Theory of IT Adoption
Stage II – Contagion
• Learning curve moves sharply upward as increasing numbers of
individuals or units adopt the technology, and as organizational members
experiment with new uses for it.
• Experimentation is more heavily emphasized than is efficiency.
• Management creates some organizational slack, committing more
resources than are strictly necessary to get the job done.
• With low control and high slack, adoption and usage grows rapidly, but at
the loss of some efficiency.
Stages Theory of IT Adoption
Stage III – Control
• By the end of stage II, the IT budget may be outpacing revenue growth, alarming
senior management. Managers “squeeze-out” slack by enforcing tighter control
through measures such as budget reviews and full chargeout systems.
• High control and low slack promote efficiency but inhibit learning, which may also
discourage diffusion of the technology to other organizational functions.
• Striking the proper balance between control and slack is a critical management
task.
Stages Theory of IT Adoption
Stage IV – Integration
• Management succeeds in striking a balance between slack and
control as the new technology becomes firmly integrated into
the company’s operational business processes.
Strategic consideration in
IT development
Functions of the Management
• Systems Development
• Operations
o Equipment Operations
o Productions Support
• Technical Support
o End-User Services
o Systems Programming
o Database Administration
Systems Development
Make or buy?
In-house development or commercial package.
SDLC Step 2: Project Initiation
Examples:
o Systems analysts
o Systems designers
o Programmers
Participants in Systems Development
(2) End Users
• those whom the system is built.
• During systems development, systems professionals work with the primary
users to obtain an understanding of the user’s problems and clear
statement of their needs.
Examples:
o Managers
o Operations personnel
o Accountants
o Internal auditors
Participants in Systems Development
(3) Stakeholders
• individuals within or outside the organization who have interest
in the system but are not end users.
Examples:
o Accountants
o External auditors
SOURCES:
• R. Schultheis & M. Sumner, “Management Information Systems The Manager’s View”, 3rd Ed,
1995
• https://trove.nla.gov.au/work/19430145?selectedversion=NBD4012171
• http://164.100.133.129:81/econtent/Uploads/MSIT-108-MIS.pdf
• https://bradybhunyamin.firebaseapp.com/management-information-systems-conceptual-
foundations-structure-and-development-mcgraw-hill-series-i-B01K92NH76.pdf
• https://scholar.google.com.ph/scholar?q=The+management+of+IT+adoption,+implementation+a
nd+use&hl=en&as_sdt=0&as_vis=1&oi=scholart&sa=X&ved=0ahUKEwje3JGV3s_aAhWBipQKHTQ
AB_wQgQMIJDAA
• https://www.pdfdrive.net/accounting-information-systems-9th-ed-e556379.html
• https://www.barnesandnoble.com/w/accounting-information-systems-james-a-hall/1100966279