Technical Judgment

Technical Judgment is the ability to exercise sound engineering judgment without doing the engineering yourself, and to own the technical responsibilities that cannot be delegated away. It is misunderstood at every scope, more than any other domain. New managers fear that stepping back from the code makes them irrelevant. New executives fear the opposite, that technical matters are now beneath them and can be handed off entirely. Both are wrong. Credibility comes from reasoning well about technical reality, not from writing the most code. Architecture, reliability, security and technical risk stay strategic concerns at the very top. The domain carries 20% of every examination: 12 questions on EMA-I, 15 on EMP-II and 18 on EME-III. Its six competencies are listed below with the questions each carries at each level, and the Exam Content Outlines give the proficiency indicators.

Each competency in this domain puts judgment ahead of throughput. That means knowing enough to ask the right questions, telling real risk from hypothetical risk, deciding when good enough is good enough and, hardest of all, knowing which decisions are yours. v3.0 adds two responsibilities that v1.0 left implicit and the job no longer can. One is AI-assisted engineering, where the evidence is mixed and the gap between a considered judgment and a fashionable one is widest. The other is security, privacy and compliance, which engineering owns instead of delegating to a separate function. The examinations favour the option that asks the sharp question, demands the evidence, installs the decision process, or takes the risk to the level that should decide it. They mark down the option that rubber-stamps, rewrites, overrides or defers.

At team scope you exercise judgment about one team's technical decisions, mostly through questions and restraint. At organisational scope you keep architecture and technical health coherent across teams while staying credible at one remove. That takes standards at the boundaries, deliberate platform bets, class-level fixes with named owners, and a decision process installed before any opinion is issued. At executive scope you own the organisation's technical strategy: the bet-the-company decisions, the platform's runway treated as business risk, the strategy for AI-assisted engineering, the organisation's security exposure, and a short, explicit docket of the decisions that are yours alone. The general pattern is in How Judgment Scales; each unit's scaling note places its own competency on it.

Start with TJ-4 Technical credibility and intervention. It holds the domain's two governing ideas, systems understanding over currency and the intervention threshold, and every other unit applies them. Then read TJ-1 Evaluating architectural decisions and their organisational consequences and TJ-2 Technical debt together, since one covers the decisions that shape systems and the other their accumulated cost. TJ-3 Code review and quality standards is the quality system and introduces the standard for AI-generated code that TJ-5 AI-assisted engineering governs, so read them in that order. TJ-6 Security, privacy, and compliance as engineering responsibilities closes the domain. Read it with DE-3 Reliability, incident response, and operational ownership, because a security incident follows the incident structure set out there.

Technical judgment depends on Strategy & Vision for the organisation that an architecture implies, in SV-6 Organisational design and leading change, and for the economics of every platform and AI decision, in SV-4 Engineering economics. It depends on Delivery & Execution for the flow that review belongs to, DE-5 Designing how work flows, and for the risk and ownership gaps that surface as incidents, DE-4 Managing scope, risk, and dependencies across workstreams. The restraint that lets a team own its decisions is the same restraint PL-1 Delegation, ownership, and decision rights describes. When a board wants a headcount plan the evidence does not support, the honest answer is the one in CC-5 Values, integrity, and ethical judgment under pressure.