
Course Overview
This course lays the foundation for everything that follows in the Decision Intelligence Program. It answers a deceptively simple question: what is business intelligence, really — and why does it matter to you? By the end, you'll see decision intelligence not as a technology reserved for data teams, but as a discipline you already practice and can learn to do far better.
Learning Objectives
By the end of this course, you will be able to:
• Explain what business intelligence and decision intelligence actually are, in plain language
• Recognize that every person and organization already practices a form of business intelligence
• Describe the core cycle behind every good decision: gather, assess, decide, act
• Distinguish between data, information, and insight
• Apply a simple decision-intelligence framework to a real decision
Course Structure
• Lesson 1: Business Intelligence Is Everywhere
• Lesson 2: From Information to Decision — The Core Cycle
• Lesson 3: Data, Information, and Insight — Knowing the Difference
• Lesson 4: How Organizations Make Decisions
• Lesson 5: A Simple Framework You Can Use Today
• Course Quiz (10 questions)
About This Course
Course Structure
Lesson 1: Business Intelligence Is Everywhere
📖 LESSON TEXT
Let's begin by dismantling a myth. When most people hear "business intelligence," they picture dashboards, data analysts, and expensive software. That's not wrong — but it's like describing music by pointing only at a concert hall's sound system. The equipment is not the music. And the software is not the intelligence.
Here is the truth at the heart of this entire program: business intelligence is simply the discipline of gathering information, making sense of it, and using it to make better decisions. That's it. And by that definition, you have been practicing business intelligence your entire life.
Consider this morning. Before you were even fully awake, before your feet touched the floor, your mind was already at work. It gathered information — the light coming through the window, the temperature of the room, how rested your body felt, the sounds from outside, your memory of what day it is and what it holds. It assessed all of that in an instant. And it made a decision: get up now, or rest a few more minutes. You ran a complete intelligence process before breakfast, and you didn't even notice.
This is the point. Intelligence — gathering, assessing, deciding — is not something alien that lives inside computers. It is one of the most natural things human beings do. We do it constantly. Crossing a street, we gather information about traffic, assess the speed and distance of cars, and decide when to step. Choosing what to eat, we assess hunger, health, time, and taste. Every one of these is a small act of intelligence informing action.
So why does business intelligence feel so intimidating? Because organizations operate at a scale and complexity where the gathering and assessing can no longer happen in someone's head. A single person can sense whether a room is too cold. A company with ten thousand customers across a dozen markets cannot simply "sense" whether its customers are satisfied. It needs to gather that information deliberately, organize it, and assess it systematically. The tools of enterprise BI — the dashboards, the databases, the models — exist for exactly one reason: to extend that natural human process of intelligence to a scale the human mind can't hold on its own.
This reframing matters enormously, and not just philosophically. It matters because it means you are not starting from zero. You already have the core instinct. Decision intelligence, as a professional skill, is about taking something you already do naturally and making it deliberate, systematic, and reliable — so that your decisions, and your organization's decisions, are consistently better.
Throughout this program, whenever a concept feels abstract or technical, return to this anchor: it's just gathering, assessing, and deciding — the same thing you did this morning before you got out of bed, done more deliberately and at greater scale.
🎬 VIDEO SCRIPT
[On camera, warm and direct] Let me start by breaking a myth. When you hear "business intelligence," you probably picture dashboards, data analysts, expensive software. Right? Here's the thing — that's the equipment. It's not the intelligence. [pause] Business intelligence is really just this: gathering information, making sense of it, and using it to make a better decision. And if that's what it is… then you've been doing it your whole life. Think about this morning. Before you even got out of bed, your mind gathered information — the light, the temperature, how tired you felt, what day it is — assessed all of it in a second, and made a decision: get up, or five more minutes. That's a complete intelligence process, and you didn't even notice. [lean in] That's what this whole program is about. Not turning you into a data scientist. Taking something you already do naturally — gathering, assessing, deciding — and making it deliberate, systematic, and reliable. Organizations need tools to do this because they're too big to just "sense" what's going on. But the core skill? You already have it. So whenever something in this program feels technical or intimidating, come back to this: it's just gathering, assessing, and deciding. The same thing you did this morning — done better, and at bigger scale. Let's build from there.
Lesson 2: From Information to Decision — The Core Cycle
📖 LESSON TEXT
In Lesson 1 we established that intelligence is something you already do. Now let's name its structure, because once you can see the structure, you can improve each part of it deliberately.
Every good decision moves through four stages. We'll call it the core cycle: Gather, Assess, Decide, Act. Understanding these four stages — and where each one tends to break down — is the practical heart of decision intelligence.
Gather
First, you collect the relevant information. In a personal decision, this happens automatically. In an organizational decision, it has to be intentional: what do we actually need to know to make this call? The most common failure here is gathering the wrong information — lots of it — while missing the one fact that matters. Good decision-makers ask, before anything else: what information would actually change my mind? Then they go get that.
Assess
Next, you make sense of what you gathered. Raw information is not yet useful; it has to be interpreted. This is where you look for patterns, weigh reliability, and separate signal from noise. The classic failure here is confirmation — seeing only what supports the decision you already wanted to make. Strong assessment deliberately looks for what would prove you wrong, not just what proves you right.
Decide
Then you choose. A decision is a commitment among real alternatives. If there's only one option, there's no decision to make — just an action to take. Good deciding means genuinely weighing trade-offs: every choice gives something up. The failure here is avoidance — delaying, deferring, or letting the decision get made by default because no one chose. Not deciding is itself a decision, usually a poor one.
Act
Finally, you act — and then you watch what happens. This last part is where intelligence becomes a cycle rather than a line. The results of your action become new information, which you gather and assess for the next decision. Organizations that skip this step never learn; they make the same decisions and the same mistakes repeatedly. The ones that close the loop — that treat every outcome as data for the next round — get smarter over time.
Here's why naming these four stages matters: when a decision goes wrong, it almost always failed at a specific stage. You gathered the wrong information. Or you gathered the right information but assessed it poorly. Or you assessed it well but couldn't commit. Or you decided well but never checked the result. Diagnosing which stage failed is how you get better — and it's a skill you'll use for the rest of the program.
🎬 VIDEO SCRIPT
[On camera] Okay — in the last lesson we said intelligence is something you already do. Now let's name how it actually works, because once you see the structure, you can improve it. Every good decision moves through four stages. Gather. Assess. Decide. Act. [count on fingers] Gather — you collect the information that matters. And the trick here isn't collecting more, it's asking: what would actually change my mind? Go get that. Assess — you make sense of it. Look for patterns, weigh what's reliable. And here's the trap: most of us only look for what confirms what we already believe. Strong thinkers look for what might prove them wrong. Decide — you actually choose. Real deciding means accepting a trade-off; every choice gives something up. And not deciding? That's still a decision — usually a bad one. Act — you do it, and then you watch what happens. [pause] That last part is everything. The result becomes new information for your next decision. That's what turns this from a straight line into a cycle — into learning. Here's the payoff: when a decision goes wrong, it failed at one specific stage. Wrong information. Or bad assessment. Or couldn't commit. Or never checked the result. Figure out which stage broke — and you know exactly how to get better.
Lesson 3: Data, Information, and Insight — Knowing the Difference
📖 LESSON TEXT
Three words get used as if they mean the same thing: data, information, and insight. They don't — and confusing them is one of the most common and costly mistakes in organizational decision-making. Understanding the difference will immediately make you a sharper thinker about any dashboard, report, or analysis you ever see.
Data
Data is raw facts, without context. "14." "Blue." "$4,200." "March 3rd." On its own, a piece of data tells you almost nothing. It's a measurement, an observation, a record. Organizations are drowning in data — they collect enormous amounts of it — but data by itself doesn't help anyone decide anything.
Information
Information is data placed in context so that it means something. "Sales were $4,200 on March 3rd" is information — the raw number now has a subject and a time. "Customer satisfaction is 14% lower than last quarter" is information. This is more useful, but notice: information tells you what happened. It doesn't yet tell you what to do.
Insight
Insight is the understanding that emerges when you interpret information well enough to act on it. "Satisfaction dropped 14% right after we changed our support hours, and the complaints cluster around evening availability" — that's insight. It connects information into a story that points toward a decision. Insight is where information finally becomes useful. It answers not just what happened, but what it means and what to do about it.
Here is the practical lesson. The value ladder goes data → information → insight, and each step requires work. Most organizations are excellent at collecting data, decent at turning it into information, and poor at reaching insight. They produce dashboards full of numbers — information — and then wonder why decisions don't improve. The numbers were never the point. The insight is the point, and getting from information to insight requires human judgment, context, and the right questions. No dashboard produces insight on its own. People do.
This is also why the "business intelligence is just software" myth is so damaging. Software can gather data and organize it into information beautifully. But the leap to insight — the leap that actually changes decisions — is a human act of interpretation. That leap is the skill this entire program is teaching you to make.
🎬 VIDEO SCRIPT
[On camera] Three words that get thrown around like they mean the same thing — data, information, insight. They don't. And mixing them up costs organizations a fortune. Let me make it stick. Data is raw facts with no context. "14." "$4,200." "Tuesday." On its own? Tells you almost nothing. Information is data with context — so it means something. "Sales were $4,200 on Tuesday." "Satisfaction dropped 14% this quarter." Better. Now it tells you what happened. But — it doesn't tell you what to do. Insight is when you interpret that information well enough to actually act. "Satisfaction dropped 14% right after we cut evening support hours, and the complaints are all about evenings." [pause] Now you know what happened, what it means, AND what to do. Here's the thing most organizations get wrong: they're great at collecting data, okay at making information, and terrible at reaching insight. They build dashboards full of numbers and wonder why nothing improves. Because numbers were never the point. Insight is. And getting there takes human judgment — the right questions, real context. No dashboard does that for you. People do. That leap — from information to insight — that's the skill we're building.
Lesson 4: How Organizations Make Decisions
📖 LESSON TEXT
So far we've talked about intelligence at the human scale. Now let's scale up, because organizational decision-making has features that individual decision-making does not — and understanding them is what separates someone who can make good personal decisions from someone who can help an organization decide well.
The first difference is distributed information. In your own head, all the information for a decision is in one place. In an organization, the information needed for a single decision is scattered across many people, departments, and systems. The salesperson knows something the finance team doesn't. The frontline staff see problems the executives never hear about. A huge part of organizational decision intelligence is simply getting the right information to the right place at the right time — which is exactly what business intelligence systems exist to do.
The second difference is that organizations decide through people, not despite them. Even the best data doesn't decide anything; a person or group of people does, and they bring incentives, politics, habits, and blind spots. This is why two organizations with identical data can make opposite decisions. Decision intelligence in an organization is never purely technical — it's also about how decisions actually get made, who's in the room, and what they're paying attention to.
The third difference is stakes and permanence. Personal decisions are usually reversible and affect mainly you. Organizational decisions often commit large resources, affect many people, and can't easily be undone. This raises the value of getting the earlier stages — gather and assess — right before committing. The cost of a poor decision scales with the organization.
There's a useful spectrum to know. On one end are operational decisions: frequent, routine, lower-stakes — which supplier to reorder from, how to schedule this week's shifts. These benefit from good information and clear rules. On the other end are strategic decisions: rare, high-stakes, hard to reverse — entering a new market, changing the business model. These require deep assessment and judgment, and no dashboard will make them for you. Most organizations over-invest in data for operational decisions and under-invest in genuine thinking for strategic ones. Knowing which kind of decision you're facing tells you how much and what kind of intelligence it deserves.
The takeaway: helping an organization decide well means understanding that its information is scattered, its decisions run through fallible people, and its stakes vary enormously. Good decision intelligence accounts for all three — it's not just about better data, but about getting the right understanding to the right people for the kind of decision they're actually facing.
🎬 VIDEO SCRIPT
[On camera] We've been talking about intelligence at the personal level. Now let's scale up — because organizations decide differently than individuals, in three big ways. One: the information is scattered. In your head, everything's in one place. In an organization, the sales team knows something finance doesn't, the frontline sees problems the executives never hear about. So a huge part of the job is just getting the right information to the right place. That's literally what BI systems are for. Two: organizations decide through people. Data never decides anything — a person does. And people bring incentives, politics, blind spots. That's why two companies with the exact same data make opposite calls. Three: the stakes are bigger and harder to undo. A personal choice is usually reversible. An organizational one commits real money and affects real people. So getting the early stages right — before you commit — matters way more. And here's a distinction to carry with you: operational decisions are frequent, routine, low-stakes — they need good information and clear rules. Strategic decisions are rare, huge, hard to reverse — they need deep judgment, and no dashboard will make them for you. Most organizations pour data into the small decisions and wing the big ones. Don't be most organizations.
Lesson 5: A Simple Framework You Can Use Today
📖 LESSON TEXT
We'll close this foundational course with something practical — a framework you can apply to any real decision, starting today. It brings together everything from the previous lessons into five questions. It's deliberately simple, because a framework you actually use beats a sophisticated one you don't.
Whenever you face a decision that matters, ask these five questions in order:
1. What am I actually deciding?
Name the real decision, precisely. Many bad decisions come from solving the wrong problem. "Should we hire another salesperson?" might really be "How do we grow revenue?" — and hiring may not be the answer. Get the question right before you answer it.
2. What would change my mind?
Before gathering information, decide what information matters. Identify the facts that would actually shift your choice. This focuses your gathering and protects you from drowning in irrelevant data — and from only collecting what confirms what you already believe.
3. What does the information actually tell me?
Assess honestly. What's the real signal here? What's the story the information tells — and what story would someone who disagreed with me tell about the same information? Deliberately consider the interpretation you don't like.
4. What are my real options, and what does each cost?
List genuine alternatives — including doing nothing. For each, name the trade-off: what you give up by choosing it. If you can't name what an option costs, you haven't understood it yet.
5. How will I know if I was right?
Before you act, decide what result would tell you the decision worked — and set a time to check. This closes the loop. It turns the outcome into information for your next decision and keeps you honest.
That's the whole framework: name the decision, know what would change your mind, assess honestly, weigh real options and their costs, and plan to check the result. Notice that it maps directly onto the core cycle from Lesson 2 — gather, assess, decide, act — with the discipline built in at each stage where people usually fail.
You don't need software to use this. You don't need a data team. You can apply these five questions to a decision you're facing this week — at work or in your own life — and you'll make it more deliberately than you would have otherwise. That is decision intelligence at its foundation. Everything else in this program builds on it: better ways to gather (data and dashboards), better ways to assess (analysis and evaluation), and better ways to decide at organizational scale. But it all comes back to these five questions.
🎬 VIDEO SCRIPT
[On camera, practical and encouraging] Let's finish with something you can actually use — today. A framework for any real decision. Five questions. And it's simple on purpose, because a framework you use beats a fancy one you don't. Question one: what am I actually deciding? Name it precisely — a lot of bad decisions are just answering the wrong question. Two: what would change my mind? Decide what information matters BEFORE you go collect it. That keeps you from drowning in data and from only finding what you wanted to find. Three: what does the information really tell me? And here's the discipline — what story would someone who disagreed with me tell about this same information? Sit with that one. Four: what are my real options, and what does each cost? Including doing nothing. If you can't name what an option costs you, you don't understand it yet. Five: how will I know if I was right? Decide that before you act, and set a time to check. [pause] That's it. Name it, know what would change your mind, assess honestly, weigh the trade-offs, check the result. No software. No data team. Try it on one real decision this week — and you'll already be practicing decision intelligence. Everything else in this program builds on these five questions. I'll see you in the next course.
Course Summary
In this foundational course, you learned that:
• Business intelligence is the discipline of gathering, assessing, and deciding — something you already do naturally, made deliberate and systematic.
• Every good decision moves through a core cycle: Gather, Assess, Decide, Act — and closing the loop is what creates learning.
• Data, information, and insight are different things; insight is where information becomes useful, and reaching it takes human judgment, not just software.
• Organizations decide differently: information is scattered, decisions run through people, and stakes vary from routine to strategic.
• A simple five-question framework can make any decision more deliberate — and it's the foundation the rest of the program builds on.
Next course: Data Literacy for Decision-Makers — where we go deeper into gathering and making sense of the information behind your decisions.
Course Quiz
10 questions. Recommended pass mark: 70% (7/10). Answer key with explanations follows — remove or hide the answer key from the student-facing version; keep it for your platform's grading setup.
1. According to this course, business intelligence is best understood as:
A) A type of software used by data analysts
B) The discipline of gathering information, assessing it, and using it to make better decisions
C) A collection of dashboards and reports
D) A skill only large organizations need
Answer: B. The course's central idea is that BI is a discipline — gathering, assessing, deciding — not the tools used to do it.
2. The "core cycle" of every good decision, in order, is:
A) Decide, Act, Gather, Assess
B) Gather, Decide, Act, Assess
C) Gather, Assess, Decide, Act
D) Assess, Gather, Act, Decide
Answer: C. Gather, Assess, Decide, Act — with the outcome of acting feeding back into the next round.
3. What makes the core cycle a "cycle" rather than a straight line?
A) It repeats the same steps forever without change
B) The results of acting become new information for the next decision
C) It can be done in any order
D) It only applies to organizations
Answer: B. Closing the loop — treating outcomes as new information — is what creates learning over time.
4. "$4,200" written on its own, with no context, is an example of:
A) Insight
B) Information
C) Data
D) A decision
Answer: C. Raw facts without context are data. Add context ("sales were $4,200 on Tuesday") and it becomes information.
5. Which of the following is an example of insight, not just information?
A) Customer satisfaction is 14% lower than last quarter
B) Satisfaction dropped 14% right after we cut evening support hours, and complaints cluster around evenings
C) We received 320 support tickets this month
D) Our support team has five members
Answer: B. Insight connects information into a story that points toward a decision — what happened, what it means, and what to do.
6. The course argues that most organizations are:
A) Excellent at reaching insight but poor at collecting data
B) Good at collecting data but poor at reaching insight
C) Equally strong at all three: data, information, and insight
D) Unable to collect data at all
Answer: B. Organizations tend to collect data well but struggle to reach the insight that actually improves decisions.
7. In the assessment stage, the most common failure described is:
A) Gathering too little data
B) Confirmation — seeing only what supports the decision you already wanted
C) Acting too quickly
D) Having too many options
Answer: B. Strong assessment deliberately looks for what would prove you wrong, not just what confirms your preference.
8. A key difference between organizational and personal decision-making is:
A) Organizations always have less information
B) Information needed for a decision is scattered across many people and systems
C) Organizational decisions are always reversible
D) Personal decisions never involve trade-offs
Answer: B. In organizations, the relevant information is distributed — a core reason BI systems exist.
9. "Strategic" decisions, as described in the course, are typically:
A) Frequent, routine, and low-stakes
B) Rare, high-stakes, and hard to reverse
C) Always made by software
D) Less important than operational decisions
Answer: B. Strategic decisions are rare and consequential, requiring judgment rather than routine rules or dashboards.
10. In the five-question framework, why do you decide "how will I know if I was right?" BEFORE acting?
A) To avoid ever having to make the decision
B) To close the loop and turn the outcome into information for the next decision
C) Because it's required by law
D) To make the decision take longer
Answer: B. Deciding your success measure in advance closes the loop, keeps you honest, and feeds the next decision.
MODEL COURSE — review notes: (1) Confirm the teaching matches how you and your consultants actually deliver this material; adjust examples to real BIIM cases where possible. (2) The video scripts are written to be spoken naturally; time them and adjust length to your format. (3) Set the quiz pass mark and certificate trigger in your platform. (4) This is Course 1 of 7 in Decision Intelligence — if the depth and voice are right, the remaining 6 follow this same structure.
Prerequisites
No prerequisites required. This course is designed for beginners.
Sample Certificate Preview




















