An agreement is impeccable when it satisfies two conditions: it is **precisely defined**, such that an objective third party could judge whether it was kept, and it is **fully agreed** by everyone relevant, in writing. The example is deliberately mundane, because the mundane version is where the standard actually gets set. Not *"we'll start back up after lunch"* but *"It is 12:04 now. We will start again at 1:00. We all agree to be in our seats and present prior to 1:00."* ### **What I'm thinking about** 1. **Ambiguity is the default failure, not dishonesty** – Most broken agreements were never agreements. They were two people with compatible-sounding but different understandings, and nobody discovered the gap until it mattered. 2. **Breaking one has a protocol** – Tell the circle as soon as you know — not when the deadline arrives — and say what you *can* do. The failure is not missing the commitment; it is letting other people plan around a commitment you already know is dead. 3. **Consequences start small and immediate** – Point it out the first time, at the time. Apologies aren't required. What matters is that the standard is visibly enforced early, because unenforced standards decay fast. 4. **And they end decisively** – If someone repeatedly fails to keep agreements, "there is only one consequence that makes sense: they can no longer be part of the company." Reliability is not a nice-to-have; it is the substrate everything else runs on. 5. **There is an explicit carve-out for stretch goals** – "Impeccable Agreements do not apply to OKRs." Goals achieved 70% of the time are optimal, and treating an ambitious target as a broken promise destroys ambition. This applies to tactical commitments — tasks, deadlines, meeting start times. ### **So what?** The carve-out is the part most people get wrong in one direction or the other. Teams that apply agreement rigour to stretch goals stop setting ambitious ones. Teams that apply stretch-goal tolerance to tactical commitments become unreliable and don't notice. Two categories, two standards, stated explicitly so nobody has to guess which one they're in. Related: [[Actions Must Be Inputs]] [[Directly Responsible Individual]] [[Bias to Action Is a Two-Minute Rule]] [[Operating Principles]] [[Executive Operating System MOC]]