WHY HARVUX

Construction does not have a shortage of systems. It has a shortage of connected memory.

Projects generate enormous amounts of useful information. The problem is that much of the context connecting that information disappears as delivery moves on.

Harvux exists to preserve more of that connection.

THE STRUCTURAL PROBLEM

The project is temporary. The organisation is not.

Projects are formed, delivered and closed. Teams move to the next job. Contractors change. People leave. Systems are archived.

The organisation remains.

Useful experience therefore has to cross a boundary that project delivery systems are not always designed to manage.

DELIVERY CROSSES SYSTEM BOUNDARIES

The same problem can appear differently depending on where you are looking.

A potential issue may begin as a Risk.

If it occurs, it becomes an Event.

It may contribute to a Forecast movement.

Someone may capture an Observation about what happened.

The project may determine that the experience matters beyond the job.

The organisation may turn that experience into a Lesson.

That Lesson may identify a Procedure that should be reviewed.

Those are not seven unrelated stories.

They are different parts of the same delivery history.

WHY GOVERNANCE MATTERS

Connecting everything without controlling who decides would create a different problem.

Project teams need authority over project decisions. Organisational knowledge needs its own review and ownership.

Harvux keeps those governance boundaries explicit while allowing useful information to move between them.

WHY RELATIONSHIPS MATTER

A list of records is not the same thing as understanding what happened.

The connection between a Risk and the Event it became matters.

The connection between an Event and the Forecast movement it influenced matters.

The connection between a Lesson and the Procedure it may change matters.

Harvux preserves those relationships so the history remains understandable after the people involved have moved on.

WHY LESSONS ALONE ARE NOT ENOUGH

By the time the lesson is written, much of the useful context may already be gone.

Traditional lessons learned approaches often begin near the end of the story. Harvux starts earlier.

Risk, Events, Forecast Reviews and Observations preserve the delivery context that can eventually become organisational knowledge.

WHY HARVUX DOES NOT TRY TO DO EVERYTHING

Specialist problems deserve specialist tools.

Harvux does not need to become the scheduling system, ERP, cost engine, document platform or quantitative risk model.

Those systems have specific jobs.

Harvux focuses on the governance, relationships and organisational knowledge surrounding delivery.

Use specialist systems for specialist analysis. Use Harvux to preserve the delivery context around them.

Harvux governs how project information becomes organisational knowledge and how that knowledge changes future delivery.

It is not trying to manage every part of project delivery.

It is trying to make sure the parts worth remembering remain connected long enough for the organisation to learn from them.