The nineteenth century saw an increasing separation between the treatment of the surface and the structure of designed objects. Mass production and a mobile market economy encouraged the production of heavily ornamented yet cheaply fabricated products. Affordable manufacture allowed the burgeoning middle class to acquire “luxury” goods fashioned after objects formerly reserved for an elite.
Put together with odd bits of the useless Clarice, a survivors’ Clarice was taking shape, all huts and hovels, festering sewers, rabbit cages. And yet, almost nothing was lost of Clarice’s former splendor; it was all there, merely arranged in a different order, no less appropriate to the inhabitants’ needs than it had been before.
The idea of overlap, ambiguity, multiplicity of aspect, and the semilattice are not less orderly than the right tree, but more so. They represent a thicker, tougher, more subtle and more complex view of structure.
Most objects which we are accustomed to call beautiful, such as a painting or a tree, are single-purpose things, in which, through long development or the impress of one will, there is an intimate, visible linkage from fine detail to total structure.
The resistant virtues of the structure that we make depend on their form; it is through their form that they are stable and not because of an awkward accumulation of materials. There is nothing more noble and elegant from an intellectual viewpoint than this; resistance through form.
In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us.
However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap.