From project experience to organisational knowledge.

This worked example follows the observation-to-lesson pathway. Harvux connects observations, evidence, lessons, repeat signals, procedures and future projects in one controlled learning model. Six steps from what happened on one project to what the next project starts with.

How organisational knowledge gets built

In this worked example, evidence from three projects supports a validated Lesson, a recommendation for procedure review, and knowledge a future team can use.

Project experience gets recorded the week it happens

A site engineer on Project North logs an access approval delay while the detail is still current: what happened, where, and what it affected. Not months later, reconstructed from memory for a close-out report.

Validate the evidence before publishing a Lesson

Capture assistance does not replace validation. People consider the supporting observations and decide what deserves to become organisational knowledge.

See when project experience repeats.

Three projects, months apart, each treated an access approval delay as a one-off. Putting the observations side by side makes recurrence visible. Supporting evidence lets people assess whether the experience warrants a Lesson.

A validated Lesson can recommend procedure review

The validated Lesson connects its supporting observations to the Procedure recommended for review. The relationship records the recommendation, not acceptance, approval or implementation of a change.

The next project starts with what the last one learned

Published Lessons and recurrence evidence can inform planning on another project. Reusing that knowledge does not establish a Procedure change or automatic distribution.

What teams start to see once project issues are connected

See the learning model in a briefing.

We walk through the observation workflow, lessons review, and repeat signal detection using practical examples from real project delivery scenarios.