I wrote a couple of articles for www.ondisruption.com recently that I think could be useful to folks in IT. (Important disclosure: this site is run by my brother Mike, a disruption consultant. But luckily, he doesn't pay me, so I don't think there's any conflict here. But let me know if you think I shouldn't post links to things I've written elsewhere.) The two articles are: -Are you a sitting duck? -Should you I wrote a couple of articles for www.ondisruption.com recently that I think could be useful to folks in IT. (Important disclosure: this site is run by my brother Mike, a disruption consultant. But luckily, he doesn’t pay me, so I don’t think there’s any conflict here. But let me know if you think I shouldn’t post links to things I’ve written elsewhere.) The two articles are: -Are you a sitting duck? -Should you pack your parachute? I won’t repeat the content here, but I think they are relevant points for Infoworld readers and folks in IT in general. The key points are to identify if your company is being disrupted and then make sure you are doing something about it, if not for your company, for the sake of your career. I think some of the points are applicable no matter what industry you’re in, but I think it’s particularly important for old-line companies that may be disrupted by new technologies, whether it’s emerging Web 2.0 sites, Software as a Service, smart phones or open source. While not all new technology that sounds disruptive has long term impact, it’s important to watch for the warning signs. Open Source