A piece on UX Collective this week traces how ninety years of loom engineering fed into the idea of teaching machines to catch their own mistakes. It is a design essay rather than news, and nothing about it requires you to change anything today.
But the underlying idea is worth borrowing, because most small business websites fail quietly. A loom that stops itself the moment a thread snaps is useful because the alternative is producing hundreds of metres of ruined cloth before anyone notices. Websites do the ruined cloth version all the time.
Here is what that looks like in practice. Your contact form stops delivering because an email setting changed at your host, and the form still shows the cheerful "thanks, we'll be in touch" message to every visitor. Your booking system quietly rejects card payments from a particular bank. A plugin update breaks the phone number link on mobile. Your site starts loading slowly enough that people leave, but not slowly enough that you notice when you check it yourself on your own fast connection at your own desk.
In every one of those cases the site looks fine to you. There is no alarm. The only signal is the phone not ringing, and by the time you connect the two things, you have lost weeks.
The fix is not complicated and it is not expensive. It is deciding which two or three things on your site actually matter to your business, and arranging for something to shout when they stop working. Uptime monitoring (a service that checks your site is loading and emails you when it isn't) costs very little. A test submission through your own contact form once a fortnight costs nothing but the minute it takes. If you take payments, a small test transaction each month tells you more than any dashboard.
What to do: nothing urgent. Next time you speak to whoever looks after your site, ask two questions. First, if my contact form stopped delivering tomorrow, how would I find out? Second, is anything currently watching the site and alerting someone if it goes down? If the honest answer to both is "we'd notice eventually," that is the thing to fix.
Reported by:
