tag:blogger.com,1999:blog-4384692836709903146.post6981441480015293220..comments2024-03-27T09:55:23.143-07:00Comments on Dispatch from the Digital Health Frontier: Troubleshooting Complex IT problemsJohn Halamkahttp://www.blogger.com/profile/04550236129132159307noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4384692836709903146.post-31974962720730228962008-12-23T15:40:00.000-08:002008-12-23T15:40:00.000-08:00A very good point. In this case we tried to repl...A very good point. In this case we tried to replicate the problem, but could not because we tried it with standard pagers, not those which were signed out. Our customers could replicate the problem, which convinced us to pursue it.John Halamkahttps://www.blogger.com/profile/04550236129132159307noreply@blogger.comtag:blogger.com,1999:blog-4384692836709903146.post-86406212788662075652008-12-23T07:53:00.000-08:002008-12-23T07:53:00.000-08:00My only modification to your recommendation is to ...My only modification to your recommendation is to do everything you possibly can to <B>replicate</B> the problem <B>before</B> worrying about possible causes.<BR/><BR/>Putting in the effort to replicate problems up-front is ultimately cheaper and faster. Testing, researching, and re-testing results in a better understanding of the problem, and can usually be done by just one person. You'll be able to eliminate any number of red herrings without having to involve unaffected teams or systems.apwhttps://www.blogger.com/profile/11849053659603568634noreply@blogger.com