Home / Insights

Insights

Direct answers to direct questions.

Where the white papers go deep, insights go straight — definitional guides and field notes from live oversight work, in plain language with the answer up front.

01The writing
02Why this section exists

The vocabulary of this industry is vague, and the vagueness is not accidental.

Ask three people at the same table what a project manager does and you will get three answers that do not overlap. Owner’s representative, client representative, PMC, development manager, employer’s agent — the titles are used interchangeably in the market and mean materially different things inside an appointment. Design governance, value engineering, and change management are worse: each names a discipline in the textbook and a negotiating position in practice.

An owner reading a proposal often cannot tell which one they are being sold. That is not a drafting failure. Imprecision is commercially useful to whoever writes the scope, because a term that means several things can be argued into meaning the convenient one later — usually in a letter about entitlement, two years after anyone remembers what was intended.

So this section defines the terms plainly, from the owner’s side of the table, and publishes what we see when those definitions meet a live project.

The answer goes first.

Every piece here is written for someone mid-decision: an appointment on the desk, a variation waiting for signature, a consultant recommending something that sounds reasonable and might not be. That reader does not need the history of the profession before the answer. So the answer comes in the first paragraph and the qualifications follow it.

The same structure happens to be what answer engines quote, which is a convenience rather than the reason. Writing that survives being summarised by a machine is usually writing that was clear to begin with.

What this is not.

It is not news, and it is not commentary on other people’s projects. Nothing goes up to fill a slot. Where a piece draws on live work, the project is not named and the numbers are changed or removed — an owner who hires us should expect exactly that treatment of their own project.

Pieces are revised rather than left to rot, and the date on the page moves when they are. Where an insight answers a question, a white paper works through a decision.

03Common questions
How often do you publish?

Insights go up when there is something worth saying, not on a schedule. White papers are planned work and appear more regularly; insights are reactive, and a slot that has to be filled gets filled with filler.

What is the difference between an insight and a white paper?

An insight answers a question: what a term means, what a role actually covers, what a clause does to you. A white paper works through a decision an owner has to make, at length, with the evidence on the page.

Do you write about live projects?

Only in general terms. Where a piece draws on current oversight work, the project is not named and figures are changed or removed. An owner who hires us should expect the same discretion.

Can I quote these?

Yes — quote what is useful, with attribution and a link back. Where we cite third-party research, the source is named in the text so you can go to the original rather than relying on our reading of it.

Want the next piece when it lands?

One email when we publish. Nothing else.

Subscribe