PREP — Point – Reason – Example – Point
Delivering a clear, convincing position in under 2 minutes: state your conclusion (Point), explain why (Reason), illustrate with a quantified example (Example), then restate your position (Point).
A clear, convincing position in under 2 minutes
Why it exists. PREP is the base structure of any persuasive answer. It forces you to have a clear opinion before speaking — something many candidates avoid out of fear of being wrong.
What it does. Answers any opinion question in a structured, punchy way. Shows confidence and clarity of thought.
State, justify, prove, restate
Entry-level version
Here's what I think (Point), here's why (Reason), here's an example that proves it (Example), and I'll restate it (Point).
Senior consultant version
PREP is the base structure you combine with others: PREP for the opening + the Pyramid Principle for the detail + CAR for the examples.
The four steps of the method
- PPoint — state your conclusion, the position you're defending.
- RReason — explain why, the logic behind your position.
- EExample — illustrate with concrete proof, quantified if possible.
- PPoint — restate your position to make it stick.
From a personal conviction to strategic synthesis
Question: "Do you think companies should adopt AI in their development work?"
Point: Yes — companies that haven't integrated AI into their development tooling by 2026 will be structurally less competitive.
Reason: AI isn't just a productivity tool — it's a velocity lever that changes the relationship between code complexity and delivery time. Teams that adopt it ship 30-40% faster with no increase in bugs.
Example: on my last engagement, we integrated GitHub Copilot into the workflow of 8 developers. After 6 weeks of adoption, code-review time dropped 25% and developers reported less cognitive fatigue on repetitive tasks.
Point: integrating AI into development isn't optional — it's a question of competitiveness over the next 3 years.
Question: "In your view, what's the main risk in an Agile transformation?"
Point: the main risk isn't technical — it's superficial adoption: going through the rituals without changing the way people think.
Reason: most transformations fail because managers learn the Scrum ceremonies but keep managing in "command and control" mode. Agile then becomes "agile-washing": an added cost with none of the benefit.
Example: across 12 Agile transformations I've supported over 8 years, the 4 that failed all shared the same pattern: an untransformed middle management that restored the old practices the moment the Agile coach left.
Point: a successful Agile transformation starts by transforming management, not the teams.
Freelance variant
PREP is the structure for your elevator pitch: what I do (Point), why it works (Reason), what I've produced (Example), what I can do for you (Point). In 60 seconds.
Common mistakes
- ✕A Point that's too vague: "I think Agile is useful" — no clear position.
- ✕Skipping the second Point — restating it is what makes it stick.
- ✕An Example with no figures — a qualitative example is less persuasive.
- ✕Confusing the Reason with the Example — the Reason is logical, the Example is factual.
Quick checklist
- ✓My Point is a clear, specific position.
- ✓My Reason is a piece of logic, not an opinion.
- ✓My Example is quantified or very concrete.
- ✓The second Point is rephrased (not copy-pasted).
- ✓The answer fits in 90 seconds to 2 minutes.
PREP in one sentence
PREP = a structured position. Point (conclusion) + Reason (why) + Example (proof) + Point (restated). It's the structure for answering any opinion question with confidence and clarity.
Want one-to-one support to prepare for your interviews?
An outside perspective to build your positions and rehearse under real conditions.