Another Otakon has gone and passed. As usual, the J-guests got the shaft, stuffed into subprime timeslots and subjected the usual lack of panel structure and random questions from an underinformed audience. I was talking to Greg about the sorry state of these panels and comparing them to some of the guest panels at Anime Expo that I had been to a number of years ago where they picked a topic that a number of guests had in common (being manga creators in this case), and then putting them onto a panel and having them discuss with live translation and audience input. What made this such an interesting experience was learning about stuff that I didn't know about and wouldn't even thought to ask. The problem is that really in the big picture, neither I nor almost any other fan is really in a position to know how to ask a really interesting question. We have so little context that we don't know what we don't know. It's like when I'm giving training and after delivering the agenda, ask if there are any questions. Well, usually there are none since the students know too little about the topic to be able to formulate questions.
Fast forward a day and I'm at a hotel in NJ im'ing Ben and Catherine about CAFE and discussing the use of questions as openers when greeting people and creating conversation. But coming up with good ones is surprisingly difficult since something very generic like "Hello, may I tell you about the anime club?" or "Are you interested?" feels flat and insipid. There's a catch-22 here where you need to know a decent amount about the subject before you can come up with a good question. (In this case the problem is tractible since we do know something about the target based on their behavior at the event.)
And then as precursors to answers, questions have a lot of power. The target of a question often feels a significant compulsion to answer a question, and thus internalizes the topic and perhaps even temporarily structures all thinking in the way indicated by the question. Imagine asking a series of questions like "When's the last time you had a really good dish of pasta? What were it's properties? How do you think they made it?" Then, follow up with "Oh, I just heard of this great Italian place that just opened. Wanna try it?" There is almost limitless potential here.
In school, training, and work, we spend most of our time learning to come up with answers and then applying that skill. However as a precursor, the question frames and structures the entire exercise. How the question is posed can determine if the problem is tractable and useful. Hard problems are often so invisible that we don't know to pose a question that hilights them and thus blissfully march onwards to doom. We are trained how to structure answers, but are left to our own devices when trying to define questions. Take for instance: "How do we save CJAS when membership has been in decline for years?" Is this the right question? What about: "Is CJAS worth saving?" Well, that's a higher-level question in some ways, but again, is it the right one? How do I know if I have the right question? How do I know how to find the right question?
To some extent, simply realizing how important it is to come up with the right question is enough to set one on the right track. It's really difficult to "know what you don't know," but acknowledging that there is this kind of boundless unknown out there that needs to be investigated somehow is enough to get started. The problem is, it's too easy to get set on the track of looking for answers prematurely without having defined the question, especially for engineers like me. I always need to consciously remind myself to stop, consider what the question is, and ponder whether that is the correct question. Unfortunately, hand in hand with "always need" is "often forget." Ah, well...