What You Need to Know
An architectural decision is a choice about how a system is built. A trade-off is what that choice gives up to get what it gains. The owner, or accountable stakeholder, carries the consequence. The sponsor funds the work.
This lesson uses one made-up example throughout: an insurance company. The company is adding Claude to answer customer questions about claims and to draft the decision letter for each claim. The head of claims is the owner and the sponsor. An engineering team builds the system. The compliance team cares what the letters say.
The Complete Communication Has Seven Parts
A complete communication lets somebody else evaluate a decision instead of merely accepting it. It has seven parts:
- The decision.
- The options genuinely considered, including the one the audience expected.
- The criteria they were judged on, so the weighting is visible and arguable.
- The evidence. For a Claude system this usually means Domain 4 measurements, not assertions.
- What each option costs and what risks it creates.
- A recommendation. Declining to recommend is a failure of responsibility, not a neutral position.
- What would change the recommendation: the measurement, the volume, the price change or the regulatory event that would reverse it.
An architect gives the seventh part, and an advocate does not. It turns a position into engineering that can be revisited without re-arguing the whole question. A decision record carries the same content in 6.4.
At the insurance company, the decision might be that a claims handler checks each draft letter. The options include the one the head of claims expected: no check. The evidence is the measured error rate on past letters. The revisit condition is the seventh part. Here it names the error rate that would remove the check.
Translation Changes the Lead, Never the Facts
Every room gets the same decision and the same facts. Only the lead, which is what you say first, and the amount of technical detail change.
- For executives, lead with business consequence and risk.
- For engineers, lead with mechanism and constraint, because that is what they build against.
- For legal and compliance, begin with a focus on the obligation and on the residual risk that remains after the controls.
- For the sponsor, lead with cost, date and precisely what they are being asked to accept.
At the insurance company, the executives, the engineers and the compliance team each hear the same error rate with a different lead.
Two failures are opposites. One gives an executive too much technical detail. The other gives a specialist generalities that the specialist cannot act on. A third failure is worse. Simplification that makes a statement untrue is not translation. The person who trusted the simplified statement always discovers the problem later.
Say the Error Rate Out Loud
These systems have error rates, and it is the architect's job to say so before anyone signs. State the rate and the population it was measured on. State the handling path for the residual errors: who catches them, how quickly, at what cost. At the insurance company, that path is the claims handler who reads each draft.
The existence of error rates makes a demonstration a communication risk rather than a communication tool. A demo is a sample from the best end of the range of outcomes. An audience that has watched five correct answers has seen a certainty of correct output that does not exist.
Communicate uncertainty as a range, together with the work that would narrow the range. Anthropic's research on evaluation gives the format. Report the interval with each score, not the score alone. When you compare two candidates, also give an interval for each pairwise difference, which is the difference between their two scores. Without these intervals, a comparison may present random variation as a finding.
The Disagreement Pattern, and Its Exception
Sometimes an accountable stakeholder wants something that the evidence contradicts. Measure, explain the trade-off and recommend. Leave the decision with the person who holds the accountability. The owner gets the quality difference as a number, and its downstream cost in the resources that the owner controls. The owner also gets the exposure to the organisation, the saving and a clear recommendation. Then the owner gets the decision.
Suppose the head of claims wants the replies to customers live before the busy winter season, although some replies are wrong. The head of claims gets the rate of wrong replies, its cost and what the date saves. Then the head of claims decides. Three responses fail: silent non-compliance, compliance without comment, and escalation above the owner as a first step.
The exception is different in kind. An owner's authority covers cost against quality and scope against date, because the owner can accept the consequence. It does not cover a legal, regulatory or safety obligation, which nobody can accept as a preference. In that case, say so plainly, and involve the department that is responsible for the obligation, which is Domain 5's area. Suppose the insurance regulator requires a person to check each letter that refuses a claim. Sending those letters unchecked breaks a regulatory obligation, and the head of claims cannot accept that as a trade-off.
Judge by the Consequence, Not by How Loud the Stakeholder Is
In a project or a question, the effect of being wrong decides which case you face. A margin, a date or a quality level means that the owner decides with all the facts. An unlawful data path, or an unsupervised action with a safety consequence, means an obligation. The loudness of the stakeholder is not evidence either way.
In the exam
Questions on this objective reward complete reasoning rather than eloquence. Both translation failures appear as wrong options.
Anthropic's Claude Academy course on rolling out Claude Enterprise covers part of this objective. It lists what each decision owner needs from the person who runs the rollout. For the visibility decision, whose owner answers for data risk, that is "The options, your recommendation, and what each costs to change." The course also uses one three-step frame for each configuration decision: the decision, the choices, and what to consider before you reverse it. Treat the rest of this objective as professional craft rather than product behaviour. The authority for this objective is the exam guide's own description of the role: collaborating with cross-functional stakeholders and communicating architectural decisions effectively. The rooms where the role works include security, legal and executive participants.
Exam Traps
Implementing a decision you hold measured evidence against, without comment
The owner decides without the one measurement that would let them accept the consequence knowingly. Present the measured trade-off with a recommendation, then leave the decision with the owner.
Building it your way quietly after you lost the argument
It removes the owner's ability to accept a consequence that is legitimately theirs, and when people discover it, it loses the trust that made the advice worth having. Record the decision, the evidence and the condition that would reopen it, then build what was decided.
Taking the disagreement to the owner's superior before the trade-off has been put to the owner
Obstruction as the first action. It uses up goodwill in the organisation on an argument that the evidence could still have won. Escalation is the last move, and only where the owner's authority does not cover the consequence.
Answering 'how accurate will it be?' with a single confident number
A point estimate with no interval and no population is a promise that no measurement supports. Give a range on a defined population plus the measurement that would narrow it.
Practice Scenario
A logistics operator's operations director has decided the route-exception assistant will ship without its confidence-banding and human-review step. That step puts each answer in a confidence band and sends the low bands to a person for review. She decided this because the review queue needs headcount she does not have. Evaluation on real exceptions puts most of the errors inside the band that step would have caught, and each undetected error triggers a re-delivery costing more than the saved headcount. She has not seen these results. Company policy requires a risk owner to see the evaluation evidence before accepting a risk, and staffing decisions stay with her. What should the architect do?
Build Exercise
Write One Architectural Decision as It Would Be Communicated
What you'll learn
- How to assemble a decision, its options, criteria, evidence and consequences into one communication
- How to write the revisit condition that keeps a decision from being re-argued from the beginning
- How to translate for an executive and an engineer without changing the facts
- How to state uncertainty as a range with the measurement that would narrow it
- How to tell an owner-decides trade-off from an obligation the owner cannot accept
- Take the hardest trade-off in a system you know and write the decision, the options genuinely considered, the criteria they were judged on, the evidence, and what each option costs and exposes
Why: Completeness is what lets somebody else evaluate the decision rather than merely defer to it, and it is what the exam rewards over eloquence.
You should see: One page carrying five parts, with the evidence traceable to a measurement rather than an assertion.
- Write the recommendation, then the sentence most architects omit: what would change this recommendation, stated as a measurement, a volume, a price or a regulatory event
Why: A recommendation with no revisit condition has to be re-argued from the beginning the next time anything changes.
You should see: A named recommendation plus one testable condition that would reverse it.
- Produce the executive version and the engineering version of the same decision, then read them against each other
Why: Translation changes the lead and the mechanism. Distortion changes the facts, and whoever trusted it discovers it later.
You should see: Two versions with different leads and identical facts.
- Write the accuracy answer as a range on a defined population, with the work that would narrow it, and note what you would need to measure to justify a single number instead
Why: A point estimate with no interval is a promise that no measurement supports, and the problem then appears as an incident after launch, not as a conversation before it.
You should see: A band, the population it applies to, and a named piece of evaluation work with a duration.
- Classify the decision: owner-decides trade-off, or an obligation the owner has no authority to accept — and write the two sentences you would say in the second case, naming the department you would involve
Why: The same evidence supports opposite moves, and the consequence of being wrong is what tells you which one.
You should see: A one-word classification with its justification, plus the two sentences and a named department.
Sources
- A Statistical Approach to Model Evaluations — Anthropic
- Building Effective AI Agents — Anthropic
- Deploying Claude Enterprise with confidence: Owners and intake — Anthropic
- Deploying Claude Enterprise with confidence: Five decisions and the frame — Anthropic
- Claude Certified Architect Professional Exam Guide (v1.0) — Domain 6 — Anthropic