Skip to content
ENRU
All articles
Fiction Lab9 min readReviewed

The Martian and Kanban: Make Survival Work Visible

Too many urgent tasks can overwhelm a system with very little capacity.

For: Managers, analysts and facilitators

Editorial owner: Methodfield editorial team

Original abstract systems illustration for The Martian and Kanban.

This is a new method study of The Martian. Its existing Fiction Lab analysis uses a different method. Here, Kanban opens a separate question. The book premise below comes from the linked publisher or author record; the management interpretation is Methodfield's.

Verified premise

The publisher describes an astronaut stranded on Mars who must solve successive survival problems with limited supplies and support.

Management thesis

Kanban helps distinguish work ready to do, work actively consuming scarce capacity, blocked work and verified completion. Visibility protects attention when every request feels urgent.

System map

  • Authority: Local autonomy is high, but remote support still influences priorities and options.
  • Information: Progress must be visible enough to detect blocked work and changing conditions.
  • Resources: Time, energy, materials and cognitive focus are shared constraints.
  • Incentives: Starting an exciting fix can displace less visible maintenance.
  • Adaptation: The board changes with new evidence; it is a control surface, not a rigid plan.

Apply the method

  1. Define the workflow and a clear exit condition for each column, especially 'done'.
  2. Limit active work to available attention and resources; mark blocked items with cause and owner.
  3. Review ageing work and replenishment at a cadence matched to the environment, not to ceremony.

Failure mode

A board can show motion while hiding whether survival outcomes improved. Pair flow with a small number of outcome checks.

Ethical cost

Capacity limits protect a person from becoming an endlessly expandable resource.

Limits of the analogy

An isolated astronaut makes ownership unusually clear; real teams need explicit handoffs and shared priority rules.

Discussion question

How much work is currently started in your team but cannot move because its constraint is invisible?

Sources and further reading