Design Pattern

A reusable solution to a commonly occurring problem in a specific context—originally from architecture (Christopher Alexander) and famously applied to software (Gang of Four). A design pattern isn't a finished design but a template: it describes the problem, the solution structure, and when to apply it. Observer pattern, Factory pattern, Strategy pattern—each names a specific recurring problem and its proven solution. Applied beyond software: organizational design patterns (matrix structure for cross-functional work), communication patterns (standup for alignment), and decision patterns (RACI for clarity) all follow the same logic.

When to use it

When facing a problem that feels familiar but you can't articulate why; when designing systems and want to leverage proven solutions rather than inventing from scratch; when teaching or communicating solutions—patterns provide shared vocabulary; when debugging—recognizing which pattern was intended reveals where the implementation diverged.

How it can help

Build a personal library of patterns for recurring situations—not reinventing solutions each time but recognizing which pattern applies. In product development: 'this is a marketplace problem' immediately suggests a known set of solutions. In management: 'this is a coordination problem' suggests known patterns (daily standup, RACI matrix, hub-and-spoke). The power of patterns: they compress years of accumulated wisdom into recognizable, nameable, reusable solutions. Pattern recognition—'I've seen this before'—is the core expert skill.