Explain an optimization model and its trade-offs to managers, and see what an operations research career requires.
Why it matters
An optimization model changes nothing until someone acts on it. The people who decide (operations directors, finance teams, hospital managers) rarely want to see a constraint matrix. They want to know what to do, what it is worth, how sure you are, and what could go wrong. Operations research analysts who can explain a model clearly are the ones whose models get used, and communication is listed in nearly every OR job description.
Lead with the decision
Structure every presentation or memo as answer first:
- The recommendation in one sentence: "Close the Riverside warehouse and move its 14 stores to Northgate and Lakeview."
- The value: "This saves about 410,000 per year (7% of distribution cost) against last year's baseline."
- The key reasons: two or three, in business language.
- The risks and conditions: "The saving holds unless freight rates rise more than 25%; transition costs of about 150,000 are included in year one."
- What you need from them: a decision, a budget, a pilot.
The method goes last, briefly, or in an appendix.
Translate the model into plain language
Replace OR words with the business meaning.
| model term | say instead |
|---|---|
| decision variables | the choices we can make (which warehouses, which routes) |
| objective function | what we are trying to improve (total yearly cost) |
| binding constraint | the limit that is holding us back (Northgate's dock capacity) |
| shadow price | what one more unit of that limit is worth (each extra dock hour saves about 85) |
| infeasible | there is no plan that meets every rule; one rule has to give |
| optimal | the best plan we found under these assumptions |
Shadow prices are especially valuable to managers: they say where an investment pays off. "An extra painter is worth 5 per hour to us; overtime at 12 per hour does not pay" is a sentence a manager can act on.
Show trade-offs, not a single answer
Optimal models are only optimal for their assumptions. Show how the answer moves.
- Scenario table: base case, demand +10%, freight +20%, one warehouse closed, two closed. One row per scenario, with cost and service level.
- Trade-off curve: cost versus service (for example, total cost against the share of stores reached within one day). Managers choose a point on the curve; that is their call, not the model's.
- Ranges, not false precision: "about 7% (between 5% and 9% across scenarios)" is more honest than "7.13%".
Make the result believable
- Start with the baseline. "The model reproduces last year's actual cost within 2%" earns trust before you show any saving.
- Explain one example in detail. Walk through why store 23 is moved: it is 40 km closer to Lakeview and the truck is half empty today.
- Name the assumptions and who agreed them.
- Show the people who run the operation the plan before the meeting. Their objections are free validation.
Visuals that work
- A map of the network before and after.
- A bar chart of cost by component (fixed versus freight) for each scenario.
- A simple table of the decision: which store goes to which warehouse.
- Avoid solver logs, matrix dumps and charts with ten colours.
Careers in operations research
Operations research analysts work in logistics and transport, airlines, manufacturing, healthcare, energy, finance, consulting, technology companies and government, including defence. Common job titles include operations research analyst, decision scientist, optimization engineer and supply-chain analyst.
What employers usually look for:
- Education: a bachelor's in a quantitative field (mathematics, statistics, industrial engineering, computer science, economics) is the usual minimum, and many roles ask for a master's in operations research, industrial engineering, analytics or a related field.
- Skills: linear and integer programming, simulation, statistics, Python or R, SQL, a solver (Gurobi, CPLEX, CBC, OR-Tools or HiGHS), spreadsheets, and communication.
- A portfolio: two or three small projects (a staffing model, a routing heuristic, a simulation of a service line) with a short write-up each, ideally on real public data.
Professional bodies. INFORMS (the Institute for Operations Research and the Management Sciences, informs.org) runs conferences, student chapters, job boards and the Franz Edelman Award; its Certified Analytics Professional (CAP) credential is optional and not required by most employers. In the UK, the OR Society (theorsociety.com) plays a similar role. For job outlook and pay in the US, see the Bureau of Labor Statistics page for operations research analysts. Requirements and credentials change, so read the official pages before you plan. Checked on 2026-10-23.
Common mistakes
- Leading with the method. Nobody needs the simplex method in slide 2.
- Presenting one "optimal" number without scenarios or ranges.
- Using jargon such as "the dual of constraint 7 is non-zero".
- Hiding assumptions. When one turns out wrong, trust in the whole model goes with it.
- No clear ask. End with the decision you need.
Quick recap
- Answer first: recommendation, value, reasons, risks, ask.
- Translate model terms into business language; shadow prices become "what one more unit is worth".
- Show scenarios, trade-offs and ranges.
- Build trust with a baseline, a worked example and operator review.
- OR careers usually need a quantitative degree (often a master's), solver and coding skills, and a portfolio.
Try it
In the Do tab, turn one of this course's models into a one-page brief for a manager and present it.