Describe vs apply: why knowing every APM model scores almost nothing
APM is an application paper — there are few, if any, marks for knowledge alone. See a describe-only paragraph score nothing next to an applied one, and the exact three moves that earn the marks.
You can name every performance-management model on the syllabus and still fail APM. The examiner has said it plainly, sitting after sitting: this is an application paper, and there are few — if any — marks for knowledge on its own.
APM tests whether you can use a model in a specific situation, not whether you can describe it.
Here's that difference, on the page.
Describe-only: the paragraph that scores almost nothing
Asked how the building-block model could help a struggling service business, a describe-only answer reads like this:
The building-block model has three levels: dimensions, standards, and rewards. Dimensions are the areas of performance measured, such as quality and flexibility. Standards should be owned, achievable, and fair. Rewards should be clear, motivating, and controllable.
Every sentence is true. It's also textbook recall set next to a scenario it never touches. A marker looking for application has almost nothing to reward.
Applied: the same model, earning the marks
For this business the dimensions that matter are responsiveness and quality — customers are leaving over slow turnaround, so measuring cost alone misses the problem. But the standards are the real weak point: staff had no say in the current targets, so they're neither owned nor seen as fair, which is why teams are gaming them. I'd fix the standards and the reward link before adding any new measures — new dimensions won't help while the targets themselves lack buy-in.
Same model. What changed is that every element is bent onto the scenario, and the paragraph carries a judgement.
Name the three moves
The applied paragraph does three things the first one didn't:
- Scenario link. Each part of the model is tied to a specific fact in the case — not "standards should be fair" but "these standards aren't owned, and here's the symptom."
- Limitation. It says where the model, or the current setup, falls short — rather than presenting it as a tidy fix.
- Judgement. It prioritises — fix standards before adding dimensions — instead of listing everything the model contains.
Do those three on any model — target costing, the building-block model, the performance pyramid — and you're writing the paper APM actually sets, not the one your notes prepared you for.
Where Ezra catches this
Describe-only writing feels productive because the words come easily — you know this material. That's exactly why it's dangerous under time pressure. Ezra flags a paragraph that's recalling instead of applying, and pushes you to link it to the scenario, name a limitation, and take a position — the same coaching behind Gradd's APM tutor.
Ezra teaches this — and checks you’d score.
Ezra spots where the marks slipped, coaches the fix, and marks you against the descriptors.
Every APM drill free. No card.
Try Ezra free →