2. What’s Your Problem?


Now that you have questions, the next step is to answer them, right?

Not exactly.

In this chapter, you will begin to find and use primary sources, and you may find the answers to at least some of your questions. But answering questions will not be the primary focus. Educating your questions will be the focus.

The questions you have generated thus far are, by and large, less developed than they could be and will become. This has nothing to do with your abilities as a researcher. Rather, it is a fundamental part of this stage of research: your questions are underdeveloped at this point because you have not yet had the chance to conduct research into your subject matter. It’s to be expected.

Wait a minute! You might protest at this moment. Before, you told me that I need to generate questions in order to do research. But now you’re telling me that I need to do research in order to generate questions? That’s impossible. It’s an infinite loop. It’s a trap!

It’s not a trap. But it is true that it takes a lot of research to arrive at the right questions. And then it takes more research to answer these questions and generate new ones. In this early stage of research, the goal is not, as many assume, the generation of answers. It is about the refinement of your existing questions and the generation of new (and better) ones.

The goal of this chapter is to help you identify and articulate the problem underlying your many research questions. Accomplish this, and you will end up asking better questions, doing more significant research, and carrying it out more effectively.

Don’t Jump to a Question (or You’ll Miss Your Problem)

Over the course of generating, analyzing, refining, and adding to your questions, you may have wondered: How do I know when I’ve found my Problem? Do I really have a “Problem,” or have I merely compiled a random set of questions that don’t really add up to anything? After all, we’re curious about many things, but we don’t launch research projects to satisfy every curiosity. Nor should we.

Here’s a simple way to distinguish a problem from a random set of curiosities: if it changes by the day, week, or month, chances are it’s a passing curiosity. If it endures, it just might be a problem.

A problem is a nagging presence within you—one that disturbs, bothers, and unsettles you, but also attracts, compels, and keeps you coming back. It’s something that generates questions in your mind—questions that, no matter how varied and unrelated they might seem to an outsider, you know to be somehow interrelated, even if you can’t explain why. A problem is something that follows you around. It doesn’t care if you are a historian of France, a sociologist of the Philippines, or a literary scholar of India—it calls out for you to try to solve it. Your job is to give that problem a name, to identify a case of that problem that you will be able to study (given your personal abilities and constraints), and to figure out how to study that case so that you might arrive at a broader solution.

Researching a problem requires asking questions, of course, but (again, to state the obvious) a question is not a problem.

You can think of plenty of questions that have answers, but whose answers do not solve any problem. Asking and answering such idle questions is a waste of time, so you want to make sure that your questions are indeed problem-driven. This is why it is so important not to jump to a question.

A problem has several functions for the researcher, among them the following:

Up to now, you have been generating “first-draft” questions based on an initial foray into sources. But you want to make sure that you are asking questions that do more than just satisfy a personal curiosity. The next steps in this chapter will help you figure out

We all know not to “jump to a conclusion”—an action prompted by prejudicial or hasty thought. We’ve all seen it happen, and we’ve all done it ourselves—we arrive at an argument or thesis about a sure thing even though we haven’t spent sufficient time thinking it over. And we end up being wrong.

What the early-stage researcher has to avoid is jumping to a question. You have generated many questions, and the risk now is that you’ll feel pressured to jump ahead and choose one prematurely.

What is your Research Question? You’ll hear this demand from other people, and eventually from a little voice in your head that tries to trick you into thinking that your project must have only one Research Question, and that you must settle on it early.

The Jump-to-a-Question Trap can be as harmful as the Narrow-Down-Your-Topic Trap.

Jumping to a question is like constructing a home without examining the ground on which it will stand. Your architectural plan might be stunning, the plot of land spacious, and the vista marvelous, but if you build on sand you are going to have serious issues when those sands shift. By the time issues show up, renovations may be costly, and you might find it impossible to relocate.

Stress-Testing Your Questions

Now that you have done the work of producing a multitude of questions—small, factual questions, ideally—you will still need to stress-test, refine, and winnow them out, removing any dead ends, enhancing the rest, and adding additional questions that will better serve your research process.

Think of a question as if it were a car. Before jumping into this vehicle, and certainly before bringing others along, you would want assurance that its steering and brakes have been subjected to rigorous testing. You’d want to know that prototypes underwent crash tests, over and over, until the manufacturer felt certain that the structure of the vehicle was ideally suited to protect the driver and the passengers.

Here are two ways to stress-test your questions and improve their soundness. The first focuses on language; the second is subject-specific and focuses on sources. We recommend that you tackle them in that order.

You Have a Problem (in a Good Way)

You have now taken a close look at your many factual questions and grouped them under parent categories by shared concern. You have formulated higher-level questions motivated by these concerns. The key concern that overshadows all others might have emerged in a flash or intuition. Or perhaps you’re still trying to decide which of them is the most important to you. If you feel like you don’t yet have enough self-evidence, you can of course repeat the exercises in this chapter. But even if you think you do, you might still wonder: How do I know when I’ve truly discovered my Problem?

A problem is never a fleeting thing. Rather, it is something that is sustained and enduring. To you, it can’t be easily dismissed or ignored. Frida Kahlo painted surrealistic self-portraits because she was driven by a problem. In the world of music, John Coltrane worked on A Love Supreme, and Billie Holiday sang “Strange Fruit” because they were driven by problems. Bob Dylan entered a “blue period” because of a problem. Researchers are just the same.

Problems are good things. They are good to have, good to worry about, good to mull over. The problems we carry around with us can be thought of as the productive frictions that happen as we move through, and rub up against, existence itself.

Ultimately, however, the final decision can only come from you. Only you can know whether or not the cluster of fascinating questions you’ve generated thus far add up to a problem, or just a highly sophisticated and interesting set of curiosities.

You may well have multiple problems, but for now let’s just tackle one problem at a time. We’ll discuss what to do with the others in the final chapter.