DORA Community Discussion - Operationalizing DORA within a large organization

DORA (speaker: Julia Jakubiec, ABN AMRO; host: Nathan Harvey) · video · 2026-06-26 source ↗ Reader 🖥️

practical · recorded community talk with host framing and Q&A (DORA Community Discussion) — A first-person practitioner change-story delivered as an informal talk. Propositions are largely prescriptive tips-and-tricks organized on Kotter's 8-step change framework; the ABN AMRO rollout is the grounding narrative. Auto-captions render the speaker's surname as 'Yukobitz'; the correct name is Julia Jakubiec.

Structure

Key terms

• Operationalize DORA / DORA
  Not the four software-delivery metrics driving behavior. In this talk DORA functions as (a) an adapted internal survey instrument reusing DORA's publicly available questions and methodology, (b) a recognized brand/authority ('Google, doing this since 2014') used to manufacture urgency and end semantic debates, and (c) a benchmarking frame (low/medium/high/elite) against competitors.
• Continuous improvement mindset
  The real, hard-to-change target of the whole program — a cultural disposition to 'get better at getting better', explicitly not any single number (responses, logged improvements). The metric counts are catalysts, not the goal.
• DevOps Center of Expertise (CoE)
  A small (5-person) central change-management-and-consultancy team inside IT strategy and transformation whose job is to drive org-wide improvement — a change agent, not a platform or tooling team.
• Kotter's 8-step change management
  The organizing scaffold for the entire rollout (urgency → coalition → vision → communicate → empower/remove barriers → quick wins → build on change → make it stick), with the last two singled out as where organizations usually fail.
• FOMO / sense of urgency
  Deliberately manufactured urgency ('everyone else is already doing it — are we late?') built on DORA's brand and competitive benchmarking, explicitly not a real crisis.
• Make it stick / anchoring
  Embedding the practice into the organization's formal control systems — company OKRs, CIO/CISO key priorities, topic-owners consuming department-level results, and 'the way we work' (business as usual) — so it persists; framed as the step organizations most often fail.
• AI is an amplifier, not a savior
  A repeated one-line vision from the year's GenAI report: AI compounds an existing strong foundation and, absent one, increases chaos instead of performance.

Propositions

• explicitOperationalizing DORA in a large organization is fundamentally a change-management problem, not a metrics problem; the ultimate goal is to create a continuous-improvement mindset, and the answer the team reached to 'can we do this?' was 'yes, we can.'conf: high
• explicitBeing in a highly regulated industry is not a valid excuse to move slowly on continuous improvement: regulations must be followed, but DORA can still drive and inform continuous-improvement practice even in a regulated bank.conf: high
• implicitDORA is not used here as the four delivery metrics driving behavior; it functions as an adapted survey instrument (reusing DORA's public questions and methodology), a recognized brand/authority, and a benchmarking frame — the report is a catalyst and vehicle, not the mechanism of change.conf: high
• explicitThe DORA/Google brand (an industry-recognized standard, researched since 2014) is deliberately leveraged as borrowed authority to end 'potato discussions' (semantic debates) and to manufacture a fear-of-missing-out sense of urgency rather than relying on a real crisis.conf: high
• explicitcorroboratedDriving org-wide change (12,000 people) with a 5-person team is only possible by strategically building a coalition that talks for you at every level — an executive sponsor (a new CIO who arrived from a rival bank), ~40 DevOps coaches (1–2 per department), and a cross-role advocates group — planned via a power/interest stakeholder matrix.conf: high
  supportsGetting Buy-In for Your Next Big Idea · p14 — Socializing with stakeholder groups and using the advocates group to validate questions/dates before publishing mirrors 'socializing the idea with stakeholders before the formal pitch so they have authorship.'
  supports ←Model the Transformation You Expect Employees to Deliver · p3 — This article's Prosci statistic (executive sponsorship the single biggest contributor to change success since 1998) corroborates, at benchmarking-research scale, the DORA case's concrete finding that a 12,000-person change effort depended critically on securing an effective executive sponsor (a new CIO) as part of its coalition.
• explicitA change vision must be radically simplified and made personal and memorable — 'get better at getting better' instead of 'continuous improvement mindset', 'AI is an amplifier, not a savior' — and then repeated relentlessly across every channel ('like a parrot').conf: high
  supportsGetting Buy-In for Your Next Big Idea · p5 — 'Repeat like a parrot' across every channel, and running the survey over a deliberately long window to keep marketing, operationalizes 'issue selling is a campaign, not a meeting.'
• explicitPeople do not resist change; they resist the effort it requires (or fear they don't know enough) — so adoption is driven by removing friction: a single no-click info page, ready-made forwardable emails, a 2–3 minute promo video, a 15-minute audio recap of the report, and department data files plus slide templates for the coaches.conf: high
  supportsGetting Buy-In for Your Next Big Idea · p4 — 'People resist the effort, not the change' plus the friction-removal tactics (one-page info, ready-made emails, recaps, templates) are a concrete instance of 'decreasing restraining forces is a better change strategy than increasing pushing forces.'
• explicitProgress must be made visible and a little addictive, like a game — a running response tally over a deliberately extended 3-week window and celebratory quick wins (a €20 cake for the department with the most responses) — because surveys are boring and fun sustains participation.conf: high
  supportsGetting Buy-In for Your Next Big Idea · p10 — The cake quick-win and public running tallies are a worked example of 'small wins create momentum and attract allies.'
• explicitSurvey anonymity (with a 30+ response threshold per department to prevent re-identification) combined with visibly acting on the results — 'it's not just a nice report laying somewhere hidden, it's really actioned upon' — is what earns developer trust and participation, answering the recurring 'senior management never listens to me' complaint.conf: high
• explicitThe two steps where change programs usually fail are the last two — building on the change and making it stick; sustaining requires keeping the exact same annual cadence, keeping your promises, and publicly tracking critique and questions.conf: high
• explicitChange becomes durable only when it is structurally anchored: the findings become CIO/CISO key priorities, metrics enter company OKRs, topic-owners consume department-level results to prioritize rollouts, and the practice becomes 'the way we work' (business as usual) — reinforced by culture work such as internal podcasts.conf: high
  refinesGetting Buy-In for Your Next Big Idea · p20 — Julia uses individual advocacy practice heavily (steps 1-7) but argues durability comes from STRUCTURAL anchoring (OKRs, CIO priorities, topic-owners, business-as-usual), refining the implicit claim that ideas survive primarily through individual practice rather than structural conditions. Lowest-confidence relation: the target is an inferred implicit premise about the HBR piece.
• explicitestablishedAI is an amplifier, not a savior: without a strong foundation, AI increases chaos instead of performance.conf: high
  supports11) AI-spesial med Vilde Opsal og Anders Sveen · p5 — 'AI is an amplifier, not a savior — without a strong foundation AI increases chaos' is the same amplification thesis as 'AI is a force multiplier in both directions: strong teams get better, weak teams get worse faster.'
  supports ←AI-Assisted Software Development: Team Profiles and Capabilities for Putting Research into Action · p1 — Same DORA/Harvey 'amplifier, not savior' thesis, here applied in an enterprise DORA-rollout case study rather than the primary research write-up.
  supports ←Ordinary Engineers, Not Heroic Inventors · p16 — Skill infrastructure and incentive design are the 'strong foundation' without which AI amplifies chaos instead of performance.
• explicitSales and marketing skills — packaging, selling, and controlling the narrative — are the transferable core competency for driving organizational transformation.conf: medium
• explicitOrganizational change is slow and cannot be rushed — 'it takes more than a minute to change an organization' — the ABN AMRO journey started around 2019 and its success metrics only became demonstrable by 2025.conf: high
  supports17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis · p1 — The multi-year timeline (2019→2025) and 'it takes more than a minute to change an organization' instantiate the claim that large organizational transformations follow an S-curve made of many simultaneous smaller S-curves and cannot be shortcut.

Arguments

Narratives

• The ABN AMRO State-of-DevOps rollout: an official DevOps transformation started around 2019; two individuals built a proof-of-concept survey reusing DORA's public questions and got 960 responses with no marketing; in 2023 Julia joined the DevOps CoE and made it an official platform (with a Formula 1 theme); by 2025 it had been IT report of the year four consecutive years, ~4,000 reads, ~800 demo/workshop attendees, and ~5,000 logged improvements across 22 departments.
  → The central proof-of-concept-to-institutionalized-practice arc that grounds every prescriptive claim in the talk.
• The cake quick-win: every year the department with the most survey responses is promised a €20 cake; it became an addictive chase, with teams theorizing about 'foul play', and 'will there be a cake?' becoming the single most-asked question.
  → Concrete illustration of a gamified quick win that sustains participation by making a boring survey fun.
• The lucky executive sponsor: while the team was mapping stakeholders, a new CIO arrived from rival bank ING, was already a DORA fan with a developer background, and readily agreed to sponsor; his quote and photo were then reused in every talk to hit both senior-management and developer audiences at once.
  → Illustrates opportunistic coalition-building and the value of an executive sponsor who bridges organizational levels.
• The internal podcast series: six episodes were produced to keep the change alive culturally, including a change-approval-process episode with developers who feel the pain, paired with a follow-up episode where a CIO and a senior division leader respond to that discussion.
  → Illustrates 'make it stick' through ongoing, engaging culture work rather than one-off communication.

Questions addressed

• ✅ Can a highly regulated bank use DORA to drive continuous improvement despite regulatory caution?
  Yes — regulations are followed (they remain a very regulated organization), but DORA still drives improvement; the team's answer was 'yes we can', demonstrated by ABN AMRO's rollout.
• ✅ How do you drive org-wide change across 12,000 people with only a 5-person team?
  Build a multi-level coalition that talks for you (executive sponsor, ~40 DevOps coaches, a cross-role advocates group) planned via a power/interest matrix, and remove friction with reusable low-effort tooling (one-page info, ready-made emails, recaps, templates).
• ✅ Why do change programs usually fail, and how do you make change stick?
  They fail at the last two Kotter steps (build on the change / make it stick); you make it stick by keeping the same cadence and structurally anchoring the practice in OKRs, executive priorities, and business-as-usual.
• ✅ Does the change come from the metrics themselves?
  No — explicitly 'it's not about the numbers... it's about having the mindset'; the report is a catalyst, and the change comes from the surrounding change program.

Gaps

• incompleteA single-organization, self-reported success narrated by the practitioner who leads it — survivorship/selection bias with no comparison organization and no counterfactual. 'Success' is measured largely by report readership and engagement (~4,000 reads, ~5,000 self-logged improvements) rather than by independently verified software-delivery performance or business outcomes.
  Read next: DORA/Accelerate outcome studies linking practices to delivery and organizational performance; controlled or multi-organization evidence on change-adoption results.
• incompleteKotter's 8-step model is itself contested and weakly evidenced empirically, yet the talk adopts it as a given scaffold without engaging critiques or comparing alternatives (Lewin, ADKAR, Fearless Change patterns).
  Read next: Critical change-management literature on Kotter's model; Fearless Change (Manns & Rising) and other pattern-based or evidence-based change frameworks.
• incompleteGeneralizability is unaddressed: the approach leans on advantages that may not transfer — a well-resourced, highly visible central CoE; a bridging executive sponsor who arrived by luck; and the borrowed authority of the DORA/Google brand. It is unclear how much of the playbook works in organizations lacking these.
  Read next: Change adoption in low-resource, low-visibility, or low-authority settings; how much of the outcome is attributable to the method versus the enabling conditions.
• incompleteThin evidence for the durability claim itself. 'Make it stick' is asserted (OKRs, report-of-the-year four years running) but four years of sustained report engagement is not the same as a proven, self-sustaining continuous-improvement culture that would persist if the driving team were removed.
  Read next: Longitudinal studies of change persistence after a champion or program team departs; measures of institutionalization beyond engagement metrics.

Closes gaps elsewhere

• Jacob Langvad Nilsson's Post · g5 — That extract's gap is the absence of any discussion of the cost, time investment, and organizational change management required to roll a structured practice across a team. This talk supplies exactly that: a concrete, staged change-management playbook (Kotter's 8 steps) for institutionalizing a measurement/improvement practice across a 12,000-person organization, including the multi-year time investment and the small-team (5-person) effort model.

Related documents

• 11) AI-spesial med Vilde Opsal og Anders Sveen
• Getting Buy-In for Your Next Big Idea
• 2024_final_dora_report
  AI as Amplifier DORA & Engineering Metrics Golden Path
• When Persuasion Is (and Isn't) Manipulation
  AI as Amplifier Managing Up & Influence Trust
• Your AI agent just blamed the network team. Now what?
  Change Management & Adoption Trust
• Nils Brede Moe's Post
  Learning Culture & Slack Technology Diffusion & Transformation Curves
• AI coding creates two kinds of debt. You're only measuring one
  DORA & Engineering Metrics Learning Culture & Slack
• AI Enthusiasts Are in a Race Against Time, AI Skeptics Are in a Race Against Entropy
  AI as Amplifier Trust
• The "funhouse mirror": How AI reflects the hidden truths of your software pipeline
  AI as Amplifier DORA & Engineering Metrics
• Achieving Compliance as a Platform Engineering Team by Helping Developers
  Golden Path Trust