# What's a good way out when research is stuck?

Consider a mid-level PhD student in a STEM field (maybe 2-3 years into the program), he and his advisor are working on something relatively new and interesting but they have reached a point where the research isn't moving ahead. How do you get out of this situation?

All papers have been read, colleagues have been consulted and top-of-the-head alternatives considered but the problem isn't moving ahead. No theory, computation or intuition helps. The only possibility left is to (optimistically) wait for a Hollywood moment when it all comes together.

Where do you go from here assuming that you cannot completely abandon that topic? At what point should you "start searching for other problems"? How do you choose what to work on next (should you start anew or pick something allied)?

• Why not switch to the other project you're also working on? (You are working on more than one project, aren't you?) Also: Congratulations! You've hit one of the most important milestones on the way to becoming a full-fledged researcher: failure. May 19 '12 at 18:09
• @JeffE Not exactly. I was working on 2 projects but both got stuck along the same lines.
– user107
May 20 '12 at 9:38
• Ouch. If it helps, remember that this happens to everyone. May 20 '12 at 17:01

Here are another three suggestions to add to Ran G.'s answer.

• The first approach is to solve a simpler version of your problem. If your problem involves some dimension that is infinite, what does the problem look like if that dimension is finite (or ignored all together). This approach worked for my PhD research. The system involving the finite dimension was easier to deal with and the technique developed to get my solution generalised to the infinite case.

• The second approach is to work through a less general version of the problem. This could involve solving some examples of the more general problem or make more concrete some of the general dimensions.

• The third approach is to solve a more general version of the problem.

These approaches are not guaranteed to work and the results they produce may not be publishable, but they might give you enough insight to move forward.

• I loved both answers. They were really good but I accepted this because it seemed more relevant to my field. (General Version and Simpler Version). I'll probably take a step back.
– user107
May 22 '12 at 18:19

two possible suggestions:

1. let it go. Take a break, or start a new project. But not for good - come back to it after a month, two months, maybe even half a year. A fresh look on the problem might be useful.

this will (a) give your mind the time needed to consider it with no pressure, and (b) will allow you to have alternatives for the case the project is a dead end.

2. Try to go in the "opposite direction" to what you've done so far. I mean, if you are trying to prove something, and it just doesn't work, assume it is false and now try to prove it wrong. Maybe you'll succeed (which is already a progress), but even if not, this might give another insight to the core of the problem and how to solve it.

Deciding when a project is a "dead end" is a tough decision, and I would say that's the role of your advisor (which depends on your current status: funding, time to graduate, current publications, and of course your advisor's estimation of the probability to solve it eventually).