ISYS90026 · Concepts In Information Systems
IS Foundations and Systems Thinking
Week 1 sets the premise the whole subject rests on: Information Systems is about the effective use of IT by people and organisations — not the technology itself. The key discrimination is IS ≠ IT: IT is the artefact (hardware, software, networks, data), while an IS is that technology plus the people, processes and organisational context that put it to use. You learn to reason with systems thinking (interdependence, feedback loops, boundaries, emergence), Leavitt's socio-technical diamond, and Kling's social informatics — “ICTs do not operate in a vacuum,” and social and technical systems co-evolve. This is not a stand-alone exam theme but the lens markers expect on every “great tech that still failed” case.
What this chapter covers
- 011. IS vs IT — IT is the artefact; IS is the socio-technical whole (people + process + data + context)
- 022. IT-in-context — why the same technology succeeds in one firm and fails in another
- 033. Systems thinking — interdependence, feedback loops, boundaries and emergent behaviour
- 044. Leavitt's diamond — People, Structure, Task and Technology are coupled; change one, re-fit the others
- 055. Kling's social informatics — ICTs do not operate in a vacuum; design, use and consequences are context-shaped
- 066. Co-evolution — tech and social practice adapt to each other (not a one-way tech → society street)
- 077. Organisation-as-system vs the biological-ecosystem analogy — designed goals vs self-regulating nature
- 088. The five stakeholder lenses — developers, users, business managers, IT managers, vendors
A technically perfect system that nobody uses
- +2Define against the case: IT = the technical artefact alone — the rostering software, servers and app RiverCity bought, measured by uptime and speed. IS = the socio-technical whole: that technology plus the people (nurses, ward managers), the processes (how a shift is actually swapped) and the ward context in which they interact to deliver value.
- +2Map to the case: RiverCity optimised the IT (uptime, load time) but the IS is what failed — nurses' real swapping practice was never part of the design, so no information value was delivered. It is a perfect artefact sitting inside a broken information system.
- +3Social informatics (Kling): ICTs do not operate in a vacuum — adoption is shaped by work practice and culture, not technical efficiency; designers who ignore behavioural factors build tools that are abandoned (reversion to paper) or cause unintended consequences; social and technical systems co-evolve, yet RiverCity treated success as a purely technical property.
- +3Systems thinking and recommendation: examine how the parts interact rather than in isolation — RiverCity optimised one component (the platform) while ignoring the feedback loop between nurses, managers and the swap process, a short-sighted isolated fix. By Leavitt's diamond it changed Technology but not People, Task or Structure. Recommend redesigning as a socio-technical system: involve nurses, model the real swap workflow, and build in feedback loops before re-launch.
Key terms
- Information Technology (IT)
- The technical artefact alone — hardware, software, networks and data; the thing an organisation buys, measured in technical terms such as uptime, speed, capacity and cost. Excellent IT does not by itself create value.
- Information System (IS)
- The socio-technical whole: IT plus the people who use it, the processes it supports and the organisational context it sits in, working together to deliver information value. The IS discipline studies this whole, captured by the premise "IT in context."
- Systems thinking
- Examining how interrelated components interact — interdependence, feedback loops, boundaries and emergent behaviour — rather than studying each part in isolation, so designers avoid short-sighted, isolated fixes.
- Leavitt's diamond
- A socio-technical model of four interdependent organisational components — People, Structure, Task and Technology. Because they are coupled, changing one (e.g. introducing new technology) forces the others to adjust, or the system falls out of balance and reverts.
- Social informatics (Kling)
- The study of ICTs in their social context: ICTs do not operate in a vacuum — their design, use and consequences are shaped by human, institutional and social factors, so technical efficiency alone does not determine adoption.
- Co-evolution
- Social and technical systems adapt to each other over time — users change how they use a tool and the tool evolves in response to social needs. The relationship is bidirectional, not a one-way path from technology to society.
- Stakeholder lenses
- The recurring roles through which an IS case is read — system developers, users, business managers, IT managers and vendors — each of whom sees the same system differently and has different interests and capabilities.
- Feedback loop
- A path by which a system's outputs loop back to influence its future behaviour; ignoring the loop between users, process and tool produces brittle designs that do not adapt to how work really happens.
IS Foundations and Systems Thinking FAQ
What is the difference between IS and IT?
IT is the technical artefact — hardware, software, networks and data. An information system is that technology plus the people, processes and organisational context that put it to use. The whole subject is built on this distinction ("IT in context"), and treating IS = IT is the most common Week 1 mistake.
Why does the same technology succeed in one organisation and fail in another?
Because outcomes depend on people, processes and setting, not technical efficiency alone. Kling's social informatics makes the point directly: ICTs do not operate in a vacuum, so adoption is shaped by culture, work practice and context — a technically perfect artefact can sit inside a broken information system.
What is systems thinking and why does it matter here?
Systems thinking studies how interrelated parts interact — interdependence, feedback loops, boundaries and emergence — instead of analysing each part alone. In an IS case it stops you optimising one component (the software) while ignoring the interactions that actually decide whether value is delivered.
What is Leavitt's diamond?
A socio-technical model with four coupled components — People, Structure, Task and Technology. Change the technology and the other three must be re-fitted, or the system rebalances by reverting to the old way. It is the systems-thinking explanation for why a "drop-in-the-new-software" rollout fails.
How is this topic examined?
Week 1 rarely gets its own essay, but it is the lens markers expect on any "we bought great tech but it failed" case, and it appears as a clean IS-vs-IT multiple-choice discrimination. Strong answers name IS ≠ IT, cite Kling by name, diagnose the missing interaction with systems thinking, and recommend a socio-technical fix.
Is this page official or affiliated with the University of Melbourne?
No. This is an independent AskSia study resource for students taking ISYS90026; it is not produced or endorsed by the University of Melbourne. Always confirm details against the official Canvas subject page and current handbook.
Exam move
Treat Week 1 as the spine for the whole subject rather than a topic to memorise. Lock in the IS ≠ IT discrimination and be able to say which layer — artefact, system or context — failed in a given case. Learn Kling's phrase "ICTs do not operate in a vacuum" verbatim and pair it with the bidirectional co-evolution point, since the exam loves the one-way-vs-two-way distractor. Practise the signature move on short cases: name IS ≠ IT, cite Kling, use systems thinking to name the missing feedback loop or the boundary drawn too narrowly, reach for Leavitt's diamond whenever users revert to the old way, read the case through at least one stakeholder lens, and always close with a socio-technical recommendation instead of a better-technology tweak.
