Recursion is a mental model used for better thinking and decision-making.

How do you apply Recursion?

To apply Recursion, identify situations where this framework is relevant, then use it as a lens to evaluate your options and decisions. The model is most useful when combined with other complementary mental models.

What category does Recursion fall under?

Recursion falls under the Computer Science & Algorithms category of mental models. Other models in this category can be found on the Computer Science & Algorithms hub page.

Why is Recursion important?

Recursion is important because it provides a structured way to think about problems that would otherwise be approached with intuition alone. Understanding this model helps you avoid common reasoning errors and make better decisions.

Recursion Mental Model: Definition &…

Recursion Mental Model: Definition &… | Faster Than Normal

Computer Science & Algorithms

Section 1

The Core Idea

Recursion is when a process or structure is defined in terms of itself: a function calls itself, a structure contains a smaller instance of the same structure, or a problem is reduced to a smaller version of the same problem. The recursion has a base case — a stopping condition — so that the chain of self-reference terminates. Without a base case, you get infinite regress or stack overflow. With it, recursion is a compact way to express repetition and hierarchical structure.

In computation, recursion often replaces explicit loops: instead of "do this N times," you say "do this once, then do the same thing on the remainder." The classic examples are factorial (n! = n × (n−1)! with base case 0! = 1), tree traversal (process a node, then recurse on each child), and divide-and-conquer (solve half the problem, recurse, combine). The mental move is to see that the problem at size N can be expressed as one step plus the same problem at size N−1 (or N/2), and to identify the smallest case that doesn't need further reduction.

Outside code, recursion appears in definitions (a sentence contains clauses that can contain sentences), in organisations (a team contains sub-teams of the same structure), and in strategy (a goal decomposes into sub-goals of the same type). The discipline is to spot when a situation is "the same thing at a smaller scale" and to define the base case so the recursion stops. The mistake is recursing without a base case (infinite loop) or confusing levels (treating the base case as if it were the recursive case).

Tail recursion — when the recursive call is the last action and its result is returned directly — can be optimised to a loop by compilers, avoiding stack growth. That's an implementation detail; the mental model is unchanged: reduce to a smaller instance, define the base case, and ensure termination. In design and strategy, the equivalent is "one level of decomposition plus the rule for the next level" with a clear stopping point.

Recursion

Contents

Popular Mental Models

How to cite

Continue exploring

The Core Idea

This connects to...