Information Systems

Chapter 1 · Strategic Information Systems

Lecture draft

From the content sections and aligned assignments.

Chapter learning objectives

  1. Distinguish an information system from its information technology components.
  2. Trace data through input, processing, storage, output, and feedback.
  3. Explain how people, management, and organizational arrangements affect system outcomes.
  4. Connect an information system investment to strategic objectives and complementary assets.
  5. Evaluate a basic value claim using explicit assumptions, measures, and tradeoffs.

Systems

Chapter 1 · Information Systems

Read: Systems

Goals for this part

  • Explain Information Systems in Business.
  • Explain System Components and Dimensions.
  • Explain Sociotechnical Perspectives.

Information Systems in Business

A system is a set of connected parts organized around a purpose. A store's order system exists to help the business accept, fulfill, and account for customer orders. Its parts include customer records, inventory records, software, employees, and rules for deciding when an order is ready.

Information Systems in Business

The relationships among those parts matter because completing one task creates information another task needs.

Information Systems in Business

An information system (IS) is an arrangement of people, procedures, data, and technology that turns recorded observations into information people can use to coordinate work, monitor conditions, and make decisions. Information technology (IT) refers to the computing and communications resources used in that arrangement. A barcode scanner is technology.

Information Systems in Business

The inventory system includes the scanner, the product identifiers it reads, the records it changes, and the people responsible for using those records correctly. This distinction follows the broad organizational treatment in Laudon and Laudon (2022) and Bourgeois et al. (2019).

Information Systems in Business

The same system can support several levels of work. An employee uses an order record to locate a purchase. A store manager uses a report to decide whether the pickup area needs more staff. A senior manager compares cancellation patterns across stores before expanding the service. Those users need different views of related data.

Information Systems in Business

A detailed receipt is useful for resolving one payment dispute; a summary of recurring cancellation causes is more useful for changing policy.

Information Systems in Business

A system boundary identifies what your analysis includes. If you study only the checkout application, the customer payment may appear successful. If your boundary includes inventory updates and physical pickup, the unfulfilled promise becomes visible. Neither boundary is automatically correct for every question.

Information Systems in Business

Choose one that includes the activities and dependencies needed to explain the outcome you are examining.

Information Systems in Business

In the opening example, the relevant boundary includes the store's inventory updates, the online promise, and the employee who prepares the order. Replacing the payment processor would have little effect if the underlying problem is an outdated inventory record.

System Components and Dimensions

Data are recorded observations, such as a product identifier, a quantity, or a sale time. Information is data arranged and interpreted for a purpose. A record showing that product P17 has two units at Store A is more useful for fulfillment than an isolated quantity of two.

System Components and Dimensions

Knowledge combines information with experience and judgment: an employee may know that the display unit should not be offered for ordinary pickup even when a count includes it.

System Components and Dimensions

Data do not become dependable information merely because a computer processes them. The meaning of a field, the time it was updated, and the conditions under which it was collected affect whether you can use it. A perfectly accurate count from yesterday can support yesterday's accounting while being unsuitable for a promise made now.

System Components and Dimensions

The input-processing-output model helps you trace how information is produced. Storage preserves records across activities, and feedback allows people or automated rules to compare results with expectations and make corrections.

System Components and Dimensions: comparison

Activity Retail example A useful diagnostic question
Input An employee records that an item was sold. Was the correct item and quantity captured?
Processing The system updates available stock and checks a new order. Does availability account for existing reservations?
Storage Product, order, payment, and reservation records are retained. Can related events be connected through identifiers?
Output The customer receives a pickup confirmation. Does confirmation mean payment accepted or stock reserved?
Feedback An employee records that the item cannot be found. Who receives the exception and can change the process?

System Components and Dimensions

Read the table from the recorded event toward the customer promise, then follow feedback back into the work. If an exception is recorded but nobody reviews it, data collection has occurred without a useful correction loop.

System Components and Dimensions

The components also have organizational dimensions. The technology dimension includes hardware, software, networks, and data tools. The people dimension includes skills, responsibilities, incentives, and judgment. The organizational dimension includes structures, routines, culture, and formal rules. Management sets priorities, allocates resources, assigns decision rights, and monitors results across these dimensions.

System Components and Dimensions

Keeping data visible in your analysis helps expose disagreements over definitions and ownership that a technology inventory would miss.

System Components and Dimensions

A status trace makes the distinction between a successful transaction and a successful service visible. In this hypothetical sequence, the application processes every message it receives correctly, but the messages do not establish that the order can be fulfilled.

System Components and Dimensions: comparison

Time Recorded event What the event establishes What remains uncertain
9:00 Inventory record shows two units. The last recorded count was two. Whether both units can be located and sold.
9:02 Customer payment is authorized. The payment provider permits the charge. Whether a unit has been reserved.
9:03 Website sends “ready for pickup.” A message was sent. Whether an employee has prepared the order.
9:20 Employee reports no sellable unit. A fulfillment exception has been observed. How quickly the customer will receive a remedy.

System Components and Dimensions

The mistake occurs when a message implies more than the preceding evidence supports. A stronger process distinguishes “order received,” “stock reserved,” and “ready for pickup.” Each status should correspond to an observable event, with a person or rule responsible for recording it. Payment authorization may justify acknowledging the order; it does not justify claiming that preparation is complete.

System Components and Dimensions

A feedback loop also needs a response. Recording the missing unit is the feedback signal. Assigning someone to correct the stock record, contact the customer, and investigate repeated discrepancies closes the loop. A dashboard that shows unresolved exceptions without ownership leaves the system able to describe the failure while unable to correct it.

Sociotechnical Perspectives

A sociotechnical system produces its results through the interaction of technical capabilities and social arrangements. A technically correct application may still support an unreliable service when roles, incentives, or work practices do not fit it. Conversely, capable employees may struggle when the system hides information they need or makes routine corrections difficult.

Sociotechnical Perspectives

Laudon and Laudon (2022, Chapter 1) use this perspective to connect technical and behavioral approaches to information systems.

Sociotechnical Perspectives

Consider the retailer's inventory problem through three lenses. A technical analysis asks how frequently inventory records update and whether a reservation prevents another sale. A behavioral analysis asks why employees delay updates and whether they trust the inventory display.

Sociotechnical Perspectives

An organizational analysis asks who owns inventory accuracy and whether store performance measures encourage employees to prioritize walk-in sales over pickup orders. The lenses complement one another; each explains a different part of the failure.

Sociotechnical Perspectives

Suppose the business installs faster synchronization but continues to reward employees only for sales completed at the register. An employee may still set aside an online order to serve a walk-in customer. Alternatively, managers may change the reward system while the reservation software still permits the same item to be promised twice.

Sociotechnical Perspectives

Either intervention leaves an important dependency unresolved.

Sociotechnical Perspectives

A more complete response connects the changes: reserve stock when a promise is made, give employees a visible preparation queue, define who handles missing items, and measure successful fulfillment alongside sales. Managers would then examine whether the combined arrangement reduces cancellations and avoid assuming that the software feature alone caused any improvement.

Sociotechnical Perspectives

This perspective changes how you diagnose a problem. Start with an observed outcome, trace the information and work that produced it, and identify the technical and organizational conditions needed for a better result.

Sociotechnical Perspectives

You do not need programming expertise to ask whether a status has a shared meaning, an employee has authority to correct it, or a manager receives feedback soon enough to act.

Quick check

Name the concept that completes this statement.

A ________ is a set of connected parts organized around a purpose.

Quick check

Name the concept that completes this statement.

An ________ is an arrangement of people, procedures, data, and technology that turns recorded observations into information people can use to coordinate work, monitor conditions, and make decisions.

Your turn

Use the chapter case: A Retailer Builds a Digital Service.

Define a familiar organizational information system and its boundary. Distinguish the service from its IT components.

Prepare a brief explanation with a stated assumption and an outcome measure.

Recap

Analyze an information system as connected work organized around a purpose. Trace inputs, processing, storage, outputs, and feedback, then examine the people, technology, and organizational arrangements that make those connections dependable.

Organizations

Chapter 1 · Information Systems

Read: Organizations

Goals for this part

  • Explain Globalization and Digital Firms.
  • Explain Organizational Context.
  • Explain Change and Performance.

Globalization and Digital Firms

Globalization involves economic and organizational relationships extending across national boundaries. Information systems make it possible to exchange designs, coordinate orders, provide services remotely, and monitor work distributed across locations. A business can reach customers farther away while also depending on suppliers, platforms, and service providers it does not directly control.

Globalization and Digital Firms

A digital firm uses digital information and processes extensively to coordinate important relationships and activities. Having a website alone does not establish that capability. The more important questions are whether customer interactions, internal work, supplier coordination, and management decisions connect through dependable digital records and processes.

Globalization and Digital Firms

Laudon and Laudon (2022, Chapter 1) place the digital firm within this broader organizational transformation.

Globalization and Digital Firms

A business process is a connected sequence of activities that produces an outcome for a customer or another user. The retailer's order-to-pickup process crosses sales, inventory, payment, and store operations. Making its website available around the clock changes the timing of demand, but employees still need a feasible way to prepare orders, resolve exceptions, and communicate with customers.

Globalization and Digital Firms

Geographic reach introduces coordination requirements. A supplier and retailer may use different product codes, work calendars, currencies, and definitions of availability. A system can transmit a message instantly while leaving its business meaning unresolved. Managers therefore need agreements about identifiers, update times, responsibilities, and escalation, as well as a network connection.

Globalization and Digital Firms

Suppose the retailer receives an overseas supplier's message that 100 units have shipped. That message can support a forecast, but it does not mean the units are available for immediate store pickup. The system must distinguish stock ordered, stock in transit, stock received, and stock ready to sell.

Globalization and Digital Firms

These distinctions become more important as more parties contribute information to the same customer promise.

Globalization and Digital Firms

Digital participation also depends on connectivity and skills. The OECD's Digital Economy Outlook 2024, Volume 2 emphasizes both, alongside trust and security. A manager should therefore examine whether staff, customers, and partners can use the service reliably rather than assuming that nominal online access removes every participation barrier.

Organizational Context

An organization coordinates people and resources through roles, routines, rules, and relationships. Members may share a broad purpose while disagreeing about priorities, acceptable risks, or how resources should be distributed. An information system operates within those agreements and conflicts. It also changes them by making some information visible, some actions easier, and some decisions more centralized.

Organizational Context

Decision rights specify who may make a decision. In a pickup service, the system may show that an order is late, but someone still needs authority to substitute an item, offer compensation, or cancel a reservation. An escalation rule is useful only when the responsible person can receive the information and act within the required time.

Organizational Context

Organizational culture includes shared expectations about how work is done and what behavior is valued. A culture that rewards reporting problems can improve the quality of exception data. A culture that punishes every reported error can encourage staff to hide problems, even when the application provides an excellent reporting screen.

Organizational Context

These are analytical possibilities, not fixed descriptions of every organization.

Organizational Context: comparison

Organizational feature Effect on the pickup process Design implication
Division of work Several teams touch the same order. Show ownership and status at each handoff.
Decision rights Staff need permission to resolve exceptions. Match permissions and escalation rules to responsibilities.
Incentives Register sales and pickup work may compete for attention. Assess the completed service, including delayed or canceled orders.
Shared vocabulary Teams may interpret “complete” differently. Define statuses through observable business events.
Informal routines Staff may rely on a separate spreadsheet. Investigate the need it meets before removing it.

Organizational Context

Use the table to connect a feature of the organization to a specific design choice. A statement such as “employees resist change” is too broad to guide action. A more useful diagnosis is that staff cannot correct a stock discrepancy without waiting for a manager who is not present.

Organizational Context

Different functions also need different information. Sales may track orders placed, finance payments settled, and operations orders fulfilled. These measures answer different questions and can all be legitimate. Managers need to reconcile their meanings before using them as if they measured the same outcome. Hay et al.

Organizational Context

(2021) highlight shared business vocabulary in digital transformation; their article is included in the chapter references as a management reading.

Change and Performance

Digitization converts an existing representation into digital form, such as replacing a paper order slip with an electronic record. Digital transformation involves more substantial changes in how an organization works, serves customers, or creates value using digital capabilities. The distinction depends on the change in the work, not the age of the technology purchased.

Change and Performance

For the retailer, copying the paper pickup list onto a tablet may improve readability. Redesigning the process so that inventory is reserved before confirmation, responsibility transfers explicitly, and customers receive accurate updates changes the service more substantially. Neither label guarantees success.

Change and Performance

A modest change that solves a well-defined problem can create more value than an ambitious initiative with unclear responsibilities.

Change and Performance

Organizational change usually includes a transition period. Staff may work with unfamiliar screens, old records may need reconciliation, and new roles may overlap with old ones. An early performance decline does not automatically prove that the design is wrong, but neither should managers dismiss every problem as temporary.

Change and Performance

They need evidence that identifies where the process is failing and whether the response addresses the cause.

Change and Performance

A small pilot provides a way to learn. The retailer might test the redesigned service in two stores, record cancellation reasons, observe employees preparing orders, and compare performance across similar days. Managers should examine both the numerical results and the work behind them.

Change and Performance

A low cancellation count could reflect better fulfillment or employees discouraging customers from placing difficult orders.

Change and Performance

Useful measures connect to the service objective. If the objective is reliable pickup, examine the proportion of promised orders ready on time, missing-item exceptions, and the time required to resolve a problem. Counting employee logins shows that the application was accessed; it does not establish that customers received the promised service.

Change and Performance

The practical management task is to align process changes, responsibilities, training, and technical capabilities, then evaluate the combined result. {doc}Business Processes <../02_business_processes/0200_business_processes> develops process analysis further. Here, the central point is that an information system changes the organization that uses it, while the organization shapes what the system can achieve.

Change and Performance

A pilot needs a denominator as well as a count. Suppose Store A has eight late orders out of 100 promised orders, while Store B has 12 late orders out of 300. Store A has fewer late orders, but its late-order rate is eight percent; Store B's is four percent.

Change and Performance

Comparing only counts would reverse the apparent service ranking. These figures are hypothetical and do not establish why performance differs.

Change and Performance

Now suppose a new policy prevents difficult orders from being accepted. The late-order rate could improve while more customers are refused service. Managers should examine accepted orders alongside attempted orders, cancellations, and customer complaints. Otherwise, a team can appear successful by changing which work enters the measure.

Change and Performance

For a useful pilot comparison, keep the meaning of “promised” and “ready” consistent, record the operating conditions, and investigate differences in order mix and staffing. A before-and-after comparison can suggest an improvement, but seasonal demand or a staffing change may also explain it.

Change and Performance

The purpose of a pilot is to build a credible explanation of the result and find exceptions before expanding the service.

Quick check

Name the concept that completes this statement.

________ involves economic and organizational relationships extending across national boundaries.

Quick check

Name the concept that completes this statement.

A ________ uses digital information and processes extensively to coordinate important relationships and activities.

Your turn

Use the chapter case: A Retailer Builds a Digital Service.

Define a familiar organizational information system and its boundary. Distinguish the service from its IT components.

Prepare a brief explanation with a stated assumption and an outcome measure.

Recap

Organizational context determines how information turns into coordinated action. Digital reach expands both opportunities and dependencies. Reliable results require clear responsibilities, shared meanings, workable routines, and evidence about the service delivered.

Value

Chapter 1 · Information Systems

Read: Value

Goals for this part

  • Explain Strategic Objectives.
  • Explain Complementary Assets.
  • Explain Business Value and Tradeoffs.

Strategic Objectives

Organizations invest in information systems for different reasons. Laudon and Laudon (2022, Chapter 1) identify six broad strategic objectives. These categories help explain why an investment might be worthwhile, but they do not establish that a particular project will achieve its purpose.

Strategic Objectives: comparison

Objective What the organization is trying to achieve Retail example
Operational excellence Perform routine work more reliably and efficiently. Reduce time spent locating and preparing orders.
New products, services, or business models Offer a different service or way of creating and capturing value. Introduce a paid delivery subscription.
Customer and supplier intimacy Use relationships and information to coordinate more effectively. Share replenishment information with a supplier.
Improved decision making Match information to the decisions managers need to make. Use demand patterns when assigning pickup staff.
Competitive advantage Perform better than rivals in ways customers value. Provide dependable pickup that competitors struggle to match.
Survival Meet conditions needed to continue operating or participating. Connect to a trading partner's required order system.

Strategic Objectives

Operational excellence concerns dependable execution of day-to-day work. Efficiency asks how many resources an activity consumes; effectiveness asks whether it achieves the intended result. Preparing orders quickly is efficient only in a useful sense when employees prepare the right orders and customers can collect them as promised.

Strategic Objectives

A business model explains how an organization creates value for users and sustains its activities, including how it obtains revenue and incurs costs. Offering pickup can change the service customers receive. Charging for priority pickup changes how some of that service value is captured. Managers still need to test whether demand, capacity, and cost support the proposed arrangement.

Strategic Objectives

Competitive advantage is relative. A system feature can improve performance without creating an advantage if competitors already offer it. Conversely, an ordinary software package can contribute to advantage when a firm combines it with difficult-to-copy routines, relationships, or knowledge. The distinction between useful capability and sustained advantage is developed in {doc}IS Strategy <../03_is_and_strategy/0300_is_and_strategy>.

Strategic Objectives

The objective also determines the evidence needed. A system introduced to satisfy a partner's minimum requirements should be assessed against that requirement and its cost. Evaluating it only by immediate sales growth could miss the reason it was necessary. For a customer-service investment, managers should connect the proposed system change to a service outcome before selecting measures.

Complementary Assets

A complementary asset is a resource or capability needed to obtain value from another investment. Software for reserving inventory needs accurate product records, reliable stock counts, employees who follow the reservation procedure, and managers who resolve exceptions. Buying the software does not automatically provide those complements.

Complementary Assets

Laudon and Laudon (2022, Chapter 1) distinguish organizational, managerial, and broader social complements. Organizational complements include workable processes and an appropriate business model. Managerial complements include leadership, incentives, and training. Broader complements include communications infrastructure, standards, skills, and institutions that support dependable exchange.

Complementary Assets

The categories overlap in practice, but they prevent a project budget from treating the software purchase as the entire investment.

Complementary Assets

Compare two fictional stores that adopt the same pickup application. Store A reconciles product identifiers, gives employees scheduled preparation time, and allows a supervisor to resolve exceptions. Store B adds the application to employees' existing duties without changing ownership or measures.

Complementary Assets

If Store A performs better, the difference may arise from the combined arrangement rather than a superior software feature.

Complementary Assets: comparison

System capability Complement needed Failure when the complement is missing
Display inventory Timely counts and shared product identifiers Customers see stock that cannot be located.
Route preparation work Assigned staff and clear priorities Orders wait in a queue that nobody owns.
Flag an exception Authority and time to resolve it Alerts accumulate without changing the outcome.
Analyze cancellations Consistent reason codes and review routines Reports contain numbers without an actionable explanation.

Complementary Assets

The third column is a useful way to test an investment proposal. If the organization cannot explain what will happen after an alert or report appears, an important complement may be absent. “Users need training” is often too general. Specify the task employees must learn, the authority they require, and the conditions under which they will perform it.

Complementary Assets

Complementary assets also take time and resources to develop. Record preparation, training, process redesign, and additional supervision belong in the evaluation. A project that appears inexpensive because those costs were omitted can become difficult to sustain. The managerial question is whether the complete set of changes can produce a worthwhile outcome under realistic operating conditions.

Business Value and Tradeoffs

A value argument needs a chain of reasoning: a system capability changes an activity; the changed activity affects an outcome; and the outcome matters to the organization or its stakeholders. The links should identify assumptions rather than conceal them. Faster inventory updates might reduce false pickup promises, but that benefit depends on accurate records and timely preparation.

Business Value and Tradeoffs

Consider a hypothetical cost example. The retailer handles 600 pickup orders each month. A redesigned workflow is expected to save three minutes of staff effort per order. The estimated capacity released is 600 × 3 = 1,800 minutes, or 30 hours per month.

Business Value and Tradeoffs

At an assumed labor cost of $20 per hour, that time has an estimated value of $600 per month.

Business Value and Tradeoffs

Suppose the recurring system cost is $250 per month and initial configuration and training cost $2,100. If the full $600 becomes a cash saving, the monthly difference is $350 and the simple payback period is $2,100 ÷ $350 = six months.

Business Value and Tradeoffs

This calculation excludes financing, taxes, risk, and benefits or costs outside those assumptions; it is an introductory comparison, not a complete investment appraisal.

Business Value and Tradeoffs

The critical issue is whether time saved becomes a cash saving. If employees work the same paid hours, payroll does not fall by $600. Instead, the organization has capacity it might use for more orders, shorter waits, or other work.

Business Value and Tradeoffs

That capacity can be valuable, but managers should name the benefit correctly and explain how it will be used. They should also avoid counting the same released time once as payroll savings and again as extra capacity.

Business Value and Tradeoffs

Measures should examine different parts of the outcome. DeLone and McLean (2003) present information-system success as a multidimensional evaluation problem. For this example, managers could examine whether the system is dependable, whether its information supports the task, whether people use it effectively, and whether the service improves.

Business Value and Tradeoffs

A single usage count would be insufficient evidence for the entire value claim.

Business Value and Tradeoffs

Tradeoffs can arise even when a system meets its main objective. Collecting more customer data may support personalization while increasing data-handling responsibilities. Keeping more inventory can improve pickup availability while tying up funds. Adding employee monitoring can provide process visibility while changing trust and behavior.

Business Value and Tradeoffs

A sound recommendation identifies who benefits, who bears costs, and what evidence would justify continuing the arrangement.

Business Value and Tradeoffs

Finally, consider opportunity cost: resources committed to one use cannot be used for another at the same time. The retailer might obtain more value from correcting product records than from adding a new recommendation feature. Comparing feasible alternatives, including a modest process change, keeps the evaluation tied to the business problem.

Business Value and Tradeoffs

A sensitivity comparison shows how strongly the recommendation depends on its assumptions. Retain the hypothetical $2,100 initial cost and $250 monthly recurring cost. The following alternatives consider only direct cash savings from released staff time; they exclude added revenue and service benefits.

Business Value and Tradeoffs: comparison

Share of the estimated time converted into cash savings Monthly cash saving Monthly cash saving after recurring cost Simple payback
All of the time $600 $350 Six months
Half of the time $300 $50 42 months
None of the time $0 -$250 No payback from labor cash savings alone

Business Value and Tradeoffs

The middle row uses $2,100 divided by $50. The final row does not imply that the project has no value: the released capacity could support better service or additional orders. It means that the stated labor-cash-saving argument does not recover the investment.

Business Value and Tradeoffs

A recommendation should identify another benefit and show evidence for it instead of quietly relabeling capacity as cash.

Business Value and Tradeoffs

A practical value statement therefore includes an owner and a review point. For example: “The store operations manager will review readiness, cancellations, and paid staff hours after the pilot. Expansion depends on reliable fulfillment and evidence that the expected benefit can be realized.” The precise thresholds belong to the decision context.

Business Value and Tradeoffs

Making the review explicit turns a forecast into a claim that managers can revisit.

Quick check

Name the concept that completes this statement.

________ concerns dependable execution of day-to-day work.

Quick check

Name the concept that completes this statement.

A ________ explains how an organization creates value for users and sustains its activities, including how it obtains revenue and incurs costs.

Your turn

Use the chapter case: A Retailer Builds a Digital Service.

Evaluate the value claim using explicit assumptions, suitable measures, and a distinction between capacity and cash savings.

Prepare a brief explanation with a stated assumption and an outcome measure.

Recap

Value comes from improved outcomes supported by a workable combination of systems, people, and organizational capabilities. State the objective, identify necessary complements, distinguish cash savings from capacity, and make the assumptions and tradeoffs visible.

Reading and assignments