Skip to content
0 / 66 sessions

Course contents

Module 2 of 13 · 66 sessions

PRINCE2® Foundation

Free
Course overview

Course progress

0%

0 of 66 sessions complete

Sign in to save your progress across devices.

Module 2Session 7 of 6612 minKnowledge check

Learn from experience

How a project looks for lessons before it starts, while it runs and when it closes, and why writing them down isn't enough.

Sign in to track progress
Guided lesson
~0:28Scene 1 of 7

Scene 1

Learn from experience

How a project looks for lessons before it starts, while it runs and when it closes, and why writing them down isn't enough.

Caption 1 of 3

Explain when and where a project should look for lessons

0:00 / 0:28
Read all scene text
  1. Explain when and where a project should look for lessons
  2. Describe who is responsible for learning from experience
  3. Distinguish recording a lesson from acting on it

Scenes animate with GSAP. Use pause or replay at any time.

In this session

  • Explain when and where a project should look for lessons
  • Describe who is responsible for learning from experience
  • Distinguish recording a lesson from acting on it

It's time to look at how projects get better at being projects.

Let's say you're about to sign the builder's contract for York. Your friend, who opened a café in Harrogate last year, rings you. "Whatever you do," they say, "check the permit for the kitchen extraction fan before the builders start. It cost us six weeks."

When should a project look for lessons?

Select the arrow to learn more

1 of 4

Before you start

Ask people who've done it before. Your friend's call is one source. Sam also digs out your notes from the Leeds fit-out five years ago.

Lessons are sought, not stumbled upon

The important word is seek. Projects are unique, so it's tempting to assume nobody has faced your problems before. Usually someone has. This principle expects everyone on the project to go looking for that experience, rather than waiting for it to turn up.

Learning is everyone's responsibility, from you as the person paying for the project to the shopfitter's apprentice. Sam keeps the lessons in a lessons log, so nothing useful gets lost.

Where lessons come from

Lessons can come from inside or outside the organisation:

  • Your own past projects: the Leeds opening, last year's kitchen refit
  • Other organisations: your friend's café in Harrogate
  • Suppliers and partners: your builder has fitted out dozens of food shops
  • The people on the project: what Priya learned in a previous job
  • Industry guidance: trade bodies, regulators and published case studies

Recording isn't learning

Writing a lesson in a log doesn't mean it's been learned. A lesson counts when it changes what people do. The extraction-fan warning only helps if checking the permit is added to the plan before work begins.

Lessons are also passed on. At the end of a stage or the end of the project, Sam can produce a lessons report so the wider business can use them, not just this project team.

Learning in short cycles

Iterative projects learn especially fast. When Fern & Flour builds its pre-order app, the team will hold a short review after every cycle: what went well, what didn't and what to change next time. The principle is the same; the rhythm is just quicker.

Key points to remember

  • Lessons are actively sought at the start, during and at the end of a project.
  • Learning from experience is everyone's responsibility.
  • A lesson is only learned when it changes what people do.
  • The lessons log records lessons. A lessons report passes them on.
Knowledge checkQuestion 1 of 4

Knowledge check

Choose one answer

Principles

When should lessons be sought on a PRINCE2 project?

When should lessons be sought on a PRINCE2 project?
Choose one answer to continue.

Sign in to save your result. Knowledge checks can be retried any time.

PRINCE2® is a registered trademark of the PeopleCert group. MockAcademy is independent and not affiliated with, endorsed by or licensed by PeopleCert.