I know what you’re talking about re: early versions of interviews. However, in my zeal I went the other way from being under prepared.
My original idea for my site was (going to be) much more about interviews. I vividly remember my first few, like a car crash, they’re burned into my mind.
I was asking a guy – twin PhD degrees – who wrote a (then) popular book. This was about business so, silly me, I asked what I though were good business questions.
Q: Your book is about some fairly complex ideas for business. If a startup was developing a business plan, what are three or five differences would there be applying your ideas versus a traditional business plan?
A: “You know, that’s a good question. I am working on a startup right now and hadn’t considered applying the ideas from the book it in that way. …”
That’s how the interview started. The last thing I remember was, after numerous questions he had no good answer for, he said “I think I want to stop talking now.”
Keep in mind I wasn’t trying to stump anybody, or grill anybody. At the end I was desperately grasping for any question (beyond name and birth date) they interviewee could answer.
After about three or four truly disastrous phone interviews I stopped doing them. Didn’t matter if the person was a popular book author or well versed in business, they couldn’t answer most of the questions I though were “soft pitches.” Forget anything designed to draw out some information.
Moral of the story: Send the questions in advance. I’ve taken up the interviews since, and had some good success – but only with email. I’m too dangerous face-to-face as I have a tendency to be like the kid pointing to the emperor’s new non-clothes. And I mean it’s actually blackly comedic what obvious, simple things people don’t think about or never consider.
…A web design firm that doesn’t know the difference between the words “tactic” and “strategy” or the words “logo” and “brand” or “message-to-market match.”
…A national chain of IT training centers whose CEO has never had a single meeting (in a dozen years) on what information is, or how you teach people to obtain information and not data from computers.
…Programmers who don’t know what a user benefit is. …Web designers who don’t have a clear idea of the user they’re building a site for.