I Don't Know

Recently, I wasn’t feeling well so I went to my doctor. He and his staff did the usual stuff: blood pressure, pulse, temperature, stethoscope on the back…a few pokes here. Some minor prodding there. The follow-on conversation went like this:

Me, “So? What is it? The flu?”

Doctor, “How the heck do I know? Could be a lot of things. From what you describe, it could be the flu, but we really don’t have any definitive way of knowing.”

Me, “Okay. Great.”

Doctor, “Give me $150.”

I like my doctor, I do. He’s honest. Doesn’t mince words, and when he’s out of his league, he gives me referrals to good specialists. Turns out, I did have the flu. So, here’s a guy with a lot more education and training than me, charging me about $125/hour and when I asked for his ideas what do I get? “I don’t know.”

Let’s parse that statement for a second. “I don’t know,” does NOT mean, “I haven’t thought about it.” or “I have no idea.” or “Let’s ask someone else.”

Over the years, I’ve become far more comfortable not knowing something. Project estimates. Test results. Requirements. Typically, the exchange goes like this:

Stakeholder/Important-person-in-meeting-who-thinks-everyone-should-have-answers, “How long will it take to jimble-wabby the gilko capacitor”

Me, “I don’t know. Depends if the thilko wookle pairs positively the boiekle cooper flange.”

Important Person, “So . . .?”

Me, “Typically these things work because of the modeling we used. My guess, jimble-wabby will be complete 15 August. But we really don’t have any definitive way of knowing.”

It’s okay not to know. It’s not okay to not think about it. It’s not okay to hope an answer drops in your lap. Most people are reasonable when provided a reasonable response. My doctor didn’t try to fool me. He was honest.

Do your homework. If you don’t know an answer, provide reasons why. And for God’s sake, be quick about it. Don’t go on for hours about alternatives and back-ups and what-if’s or maybes.

Not knowing something is cool. It gives you something to do.