The idea
Dimensional consistency tests whether quantities in a model can sensibly combine. A result measured in completed tasks per week must arise from inputs whose units reduce to that form. Unit checking often exposes mistakes before a complicated model is run.
Worked example
A fictional workshop estimates weekly output using five workers, 20 hours per worker per week, and two completed units per worker-hour. Multiplication gives 200 units per week. If someone instead enters a monthly productivity estimate without conversion, the numerical result may look plausible while representing the wrong quantity. Writing units beside every number makes the mismatch visible and invites discussion about whether the productivity assumption is realistic.
Use it carefully
Consistent units do not guarantee a true model. Productivity may fall with overtime, jobs may vary in difficulty, and workers may need shared equipment. Unit checking catches one class of errors while leaving causal assumptions to be tested separately. Keep definitions stable across data sources and document conversions. A clean equation should make its operational meaning easier to examine, not conceal uncertainty behind formal notation.
FROM UNDERSTANDING TO ACTION
Put it to work.
Write an output equation for a familiar process. Include units on every term and identify one assumption that units cannot test.
RETRIEVE. REASON. REMEMBER.
Knowledge check.
Choose one answer for each question, then check your reasoning.
Sources & further reading.
Links support the core concepts or identify the book. Examples, exercises, and critical analysis are original Institute material. Source checks are not an independent expert review of every claim.
- MIT System Dynamics: operational thinking and dimensional consistency ↗
MIT System Dynamics: operational thinking and dimensional consistency; supports the core concept. Scenarios, calculations, and practice questions are original. Source reviewed 2026-10-19.