Getting Unstuck: What to Do When You Don't Know How to Start

I have spent a full ten minutes reading the same problem three times. Not solving, not thinking — reading, the way you reread a door sign while waiting for someone. Nothing moved. The page stayed blank, the clock did not, and by minute ten I had a new problem on top of the old one: the certainty that I was the kind of person who could not start.

That certainty is the only part that was false. Being stuck is not a verdict on ability. It is a state, and states have exits. What follows is the exit I use: a fifteen-minute protocol with the clock running, six steps, each with a time box. It does not require inspiration. It requires a pencil and the willingness to write something small and possibly wrong. The timer matters as much as the steps — without it, step one quietly becomes another ten minutes of reading.

The fifteen-minute protocol

The idea is older than any of us. In 1945 a mathematician named George Pólya published a small book called How to Solve It, which argued that problem-solving is a list of questions asked in order, not a flash of insight. The protocol below is that idea with a timer attached. Set fifteen minutes and do not skip steps.

1. 0:00 – Copy it out. Write the problem by hand, every word. Half of stuck is misread: a "more than" skimmed as "less than", a unit ignored, a condition on the second line never seen. Copying forces the eyes to visit each word once.
2. 0:02 – Describe the finish line. Write one sentence saying what an answer would look like: "I need a width, in inches, such that the perimeter comes out 36." A problem you cannot describe the end of is a problem you have not read yet — go back to step one.
3. 0:05 – Try the smallest case. Replace the big numbers with tiny ones, or fewer items. If the problem asks about 36, try 10 in your head. Small cases are cheap and they show the shape of the work without the arithmetic getting in the way.
4. 0:08 – Draw it or tabulate it. A quick sketch, a two-column table, a number line with three marks on it. The format does not matter. What matters is moving the problem out of sentences and into something you can point at. Our word problems guide covers why translation into pictures is usually the step where things unlock.
5. 0:11 – One backwards step or one honest guess. Start from the answer and undo one operation, or guess a simple number and test it properly. Our problem-solving playbook works through both moves in full; here they are just step five of six, which is the point — a technique used on schedule beats a technique waited for.
6. 0:14 – Write down exactly where you stopped. One sentence a teacher could answer: "I got width 5 gives perimeter 32, and I do not see how to close the last 4." That sentence is the product of the fifteen minutes even if the answer is not. Our showing work guide explains why written steps are askable steps.

Watch it work once

Problem: a rectangle's length is 3 more than twice its width, and the perimeter is 36. How wide is it? The staring version of this takes ten minutes and produces nothing. The protocol version goes like this. Copy it (step one). Finish line: a width in some unit such that twice width-plus-length equals 36 (step two). Smallest case: guess width 5 (step three). Then length is 2 times 5 plus 3, which is 13. Perimeter check: 2 times 5 plus 13 is 36 (steps four and five collapse into one line of arithmetic). Answer: 5.

It worked on the first guess, so here is the version where it does not. Guess width 6 instead: length becomes 2 times 6 plus 3, which is 15, and the perimeter comes out 2 times 6 plus 15, which is 42. Too big by 6. Now the guess has earned its keep, because it tells you the direction: 42 is above 36, so the width must come down. Try 5, get 36, done. Two guesses, one correction, under five minutes. That loop — guess, test, read the direction, adjust — is the entire content of guess-and-check done honestly, and it only works because step two already told you what the finish line looks like. A guess without a finish line is a shrug. A guess with one is a measurement.

It worked on the first guess, which will not always happen, but notice what the protocol bought even so: a guess that could be tested, in under five minutes, from a standing start. And the test is the whole game — plug the answer back into the original words and see if they hold. Our checking work guide is about exactly that habit: the problem is not finished when you have an answer, it is finished when the answer survives contact with the question.

When to stop pushing

The protocol has a stop rule, and the stop rule is part of it. Fifteen minutes with nothing new written down means stop: write the stuck-point sentence from step six, close the book, and ask someone tomorrow or sleep on it. Stopping is not surrender. It is the recognition that an empty page after fifteen honest minutes is data — it says exactly which sentence to ask about, instead of "all of it."

Most stuck I have seen, in classrooms and at kitchen tables, ends the same way: not with a breakthrough but with a first small mark on paper, ten minutes late. The protocol just moves that mark to minute one. Start there and the rest is arithmetic. And if the fifteen minutes end with nothing but the stuck-point sentence, that sentence is still further than rereading ever got you — it is a question with an address on it, ready for a teacher, a parent, or tomorrow morning.