Form Follows Function

An architectural principle associated with Sullivan that relates form to a building's functions. Broader uses ask how design serves intended activities and experiences, while allowing multiple purposes and possible forms.

Sullivan's architectural principle connects a building's expression to what its parts do. As a broader design heuristic, it asks whether a chosen arrangement serves the activities and experiences that matter. Function need not mean bare utility: orientation, accessibility, beauty, symbolism, and adaptability can all be legitimate purposes when they are actually relevant.

A purpose rarely determines one unique form. Several designs can serve the same activity, and an unfamiliar form may suggest a useful new activity. Define priorities, inspect constraints, and compare candidates instead of treating every element as a simple pass-or-fail test. When a structure persists after its purpose changes, investigate what it still supports before removing it.

When to use it

When organizational structures seem to constrain rather than enable strategy; when products have features nobody uses; when processes exist without clear purpose; when designing anything new and need a first principle to guide decisions.

How it can help

For any design decision—product, organization, process, or communication—start by defining the function clearly, then design the form to serve it. When evaluating existing designs, ask: is the form serving the function or has it become its own justification? Organizational structures that persist after their original purpose has changed violate form follows function. Products with features that serve no user need violate it. Meetings that exist because 'we've always had them' violate it. Realign form to function regularly.