Function-Behavior-Structure Matrix¶

An analytical model — instantiates Design-Principle Extraction and Reapplication

Documents a source as three linked layers — the structure it is built from, the behavior that structure produces, and the function that behavior serves — so visible structure is never mistaken for the whole explanation.

The Function-Behavior-Structure Matrix takes a source apart conceptually into three columns and draws the arrows between them: structure (how it is physically or logically organized), behavior (what that structure actually does when it runs), and function (what that behavior is for). Its whole reason for being is to break the most common extraction error — reading a design off its visible structure and stopping there, as if the shape were the explanation. By forcing each structural element to name the behavior it produces and each behavior to name the function it serves, the matrix reveals that the same function can often be met by very different structures — which is exactly the freedom a reapplication needs. The topmost layer, function, is where the source's objective becomes legible.

Example¶

A furniture maker wants to borrow the earthquake resilience of traditional Japanese timber joinery for a modern shelving system, without simply copying the joints for their looks. In the matrix, the structure column lists the interlocking mortise-and-tenon brackets cut to slide together without glue or nails. The behavior column asks what that structure does: under lateral load the joints flex and slip slightly, dissipating energy instead of resisting it rigidly. The function column asks what that behavior is for: survive seismic shaking without the brittle snap a rigid glued frame would suffer.

Laid out this way, the lesson stops being "use these beautiful joints." The function is energy dissipation through controlled flex; the behavior is slip-and-recover under lateral load; and the structure is only one way to get there. The furniture maker can now hunt for a structure suited to plywood and steel fasteners that reproduces the same flexing behavior — because the matrix separated the function they need from the specific joinery they were tempted to copy.

How it works¶

The matrix's distinguishing discipline is the two mappings: structure→behavior and behavior→function, made explicit rather than assumed. A structural element with no behavior arrow is decorative or vestigial; a behavior with no function arrow is a side effect; and a function reachable by more than one structure marks a degree of freedom the target can exploit. Reading up the columns yields the objective trace — the function layer names what the source is ultimately optimizing — while reading down exposes exactly which structures are load-bearing for that objective and which are incidental. It is the conceptual complement to a physical teardown: the teardown exposes the parts, the matrix explains what they are doing there.

Tuning parameters¶

Decomposition depth — how finely structure is broken down before mapping. Deep decomposition catches subtle structure→behavior links but multiplies rows; shallow decomposition is legible but can lump a critical element into a coarse block.
Behavior specificity — describing behavior qualitatively ("flexes") vs quantitatively ("dissipates ~X% of lateral energy"). Quantified behavior transfers more precisely but demands measurement.
Function abstraction — how far up the "what is it for?" ladder the function column reaches. Higher functions reveal more alternate structures; too-high functions become vague objectives that guide nothing.
Arrow completeness — whether every element is required to link both ways. Enforcing complete mapping surfaces decorative structure and side-effect behavior, at more analytic effort.

When it helps, and when it misleads¶

Its strength is that it manufactures design freedom: by proving a function is separable from any one structure, it licenses the target to meet the same function with different materials — the core move of the whole archetype. It also catches decorative structure (no behavior) and accidental behavior (no function) that a structure-only reading would preserve.

Its failure mode is retrofitting intent — narrating a clean function for a structure that was actually an accident, so the matrix reads more purposeful than the source ever was. It can also mislead when a structure serves several functions at once and the analyst records only the obvious one. The anchor here is Gero's Function-Behavior-Structure framework, which formalizes exactly these three views and the mappings between them^[1]; used honestly, it forces the analyst to show the behavior that connects a structure to its claimed function, rather than asserting the function directly. The discipline is to leave a function cell empty when no behavior actually delivers it, rather than inventing one.

How it implements the components¶

function_behavior_structure_map — the matrix is this map: it separates what the source is for, what it does, and how it is organized, and draws the arrows that keep structure from being mistaken for the whole explanation.
optimization_objective_trace — the function layer, read from the top down, names what the source is optimizing, distinguishing the objective from the structures that happen to serve it.

It analyzes conceptual structure-behavior-function, where the Teardown Workshop physically exposes the parts and the Constraint Laddering Interview elicits *why they exist; it does not classify features as essential vs incidental (the Essential/Incidental Feature Sort) or record the resulting principle (Design Principle Card).*

Instantiates: Design-Principle Extraction and Reapplication — the matrix supplies the structure-behavior-function analysis the principle is abstracted from.
Consumes: the Teardown Workshop exposes the raw structure the matrix organizes.
Sibling mechanisms: Teardown Workshop · Essential/Incidental Feature Sort · Analogy Mapping Canvas · Benchmark Deconstruction Grid · Biomimetic Translation Sheet · Constraint Laddering Interview · Design Principle Card · IP and Provenance Checklist · Post-Transfer Boundary Review · Transfer Prototype Experiment

References¶

[1] John Gero's Function–Behavior–Structure framework models designs in three linked views — function (what it is for), behavior (what it does), and structure (how it is composed) — with explicit mappings between them. Separating the three is what lets a designer see that one function can be met by many structures, the degree of freedom a reapplication exploits. ↩