Problem Set Workflow: From Worked Examples to Solving Alone
A step-by-step problem set workflow for math, physics, chemistry, and coding courses: study worked examples, fade the help, solve cold, and log mistakes.
Problem sets are where most STEM courses are actually won or lost. Lectures show you that a method exists. Problem sets show you whether you can use it when nobody is pointing at the right formula. The trouble is that many students “do” a problem set by copying the pattern from a worked example next to it, get the right answer, and then freeze on the exam when the same idea shows up without the example nearby.
This guide is a problem set workflow that closes that gap. It works for calculus, statistics, physics, chemistry, economics, and intro programming exercises. You need the problem set, your notes or textbook, and a blank sheet. No paid apps, no special software.
The core idea is simple: move from full help, to partial help, to no help, and write down every place you needed help. That record becomes your revision list.
Why copying the example feels like learning (and isn’t)
When a worked example sits right beside a problem, your brain gets two jobs done for free: it recognizes which method applies, and it is reminded how the steps go. On an exam, both of those jobs are yours. If you only ever practiced with the example open, you trained step-following, not method selection.
That doesn’t mean worked examples are bad. They are the right starting point for something new. The mistake is staying there. The workflow below uses examples on purpose at the start, then removes them on purpose.
| Practice mode | What it trains | When to use it |
|---|---|---|
| Reading a worked example | Seeing the full method once | First contact with a new topic |
| Solving with the example open | Following steps | Two or three problems at most |
| Solving with a one-line hint | Recalling the steps | Middle of the set |
| Solving cold, mixed order | Choosing the method and executing it | End of the set and exam prep |
The 6-step problem set workflow (overview)
| Step | Time | Outcome |
|---|---|---|
| 1. Triage the set | 10 min | Every problem tagged by topic and difficulty |
| 2. Study one worked example per topic | 10–15 min per topic | You can explain each step in your own words |
| 3. Solve “near” problems with help | 20–40 min | First problems done, help use recorded |
| 4. Fade the help | 30–60 min | Middle problems done with hints only |
| 5. Solve cold and check | 20–40 min | Final problems done without notes |
| 6. Mistake log and re-do list | 10 min | A short list of what to practice again |
You don’t have to do all six in one sitting. Steps 1–3 make a good first block; steps 4–6 make a good second block on another day. If you are planning the whole week, slot the two blocks into your weekly study schedule the day the set is released, not the night before it is due. The backward-planning method helps if the set is large.
Step 1: Triage the set (10 minutes)
Before solving anything, read every problem once and tag it. You are not solving yet. You are building a map.
- Write the problem numbers down the left side of a blank sheet.
- Next to each, write the topic in two or three words (for example “chain rule”, “free-body diagram”, “for loop with accumulator”).
- Mark difficulty with a quick guess: E (looks routine), M (some thinking), H (no idea yet).
- Circle any problem that combines two topics. These are the most exam-like.
- Note which lecture or textbook section each topic came from.
This sheet is your problem set dashboard. It also tells you honestly how big the job is. Ten E problems and two H problems is a very different evening from the reverse.
Step 2: Study one worked example per topic (10–15 minutes per topic)
For each topic on your map, find one worked example in the lecture notes or textbook. Not five. One good one.
- Read the example once straight through without writing.
- Cover the solution and read only the question again.
- Uncover one line at a time. Before each line, say what you expect the next step to be.
- For every step, write a short “why” in the margin: “divide both sides to isolate x”, “sum forces in the vertical direction because acceleration is horizontal”.
- Write the method as 3–5 numbered steps in your own words at the bottom of the page.
That short numbered method is what you will use as a hint later. If you can’t write it, you don’t yet understand the example well enough to fade it, so spend a few more minutes here or bring the question to office hours.
Step 3: Solve “near” problems with help (20–40 minutes)
Start with the E problems that are closest to your worked examples. Here it is fine to keep the example open.
- Solve one problem per topic with the example visible.
- Each time you look at the example, put a small tick next to the step where you looked.
- After finishing, check the answer if one is available.
- Limit this mode to two or three problems per topic. After that, you are just copying.
The ticks matter. They show you exactly which step you can’t yet do from memory. Most students discover it is one or two specific steps, not the whole method.
Step 4: Fade the help (30–60 minutes)
Now close the worked example. Keep only your 3–5 line method summary from Step 2.
- Solve the M problems using only your method summary as a hint.
- If you are stuck for more than about five minutes, allow yourself one look at the full example, then close it again. Add a tick.
- If you are still stuck after one look, mark the problem S (stuck), write one sentence about where you got stuck, and move on.
- Do not re-read the whole chapter in the middle of a problem. That turns a 10-minute problem into a 60-minute detour.
The “stuck sentence” is more valuable than it looks. “I don’t know how to set up the integral bounds when the region is between two curves” is a precise question you can take to a classmate, a tutor, or the textbook index. “I don’t get it” isn’t.
Step 5: Solve cold and check (20–40 minutes)
The last block should feel a little like a mini exam.
- Put all notes, examples, and summaries out of sight.
- Pick the remaining problems, including the circled mixed-topic ones and any H problems.
- Solve them in a mixed order, not grouped by topic. This forces you to decide which method applies.
- Before you start each problem, write the method name at the top. Then solve.
- When you finish, check every answer. For problems without answers, check units, signs, and whether the size of the answer is reasonable. For code, run it on a small test case you can work out by hand.
If you can’t solve a cold problem, that’s useful information, not failure. Mark it and move to the log.
Step 6: Mistake log and re-do list (10 minutes)
Close the session by turning your ticks, S marks, and wrong answers into a short list.
| Problem | Topic | What went wrong | Type | Re-do date |
|---|---|---|---|---|
| 4 | chain rule | Forgot inner derivative | Step slip | Fri |
| 7 | free-body | Chose wrong axis | Method choice | Sat |
| 11 | loops | Off-by-one in range | Careless | Fri |
Use three simple mistake types:
- Method choice: you didn’t know which approach to use.
- Step slip: you knew the approach but couldn’t execute a specific step.
- Careless: arithmetic, sign, unit, or typo errors.
Then:
- Pick the 3–5 most important problems from the log to re-do cold in two or three days.
- Put the re-do session on your calendar now.
- Add method-choice mistakes to your exam revision list. They are the ones most likely to cost marks.
This is the same idea as an error log after a graded exam, just applied earlier, when fixing a mistake is cheap. If you already use a spaced repetition routine, add each re-do problem as a card: the question on the front, the method summary on the back.
Working with classmates without copying
Study groups are great for problem sets, as long as everyone still does the cold step themselves. A simple rule set:
- Each person attempts the set through Step 4 alone first.
- Meet to compare stuck sentences, not finished answers.
- Explain solutions out loud to each other. If you can’t explain a step, you’ve found a gap.
- After the meeting, each person writes up their own solutions from scratch.
Always follow your course’s academic integrity rules. Some courses allow discussion but require individual write-ups; others don’t allow collaboration on graded sets at all. When in doubt, read the syllabus or ask the instructor. The group project workflow guide covers shared work when collaboration is explicitly allowed.
Common problems and quick fixes
“I can do it with the example but not without it.” That’s normal at Step 3. Spend more time at Step 4 with only your short method summary. The summary is the bridge.
“I get stuck on the first line every time.” Your issue is probably method choice, not execution. Practice just the first line: for ten problems, write only the method name and the first step, then stop. That builds recognition fast.
“The set takes me five hours.” Check your triage sheet. If most of the time is going to H problems, you may need to go back to the lecture first. If the time is going to re-reading, set a firm five-minute stuck limit and write the stuck sentence instead.
“I finished but I’m not sure anything stuck.” Do the re-do list in two or three days. If you can solve those cold, it stuck. If you can’t, you’ve learned where to focus, and that is still progress.
A printable one-page version
Copy this onto the top of your problem set sheet:
- Triage: topic + E/M/H next to every problem; circle mixed ones.
- One example per topic: cover, predict each line, write a 3–5 step method.
- Near problems with help: max 2–3 per topic; tick each look.
- Fade: method summary only; five-minute stuck limit; write stuck sentences.
- Cold, mixed order: no notes; name the method first; check everything.
- Log: problem, topic, what went wrong, type, re-do date.
Summary
A problem set is practice for the moment when nobody tells you which method to use. Start with a worked example, then steadily take the help away, and finish by solving cold in mixed order. Keep a short mistake log, re-do the important problems a few days later, and you will walk into the exam having practiced the real skill, not just the copying.