Notes tagged
gaps
15 notes on gaps. All notes.
The site and the head office are looking at different numbers
The site records what physically happened and the office records what was ordered and paid. They diverge for structural reasons, not because anyone is lying.
One buyer, three enquiries, three salespeople
The same person arrives through a portal, a hoarding number and a broker. Exact matching will not catch it, and a merge is an ownership decision.
The complaint names the wrong thing
One link was reported broken twice in a single day. Nothing was ever wrong with that link. Two unrelated faults were eating clicks and looked identical.
Written, and never wired
The code to undo a wrong stock entry already existed and had no callers. Nobody had asked for the button, because a workaround was already doing the job.
Filed as chatter
A document was waiting on one person's signature, and the request reached them as a line in a digest. Not a training gap. A row in a routing table.
A fact that had no owner
A payment made in instalments was invisible to half an application, because one plain fact was being worked out separately by every screen that needed it.
How we find our own problems
Nothing here starts with a market report — it starts with hitting the same wall for the tenth time. Notice, build, keep alive, and why stage three decides it.
Why measured and docketed quantities disagree
The number on the docket and the number your side measures are rarely identical. Most of the gap is ordinary physics and method. Some of it is not.
Why staged payments break accounting systems
Most systems store one paid date per bill. A payment in stages never writes it, so every screen asking "is this paid?" goes blind on exactly the biggest orders.
Money before material, and how to sign for it honestly
Paying before delivery is normal in construction. What is not normal is a system that hides which payments are advances and which are for goods already in.
Why tasks stall between people
Work rarely stops because somebody refused. It stops in the handover, where one person has finished and the next has not been told they are now waiting on.
What makes a handover fail
A handover fails when knowledge that lived in one person's head was never written down, and nobody discovers which knowledge that was until it is needed.
The daily progress report nobody reads
Most DPRs are written by somebody who gains nothing from writing them, for somebody who does not read them. There is a version that survives that fact.
The app should tell you why
A refusal with no reason, an empty screen with no cause, a score with no basis. Each teaches that the software is arbitrary, and arbitrary things get routed around.
The gap you stopped noticing
Most broken things at work are not unsolved — they are worked around so smoothly nobody calls them broken. Breaking that habit is why BE Teck exists.