# Project delivery field notes

Short practical essays on the reasoning behind status, risk and change decisions, with links to worked examples you can use.

Canonical: https://project.responseshift.academy/blog/
Publisher: Response Shift
Updated: 2026-11-13

## How do you run a lessons learned meeting that works?

Run a lessons learned meeting that changes the next project: a timeline before opinions, causes before blame, and each lesson turned into an owned change.

- [Read the field note](https://project.responseshift.academy/blog/lessons-learned-meeting/)

## How does three-point estimation work in a project?

Three-point estimation with a worked schedule: the PERT formula, what the spread tells you, how to add tasks up honestly and where the method misleads.

- [Read the field note](https://project.responseshift.academy/blog/three-point-estimation/)

## How should a project change request process work?

A change request process that keeps momentum: explore before committing, size the impact, route by authority and record the decision, with a worked example.

- [Read the field note](https://project.responseshift.academy/blog/change-request-before-commitment/)

## What should red, amber and green mean on a status report?

Define RAG status by the decision a sponsor needs, not task counts: written criteria, baseline against forecast, a worked report and how a status turns amber.

- [Read the field note](https://project.responseshift.academy/blog/green-status-late-project/)

## Risk owner vs action owner: who does what?

The difference between a risk owner, an action owner and an approver, how to write a response with a trigger that arrives in time, and a worked register row.

- [Read the field note](https://project.responseshift.academy/blog/risk-owner-is-not-an-action/)

## Continue

[Project practice week](https://project.responseshift.academy/practice-week/)
