Chapter title: Setting the Stage
This page turns the Chapter 1 slides into a cleaner study guide with precise vocabulary, clearer explanations, and a 5-question multiple-choice quiz. The main themes are mental models, the curse of knowledge, communication in information systems, the technology hype cycle, AI hype versus real adoption, and practical Excel expectations for the course.
Chapter 1 is not just an introduction to the course. It explains why MIS is about people, communication, business processes, and decision-making just as much as it is about software and hardware.
| Term | Precise definition | Why it matters in MIS | Citation |
|---|---|---|---|
| Self-directed learning | Self-directed learning is the process of identifying what you need to learn, finding reliable sources, and teaching yourself how to solve the problem instead of waiting for step-by-step instructions. | MIS work changes constantly, so professionals often have to learn new tools, systems, and workflows on their own. | Course slides, pp. 2–3 |
| Mental model | A mental model is an internal representation of how something works. It shapes how a person interprets information, predicts outcomes, and makes decisions. | Designers, managers, and users all bring different assumptions to an information system, which affects how the system is built and understood. | Course slides, pp. 8–11; Johnson-Laird/Wikipedia source list |
| Information system (IS) | An information system is a system that collects, processes, stores, and communicates information so that people and organizations can perform tasks and make decisions. | The slides emphasize that systems are only as good as the information they transmit and the people who design the process behind them. | Course slides, pp. 9, 11, 13 |
| Curse of knowledge | The curse of knowledge is a communication problem in which people who already know something struggle to imagine what it is like not to know it. | This explains why experts may design confusing systems or give poor instructions to beginners. | Course slides, p. 12; Heath & Heath summary source |
| Business process | A business process is a repeatable sequence of activities used to accomplish organizational work, such as approving a purchase, processing payroll, or handling customer support. | Programs and system rules come from business processes, and those processes come from people. | Course slides, p. 13 |
| Hardware | Hardware is the physical equipment used in computing, such as servers, laptops, phones, routers, and chips. | Hardware is one part of the full MIS stack, but it does not create business value by itself. | Course slides, p. 13 |
| Software | Software is the coded set of instructions that tells computer hardware what to do. | Software reflects human assumptions, so poor mental models can lead to poor software design. | Course slides, p. 13 |
| Data | Data are raw facts or recorded values that can be stored, processed, and turned into information. | If the underlying data are inaccurate, incomplete, or badly structured, the system output will be weak. | Course slides, pp. 9, 13 |
| Technology hype cycle | The hype cycle is a framework that describes how new technologies often move from early excitement to inflated expectations, then disappointment, and eventually more realistic productivity. | It helps managers separate excitement from business value and avoid making bad timing decisions. | Course slides, p. 15; Gartner methodology |
| Emerging innovation | The early stage of a technology when attention is rising, practical use cases are still forming, and future potential is highly uncertain. | At this stage, managers must be careful not to confuse potential with proven value. | Course slides, p. 15 |
| Inflated expectations | A phase where excitement and predictions about a technology grow faster than proven business results. | Managers may overspend, overpromise, or copy competitors without evidence of real demand. | Course slides, p. 15; Gartner methodology |
| Trough of disillusionment | A phase where enthusiasm drops because the technology fails to meet unrealistic expectations or adoption is slower than expected. | This is where firms start distinguishing real use cases from hype. | Course slides, pp. 15–16, 21 |
| Slope of enlightenment | A stage where organizations learn what the technology is actually good for and begin using it more realistically and effectively. | This stage matters because value becomes tied to better workflows, not just excitement. | Course slides, pp. 15–16 |
| Plateau of productivity | The stage where a technology becomes more stable, useful, and broadly understood, so it can deliver repeatable value. | At this point, firms can make better long-term decisions because performance is clearer. | Course slides, p. 15 |
| Tech adoption | Adoption is the decision by users or firms to begin using a technology in practice. | A technology can receive attention and investment without being widely adopted. | Course slides, pp. 20–22; Rogers diffusion source |
| Diffusion | Diffusion is the broader spread of an innovation across a population, market, or social system over time. | Diffusion is wider than adoption because it focuses on how usage spreads beyond early users. | Course slides, p. 22; Rogers diffusion source |
| Actual demand | Actual demand is the real level of customer or organizational usage shown by behavior, purchases, and repeated use. | Actual demand is stronger evidence than headlines or investor excitement. | Course slides, pp. 20–21 |
| Perceived market readiness | Perceived market readiness is what firms believe the market wants, whether or not customers are truly ready to adopt the product. | Bad strategic decisions happen when perception is mistaken for reality. | Course slides, p. 20 |
| Speculative or anticipatory adoption | Speculative adoption occurs when early adopters or investors commit to a technology because they expect future value rather than current proven value. | This helps explain bubbles and hype-driven investment waves. | Course slides, pp. 20–21 |
1) Mental models shape systems. The slides argue that information systems do not appear out of nowhere. People define the business process, decide what counts as important data, and build software around their own assumptions. That means every system contains human judgment. When those judgments are narrow or incomplete, the system can frustrate users even if the technology itself works.
2) MIS is fundamentally about communication. Chapter 1 pushes against the idea that MIS is only about coding or tools. A system exists to communicate information. If the information is inaccurate, badly timed, badly formatted, or hard to interpret, then the system is not doing its job well.
3) The curse of knowledge creates bad explanations. Experts often skip steps because the basics feel obvious to them. In MIS, that can lead to confusing training, unhelpful interfaces, and weak documentation. This is one reason a TA may explain Excel homework better than a professor who has used Excel for decades.
4) Hype is not the same thing as value. The slides use the hype cycle to show that strong excitement around a technology does not prove that it is mature or useful in every setting. The course applies this to AI: huge investment and media attention can exist even when actual business adoption is flatter or slower than expected.
5) Investment ≠ adoption ≠ diffusion. A firm can spend billions on AI infrastructure, but that does not automatically mean customers are using AI heavily, or that the technology has diffused through the economy. These are separate stages and should be analyzed separately.
A student org creates a sign-up system for event volunteers. The form requires students to select from confusing labels that make sense to the officers who built it, but not to new members. Which concept BEST explains why the system is difficult to use?
A manager says, “Our company invested heavily in AI servers, so clearly AI is already transforming the whole firm.” Which idea from Chapter 1 shows the weakness in this claim?
A professor who has used Excel for 25 years explains formulas very quickly and skips basic setup steps. Students remain confused, but the TA gives a clearer explanation. Which concept BEST explains this difference?
A startup gets huge attention, press coverage, and investor funding for a new app, but few customers keep using it after trying it once. In hype-cycle terms, what is the BEST interpretation?
A company automates a reimbursement process, but employees complain that the system rejects valid requests because the workflow assumes every expense follows the same pattern. What is the BEST explanation?