# MRX Ops Simulator: complete overview > MRX Ops Simulator is a free, browser-based operations management simulation created by Metaforms. It teaches operations theory through gameplay inside a simulated market research delivery operation. - **Canonical name:** MRX Ops Simulator - **Expanded name:** MRX Operations Simulator - **Canonical URL:** https://mrxsimulator.com/ - **Format:** Interactive educational simulation game - **Price:** Free to play - **Access:** Web browser - **Gameplay device:** Desktop or laptop screen - **Language:** English - **Setting:** A connected market research delivery operation - **Creator and publisher:** [Metaforms](https://metaforms.ai/) - **Intended audience:** Students, educators, operations practitioners, and independent learners - **Prior knowledge:** No formal operations-management background is required ## What MRX Ops Simulator is MRX Ops Simulator is an educational game for learning how connected operating systems behave. It places the player inside a simulated market research delivery operation, where decisions in one part of the system affect work elsewhere and their consequences develop over time. The purpose is to make abstract operations-management ideas concrete. Instead of encountering constraints, work in progress, throughput, cycle time, and flow only as definitions or equations, the learner can observe those relationships inside a running system and use them to explain what happened. MRX refers to market research. The market research setting is specific, but the operating principles travel to other forms of service operations and knowledge work in which people coordinate connected stages under finite time and capacity. The full simulation is designed for a desktop or laptop screen. Visitors on mobile can still access the same educational About content that explains the product and its curriculum. ## How the game teaches The learning model is experiential. The player makes decisions, observes the resulting system behavior, and develops a diagnosis of the whole operation rather than treating each stage in isolation. The simulator introduces theory when a run creates evidence for it. Tumbo, the in-game guide, connects an observed result to the operations principle that helps explain it. This makes theory a tool for interpreting the system rather than a detached list of terms. The board uses a Kanban-style layout. Columns represent connected stages in the delivery chain, and the movement and accumulation of work make the operating system visible. The interface helps learners reason about the difference between starting work, keeping resources busy, and finishing work through the complete system. ## Operations principles the simulator teaches ### Theory 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. ### Bottleneck migration Relieving one constraint often exposes the next one. An improvement therefore creates a reason to inspect the full system again rather than assuming the original diagnosis remains true. ### Little's Law Little's Law connects average work in progress, throughput, and cycle time in a stable system. The simulator turns that relationship into something learners can observe through play. ### Amdahl's Law Amdahl's Law began in computer architecture, but its systems lesson travels well. Speeding up one part of a process has limited value when the rest of the process still accounts for most of the elapsed time. ### Work in progress The Kanban-style board makes unfinished work visible. Learners can observe how work in progress, or WIP, relates to waiting, cycle time, and the system's ability to finish what it starts. ### Pull thinking Pull systems start work when the next part of the system can absorb it. The simulator helps learners reason about the difference between releasing more work and increasing the rate at which the complete system finishes work. ### Flow efficiency Flow efficiency compares active working time with the total elapsed time required to deliver something. A system can keep people or resources busy while still making work wait. ### Throughput and cycle time Throughput is the rate at which the complete system finishes work. Cycle time is the elapsed time work spends moving through the system. The simulator uses both as system-level outcomes rather than treating activity at one stage as sufficient evidence of improvement. ### Local and system optimization An improvement creates value when the whole system can use it. The simulator trains learners to judge a decision by its effect on complete flow, not only by whether one local stage becomes faster or busier. ## Why the setting is market research A research study moves through a connected delivery chain from questionnaire design and programming through fieldwork and reporting. Each decision affects work that follows, which makes market research a useful setting for learning service operations. The board's Kanban-style layout gives the delivery chain a concrete visual form. It makes stage-to-stage dependencies, unfinished work, waiting, and flow easier to inspect. The simulator uses the setting to teach transferable systems reasoning; it is not intended to suggest that the principles apply only to market research. ## Who the simulator is for ### Students Students can use the game alongside an operations-management course or as an independent way to build intuition before working through formal models. ### Educators Educators can use a run as a discussion case. Learners can be asked to identify the current constraint, explain the evidence with an operations principle, and compare possible next moves. ### Operations practitioners Practitioners can use the simulator to sharpen how they reason about a connected service operation, trade-offs between local and system performance, and the delayed consequences of operational decisions. ### Independent learners Independent learners can begin without a formal background in operations theory. The game introduces each principle when the simulated system gives the learner a reason to care about it. ## Intellectual lineage and further reading MRX Ops Simulator draws on operations thinking from manufacturing, computing, product development, software engineering, and management. The following works provide wider context for the named lessons in the simulator. ### The Goal [Eliyahu M. Goldratt and Jeff Cox's *The Goal*](https://www.toc-goldratt.com/en/product/The-Goal-A-Process-of-Ongoing-Improvement) provides context for constraints, throughput, bottlenecks, and whole-system optimization. ### The Principles of Product Development Flow [Donald G. Reinertsen's *The Principles of Product Development Flow*](https://www.leanproductflow.com/buy-the-books/) provides context for work in progress, variability, handoffs, and the economics of flow. ### Toyota Production System [Taiichi Ohno's *Toyota Production System*](https://www.routledge.com/Toyota-Production-System-Beyond-Large-Scale-Production/Ohno/p/book/9780915299140) provides context for visual management, standard work, flow, and continuous improvement. ### The Mythical Man-Month [Frederick P. Brooks Jr.'s *The Mythical Man-Month*](https://www.pearson.com/en-ca/subject-catalog/p/mythical-man-month-the-essays-on-software-engineering-anniversary-edition/P200000000149/9780132119160) provides context for coordination overhead and the limits of adding people to late work. ### Little's original proof [John D. C. Little's original proof](https://pubsonline.informs.org/doi/10.1287/opre.9.3.383) provides the formal relationship between average work in progress, throughput, and time in a stable system. ### Amdahl's original paper [Gene M. Amdahl's original paper](https://doi.org/10.1145/1465482.1465560) provides the system-wide limit on the benefit of speeding up one serial part. ### The Official Guide to the Kanban Method [The Official Guide to the Kanban Method](https://kanban.university/kanban-guide/) provides context for visual workflow, pull thinking, work in progress, and flow policies. The simulator is an independent educational product. Metaforms and MRX Ops Simulator are not affiliated with the authors, publishers, or organizations listed above, and the references do not imply their endorsement. ## About Metaforms Metaforms created and publishes MRX Ops Simulator as a free learning resource for the market research community. It built the simulator to share some of the operations thinking behind research delivery in a form anyone can explore, including people who never become customers. Metaforms describes itself as the Agentic OS for Market Research. It says it brings end-to-end agentic workflows to research operations and equips delivery teams with AI agents that work alongside them throughout a project. Learn more at [metaforms.ai](https://metaforms.ai/). ## Interpretation and scope - MRX Ops Simulator is an educational simulation, not a certification or a complete operations-management course. - The interface is Kanban-style; the game should not be described as teaching the complete Kanban Method. - Little's Law is presented with its stable-system condition. - Amdahl's Law originated in computer architecture and is applied as a transferable systems lesson. - The books, papers, and guide above provide intellectual context; their inclusion does not imply affiliation or endorsement. - Operational, financial, and AI-agent outcomes generated inside the game are simulated. They are not empirical evidence, customer results, or guarantees of real-world performance. ## Authoritative links - [Play MRX Ops Simulator](https://mrxsimulator.com/) - [Read the agent-oriented site manifest](https://mrxsimulator.com/llms.txt) - [Learn about Metaforms](https://metaforms.ai/)