Q.Explain, using the analogy of a cricketer's batting average, why the Marginal Cost curve must lie below the Average Cost curve whenever average cost is falling, and above it whenever average cost is rising.
You're viewing a preview — the full solution, concept, methods & PYQ mapping are locked.
Start your 14-day free trial to unlock the full solution →A cricketer's batting average, at any point in her career, is the average of all her innings scores SO FAR. Whenever she plays a new innings, two things can happen: if her score in that new innings is BELOW her existing average, including this new score in the average must pull the average DOWN — because a below-average number was just added to the pool. Conversely, if her new score is ABOVE her existing average, it pulls the average UP. Only when her new score exactly EQUALS her existing average does the average stay exactly unchanged.
Marginal Cost and Average Cost relate to each other in EXACTLY the same arithmetic way. Marginal Cost is the cost of the "newest" unit of output — analogous to the batter's latest innings score — while Average Cost is the average cost of ALL units produced so far. So:
- Whenever : the newest unit costs less than the existing average, so including it pulls the average DOWN — Average Cost is falling.
- Whenever : the newest unit costs more than the existing average, so including it pulls the average UP — Average Cost is rising.
- Only when does adding the newest unit leave the average exactly unchanged — this is precisely the average's minimum (or turning) point. …
Unlock everything free for 14 days
- Full step-by-step solutions
- Concept-first explanations
- Methods, shortcuts & mistakes
- PYQ mapping + timed mock tests
Full access for 14 days. No credit card required.