Agility at Scale: Alignment, Autonomy and Two Mindsets

Daniel Terhorst-North and Anna Urbaniak discuss coordination and learning in large organizations.

DTDaniel Terhorst-North연사AUAnna Urbaniak연사
채널
GOTO Conferences
게시일
2022년 3월 2일
영상
51:15
읽기
2분
원문
영어
YouTube에서 열기
스크롤하면 영상이 오른쪽 아래로 작아져 계속 재생됩니다. 자막은 읽기 언어를 따릅니다.
읽기 언어2개 언어로 읽을 수 있음
이 글은 아직 한국어 번역이 없어 영어 원문으로 표시합니다.
요약

30초 요약

The speakers contrast digital-product and industrial mindsets, then propose alignment and six conditions for team autonomy. They suggest identifying the most limiting organizational constraints first.

  1. 1Two mindsetsThe speakers contrast discovery with predictable execution.
  2. 2Product practicesCross-functional work and direct customer contact support learning.
  3. 3SynthesisLarge organizations need coordination as well as adaptation.
  4. 4AlignmentShared direction provides context for local decisions.
  5. 5AutonomyAutonomy needs goals, constraints, accountability, capability, resources and authority.
  6. 6LiquidityTeams can assess how easily missing conditions can be obtained.
  7. 7Start with constraintsIdentify the most limiting obstacle first.

핵심 정리

  1. The speakers contrast discovery with predictable execution.
  2. Cross-functional work and direct customer contact support learning.
  3. Large organizations need coordination as well as adaptation.
  4. Shared direction provides context for local decisions.
  5. Autonomy needs goals, constraints, accountability, capability, resources and authority.
  6. Teams can assess how easily missing conditions can be obtained.
  7. Identify the most limiting obstacle first.
전문

챕터별로 다듬은 전문 읽기

원본 자막만 보기
01

Two mindsets

Digital products and industrial execution.

At GOTO Copenhagen 2021, Daniel Terhorst-North and Anna Urbaniak discuss organizational agility at scale. They present a synthesis of digital-product and industrial approaches based on their experience; their framework is a model for discussion, not a proven universal formula.

They contrast a digital-product mindset, which emphasizes uncertainty, customer outcomes and experimentation, with an industrial mindset that values specialization, predictable output and controlled variation. Their characters are deliberately simplified examples.

The digital-product discussion includes making decisions where information is available, building cross-functional teams, talking directly to customers and improving the wider system of work.

The speakers argue that established governance and specialist practices have reasons to exist, even when they appear to impede delivery. Rather than remove a rule blindly, investigate the purpose it serves and adapt it to the context.

02

A synthesis

Why scale needs both coordination and discovery.

Their central argument is that large organizations need both mindsets: discovery and adaptation where uncertainty is high, and coordination and reliable execution where dependencies and constraints matter.

03

Alignment and autonomy

Conditions for teams to act effectively.

The second half introduces alignment: teams need shared direction and understanding across product, technology, delivery and ways of working. Alignment gives local decisions a common context.

They describe six conditions for effective autonomy: objective, constraints, accountability, capability, resources and authority. A team given a goal without the information, skills or permission to act may not be meaningfully autonomous.

Terhorst-North extends the idea of liquidity to these conditions: how easily can a team obtain missing resources, skills or authority? Depending on the constraint, it might acquire, borrow, develop or work around what it lacks.

The presenters argue that alignment without autonomy can become controlling, while autonomy without shared direction can produce conflicting decisions. These are conceptual risks, not automatic outcomes in every organization.

04

Getting started

Identify the most limiting constraints.

They suggest asking teams whether strategy, tools, experience and decision rights are clear, then identifying the most limiting obstacles rather than attempting to fix everything at once.

Their conclusion is that organizational agility comes from aligning direction and enabling teams to act within it, using both coordination and experimentation as needed.

같은 채널의 다른 글

슬라이드 3장39:12EN
GOTO Conferences· 2026년 10월 28일Cate Huston: How Rigour Supports AI-Assisted Development VelocityCate Huston · TwillA two-person team’s experience with release gates, automated checks, prioritization and the cost of shipping faster.AI 엔지니어링 리더십Software engineeringAI agents
슬라이드 4장22:33EN
GOTO Conferences· 2026년 10월 26일William Schor: From Unit Tests to Synthetic Canaries at NetflixWilliam Schor · NetflixHow generated workloads and production-like infrastructure help test a distributed key-value service.Software engineering
슬라이드 5장34:11EN
GOTO Conferences· 2026년 10월 23일Anatoliy Bilenko and Alberto Carretero: Making Database Protocols Reliable with Formal Methods and AIAnatoliy Bilenko, Alberto Carretero · CanonicalCanonical’s database engineers connect executable specifications, model-based tests, failure exploration, and reconstructed execution histories—and explain why none of these techniques proves a real system correct on its own.개발 워크플로와 테스트Code review & verification관측 가능성과 안정성+2
28:15EN
GOTO Conferences· 2026년 10월 22일Steve Poole on Open-Source Security and AI’s Maintenance ChallengeOlimpiu Pop, Steve PooleWhy faster vulnerability discovery increases pressure on maintainers, dependency users and upgrade processes.Software engineeringAI security
슬라이드 5장46:36EN
GOTO Conferences· 2026년 10월 21일Don Syme: Building Agentic Automation Around Human CollaborationDon Syme · GitHubContinuous AI, repository workflows and the guardrails needed for unattended software maintenance.Agent orchestrationSoftware engineering코딩 에이전트
28:23EN
GOTO Conferences· 2026년 10월 19일Learning Ash: Declarative Elixir Apps, Testing and ExtensibilityChristian Alexander, Rebecca Le, Zach DanielRebecca Le and Zach Daniel explain how their book and the framework evolved together.Software engineering