Values, integrity, and ethical judgment under pressure

Culture is not a values poster; it is the accumulated pattern of what behaviour gets rewarded, tolerated and punished, and it is defined by what leaders do when the stated values are costly. Everyone watches the gap between word and action and believes the action. v1.0 framed this competency as modelling values under pressure; v3.0 widens it to ethical judgment, because the situations that test a manager most are the ones where the organisation's stated values, the law, the policy and the pressure of the moment do not settle the question, and the manager has to. The competency is upholding values precisely when it is expensive — the brilliant jerk addressed rather than banked, the status reported truthfully rather than shaded, the error budget obeyed when the launch is due — and, at scope, running culture as the system it is: what leadership visibly does, rewards, promotes and tolerates. It matters because tolerating a behaviour endorses it, because a value with a seniority exemption is not a value but a price, and because one visible exception undoes quarters of work. The examinations test it through the high performer whose behaviour buys silence, the manager asked to report a slipping project as on track, and the leadership that shipped through an exhausted error budget while everyone noticed.

1. The costly moment is the culture. Values that survive only when they are free are decoration. What a leader does when the right call costs something — a launch, a customer, a person — is what the organisation learns and copies.
2. Tolerating is endorsing. What gets rewarded gets repeated, and what gets tolerated gets learned. The brilliant jerk who is banked teaches everyone that results buy exemption.
3. Consequences reach the powerful, or they are pricing. A value enforced only below a certain level is not a value. The senior, high-impact leader who breaches one faces real, visible consequences, and how results are achieved is part of the result.
4. Do not shade the truth upward, and absorb the cost of declining. A status, a rating or a commitment asked to be reported better than it is, is declined — and the cost of declining is carried by the manager, not passed down to the team.
5. Behaviour changes when the system changes. A third mandate for what two mandates did not fix will fail; behaviour yields when the wanted thing becomes the easy path, is visibly valued, and the friction of doing it drops. Culture change is a multi-quarter realignment of hiring, promotion, recognition and consequences, never an announcement.
6. Where the rules do not settle it, judgment does — and it is explained. A request that is legal and wrong, a policy that would produce a bad outcome in this case, a value in tension with another: the manager decides on the merits, says why, and owns it.

Culture has a deep research literature and thin experimental evidence about how to change it; the unit grades its models as practice and draws its operating definition from the field's foundational work.

Artifacts, espoused values, and assumptions practice

The three-level model in Edgar H. Schein, Organizational Culture and Leadership (1985): the visible artifacts of a culture, the values it espouses, and the underlying assumptions that actually drive behaviour, which are usually unspoken and often at odds with the espoused values. Its use in this unit is diagnostic: where the espoused values and the behaviour diverge, the behaviour is the culture, and the assumptions it reveals — "results buy exemption", "the budget is obeyed unless it is inconvenient" — are what a leader is actually managing.

Culture as what is rewarded, tolerated, and punished practice

Less a named model than the operating definition this standard uses: culture is the accumulated pattern of actual behaviour, set by what leaders visibly do, reward, promote and tolerate, far more than by stated values, policies or announcements. Its corollary for change is that culture is realigned through the systems — hiring, promotion, recognition, consequences — and that a single visible exception, the tolerated brilliant jerk or the value waived for a launch, can undo quarters of work.

Service-level objectives and error budgets practice

The mechanism from Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy (editors), Site Reliability Engineering: How Google Runs Production Systems (2016), introduced in DE-3 Reliability, incident response, and operational ownership and treated here as this unit's defining test case: the error budget converts "reliability first" from a poster into a pre-agreed rule, and it is only as good as leadership's willingness to obey it when a launch is due. Shipping through an exhausted budget in front of the whole organisation teaches everyone the real policy; obeying it at cost is the most legible cultural act an engineering leader can perform.

Leading change practice

The model from John P. Kotter, Leading Change (1996), used in SV-6 Organisational design and leading change for structure and here for norms: a coalition of credible leaders modelling the new behaviour, systems realigned behind it, early wins made visible, persistence measured in quarters, and the change anchored in how decisions are actually made. The steps most often skipped in culture change are the last — consolidation and anchoring — and the announcement is merely the starting gun.

The costly moment practice

Not a named model but the concept this unit is organised around: the situation in which a stated value and the pressure of the moment point in different directions, and the decision is watched. Its provenance is experiential; its recognisability is why nearly every scenario in this competency is built from one.

The values audit, in behaviour

Once a year the manager lists the organisation's stated values and, beside each, what actually happened the last time it was costly. Where the two diverge, the divergence is the culture, and it is named as such before anything is changed.

The brilliant-jerk decision

When a high performer's behaviour breaches the team's values, the manager acts within the month: specific feedback, an explicit expectation, a date, and consequences that follow if the pattern holds, through PL-4 Performance management. The output is not a reason to wait; every week of tolerance publishes the real values.

Declining to shade

When asked to report a project, a rating or a forecast as better than it is, the manager declines, plainly, with the honest picture and options, and carries the discomfort personally rather than passing it to the team. The habit is what makes the manager's good news believable.

Changing behaviour by changing the system

For a norm the organisation wants — documentation, blameless reviews, a practice from one team spread to others — the manager makes it the easiest path to something people already want, values it visibly in recognition and promotion, and drops the friction. A mandate is not issued for what two mandates did not fix.

Consequences at the top

When a senior leader breaches a core value, the consequence is real and visible, and how their results were achieved is treated as part of their performance. The executive starts with the mirror: when the leadership team models behaviours the organisation should not copy, that is the first culture problem, handled with the directness expected of any manager.

Owning the contradiction

When leadership itself breaches a stated value — ships through the budget, waives the process for a launch — and everyone noticed, the only repair is to own the contradiction publicly and behave differently at the next costly moment. Anything less converts the value into décor.

At team scope the object is the example in the room: values upheld when costly, credit given, mistakes owned, the brilliant jerk addressed. At organisational scope the manager learns culture's mechanics — behaviour is the culture, it is set by what managers do daily, it changes when the system changes, practices spread by pull — and polices the values between people, backing a new manager against a senior engineer who undermines them. At executive scope culture is the executive's system: the costly moment decided in line with the stated value or the contradiction owned, consequences that reach the powerful, culture change run as a multi-quarter realignment, beloved-but-costly norms evolved with their champions, culture institutionalised so it survives growth, and direction carried by line leaders who visibly believe it. The pattern is in How Judgment Scales; the safety that lets people say when a value has been breached is CC-1 Psychological safety and productive conflict.

• Upholds values precisely when they are costly, and knows the team is watching. team
• Gives credit, owns mistakes, respects boundaries; aligns actions with stated principles. team
• Addresses a values breach by a top performer rather than banking the output. team
• Recognises when they are being asked to shade the truth about status and declines.
• Failure mode — values that evaporate under deadline pressure. team
• Failure mode — saying one thing and rewarding another. team
• Failure mode — assuming you are only modelling when you intend to. team
• Reads culture from behaviour, not posters, and treats a divergence from the stated values as the actual culture. org
• Changes behaviour by changing incentives and friction; does not issue a third mandate for what two did not fix. org
• Spreads a good practice by pull — visible value, easy adoption, champions — not by decree. org
• Addresses a respected senior engineer who subtly undermines a newly promoted manager, directly and privately, as the behaviour it is, while visibly backing the manager. org
• Holds managers to the organisation's values, including the manager who keeps a toxic high performer because the numbers are good. org
• Declines to shade status, ratings or commitments upward, and absorbs the cost of declining rather than passing it down. org
• Failure mode — a third mandate for the thing two mandates did not fix. org
• Failure mode — expecting a values statement to outvote the reward system. org
• Failure mode — leaving a new manager to survive a senior saboteur alone. org
• Decides the costly moment in line with the stated value — obeys the error budget with the launch due — or owns the contradiction publicly and behaves differently next time. exec
• Ensures consequences reach the powerful: a senior leader who breaches a core value faces real, visible ones, and the director who hits every number through fear is acted on for how. exec
• Starts with the mirror: fixes the leadership team's own modelled behaviour first, because the organisation copies the top table. exec
• Runs culture change as a multi-quarter system realignment — credible leaders modelling, incentives and promotions realigned, early wins visible, persistence — with the announcement as the starting gun. exec
• Evolves a beloved-but-costly norm without breaking trust: honours what it did well, involves its champions in the successor, is honest about what changed and why. exec
• Institutionalises culture so it survives growth past a few hundred people: leaders hired and promoted for it, norms taught, systems aligned. exec
• Carries direction through line leaders who visibly believe it; direction that dies two levels down was announced, not communicated. exec
• Exercises ethical judgment where the law, the policy and the pressure do not settle it, and explains the decision. exec
• Failure mode — shipping through the error budget and expecting the poster to survive. exec
• Failure mode — values with a seniority exemption. exec
• Failure mode — culture change by all-hands announcement. exec
• Failure mode — scaling by dilution. exec
• Failure mode — mistaking cascade emails for communication. exec

Results versus methods. The person or the leader who delivers and breaches the values forces the question of what performance is. This standard's answer, as in PL-4 Performance management, is that the methods are part of the result; the pull toward the number is strong, and the examinations test whether the candidate resists it.

Consistency versus context. Values applied identically in every case can produce a bad outcome in the case the rule did not foresee; values applied with judgment can look like values applied selectively. The resolution is to decide on the merits, say why, and own it — the explanation is what distinguishes judgment from exemption.

Change versus trust. Changing an entrenched norm, even a costly one, breaks something people were attached to. Evolving it with its champions, honouring what it did well, and being honest about why is slower than announcing the new norm and is the only version that does not spend trust.

Honesty upward versus safety downward. Declining to shade a report costs the manager with their leadership; passing the pressure to the team to make the report true costs the team. The manager absorbs the cost, and that absorption is the competency.

Rules versus judgment. A request that is legal and wrong, a policy that would produce harm in this case: the rule does not settle it, and the manager's judgment does. The tension is that judgment is harder to defend than compliance, and the resolution is to explain the reasoning as carefully as the decision.

A head of engineering leads an organisation whose stated value, printed on the wall and repeated at every all-hands, is "reliability first". Six weeks ago a major launch coincided with an exhausted error budget on the core service. The rule the organisation had agreed — budget exhausted, stabilise — said the launch should wait. The chief executive wanted the date, the head of engineering agreed to ship, the launch went out, and a week later the core service had its worst incident of the year. Everyone in the organisation noticed the sequence. In the weeks since, two teams have quietly stopped tracking their error budgets, and a principal engineer has said in a skip-level that "reliability first" is now a joke.

The cultural significance is total. The organisation did not learn that the launch was important; it learned the real value, which is that the budget is obeyed unless a launch is due. Two easy responses present themselves: say nothing and let the incident fade, or re-communicate the value with a new policy and firmer language. The first confirms the lesson; the second is the third mandate for what the organisation just watched leadership break, and it will be read as exactly that.

The only repair is to own the contradiction publicly and behave differently at the next costly moment. The head of engineering does both. At the next all-hands they say what happened in plain terms: the organisation had a rule, leadership broke it for a launch, the incident followed, and the two teams that stopped tracking their budgets drew the correct conclusion from what they saw. They say that the contradiction was theirs — the head of engineering agreed to ship — and that the value is worth nothing unless it holds when it is expensive. They do not explain the launch's importance, because the organisation already understood it and it is not the point.

Then the behaviour. The head of engineering re-establishes the budget rule with one change: a decision to ship through an exhausted budget can only be made at the executive table, in writing, with the reason and the accepted risk recorded and published to the organisation. The rule is applied at the next opportunity, four weeks later, when a second launch meets a red budget on a different service and the head of engineering holds it, at a visible cost to a customer commitment, and says so. The chief executive is told in advance why, and the reasoning is given in the organisation's terms and the business's: the value only exists if it costs something, and the last time it was waived the organisation paid more.

The two teams resume tracking their budgets without being asked. The principal engineer says nothing, which is its own signal. What the head of engineering does not do is issue a reminder about the value, which would have been the cheapest response and the one that would have finished it off.

• PL-4 Performance management — the brilliant jerk and the leader who delivers through fear as performance problems.
• CC-1 Psychological safety and productive conflict — the safety that lets people say a value has been breached, and trust as a behavioural account.
• DE-3 Reliability, incident response, and operational ownership — the error budget as the mechanism, and the review after the failure.
• DE-2 Estimation, planning, and honest commitments — declining to give a false forecast under pressure.
• SV-6 Organisational design and leading change — leading change through structure; evolving norms with their champions.

1. Why do teams believe actions over stated values?
   Answer

   Because culture is the accumulated pattern of what is actually rewarded, tolerated and punished, and the costly moment reveals it. A value that survives only when it is free tells people nothing; what a leader does when it is expensive is what they learn and copy.
2. What does tolerating a brilliant jerk teach a team?
   Answer

   That results buy exemption from the values. Every week of tolerance publishes the real culture more loudly than any statement, and the fix is feedback, an expectation, a date and consequences within the month.
3. You are asked to report a slipping project as on track. What do you do, and who carries the cost?
   Answer

   Decline, plainly, with the honest picture and options. The manager carries the cost of declining rather than passing the pressure to the team to make the report true.
4. Two documentation mandates failed. What does the third attempt have to change, and why? org
   Answer

   The system, not the mandate: documentation becomes the easiest path to something people already want — onboarding, review, incident response — writing it is visibly valued, and the friction of maintaining it drops. Behaviour changes when the system changes; a third mandate for what two did not fix will fail the same way.
5. A respected senior engineer is subtly undermining a newly promoted manager. What is the response? org
   Answer

   Address the engineer directly and privately, naming the behaviour as what it is, while visibly backing the manager. Letting it slide teaches the department that authority is negotiable for anyone with tenure.
6. Leadership shipped through the error budget and everyone noticed. What did the organisation just learn, and what is the only repair? exec
   Answer

   The real value: the budget is obeyed unless a launch is due. The only repair is to own the contradiction publicly and behave differently at the next costly moment; a reminder or a new policy converts the value into décor.
7. A director hits every number and leaves a trail of burned-out people and fear. Why must the executive act, and on what? exec
   Answer

   On how the results are achieved, because every quarter of tolerance publishes the organisation's real values, and a value enforced only below a certain level is pricing, not a value. Consequences must reach the powerful.
8. How does culture survive growth past a few hundred people? exec
   Answer

   By being deliberately institutionalised — leaders hired and promoted for it, norms taught, systems aligned — because at that size the founders' gravity no longer reaches everyone, and dilution is a leadership responsibility to manage rather than weather to endure.

• Edgar H. Schein, Organizational Culture and Leadership (1985) — artifacts, espoused values and underlying assumptions.
• Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy (editors), Site Reliability Engineering: How Google Runs Production Systems (2016) — error budgets as a pre-agreed rule, and what obeying them costs.
• John P. Kotter, Leading Change (1996) — the steps of change, and the ones most often skipped.