A promise made in a meeting lands differently by the next morning. The project manager says ‘I will have the proposal ready by Thursday’; Thursday afternoon passes in silence, and a brief apology arrives Friday morning. On its own, a minor hiccup. But in a mid-size construction and contracting firm operating in Ankara — 312 employees across eight active project sites — when this kind of drift becomes weekly routine, the picture shifts entirely. The client is no longer evaluating the proposal; they are evaluating whether the proposal will actually arrive. This article defends a single, uncomfortable thesis: reliability is not a character trait but a measurable business process, and because most managers treat it as a personal quality, they never calculate the cumulative operational cost of small inconsistencies. What you do not measure, you cannot fix.The most common mistake in reliability discussions is framing the subject morally. ‘Keeping your word’, ‘being honest’ — these phrases are accurate but insufficient. They locate the problem at the level of individual character and miss it entirely as a systemic process failure. In construction, each workflow — progress billing cycles, subcontractor coordination, materials procurement — rests on trust chains built from consistent behavior. When the site supervisor tells a subcontractor ‘materials arrive Wednesday’ and that commitment fails three times in a row, the subcontractor adjusts internally: they carry buffer stock, keep workers on standby, take on other work and quietly reprioritize this site. Each adjustment carries a cost. Reliability here is not a personality variable; it is an operational variable that directly determines supply chain productivity.There is a legitimate counter-argument worth acknowledging at the outset: consistent behavior is not always possible. In construction, weather conditions, municipal permit timelines, procurement delays, and currency volatility — recall the exchange rate swings in early 2016 — generate genuine uncertainty. A project manager sometimes has no choice but to revise a committed date. The problem is not the revision. The problem is this: most managers use the inevitability of uncertainty as a justification for not communicating that uncertainty early and explicitly. Reliability does not mean keeping every commitment perfectly; it means, when you know you cannot keep one, communicating that as early as possible with a clear reason. This distinction changes operational planning for the counterparty entirely. Informed early, they revise their plan; informed late, they lose confidence and build buffers. The cost of the buffer is the invoice for distrust.The cumulative effect of inconsistent behavior shows most clearly in the quality of in-team decision-making. In a construction firm like the Ankara example — a representative pattern common across the sector — tracking what proportion of decisions made in project meetings are actually executed before the next meeting reveals a sharp drop in teams with inconsistent leadership profiles. When team members do not know whether accountability will genuinely be followed up, two defensive behaviors emerge: avoiding commitment in the first place, or making the commitment but deprioritizing it. Both are invisible to the manager, because no one objects in the meeting itself. The agenda moves forward, minutes are filed, reports are sent — but the work stays where it was. Management literature names this the ‘action gap’; it is the most expensive output of reliability problems because it generates invisible cost, the kind that never appears in a budget line.Measuring reliability behavior is entirely feasible, and organizations that skip this step are left using personal impression as their only data point. A practical starting point: systematically log decisions made in meetings, record the responsible person and committed date, then track in the next session what proportion were completed on time. Call this the ‘commitment-to-action ratio.’ Calculated at both individual and team level across three meeting cycles, the Ankara firm can see numerically which project managers run predictable teams. A second step: a short survey asking team members how frequently their manager meets stated deadlines, then correlating those results with the commitment-to-action ratio. High correlation indicates a behavioral problem; low correlation points to system and resource planning failures. This distinction changes the remediation strategy entirely.Reliability in client relationships carries its own distinct dynamic. In B2B contexts — construction, engineering, project-based services — clients internalize inconsistent behavior quickly and embed their response in contract terms. Payment windows shorten, retention percentages rise, project scope gets sliced into smaller approval stages, and sign-off processes grow heavier. Each of these is distrust written into a legal document. An experienced procurement director puts it plainly: ‘I do not evaluate a firm’s proposal. I evaluate the historical overlap between what that firm has told me and what it has delivered.’ Building that track record typically takes four or five project cycles; destroying it can take a single bad experience. This is the asymmetric cost structure of reliability: earned slowly, lost instantly.Return to that Ankara construction firm and its project manager. Can he still get the proposal out by Thursday? Perhaps not. But he can send two sentences Tuesday afternoon: ‘Additional technical detail came up in the proposal; I will send it Monday morning instead of Thursday.’ Those two sentences represent a trust payment that no competency development programme alone can produce. Reliability is not about perfect delivery; it is about sharing uncertainty in time for the other party to act. As long as managers treat this as a character question, no systematic measurement or feedback loop gets built around it. And what is not measured does not improve — that was true in 2016, and it will remain true a decade from now.
This article was originally published in Turkish by Gökhan MERCANOĞLU on March 5, 2016. The English edition has been reviewed and edited by the author.