Sometimes people tell me that 5S only applies in factories, and if they\u2019ve been exposed to the \u201cinactive banana\u201d school of dim-witted implementation I can\u2019t blame them. But here\u2019s a cautionary tale that might persuade you that the principles \u2013 intelligently applied \u2013 are sound.<\/p>\n
Supply Chain View has been \u201coff air\u201d for a while now. I have been fighting a running battle with hackers for months. I would find strange files in my webspace, and other files would contain strange extra bits of code. It was quite hard to spot \u2013 I have some technical knowledge but I\u2019m no web developer, and I don\u2019t have the time to trawl through looking for suspicious stuff all the time. But I mostly managed to delete the dubious files and fix the code. I also changed passwords for various things, but somehow the vandals were able to continue.<\/p>\n
It came to a head when I found that trying to visit my own website led instead to a warning screen advising me that Supply Chain View was a dangerous site. It turned out that I had been blacklisted by Google and StopBadware.org<\/a> because they had detected malicious code on my site. (I was also not sure this was my fault for a while, because this happened about the same time that a Google bug managed to blacklist the whole internet<\/a>.) Sure enough, the hackers had been back, but this time they had tried to redirect visitors to this site to a site that distributed \u201cAdware\u201d (a programme that sits on your PC bombarding you with ads, and which is made hard to uninstall).<\/p>\n I decided it was time for a drastic solution. I couldn\u2019t be sure I had found all the malicious files, or all of the parts of the files that had been modified. So I thought: let\u2019s start from scratch. I removed all the files from my website, and then restored them with a clean version from the middle of last year.<\/p>\n Unfortunately, along the way I managed to mess something up with a critically important file \u2013 as I said, I\u2019m no web developer. (Google\u2019s own aforementioned incompetence makes me feel no better about this.) Now I didn\u2019t have a hacked site \u2013 I didn\u2019t have a site at all! When I found the time I did a few tests and tried a few obvious things, without any luck. Happily, my helpdesk ticket with my web host was answered very promptly, and they managed to solve the problem first time.<\/p>\n Now I\u2019m glad that my website does not form a vital part of my livelihood. My consulting business fulfils that role, and the temporary loss of my website, though annoying and potentially damaging to the brand, doesn\u2019t have direct bearing on that. It has also damaged my Google rankings, which will mean fewer people finding the site.<\/p>\n But it has given me a sharp lesson in the importance of preventive maintenance. Because the first attempts to hack my site had no malignant effect, I didn\u2019t address them seriously. I let them go. I should have realised they were a symptom of a bigger problem, whose pain I had not yet felt. It\u2019s easy to see that the 5S approach to workplace organisation translates perfectly to the management of my website. Like seeing a puddle of oil beneath a piece of factory equipment, I had spotted some \u201cdirt\u201d or \u201cdisorder\u201d and I wiped it away, but with no real attempt at looking at the root causes. And when the machine broke, I paid the price.<\/p>\n Now that reminds me, I must chase the plumber to mend that leaking tap in my kitchen.<\/p>\n","protected":false},"excerpt":{"rendered":" Sometimes people tell me that 5S only applies in factories, and if they\u2019ve been exposed to the \u201cinactive banana\u201d school of dim-witted implementation I can\u2019t blame them. But here\u2019s a cautionary tale that might persuade you that the principles \u2013 intelligently applied \u2013 are sound. Supply Chain View has been \u201coff air\u201d for a while […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[62],"tags":[63,11,65,64,5],"_links":{"self":[{"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/posts\/136"}],"collection":[{"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/comments?post=136"}],"version-history":[{"count":4,"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/posts\/136\/revisions"}],"predecessor-version":[{"id":211,"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/posts\/136\/revisions\/211"}],"wp:attachment":[{"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/media?parent=136"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/categories?post=136"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.supplychainview.com\/blog\/wp-json\/wp\/v2\/tags?post=136"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}