Sign in or create a free account to save this Card to your Deck.
Performance Card · Evidence of progress
Deliver promises to an agreed quality standard
DONE HAS TO MEAN WHAT THE CUSTOMER EXPECTED.
Delivered output meets the promise only when the customer receives it to an agreed standard. Completion of internal tasks is distinct from acceptance and client use. The standard is repeated observable capability under comparable conditions. Intent, documentation, or tool adoption alone does not establish performance.
Expanded teaching
Expanded teaching
The observable standard
Delivered output meets the promise only when the customer receives it to an agreed standard. Completion of internal tasks is distinct from acceptance and client use. Performance means the capability produces a repeatable result under comparable conditions, not merely that a policy, dashboard, checklist, or tool exists.
What to measure
For recent deliveries, can the team show scope, quality criteria, review and customer acceptance evidence? Measure on-time delivery, first-pass acceptance, rework, scope-change reasons, exception lead time, client uncertainty, founder intervention, delivery margin, quality-review failures, and handoff completeness. Define the sample, period, baseline, and person authorized to judge the standard.
What does not count as evidence
Intent, training completion, software adoption, a single successful case, or a manually repaired exception cannot establish systemic capability.
Improvement cycle
Define acceptance conditions at the beginning of the next engagement and inspect actual results against them. Compare the observed result with the baseline, identify meaningful variation, test one improvement at a time where practical, and review whether the change remains effective under normal operating pressure.
Where AI belongs
AI can draft scope summaries from approved discovery, check for missing criteria, prepare status updates, surface exception signals, and support handoff communication. People own quality acceptance, commercial exceptions, client repair conversations, and consequential delivery commitments.
Measurement limits
Metrics can reveal delay, error, variation, and progression without explaining every cause. Use them to select questions for investigation and add human context before consequential decisions.
Diagnostic inquiry
Questions to ask, not conclusions
What repeated observable evidence would show that “Deliver promises to an agreed quality standard” is working at the required operating standard?
Questions that distinguish possible explanations
- For recent deliveries, can the team show scope, quality criteria, review and customer acceptance evidence?
- What upstream condition, control failure, or missing information could produce the same symptom?
- If you take the proposed next action, what observable result will tell you whether it helped? Proposed action: Define acceptance conditions at the beginning of the next engagement and inspect actual results against them.
Practical application
Practical application
Define acceptance conditions at the beginning of the next engagement and inspect actual results against them. Use a recent, bounded sample instead of hypothetical data. Name one accountable owner, record the current baseline, define the acceptance or completion standard, and run the change through a normal operating cycle. At review, decide whether to keep, revise, expand, or stop the intervention based on evidence. Escalate immediately where privacy, security, legal, customer-harm, or material financial risks cannot safely wait for the test cycle.
Ask Atria
Talk through this Card
Talk it through with us
If this Card describes your week, a free conversation is the fastest way to see what it means for your company and what to do next.
Book a free conversation