Worked Examples vs. PYQs: Two Different Jobs, One Complete Prep
Worked examples teach you the clean method. PYQs show you how the exam disguises it. Here’s why you need both, and the order to use them.
A textbook’s worked example and a previous-year question (PYQ) might look like the same thing — a problem with a solution — but they are two different tools doing two different jobs. Confusing them is one of the most common reasons a student can follow every solved example in the chapter and still freeze on exam day. Here’s the distinction, and the sequence that actually works.
What a worked example is actually teaching you
A worked example is a demonstration. Its job is to show you the clean, intended path from a concept to an answer, with every step visible and justified. When you read one, you are not being tested — you are being shown the architecture of a method: why this formula applies here, how the units cancel, where the sign convention flips.
The value of a worked example is that it isolates the concept from noise. There are no traps, no misleading diagrams, no extra variables thrown in to confuse you. It is the concept in its purest form. Your job while reading it is not to memorize the numbers, but to internalize the logic — the sequence of decisions that turns a blank page into a correct solution.
A worked example answers the question: “How is this concept supposed to work?”
A PYQ answers the question: “How does the exam actually test this concept?”
These are different questions. Prepare for both.
What a PYQ is actually testing
A PYQ is a disguise. The examiners know the syllabus, and they know the standard methods — so their job is to take a concept you know and present it in a way you don’t immediately recognize. They combine two concepts you’ve studied separately. They hide a known formula inside an unfamiliar context. They add an extra step that forces you to choose which of two valid approaches is faster under time pressure.
When you solve a PYQ, you are not just practicing the concept — you are practicing recognition. You are training your brain to see past the surface wording and identify the underlying principle. That skill is not taught in any worked example. It only develops by meeting the exam’s specific habits: the way it frames questions, the way it sets up distractors, the way it sequences parts of a multi-step problem.
The gap if you rely on only one
If you only do worked examples, you know the method but not the exam. You can solve a problem when it’s clearly labeled, but you’ll struggle when the same concept appears wrapped in an unfamiliar story or combined with a second topic. You’ll also be slow — worked examples don’t train you to make the quick judgment calls that timed exams demand.
If you only do PYQs, you’ll hit the opposite wall. You’ll learn the exam’s patterns without understanding the underlying logic, so when the paper throws a genuinely new twist — and it will — you’ll have no foundation to fall back on. You’ll memorize solutions to specific questions instead of building the transferable method that lets you handle anything.
Solving a PYQ before you understand the concept is not “practice” — it’s pattern-matching. You’ll feel productive, but you’re memorizing answers, not building understanding. That gap shows up exactly once: on exam day.
The sequence that closes both gaps
Step 1: Read the worked examples first. Go through each one slowly, covering the solution and trying to predict the next step. If you can’t predict it, that’s the exact point where your understanding is thin — go back to the theory and re-read. The goal is to be able to reproduce the method from scratch, not just nod along.
Step 2: Do the chapter’s unsolved exercises. These are the bridge — they’re still in the textbook’s clean style, but now you’re producing the solution yourself. This is where you confirm you actually own the method, not just recognize it.
Step 3: Only then, open the PYQs. Now you’re ready for the exam’s disguises. Time yourself on a small set — five to eight questions from that chapter across different years. After each one, ask two questions: Which concept was this really testing? and What disguise did the examiner use? Write those answers down. That list of disguises is your real revision material.
Step 4: Revisit the PYQs a week later, untimed. This second pass is where recognition becomes automatic. You’re not checking whether you can solve them — you’re checking whether you can identify the concept within seconds of reading the question. That speed of recognition is what separates prepared students from surprised ones.
The takeaway
Worked examples build your toolkit; PYQs teach you when to reach for each tool. Do the examples first to learn the method, then use PYQs to learn the exam’s disguises — and keep a running list of those disguises as your final revision sheet. One without the other leaves a hole; together, they cover the full distance from understanding to performing.