I was thinking about my article pull your laces tight! A similar analogy could be constructed with a zip.
By abstracting the content of the analogy (relationships) from the form of the analogy (a shoe), I can see that both shoe and zip could be metaphors for any activity that requires regular monitoring to ensure quality or a successful outcome, and where inaction results in a deterioration. Ideally though, the analogy should perhaps be restricted to systems where there are two main players that in some way need pulling together.
Initially, I decided that this metaphor would be suitable for software development for companies that trade using that software – this is called enterprise software. In the enterprise software world, where real life is constantly changing, and real business must me react accordingly, the software that models and operates the business process must always change to suit. It is never considered finished. Such software is either constantly improving by concerted effort, or degrading by ignorance, or degrading by growth of data – the journey, in the original article – namely, even if the software is not made worse, an increase of data means more data problems to fix when the inevitable manifests.
However, having added the qualifier that there are two main players that in some way need pulling together, I now think my zip / shoe metaphor is not great for software.
If you can think of any suitable metaphors for my enterprise software scenario, please send let me know. Similarly, if you can think of further usage of the shoe / zip metaphor, I would love to hear them.