A distinctive shape used once is a design choice. The same shape used three times, at three different scales, in three different roles, is a system — and the difference between those two things is almost entirely about repetition, not cleverness. This is the part of the one-feature framework that trips teams up even after they’ve done the hard work of finding a real feature: they find the thing, use it once in the logo, and then quietly go back to category defaults for everything else. The feature never gets the chance to become recognizable, because it only shows up in one place.
What “three scales” actually means
On Models Oddavell, the source feature was the tower’s balcony curves — a soft, sculptural line the designer traced directly to the finished identity: “Same feature. It mainly comes from the balcony curves.” What makes that identity read as considered rather than accidental is that the curve doesn’t stop at the wordmark. It shows up at three distinct scales, each doing a different job:
Identity scale — the wordmark. The letterforms in “Oddavell” carry repeating organic curves through the O, both D’s, and the A, plus a subtle calligraphic flourish on the V and the double L. This is the smallest, most concentrated expression of the shape — the one a viewer sees fastest and remembers most literally.
Surface scale — the pattern. The same curve family, drawn out and repeated, becomes a signature wave-line pattern used as a textural motif across the brand system — on print collateral, as a background treatment, wherever the identity needs to fill space without resorting to a stock texture. Asked directly whether the pattern traces back to the same architectural source as the logo, the answer was unambiguous: it’s drawn “directly from the building’s soft, sculptural architecture… its flowing forms and rhythmic curves.”
Interface scale — the component. The same curve logic reappears as the actual geometry of a UI element: a 1000px top radius on a flat base, used on every amenity tile across the site. It’s not a rounded corner borrowed from a component library — it’s an arch, sized and proportioned to read as the same family of curve as the logo and the pattern, just functioning as a container instead of a mark.
Three completely different jobs — a wordmark identifies, a pattern decorates, a component holds content — built from one shape family. That’s what “three scales” means in practice: not three variations on a theme, but the same specific geometry doing three different kinds of work.
Why repetition is the mechanism, not the polish
It’s tempting to treat this kind of cross-scale consistency as a finishing touch — the thing a senior designer adds once the “real” decisions are made. It’s closer to the actual mechanism of differentiation. A shape a viewer sees exactly once, in exactly one context, registers as a single design decision among many and is easy to forget. A shape a viewer encounters in the logo, then again in the background texture, then again in the shape of a UI card, accumulates — the eye starts to register the pattern before the conscious mind can name what it’s noticing. That accumulation is what makes an asset feel distinctive rather than merely look distinctive in any single instance.
This is also, not coincidentally, exactly what raises an asset’s uniqueness score in the Distinctive Brand Assets framework we referenced in the hub post: a shape repeated at scale across an entire system is a much larger asset for a competitor to replicate than a single logo mark. Copying a wordmark is a Tuesday afternoon. Copying a wordmark, a pattern, and a component geometry that all trace back to a physical feature of a different building entirely isn’t something a competitor can do at all.
Where the discipline can break
The place this most often falls apart in practice isn’t the identity or the pattern — teams usually get those two right, because they’re the obviously “brand” deliverables. It’s the interface layer, where a project’s UI defaults quietly slip back to generic conventions: default corner radii, default drop shadows, default card treatments pulled from whatever component library is fastest to ship. Every one of those defaults is a small readmission of the category sameness the first two scales were built to escape.
Oddavell’s interface layer holds the line partly through what it removes, not just what it repeats — no drop shadow anywhere across the page, argued through in the case against shadows in luxury digital design, and a palette that skips the category’s most obvious colour choice, covered in why a sea-facing brand left blue out of the palette. Subtraction and repetition turn out to be two sides of the same discipline: keep repeating the thing that’s actually yours, and keep removing the things that came from somewhere else.
The practical test for your own project is simple to state and harder to run: pick your one feature, then audit every touchpoint — logo, pattern, packaging, UI, signage, whatever applies — and ask honestly whether that feature shows up there, or whether that touchpoint quietly reverted to a category default the moment nobody was watching closely.
