Supply Chain Management · Operations
Business operations management, from the operator's side
What the discipline covers, the systems and measures an operations function actually runs on, and the point at which a growing company needs one. Built on Bureau of Labor Statistics data rather than a course prospectus.
Reviewed August 2026 · The Insight Journal Editorial Team
In short
The definition
What business operations management is
In short
A company's operations are the repeatable parts of its work: the things it will do again next week because it did them last week. Operations management is the discipline of running that repeating machine on purpose rather than by accident.
Strategy decides what a company is trying to be. Operations decides whether any of that survives contact with a Tuesday.
Four activities, whatever the list calls them
Published breakdowns of this field vary in length and in vocabulary. Underneath the variation, the same four activities keep appearing: design the work, plan the capacity to do it, control the quality while it runs, and improve it afterward.
Hold those four and every framework you meet becomes navigable. Lean is mostly design and improve, Six Sigma is mostly control and improve, and an ERP implementation is mostly plan.
What the word business is doing
Operations management grew up in manufacturing, and its vocabulary still shows it: takt time, changeover, first pass yield. Putting business in front of the phrase signals a services and back-office framing, not a different subject.
The mechanics transfer more cleanly than people expect. A support queue has a bottleneck and a cycle time in exactly the sense a production line does.
A question worth refusing
Why nobody agrees on how many functions it has
In short
Search this field and something odd happens. Every explainer offers a numbered list of functions, and the lists do not match each other in length or in wording.
That is not sloppiness. Enumerating a discipline is a way to teach it, and different teachers slice it differently for different courses. The number is a pedagogical choice, and treating it as a fact is how a reader ends up memorizing a list that no employer uses.
Standardized frameworks do exist, which is exactly why the contrast is useful. They are published, versioned and auditable by somebody other than the author.
Quality systems
ISO 9001 is the international standard for quality management systems. It is written to be certified against, which means an outside auditor has to be able to check it.
Performance excellence
The Baldrige Excellence Framework is run by NIST, part of the US Department of Commerce. It scores an organization across categories including operations, workforce and results.
Process reference
SCOR, the supply chain operations reference model maintained by ASCM, gives the material flow a shared measurement vocabulary. ASCM also administers the CPIM, CSCP and CLTD credentials.
Boundaries
Where operations ends and the neighboring disciplines begin
Most confusion about this field is really confusion about its edges. Four disciplines sit against it, and each boundary is drawn in a different place.
In short
| Discipline | What it owns | Where it meets operations |
|---|---|---|
| Supply chain management | Flow of materials and information from supplier to customer | Production scheduling against supplier lead times |
| Project management | Scoped work with a start, a finish and a team that disbands | Handing a finished project over as a process somebody now runs forever |
| Human resources | Who is in the roles, how they are paid, and the legal frame around that | Staffing a schedule, and training into a documented procedure |
| Finance | Capital, budget, reporting and the cash position | Cost per unit, working capital tied up in inventory, and capacity investment |
The supply chain edge
Any company that makes, stores or ships something runs both functions side by side. One keeps the internal machine running, the other keeps material flowing through it.
The seam between them is where a surprising share of operational pain starts. A production schedule that ignores a supplier's lead time is an operations decision that fails for supply chain reasons, and the supply chain management process sets out the sequence it was supposed to respect. For scale, CSCMP put US business logistics costs at $2.6 trillion in 2025, equal to 8.7% of GDP, which is the system most operations functions are quietly plugged into.
The HR comparison the search box keeps making
Google's People Also Ask box on this topic asks which is better, HR or operations. The two disciplines do not ask that about each other, because they own different halves of the same problem.
The comparison persists because in a company under about 50 people the same person often does both. That overlap is a stage, not a structure, and it usually ends the first time a hiring plan and a capacity plan contradict each other in public.
The working half
The systems an operations function actually runs
Definitions describe the field. This is the part that describes the job, and it runs as a loop rather than a list.
In short
- 01
Design
Decide how the work should run before anyone runs it: the sequence, the handoffs, the decision rights. Value stream mapping is the usual tool, because it makes waiting time visible in a way a flowchart does not.
- 02
Document
Write the standard operating procedure and the standard work behind it. The test of a good one is simple: a competent new hire can follow it without asking the author a question.
- 03
Run
Schedule against real capacity, not against optimism. Theory of Constraints puts it bluntly: an hour lost at the bottleneck is an hour lost for the whole system, and an hour saved anywhere else is a mirage.
- 04
Measure
Instrument the process while it is running, not at quarter end. Statistical process control exists to separate the variation that is normal from the variation that means something changed.
- 05
Improve
Close the loop with a structured cycle: PDCA from Deming, DMAIC from Six Sigma, or kaizen run as a standing habit. The framework matters less than whether the change gets written back into the procedure.
-
The systems layer
ERP is the system of record, with MRP for material planning, MES on the shop floor, WMS in the warehouse and CMMS for maintenance. Services teams substitute workflow and business process management tools for the last three. For a neutral view of which category does what, read how the software categories actually divide up.
Credentials exist for this half of the field too, and they are worth knowing by name even if you never sit one. ASQ administers the Certified Manager of Quality and Organizational Excellence and the Certified Six Sigma Black Belt, while ASCM covers the planning and material side. Neither body is a vendor, which is what makes their vocabulary usable as a common language.
Measurement
The metrics that tell you operations is working
Guides on this subject promise efficiency without naming a single measure of it. These are the measures an operations function reports on, and what each one is actually good for.
In short
| Metric | What it measures | What it exposes |
|---|---|---|
| Cycle time | Elapsed time for one unit of work, start to finish | How much of the time is waiting rather than working |
| Throughput | Units completed per period | Whether the constraint has moved since you last looked |
| Capacity utilization | Share of available capacity in use | Past roughly 85%, queues grow faster than volume does |
| First pass yield | Share of output correct with no rework | The true cost of quality, which rework hides |
| On time in full (OTIF) | Orders delivered complete and on the promised date | Whether delivery promises match delivery reality |
| Schedule adherence | Work completed in the period it was planned for | Whether planning is a forecast or a wish |
| Cost per unit | Fully loaded cost to produce one unit of output | Whether scale is actually making anything cheaper |
Manufacturing adds overall equipment effectiveness, which multiplies availability, performance and quality into one number. It is a good summary and a poor diagnosis, because three very different failures produce the same score.
Cost per unit is where this discipline meets finance directly, which is why it belongs alongside cost per unit and the wider cash flow picture. Any single metric run alone will eventually be gamed, so pair a speed measure with a quality measure and read them together.
The numbers
What operations management pays, and how large the field is
In short
$102,950
Median annual wage for general and operations managers, May 2024
US BLS
4,022,200
Jobs in the BLS top executives group, which contains general and operations managers, 2024
US BLS
+4%
Projected growth for that group 2024 to 2034, about as fast as average
US BLS
331,000
Openings projected each year on average over the decade, same group
US BLS
Reading these figures honestly
Only the wage figure is specific to general and operations managers. The employment, growth and openings numbers describe the whole top executives group, which also contains chief executives and legislators.
That distinction gets flattened constantly in career content, usually in a direction that makes the field look bigger. It is kept here because the group figure is still the honest way to show scale, provided it wears its own label.
The question we are not answering
Google's People Also Ask box wants the highest salary for an operations manager. No verified public figure answers that, because BLS publishes medians and percentiles rather than a ceiling.
A maximum quoted by a salary aggregator is a self-selected sample, not a measurement, so we are not going to reprint one. For the adjacent field where we do have federal data by title, see what the wider field pays and the paths into it.
Decision
When a growing company actually needs the function
Nothing in the ranking set answers this, and it is the question an operator actually arrives with.
In short
| Stage | What operations looks like | The signal you have outgrown it |
|---|---|---|
| Under 20 people | The founder is the operating system. Decisions are fast, consistent and entirely undocumented | The same question gets two different answers in the same week |
| 20 to 100 people | Procedure gets written down, a system of record appears, someone owns scheduling | New hires learn by shadowing because the written version is already out of date |
| 100 and above | A named owner, a measurement cadence, and improvement run as a standing cycle | Two teams both hit their targets and the customer order still slips |
Standardize or stay flexible
Standard process buys consistency and makes a company easier to train into, audit and scale. Flexibility buys speed and the ability to change direction without rewriting anything. Most growing companies need to choose function by function rather than defaulting to one everywhere.
Standardize when
- The same process repeats across several teams or locations.
- Quality or compliance requirements apply company wide.
- You are hiring faster than you can mentor people individually.
- The cost of a mistake is paid by the customer rather than by you.
Stay flexible when
- The product or the market is still moving under you.
- One small team owns the whole workflow end to end.
- Iteration speed matters more than uniformity this quarter.
- The process has changed twice since you last wrote it down.
Getting the sequence wrong is expensive in a specific way, which is the subject of growth that outruns its own operations. It is also worth reading alongside growth strategies that assume the operations can carry them, because most of them quietly do.
Failure modes
Where operations breaks first
Generic challenge lists name pressures. These are the specific ways an operation that worked last year stops working this year.
-
Process that lives in one head
The most common failure, and the least dramatic. Nothing goes wrong until the person holding it takes leave, and then three teams discover they were each guessing.
-
Capacity planned once
A schedule built on a forecast that nobody revisits will hold right up until demand moves. Capacity utilization above roughly 85% also stops absorbing variability, so queues grow faster than the extra volume suggests.
-
Quality drift
When one person checked every unit, quality was a personality trait. At volume it has to become a measured property, which is what first pass yield and statistical process control are for.
-
Handoff failure
Two teams hit their own targets and the customer still gets the order late. Most operational pain originates at a boundary rather than inside a function, which is why a RACI beats another dashboard.
-
Tooling sprawl
Five tools, four spreadsheets, and no system of record. The cost is not the licences, it is that no two reports agree and nobody can say which number is true.
-
The shared root
Four of these five are coordination failures wearing different costumes. That is also why the fix is usually structural rather than technical, and why designing for resilience rather than reacting to shocks applies just as well inside the building as it does across a supplier network.
Method
How we researched this page
Primary sources only
Pay and employment figures come from the Bureau of Labor Statistics Occupational Outlook Handbook, read on 17 August 2026. Sector cost comes from CSCMP. Frameworks are cited to ISO, NIST, ASQ and ASCM rather than to a page that cites nobody.
Figures carry their date
Every number on this page is printed with its publisher and its reference period. The median wage is May 2024 and will be superseded, so it says so rather than aging silently into a claim about today.
What we leave out
Where no verified figure exists we say that instead of estimating, which is why the highest-salary question above ends without a number. There are no invented case studies or practitioner anecdotes here. Our verification standard sets out the rest.
Questions