About MRX Ops Simulator
Learn operations management through gameplay
MRX Ops Simulator is a free, browser-based operations management simulation set inside a market research delivery operation. It is designed for students, educators, practitioners, and anyone who wants to develop first-principles intuition for how operating systems behave.
You make decisions inside a connected system and watch the consequences develop over time. That gives abstract ideas a concrete setting, so principles such as constraints, work in progress, flow, and throughput become easier to reason about.
Free to playBrowser basedDesktop gameplayEducational simulation
The curriculum
Operations principles you can learn
The simulator introduces operations theory when your run creates evidence for it. Tumbo, the in-game guide, connects what happened in the system to the principle that explains it.
01 · ConstraintsTheory of Constraints
Every system has a current constraint that limits its throughput. Improving the constraint can move the whole system. Improving another part can leave the outcome unchanged.
02 · ConstraintsBottleneck migration
Relieving one constraint often exposes the next one. The game teaches you to keep looking at the system after an improvement lands.
03 · FlowLittle's Law
Little's Law connects average work in progress, throughput, and cycle time in a stable system. The game turns that relationship into something you can observe through play.
04 · SystemsAmdahl's Law
Amdahl's Law began in computer architecture. Its systems lesson travels well. Speeding up one part has limited value when the rest of the process still takes most of the time.
05 · FlowWork in progress
The Kanban-style board makes unfinished work visible. You can see how WIP relates to waiting, cycle time, and the ability of the system to finish what it starts.
06 · PolicyPull thinking
Pull systems start work when the next part of the system can absorb it. The simulator lets you reason about the difference between starting more work and finishing more work.
07 · FlowFlow efficiency
Flow efficiency compares active working time with the total time required to deliver something. A busy system can still make work wait.
08 · SystemsLocal and system optimization
An improvement creates value when the whole system can use it. The simulator trains you to judge decisions by their effect on the complete flow.
The setting
Why market research is the system you run
A research study moves through a connected delivery chain from questionnaire design and programming through fieldwork and reporting. That makes market research a useful setting for learning service operations because each decision affects work that follows.
The board uses a Kanban-style layout to make the system visible. Each column represents a stage in the delivery chain, and the movement of work gives the theory a concrete form.
The setting is specific. The operating principles travel to other forms of knowledge work where people coordinate connected stages and make decisions under finite time.
Design
Build
Review
Deliver
Who it is for
Built for anyone learning how systems behave
Students
Use the game alongside an operations management course or as an independent way to develop intuition before working through the formal models.
Educators
Use a run as a discussion case. Ask learners to identify the current constraint, explain the result with an operations principle, and compare possible next moves.
Practitioners
Use the simulator to sharpen how you reason about a connected service operation and the delayed consequences of operational decisions.
Independent learners
Start with no formal background. The game introduces each principle when the system gives you a reason to care about it.
Intellectual lineage
Ideas behind the simulator
The simulator draws on a body of operations thinking from manufacturing, computing, product development, and management. These works give the game's named lessons their wider intellectual context.
TGBookThe Goal
Eliyahu M. Goldratt and Jeff Cox on constraints, throughput, bottlenecks, and whole-system optimization.
PFBookThe Principles of Product Development Flow
Donald G. Reinertsen on WIP, variability, handoffs, and the economics of flow.
TPSBookToyota Production System
Taiichi Ohno on visual management, standard work, flow, and continuous improvement.
MMBookThe Mythical Man-Month
Frederick P. Brooks Jr. on coordination overhead and the limits of adding people to late work.
LPaperLittle's original proof
John D. C. Little on the relationship between average WIP, throughput, and time in a stable system.
APaperAmdahl's original paper
Gene M. Amdahl on the system-wide limit of speeding up one serial part.
KGuideThe Official Guide to the Kanban Method
Kanban University on visual workflow, pull thinking, WIP, and flow policies.
The simulator is an independent educational product with no affiliation to the authors or publishers listed here.
