CIO — In 1999, a three-year old girl in London named Isabel received a diagnosis of chicken pox. Overnight she took a turn for the worse and at the hospital was diagnosed with a deadly flesh-eating disease. Fortunately she recovered, but her stockbroker father, Jason Maude, wanted to develop a way to prevent such misdiagnoses. Together with Dr. Joseph Brito, who had treated his daughter in intensive care, he developed a diagnostic decision-based software tool that would help physicians make more accurate diagnoses. He called it Isabel.

Isabel is not the only tool of its kind, but it does have an interesting feature that Ian Ayres describes in his book, Super Crunchers. As Ayres writes, "The biggest reason for misdiagnosis is 'premature closure.' Doctors think they have a bead on the correct diagnosis...and close their minds to other possibilities."

That's exactly what Isabel is designed to prevent. Ayres describes Isabel as a "reminder system" that prompts a simple question, "Have you considered...", followed by a list of possible diseases to consider for diagnosis. This feature helps doctors think beyond what's known and consider the unknown.

Good leaders also need to think about the unknown in order to plan for the future of their organization. For that reason, you may wish to employ you own "have you considered" questions when making an important decision. Start the process by asking yourself the following:

What have we missed? One of the greatest dangers facing any team is groupthink, or everyone adopting the same point of view. Sometimes this occurs malevolently; the boss makes it uncomfortable for people to disagree. But it also happens without malice; people all agree on something because it makes sense. Inviting others (ideally those without bias or exposure to the issue) to examine the decision is good practice. Consumer-products companies regularly show prototypes to customers to gauge their reactions; often their input is completely different from that of anyone on the team.

What if we did the opposite? Turn the problem upside down. Consider doing the exact opposite of what you have done. That is, if you are about to implement a process, consider not doing it or doing something completely different. Again, getting an outsider's point of view is worthwhile. You don't have to stretch the problem to absurd lengths, but you can invite people to comment on the assumptions you made. Ask them to challenge your data, research, pricing, market or whatever. Yes, it can be tedious and even annoying, but it may reveal something you overlooked.

Continue Reading