I used to believe that my approach to designing websites was more akin to an architect than a gardener (see Architects and gardeners).
With this mindset, designing and delivering a website is a little bit different to designing as a gardener.
Much like a garden needs tending and pruning (see Websites as gardens), a house also needs cleaning and maintenance.
The difference is perhaps in the creation process. The role of the architect implies a clear, grand vision from the outset. The strategies and processes are laid out and communicated in relative completeness early on.
This makes for a somewhat more predictable, but less agile process, and it’s harder to track back and change something because it means losing face.
The ego might get in the way of the final product.
But for certain buildings, it is absolutely necessary for an architect to be involved. It is necessary because there are many more parties involved.