Property transactions, and especially those involving specialised assets such as hangar space or land beside an airfield, have a habit of stalling at the same points. A buyer’s paperwork comes back incomplete. A viewing is rescheduled twice. A conveyancing step takes weeks longer than anyone expected. Each time, the first explanation is a specific, local one, and each time the team adapts and carries on. What follows is a staged method for tracing recurring delays to their source by asking why five times, applied to real estate with an aviation flavour. It deals only with administration and process; nothing here amounts to legal, financial or investment guidance, and no particular deal’s terms are discussed.
Step 1: Define the delay as a measurable observation
Start with a statement that a colleague could verify. “Deals are slow” is an impression. “In the last quarter, four of six transactions waited more than a week for a signed document” is an observation. Specify what waited, for how long, and at which stage. Precision matters here because every later question is built on this sentence, and a vague starting point produces vague answers.
Step 2: Collect the facts from the record, not from recollection
Open the correspondence trail, the document tracker or the diary for each affected deal. Note the dates on which a request was sent, when it was acknowledged and when it was fulfilled. A timeline built from records often contradicts the story people tell from memory, and it is the timeline you will be questioning. If no tracker exists, that is itself a first finding worth noting.
Step 3: Ask the first why and accept that it will be a symptom
Why did the signed document arrive late? Because the counterparty returned it after the deadline. This is a factual answer and it is not yet useful, since it points at someone outside your control. Record it and continue.
Step 4: Ask why again, turning inward at each step
A productive habit is to steer each question toward what your own side could influence. Why did the counterparty return it late? Because they received it after a long delay. Why was it sent late? Because it had to be reviewed internally before dispatch. Why did the review take so long? Because the reviewer only checks a shared folder once a week. The chain has moved from an outside party to an internal routine, which is precisely where you can act.
Step 5: Reach the cause that names a process
Why does the reviewer check weekly? Because document review was never assigned as a task with a deadline; it was added to an existing role as an informal duty. That is the root. It is not a person’s failing but a gap in how responsibilities were defined. When an answer names an unassigned duty, an unclear handover or a missing standard, you have arrived.
Step 6: Test the chain in both directions
Read the chain forward from the root: if review had a named owner and a two-day standard, would the document have been sent sooner? Would the counterparty have returned it on time? If every link holds, the chain is sound. If one link is doubtful, treat it as a hypothesis and look for evidence before acting. Read the chain backward as well, asking at each answer whether there could be a second, parallel cause. Complex transactions often have two.
Step 7: Pick one change, give it an owner and fix a review day
Resist writing a long action list. For the example above, the single change might be: “Document review is assigned to a named person, with a two-working-day turnaround, starting on the first of next month.” Write down the owner’s role and the review day. In professional practice, a change without a named owner and a date is a wish.
Step 8: Review the effect
At the agreed date, return to the original observation. Did the average wait for signed documents fall? Compare like with like, using the same stages and the same measure. If the symptom has faded, record the change as part of the standard procedure. If not, add one more why to the answer you thought was solid.
Where this fits in wider client service
Delays are felt by clients as service problems, whatever their cause. Working out why they recur is therefore part of looking after the people you serve. For perspective on the client side of the relationship, see an article about tailoring the client journey in luxury real estate. The costs of recurring friction are discussed from another angle in an article on locating and closing hidden drains on your finances, and the root-cause habit complements both.
Common errors in applying the method
- Ending the chain at a counterparty. “The other side was slow” gives you nothing to change. Turn the question toward your own routine.
- Treating a person as the cause. If a chain ends with a name, ask what in the arrangement allowed one individual’s absence to hold up the deal.
- Skipping the record. Conclusions drawn from memory tend to favour dramatic explanations.
- Making several changes at once. Afterwards, nobody can tell which change did the work.
The same discipline elsewhere
This is a general management technique, and it appears well outside property. A directory-type website such as a directory website laid out in hospital, doctor, forum and blog areas must keep a large set of pages current, and an out-of-date entry there prompts the same question: which routine failed to catch it? The sector is unrelated; the method is not.
A note on scale
The method is equally at home in a two-person agency and a larger firm. In a small team, the chain is short and the owner is obvious. In a larger one, the value lies in the written record, because the people who answer the questions may not be the people who inherit the fix. Either way, keep the sessions brief, the language plain and the output to a single page that can be filed with the deal records.
A summary of the procedure
- State the delay as a verifiable observation.
- Gather dates and facts from the record.
- Ask why, and record the answer as a symptom.
- Continue, steering each question toward your own routines.
- Stop when an answer names a process, owner or standard.
- Test the chain forward and backward.
- Introduce a single change, owned and dated.
- Review against the original observation.
Used consistently, the procedure produces a modest but valuable asset: a written record of why delays occurred and what was changed. Over time that record shows which parts of the transaction process generate the most friction, and it provides a sound basis for improvement that rests on documented causes rather than on recollection or assumption.

