A Question That Gets Skipped
Every site visit I have ever sat through starts with the same questions. What is the soil like. What is the zoning. Who are the contractors. What is the timeline. These are the right questions, and I ask them too.
But there is one question I almost never hear anyone ask out loud, and it is probably the most expensive one to skip: where does the information live once the people who gathered it move on?
Not the blueprints. Not the contracts. The small stuff. The conversation with a local official that never got written down. The reason a permit took six weeks instead of two. The name of the engineer who actually knows why a load calculation was done a certain way. That knowledge sits in someone’s head, or in an email thread, or in a notebook, and then that person rotates off the project or the project pauses for a season, and the knowledge is just gone.
Why This Keeps Happening
Construction and infrastructure work moves fast when it moves. Everyone is focused on the next milestone, not on whether the last one got documented in a way a stranger could pick up and understand. That is true on a single site in one city. It gets worse the moment a project crosses a border.
I have worked across multiple countries, and the pattern repeats every time. A team in one country solves a problem a certain way, and a team somewhere else runs into the same problem six months later with no idea the first solution exists. Different language, different regulatory system, different software if there is software at all. The information was never lost in a dramatic way. It just never traveled.
The honest reason this happens is that information systems are treated as an afterthought on development projects. Everyone budgets for steel and concrete and labor. Almost nobody budgets time for making sure what gets learned on one project reaches the next one.
What Changes When You Ask
I started asking this question on every new site, every new country, every new partner: if I disappeared tomorrow, could someone else pick this up using only what is written down? Most of the time, early on, the honest answer was no.
Asking that question does a few concrete things. It forces decisions out of people’s heads and onto paper, or into whatever system the team actually uses, while the reasoning is still fresh. It surfaces the gaps before they become expensive, not after a permit gets rejected or a plan gets reworked because nobody remembered why the first version was drawn that way. And it gives you something to hand to a new partner or a new government contact that is not just a stack of technical drawings, but an actual record of what happened and why.
It also changes how you treat the people doing the work. If the plan is for knowledge to leave the building system when a person does, you end up with a project that depends entirely on a few individuals never leaving, never getting sick, never retiring. That is not a plan. That is luck.
A Simple Habit That Fixes Most of It
I do not think this needs a complicated system to solve. It needs a habit. After any meeting where a real decision gets made, someone writes down what was decided and why, in plain language, in a place more than one person can reach. Not a transcript. A short record: here is the problem, here is what we chose, here is what we would do differently if the situation shifts.
That sounds small. It is small. But across a project that runs for years, across borders, with teams that do not all speak the same first language, that habit is the difference between institutional memory and institutional guesswork.
The next time someone walks a site and starts listing off the usual questions about soil and zoning and timeline, I would add one more to the list, further down but not forgotten: when this phase is over and the people in this room have scattered to other projects, will what we learned here still be usable by someone who was not in the room? If the answer is no, that is worth fixing before the next phase starts, not after it has already cost you something.