UPI Study › Courses › Principles of Management › Free lessons › Lesson 5.2 Free with a free account
Decision Science at Work: The Quantitative Approach to Management
Principles of Management · Chapter 5: Modern Management PerspectivesSection 5.2 · lesson 20 of 11713 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Principles of Management.
Lesson complete
Earn the 3 college credits for Principles of Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Running the Operation: Balancing Efficiency and Customer Value →← Contemporary Schools of Management: A Comparative ViewNext lesson: Running the Operation: Balancing Efficiency and Customer Value →
In this lesson
The quantitative approach to management.
- Describe the origins and premise of the approach
- Explain the 6 categories of quantitative technique
- Weigh its strengths against its limits
- Judge when to model, and when not to
Transcript
Everything said in the video, section by section (1,768 words). Read along, or search it.
Modern Management Perspectives
Decision Science at Work
The last section mapped five modern schools. This one opens the first of them, the quantitative approach. It is often called decision science, or management science. We'll trace where it came from, and the premise it rests on. We'll name its six categories of technique, and the kind of problem each one addresses. Then we'll weigh what the approach genuinely contributes, against limits that deserve equally honest statement. Along the way, we'll meet one idea that matters more than any formula. Whatever a model cannot represent, it treats as if it did not matter at all. By the end, you should be able to judge when a model is the right tool, and when it is not.
Origins
Born in Wartime Operations Research
The quantitative approach traces to operations research. Operations research is the application of mathematical and statistical analysis to complex logistics and resource allocation problems. It was developed and refined during large-scale wartime military operations, in the mid twentieth century. The problems were hard ones. Allocating scarce supplies optimally, planning convoy routes, and scheduling complex operations under uncertainty. They demanded more rigor than judgment alone could reliably supply. Once these methods had proved their value under wartime conditions, they moved into industry in the decades that followed. Ordinary organizations faced analogous problems in peacetime. Resource allocation, and scheduling. Those peacetime applications formed the basis of the school this section covers.
The Premise
Represent the Problem as a Model
The approach rests on a specific premise. A management problem can be represented as a model. A model is a simplified representation of a real situation. It specifies the relevant variables, and the relationships between them, explicitly. That model can then be analyzed mathematically, to find a better decision than unaided judgment would reach on its own. Notice what the premise does not claim. It does not claim a model replaces judgment entirely. It claims that, for problems with enough well-defined structure, a properly built model can process more variables, more consistently, than intuition alone. So the premise has a condition built in. Enough well-defined structure. Much of this section is really about what happens when that condition fails.
Technique Categories
6 Tools, 6 Kinds of Problem
There are six categories of quantitative technique, and each suits a different type of problem. Optimization, including linear programming, allocates scarce resources among competing uses. The aim is to maximize or minimize some objective. For example, maximizing output within a fixed labor and material budget. Queuing analysis deals with waiting and service capacity. How many service stations does a system need, to keep waiting times acceptable for a given arrival pattern? Inventory models answer how much of an item to order at once, and when. They balance the cost of holding inventory against the cost of ordering too often, or running short. Forecasting projects future demand, or other uncertain quantities, from historical patterns. Simulation handles systems too complex to solve with a direct formula. It models the system's behavior computationally across many trial runs, to see what outcomes result. And network techniques handle project scheduling, mapping activities and their dependencies. That's the same kind of timing question Subchapter three point four introduced with the Gantt chart. Each category gets its tools and worked calculations in Subchapter fourteen point five. Here we only name them.
Table 5.2.1
What Each Technique Needs, and Where It Fails
Table five point two point one adds two more columns. What each technique requires, and its principal limitation. Optimization needs a defined objective and a set of constraints. Its limit is that the relationships must be stated as clean mathematical constraints. Queuing needs arrival and service rate patterns. It assumes those patterns are reasonably stable and well-described. Inventory models need the demand rate, the holding cost, and the ordering cost. They are sensitive to how accurately those inputs are known. Forecasting needs historical data with a discernible pattern. Its built-in assumption is that the future will resemble the past. Simulation needs a defined set of rules governing the system's behavior. It is only as realistic as those rules. Network techniques need activities, durations, and dependency relationships. Their weakness is that duration estimates are often uncertain, especially for novel work. Read down the limitation column and a pattern appears. Every technique depends on its inputs, and on assumptions about how the world behaves.
Delivery Mechanism
From Specialists to Managers
For these techniques to matter in everyday management, they had to reach working managers. Otherwise they would have stayed with trained specialists, running calculations by hand or on dedicated mainframe time. Two kinds of system made the difference. A management information system organizes and reports routine operational data, for managers to use directly. A decision support system goes further. It embeds one or more of the technique categories into software a manager can query directly, for a recommendation or an analysis. The manager doesn't need to understand the underlying mathematics personally. That delivery shift is a large part of why these techniques entered ordinary management practice, over the second half of the twentieth century.
Contributions
What the Approach Does Well
So what does the approach genuinely contribute? Four things. First, it forces explicit assumptions. Building a model means stating exactly what you assume about how variables relate. That surfaces disagreements and gaps that might otherwise stay hidden inside an unexamined judgment call. Second, consistency. The same inputs produce the same recommendation every time. Judgment, by contrast, can vary from one occasion to another, and from one decision-maker to another. Third, it handles more variables than intuition can reliably track, especially where variables interact in ways that aren't obvious. Fourth, it imposes the discipline of stating a problem precisely enough to model it. That discipline pays off even when the resulting model is imperfect. Trying to specify a problem precisely often reveals what was actually unclear about it.
Limits
The Limits, Stated Honestly
The limits deserve equally direct statement. First, a model is only as good as its assumptions. If the relationships it specifies don't hold in reality, the output is precise, but wrong. Second, unquantifiable factors are excluded, and so they are implicitly weighted at zero. A model that cannot represent morale, trust, or fairness doesn't judge them unimportant. It simply cannot see them. But in the recommendation, that works exactly like assigning them no weight at all. Third, precision can be mistaken for accuracy. A result shown to several decimal places looks authoritative. That precision says nothing about whether the assumptions were correct. Fourth, a model can obscure the value judgments built into it. Choosing to optimize for cost rather than employee wellbeing, or for speed rather than quality, is itself a value choice. A polished quantitative output can make that choice look like a neutral, purely technical finding. It isn't. It is a value-laden decision, presented as a calculation.
Captured Or Excluded
A Call Center Schedule, Modeled and Unmodeled
Here is a staff scheduling decision at a fictional call center. What the model captures sits beside what it excludes. The model captures the total labor hours available each week. It captures each employee's contracted shift-hour eligibility, and the minimum staffing level required per shift. And it captures the cost per labor hour, at standard versus overtime rates. Every one of those is precisely the kind of variable a scheduling optimization handles well. Now the other side. Which shifts individual employees have relied on, for childcare or other commitments. How a schedule change affects trust in management. Long-tenured employees' informal, unwritten shift preferences. And the morale cost of overriding an existing informal arrangement. None of these was judged unimportant. They are excluded because they don't reduce to the kind of input the model requires.
Human Factors And Analytics
The Blind Spot Carries Forward
Look at that excluded list again. It is, in large part, exactly what Chapter four addressed. Morale, group norms, the difference between compliance and genuine commitment, and a manager's assumptions about why people behave as they do. A model can compute an efficient schedule. It cannot tell a manager whether that schedule will be accepted willingly, or resented. That is precisely the distinction Subchapter two point two drew between compliance and commitment. This isn't a flaw of any one model. It is the structural blind spot the quantitative school carries, as the cost of its precision. Table five point one point one named that blind spot directly. The modern extension into analytics and algorithmic decision making carries the same limits forward. An algorithm trained on historical data captures only the variables it was given, and the patterns in its training data. It still excludes whatever was never represented, including human factors that were never recorded in the first place. And its recommendations still embed the value judgments of whoever chose what it should optimize for. The difference is that the choice is far less visible than in an explicitly built mathematical model.
Model Or Not
When to Model, and When Not To
So the practical judgment is knowing when a model is the right tool, and when it is not. Modeling tends to serve well under three conditions. The problem has clearly defined variables. Its structure is stable and reasonably well understood. And its objective can be stated precisely. Modeling serves poorly, or at least needs real caution, under three others. When the problem's most important factors resist quantification. When the relationships involved are genuinely uncertain, not merely unmeasured. And when the value judgment in the model's objective is itself, really, what is at stake in the decision. A manager who can tell these situations apart can use the approach for what it does well. She avoids both mistakes. She won't reject modeling outright, and she won't trust it beyond what it can actually support.
Case Vignette
The Optimal Schedule Nobody Would Accept
Here's a composite case, constructed for instruction. A planning team at Harborline Manufacturing built a linear programming model, to optimize a production line's weekly shift schedule. Its goal was to minimize total labor cost, while meeting every coverage requirement precisely. By its own internal measure, the output was genuinely optimal. No other feasible schedule could meet the same coverage requirements at a lower total cost. When the schedule was proposed, the workforce met it with immediate and widespread resistance. In minimizing cost, the solution had moved a cluster of senior employees off a shift pattern, one they had held informally for years. They had structured significant parts of their personal lives around it, even though no formal rule guaranteed it. The model had no variable for that arrangement. Nothing in the coverage requirements or cost data captured it. The team's mathematics were not wrong. The model correctly solved the problem as specified. What went wrong was the specification itself. An important factor was excluded, not by a deliberate judgment that it didn't matter, but because it was never quantified. And in a quantitative model, an excluded factor is functionally identical to a factor weighted at zero. Next, Subchapter five point three turns to operations management, and how a process that converts inputs into outputs is designed and run.
About Principles of Management at UPI Study
Principles of Management (Business 101) is a self-paced online course of 117 video lessons in 17 chapters, from the classical schools and the four management functions to leadership, motivation, change, human resources, strategy and ethics. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus Every course with PRO →
Why take it here
Why students take Principles of Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Principles of Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Decision Science at Work: The Quantitative Approach to Management
What is the quantitative approach to management?
What are the main quantitative techniques used in management?
What are the limitations of quantitative models in management?
When should a manager rely on a quantitative model to make a decision?
About the Principles of Management course
How many college credits is Principles of Management?
How much does Principles of Management cost and what is included?
Which universities accept UPI Study credits?
How long does Principles of Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Principles of Management.
117 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →