Supposing I found myself chasing another fly ball and ran head-on into a basketball backboard, supposing I woke up once again lying under an arbor with a baseball glove under my head, what words of wisdom could this man of thirty-odd years bring himself to utter? Maybe something like: This is no place for me.
Our culture reveres youth, aspires to agelessness and is frightened by signs of age, wear and decay. As a consequence of this obsession, and the qualities of our man-made materials, contemporary environments have lost their capacity to contain and communicate traces of time. Our buildings often seem to exist in a timeless space without contact with the past or confidence for the future.
One thing I assume of age is weariness.
Damned if I don’t get more tired every day.
Tired of what I do, following arcs like lobbed rocks — the inevitability of truth.
But the complexity and the gray lie not in the truth, but in what you do with the truth once you have it.
Building structure requires serious listening, serious reflection, and serious imagination. All this requires experience, and no matter how experienced you are, it costs you. We spend our time and nerves to save users their time and nerves. Well-designed things give us the invaluable present of time. Well-designed products do not just save us time, they make us enjoy the time we spend with them. They make us feel that someone has been thinking about us, that a nice person took care of the little things for us. This is mainly why we perceive well-designed things as more beautiful the longer we use them, and the more used they become.
Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business.
Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'.