LEGO Agility Workshop
A building-brick simulation for large organizations: participants turn strategy into OKRs, map value streams, build backlogs, plan dependencies and deliver visible increments in short Inspect & Adapt cycles.
Intro Material
The page is based on the uploaded Enterprise Agility Simulation Workshop master deck. It keeps the building-brick simulation as the learning engine and translates the former company-specific context into a reusable enterprise workshop architecture.
The uploaded master deck reconstructs the Digital-Hangar building-brick simulation, generalizes it for large enterprises and adds roles, artifacts, timings, debrief questions, variants and facilitator hints.
A physical city model turns abstract agile principles into visible value flow: OKRs, backlogs, dependencies, PI Planning, increments and Inspect & Adapt.
The city model exposes products, platforms, citizens, goals, constraints and cross-team dependencies.
Vision, OKRs, guardrails, hypotheses and backlogs become one visible chain.
Teams plan, build, review, reflect and adapt instead of only hearing about agile theory.
Format options
The Master Blueprint recommends choosing the depth by audience, learning goal and available time. The same structure can be used for onboarding, leadership alignment, LACE work, product/portfolio groups or train-the-trainer formats.
Good for onboarding and agile foundations.
Better for deeper debriefs, customer-specific conflict sets and transfer canvas.
Fewer build cycles, stronger focus on trade-offs, guardrails and decision rights.
Includes setup, facilitation practice, variants and troubleshooting.
Material system
The simulation is strongest when materials are sorted, roles are clear and every artifact has a purpose. Otherwise the workshop becomes a craft exercise instead of an organizational lab.
Standard bricks, base plates, vehicles, figures and special parts — or paper/cardboard fallback.
Vision / OKR Board, Team OKR Board, Backlog Board, PI Board, Retro Board.
OKR, Benefit Hypothesis, Backlog Item, Dependency, Risk, Review, ROTI and Transfer Action Plan.
Timer, role cards, color-coded post-its, markers, tape, dot voting and a clear signal for timeboxes.
Module 00
Prepare the scenario, target group, trade-offs, materials and facilitation setup so the workshop becomes more than a building game.
Use Enterprise City as the default, or adapt the story to a bank platform, mobility ecosystem, factory, clinic, energy grid or retail journey.
Prepare three to five objectives with realistic tension: growth vs. stability, speed vs. compliance, standardization vs. autonomy.
Sort bricks, boards, role cards, post-its, timers, dependency cards and templates so the simulation starts smoothly.
Module 01
Participants enter a city that already works, but is incomplete. The model reveals products, infrastructure, citizens, constraints and stakeholder pressure.
Show the starting landscape, existing buildings, paths, empty areas and bottlenecks. Make clear that this is the start state, not the target picture.
Introduce Sponsor / Mayor, Customer Voice, Product Owners, Scrum Masters, Teams, CoP Guardrail Owners and Facilitators.
Ask what already exists, who benefits, what infrastructure is shared and which assumptions feel unclear or familiar from the real enterprise.
Module 02
The Sponsor sets a future city vision, enterprise OKRs and guardrails. Teams learn that autonomy needs direction and clear boundaries.
Use a short, memorable target picture such as a safe, joyful and sustainable city where residents, visitors and businesses receive value.
Separate objectives from measures. Show how city-level OKRs become a bridge between strategy and team work.
Add rules for scale, stability, safety, UX, sustainability or compliance. Guardrails should be testable and create real trade-offs.
Module 03
Participants identify product areas, platform work, value streams and team boundaries. The city map becomes a visible model of value flow.
Map areas such as Housing, Transport, Public Facilities, Business, Leisure or customer-specific domains like payments, cloud, clinical workflow or service.
Assign Product Owner, Scrum Master and Team Members. Make overlaps, gaps and hidden handoffs visible.
Identify roads, bridges, transport, DevOps, security, data or infrastructure work that multiple teams depend on.
Module 04
Teams write their own OKRs and align them with the city goals. This is the first real coordination test: missing contributions, conflicts and dependencies become visible.
Teams formulate objectives and key results with measurable value, stakeholder effect and guardrail evidence.
Map team OKRs to enterprise OKRs. Use lines for contribution, dependency, duplication, conflict and missing support.
Sponsor and Customer Voice ask which goals are under-supported. CoPs check whether quality, scale, safety or standardization are at risk.
Module 05
Teams derive backlogs from OKRs, write benefit hypotheses, mark risks and negotiate dependencies before everything turns into build chaos.
Use the pattern: we believe that this intervention benefits these users because this need changes, and we measure progress through this KR.
Prioritize by objective contribution, dependency, risk and learning value. Do not let teams plan everything at once.
Use dependency, risk and blocker cards early. Dependencies are the didactic gold of the workshop.
Module 06
The PI board translates team backlogs into iteration logic. Participants see sequence, capacity, dependencies, risks and the purpose of an IP iteration.
Use team rows, iteration columns, feature cards, enabler cards, dependency lines, risk cards and an intentionally protected IP iteration.
Ask which KRs move through this plan, which enterprise OKRs are still under-supported and whether output has replaced outcome.
Review whether the plan is realistic, goal-oriented and synchronized enough for teams to start building.
Module 07
Teams build the city in short PDCA cycles. Reviews, retrospectives, IP iteration and ROTI turn the physical result into enterprise learning.
Each team pulls items, builds a visible increment, reviews it and changes its working agreement before the next iteration.
Create space for innovation, learning, system improvement and preparation instead of filling all capacity with planned work.
Reflect on flow, dependencies, local optimization, guardrails, decision rights and what the real organization should change next.
Transfer
The real product is a shared mental model of agile work in a complex enterprise: how goals, value streams, platforms, backlogs, dependencies, planning, learning and decision rights work together under uncertainty.
Dynamic Agility
Use the LEGO Agility Workshop for onboarding, leadership alignment, agile foundations, train-the-trainer formats or as a playful but serious introduction to value flow and coordination.
LEGO Agility Workshop anfragen