How Judgment Scales

The three certifications assess the same twenty-nine competencies. What separates an Associate from a Professional from an Expert is not which competencies they hold but the scope at which each one is exercised. The previous edition of this standard expressed that by writing every competency three times, once per level. Readers found the bands repetitive, and the repetition hid the real pattern: scope changes every competency in the same handful of ways. This chapter states those ways once. Each knowledge unit then carries a short scaling note and tags its signals of strong and weak practice with the scope where they apply, and the Exam Content Outlines say what each level's questions expect.

Read this chapter before the domain units. It teaches the pattern every unit follows, and it is the key to the scope tags.

Scope is not seniority and not headcount. A manager with thirty reports in one team is still exercising team-scope judgment; a director with twelve people across three teams is not. Scope is what changes about a decision when the object of the decision gets larger. Six things change, and they change together.

1. The object of judgment

The most useful question about any competency is: what is being decided about? At team scope the object is concrete and close — a task, an engineer, a sprint, a service, a conversation. At organisational scope the object is a class of those things — a team's charter, a manager's judgment, a delivery system, a platform, a hiring bar. At executive scope the object is the system that produces the class — the structure that decides who owns what, the leadership pipeline, the operating cadence, the technical strategy, the culture. The table in the next section gives the object for every competency. It is the single most important thing to understand about how a competency scales, because the same instinct applied to the wrong object is the most common way strong managers fail after promotion.

2. Time horizon

Team-scope decisions resolve in days or weeks; their feedback arrives before the next similar decision. Organisational decisions play out over quarters: a manager appointment, a team split, a platform bet. Executive decisions play out over years, and some of the most consequential — a technical strategy, an organisational design, a culture — are only judged in hindsight by people who will not know what the alternatives were. The longer the horizon, the less the decision can be corrected by iteration and the more it must be right on first principles.

3. Ambiguity

At team scope the goal is usually given and the question is how to reach it. At organisational scope the goals of different teams conflict and the question is which to favour. At executive scope the goal itself is often unclear, contested or shifting, and part of the work is deciding what the question is. Strong judgment at each level is comfortable with the ambiguity that level carries and does not manufacture false certainty to escape it — nor does it import ambiguity the level does not have. An Associate who treats a clear sprint goal as a strategic question is as mis-scoped as an Expert who treats a strategic question as a scheduling problem.

4. Consequence and reversibility

A bad delegation costs a week and teaches everyone something. A bad manager appointment costs a team a year. A bad organisational design costs a company the ability to execute for as long as it stands. As scope widens, the cost of error rises and the chance to reverse falls, so deliberation should be spent where the door is one-way. The complementary failure is real too: executives who bring executive-grade deliberation to every reversible decision slow the whole organisation to their own pace.

5. Who you act through

At team scope you act directly: you have the conversation, you review the design, you make the call. At organisational scope you act mostly through the managers who report to you, and your leverage comes from what you delegate to them, how you develop them, and what you hold them to. At executive scope you act largely through systems — structures, cadences, standards, incentives — and through leaders you rarely see day to day. Each step removes you from the work and adds a layer whose judgment you must develop and trust. Every competency in this standard has a "through others" form, and the temptation to skip the layer and act directly is the signature failure of the newly promoted at every level.

6. Information latency and filtering

The further you are from the work, the later and more filtered your information arrives. A team lead hears about a problem the day it happens. A director hears a version of it in a weekly update, after the manager has decided how to present it. An executive hears a narrative, weeks later, shaped by everyone it passed through. Strong judgment at scope compensates deliberately: skip-level conversations, direct observation of artifacts, metrics that do not pass through a person, and a visible reaction to bad news that makes it safe to deliver early. Weak judgment at scope mistakes the absence of bad news for its absence.

The table below is the reference the scaling note in each unit points to. For each competency it names what is being decided about at each of the three scopes. Read down a column to see a level; read across a row to see how one competency changes shape.

Two competencies, PL-6 and SV-6, have no team-scope object. Leading through leaders requires leaders to lead through, and organisational design requires an organisation to design. Both are therefore assessed from EMP-II upward; the EMA-I Exam Content Outline lists them explicitly as not assessed.

Each unit's judgment section lists signals of strong practice and failure modes as one list, and tags an item with the scope where it applies:

• [team] — one team, direct reports; the manager acts directly.
• [org] — several teams, usually through other managers.
• [exec] — an engineering organisation, largely through systems and other leaders.

An item with no tag applies at every scope. An item tagged [org] [exec] applies at both of those and not at team scope. The tags map onto the certifications — EMA-I assesses [team], EMP-II adds [org], EME-III adds [exec] — but they are a property of the judgment, not of the reader. A first-line manager reading an [exec] item is reading about the scope their own manager's manager works at, which is useful for understanding the decisions that arrive from above and for knowing what the next level of the job actually is.

The Exam Content Outlines use the same three words as the scope of every proficiency indicator. Because the certifications are cumulative, a Professional is held to every team indicator as well as every org one.

Some things do not change with scope, and it is worth being explicit. The obligation to tell the truth about status does not become more negotiable with seniority; if anything the consequence of shading it grows. The distinction between an estimate and a commitment is the same at every level. The reaction to bad news that makes it safe to deliver is the same reaction whether the messenger is an engineer or a vice-president. And the question that tests any plan — pick any item and ask the person doing it why it is there — works at every altitude.

Judgment scales. Integrity does not need to.