6.3 — Expectation Alignment and Service-Level Commitments

CCAR-P Domain 6 · Task 6.3

What You Need to Know

Engineer first, then promise. Never the reverse.

Anatomy of a Defensible Commitment (Six Elements)

1. Metric — what is measured and how
2. Percentile or threshold — means conceal the tail
3. Measurement point — where the clock starts and stops
4. Window — over what period compliance is assessed
5. Population — who and what it covers (defined before measurement)
6. Breach behaviour — what happens when it is missed

You Cannot Promise Above Your Dependencies

Check what the platform underneath commits to. A promise above that envelope is written against somebody else’s best effort.

Negotiating the Impossible Ask

Show the decomposition so the figure stops being arbitrary. Close perceived gaps with streaming, progressive disclosure, partial results, or async + notification — none of which move total completion time. Accepting the number is capitulation; deleting a control to hit it is worse.

Quality Is a Measured Claim

Same six elements. Where shortfall concentrates in a segment, say so and give that segment its own plan and owner. Hidden population narrowing is the most dangerous option.

Feedback Is Instrumentation

A feedback channel must produce evidence and a disposition. Confirmed failures route into the regression set. Anecdotes routed into prompt edits make a system rot.

Exam Traps

• Writing a bare number into a schedule as the service level
• Meeting a latency target by dropping a retrieval or verification stage
• Offering streaming/partial results where the consumer is a pipeline, not a person
• Quietly narrowing the covered population until the headline figure becomes true