Chapter 1: Foundations of Information Systems#

Every time you scan a loyalty card, place an online order, or check a weather app, you are part of an information system (IS). These systems are not just computers. They are the nervous system of a business. They capture raw facts and turn them into insights that guide decisions. This chapter builds a way of thinking that will help you see how organisations use technology to get things done, compete, and survive.

The Big Picture#

An information system is a set of people, processes, and technology that work together to collect, transform, store, and share data. The real question this chapter answers is: what makes a collection of gadgets and software an information system — and how does that system create value for a business? We will explore the basic blueprint that every successful IS follows, from the moment a customer taps a screen to the moment a manager sees a trend. By the end, you will have a way of thinking about any business technology, from a simple spreadsheet to a global enterprise platform.

What Is an Information System?#

An information system is more than a computer program. It is a coordinated network of parts that work together to handle data.

Information System: A set of connected parts that collect, process, store, and share data. It helps people make decisions, coordinate work, and control processes.

Three ideas are in that definition. First, an IS has components — hardware, software, data, procedures, and people. Second, those components follow a cycle: input, processing, output, and feedback. Third, the purpose is always to help someone in the organisation make a better decision, coordinate work, or control a process.

Data versus Information#

A lot of confusion disappears when you separate data from information.

Data: Raw facts — numbers, dates, words, images — that don’t mean much on their own. Information: Data that has been processed, organised, or given context so that it becomes meaningful and useful.

Think of a kitchen thermometer. It gives you a number: 18°C. That is data. When you know that 18°C is the temperature of the dough you are proofing, and that yeast works best between 24°C and 27°C, the data becomes information. You realise: “The dough is too cold; I need to warm it up.” The same raw number means something completely different if it is measuring the outdoor temperature on a spring morning. Context and processing turn data into information.

The Input-Processing-Output-Feedback Loop#

Every information system follows a simple rhythm: input, processing, output, and feedback.

• Input captures raw data from inside or outside the organisation. A barcode scanner at a checkout counter reads a product’s code; a sensor in a factory measures vibration; a keyboard entry records a customer’s address.
• Processing converts that raw data into a more useful form. The checkout system looks up the product’s price, calculates the total, and updates the inventory count.
• Output delivers the processed information to the people or machines that need it. The receipt you get, the dashboard a manager sees, the alert that a part is about to fail — all are outputs.
• Feedback is the loop that makes the system smarter. Outputs are fed back into the system as new inputs so it can adjust. When a store’s inventory system notices that a particular style of shoe sold out on a Tuesday, it can trigger a reorder automatically. Without feedback, a system runs blind.

A room thermostat is a perfect miniature example. The input is the current temperature (data). The processing compares it to the set point. The output is a signal to the heater or air conditioner. The feedback is the new temperature reading, which tells the system whether to turn the heating on or off again. This continuous loop keeps the room comfortable.

📝 Section Recap: An information system is a set of parts that turns raw data into useful information through a cycle of input, processing, output, and feedback. Its goal is to help someone make a decision or control a process.

The Three Dimensions of Information Systems#

An information system is not just technology. It always sits inside an organisation and serves a management purpose. This three-sided view — management, organisation, and technology — is the lens that helps us understand why some systems succeed and others fail.

The Organisation Dimension#

Every organisation has a structure, a culture, and a set of business processes. Information systems are built on top of these existing ways of working. A hospital’s patient-records system, for example, must respect the chain of command of doctors, nurses, and administrators. The system’s design must fit the organisation’s routines, not the other way around — at least if people are going to use it. Organisational culture — the shared values and habits — also shapes how workers react to new technology. A firm that values privacy will design its data-handling rules very differently from one that encourages open sharing.

The Management Dimension#

Managers do not just push buttons. They make decisions, decide how to use resources, and deal with uncertainty. Information systems provide the raw material for those decisions. A production manager looking at a weekly defect report is using the IS to spot a problem. But the report itself is useful only if the manager knows what to do with it — how to interpret the numbers, where to investigate, and what action to take. So the management dimension includes not just the formal reports but also the leadership, judgment, and problem-solving skills that surround the technology.

The Technology Dimension#

This is the dimension most people picture first: the hardware, software, and networking that make the system run. Servers, smartphones, databases, Wi‑Fi, and the code that ties them together are all part of the technology dimension. But technology alone is never enough. The same checkout terminal that works beautifully in one coffee shop might be a disaster in another if the shop’s layout, staff training, or management goals are different.

The three dimensions are not separate layers. They are interwoven. A change in technology (a new mobile app) affects the organisation (customers can order ahead, so the kitchen workflow changes) and management (the shift supervisor now sees real-time sales trends). The best information systems are designed with all three dimensions in mind from the start.

📝 Section Recap: To understand any information system, look at its management, organisation, and technology dimensions, and how they fit together. Technology is just one piece of the puzzle.

The Business Information Value Chain#

How does a pile of raw data become a competitive edge? The business information value chain answers that question. It shows the path from data capture to business value, adding context and analysis at each step.

Imagine a bike-sharing company. The raw data is a stream of timestamps and GPS coordinates each time a bike is rented or returned. That is the first stage: data collection. The second stage is data processing: the system cleans the data, removes duplicates, and stores it in a database.

The third stage — and the one that creates real value — is transformation into business intelligence (useful insights for making decisions). The company might notice that most bikes are returned within one kilometre of a popular train station between 7:00 and 8:00 a.m. That is information. Further analysis could reveal that on rainy days, rides drop by 40% in the city centre but only 10% in the student neighbourhood. That is knowledge. The firm can then act: they might reposition bikes away from the city centre on wet mornings, or offer a discount to riders who return bikes to the station. That action — a business decision — is the value.

The value chain is not a one-way street. The results of those decisions (did repositioning bikes actually increase rentals?) are fed back as new data, restarting the loop. This is the feedback mechanism we met earlier, now operating at the scale of an entire business.

📝 Section Recap: The business information value chain shows how raw data, when processed and analysed, becomes useful insights that drive decisions and create value. Feedback loops keep the process improving.

IT Infrastructure: The Building Blocks#

Every information system relies on a shared IT infrastructure. Think of infrastructure as the base that all business applications plug into — like the roads, bridges, and power grid that a city’s services depend on.

The four building blocks are:

1. Hardware — the physical machines: computers, servers, smartphones, routers, and sensors.
2. Software — the instructions that tell the hardware what to do. This includes operating systems (like Windows, Linux, iOS), database software, and the many application programs that run the business.
3. Data — the raw material. Data is stored in databases, files, and more recently in massive storage pools called data lakes. Managing data well — keeping it accurate, secure, and accessible — is one of the hardest jobs in IT.
4. Networking and telecommunications — the wires, radio waves, and rules (protocols) that let the components talk to each other. The internet, Wi‑Fi, Bluetooth, and corporate Ethernet networks all belong here.

These four pieces are not just a shopping list. They must be matched carefully to the organisation’s needs. A small bakery might run its entire business on a single tablet with a 4G connection. A global bank needs thousands of servers, multiple data centres, and a network that can handle millions of transactions per second. The infrastructure is the foundation; get it wrong, and every application built on top of it will wobble.

📝 Section Recap: IT infrastructure is made up of hardware, software, data, and networking. These building blocks form the shared platform that supports all information systems. They must fit the business’s size and strategy.

Six Strategic Business Objectives#

Businesses do not invest in information systems because they love technology. They invest because they expect the system to help them achieve one or more of six strategic objectives. These objectives are the “why” behind every IT project.

1. Operational excellence — doing things faster, cheaper, and more reliably. A retailer that uses an automated inventory system cuts the number of times items are out of stock and reduces labour costs.
2. New products, services, and business models — an IS can enable a whole new way of doing business. Streaming services replaced physical rentals; ride-hailing apps created a new model of transport.
3. Customer and supplier intimacy — when a hotel knows your pillow preference or a supplier can see your production schedule in real time, the relationship becomes sticky. Serving a customer well is cheaper than finding a new one.
4. Improved decision-making — managers with real-time data make better choices. A logistics firm that can see traffic jams forming can reroute trucks before they are stuck.
5. Competitive advantage — when you do something your rivals cannot easily copy, you win. A system that cuts delivery times from two days to two hours can be a powerful advantage.
6. Survival — sometimes the goal is simply to stay in the game. If every competitor offers online ordering, you must offer it too, or you risk losing customers.

A single information system can serve several objectives at once. An online banking app, for example, improves operational excellence (fewer tellers needed), offers a new service (mobile check deposit), deepens customer intimacy (personalised spending alerts), and provides better decision-making (real-time balance and fraud alerts). The six objectives act as a checklist for evaluating any technology investment.

📝 Section Recap: The six strategic business objectives are the reasons organisations build information systems: operational excellence, new products, customer and supplier intimacy, better decision-making, competitive advantage, and survival. Judge any system by which of these goals it helps achieve.

Complementary Assets and Organizational Capital#

A brilliant information system will fail if the organisation around it is not ready. The non-technical ingredients that make a system effective are called complementary assets. These are the organisational and human pieces that fit together with the technology.

Think of a new CRM (customer relationship management) system. It requires:

• Organisational assets — a supportive culture that values using data, standard ways of working that feed clean data into the CRM, and clear rewards for salespeople to log their calls.
• Managerial assets — strong leadership from the top, a management style that encourages collaboration, and a team that understands how to interpret the reports.
• Social assets — the legal environment, the company’s reputation, and the trust that customers have in the firm. A system that collects personal data but is used in a company with poor privacy practices will cause more harm than good.

When these complementary assets are in place, the technology investment pays off well. When they are missing, the same software can sit unused, or worse, create chaos. The package of complementary assets an organisation builds up over time is sometimes called organisational capital — the invisible wealth that makes a company more than the sum of its machines and people.

📝 Section Recap: Complementary assets — the organisational, managerial, and social conditions around a technology — often decide whether a system delivers value or gathers dust. Organisational capital is the total set of these assets.

The Sociotechnical Systems Perspective#

The final lens we need is the sociotechnical systems perspective. It does not accept the idea of designing technology first and then fixing the people. Instead, it sees the social system (people, structure, culture) and the technical system (hardware, software, processes) as two halves of a whole that must be designed together.

Imagine a hospital introducing an electronic health record system. A purely technical approach would install the software, train the staff on the buttons, and declare victory. A sociotechnical approach would start by asking: how do doctors and nurses actually work? What are their pain points? What workflows will change? The design would be shaped by these answers, and the rollout would include ongoing adjustments based on feedback. The goal is to optimise both together — the best mix of technology and human work, where each makes the other better.

This perspective also explains why copying a successful system rarely works. A system that thrives in one organisation carries the invisible social and organisational assumptions of its birthplace. When you drop it into a different culture, with different management styles and different trust levels, it often breaks. The sociotechnical view reminds us to look at the whole picture, not just the shiny new software.

📝 Section Recap: The sociotechnical systems perspective says that the social and technical parts of an information system cannot be separated. The best results come from designing both halves together, not from attaching technology to an unprepared organisation.

Summary#

We started with a simple idea: an information system is a set of people, processes, and technology that turns raw data into useful information. Then we saw how the input-processing-output-feedback loop runs through every business, how the three dimensions (management, organisation, technology) must work together, and how the value chain turns data into decisions. We learned the six strategic objectives that give every IS project its purpose, that IT infrastructure is the shared foundation, and that complementary assets often decide success or failure. Finally, the sociotechnical perspective reminds us to design the social and technical systems as one.

Here is a quick-reference table that captures the key ideas from this chapter in plain English: