Ornament & Decoration
249. Ornament
Fine arts and decorative arts
Chapel of St. Ignatius, Seattle, 1995–7
- Bells
Presentable
I have sometimes wondered whether our unconscious motive for doing so much useless work is to show that if we cannot make things work properly we can at least make them presentable.
Sine qua non
What we see of a device is rarely the essential part, the sine qua non, but nearly always the superstructure which economy has imposed on it.
It seems that the work we call purely utilitarian is not more useful than its more ornamental counterpart. It is merely more economical.
Merely ornate
There is nothing merely ornate about nature: every branch, twig, or leaf counts.
Errors & Crimes
"A builder who hides any part of the building frame, abandons the only permissible and, at the same time, the most beautiful embellishment of architecture. The one that hides a loadbearing column makes an error. The one who builds a false column commits a crime."
— Auguste Perret
The problem with ornament
An ArticleContemporary architects are, however, increasingly engaging with ornamentation. The zenith was Grayson Perry and Charles Holland of FAT’s fairytale House for Essex (p64), but it does not serve as an indicator because the involvement of an artist has allowed an enhanced engagement with ornament until it surpasses mere decoration and becomes embodied in the architecture in a way that architects do not allow themselves to do. Think of FAT’s old work: the ornament is all contained within a surface - a facade - which allowed them to separate out the (Modernist) architecture from the (kitsch) superficiality of the elevation. Like Venturi before them, their ornament allowed them to have their ornamentally iced cake - and eat the Minimal Modernist sponge underneath.
The Fidelity Curve
How do we choose which level of fidelity is appropriate for a project?
I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.
I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.
Four levels of fidelity
Suppose we have four levels of fidelity…
- Rough sketch (on paper or an iPad)
- Static mock-up (eg. Photoshop or Sketch)
- Interactive mock-up (eg. Framer, InVision)
- Working code prototype (HTML/CSS, iOS views)
Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained
Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it.
Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.