The LEGO® SERIOUS PLAY® Methodology and the Art of Thinking in Systems
There's a scene in the TV show Succession where the Roy family convenes to plan the future of their media empire. The table is expensive. The consultants are expensive. Everyone in the room is smart, experienced, and deeply invested in the outcome. And yet the meeting produces nothing. Every person walked in with a private agenda, a rehearsed position, and no real intention of updating either. The conversation was sophisticated, but the planning was theater.
Most organizational planning conversations look a lot like that. Not because the people in the room aren't capable, but because the format of the conversation isn't designed for the kind of thinking that strategic planning actually requires. Verbal, sequential, and usually dominated by whoever holds the floor, the standard planning meeting is built for information transfer and position-taking. It's not built for collective sense-making, systems thinking, or the kind of shared understanding that turns a plan into something an organization can actually execute.
That's the problem LEGO® SERIOUS PLAY® methodology is solving. Not the fun problem. Not the creativity problem. The representational problem: the gap between what a leadership team thinks it knows collectively and what it can actually see, name, and work with together.
When the Format Is the Constraint
Here's something worth sitting with when a planning process stalls: the problem might not be the strategy. It might be the medium. Consider the default formats organizations use for their most consequential conversations. PowerPoint decks built before the meeting begins, presenting a pre-formed conclusion. Whiteboard diagrams that capture only what the person holding the marker could articulate fast enough. Round-table discussions where depth of insight is often inversely correlated with willingness to speak. These aren't neutral tools. They carry structural biases that shape which ideas surface, whose thinking gets centered, and how complexity gets quietly flattened in the name of a clean slide.
Cognitive scientists Zhang and Norman (1994) made a point that doesn't get nearly enough airtime in organizational life: human thinking is partially offloaded to external representations. We don't just think and then record our thinking. We think through the objects, diagrams, and formats we use. Change the representation, change the thinking that's available.
This means that if your planning conversations keep producing the same results, the same priorities, the same unresolved tensions surfacing six months later, it's worth asking whether the format itself is the constraint, rather than the people.
What Gets Built Is What Gets Seen
LEGO® SERIOUS PLAY® is a facilitation methodology built on a deceptively simple premise: when people construct a physical, three-dimensional model of something abstract, their team, their strategy, the forces shaping their organization, they access thinking that verbal conversation doesn't reach.
This isn't a metaphor for creativity. There's a well-established body of work on the relationship between the hands and the mind. Neurologist Frank Wilson (1998) documented how hand-based activity activates cognitive processes that language-based exchange often bypasses. Seymour Papert, who developed constructionist learning theory with Idit Harel, argued that knowledge isn't transmitted. It's built. Literally. People think most effectively when they're constructing shareable artifacts, not receiving information passively.
The LSP methodology operationalizes this concept through structured builds, with boundaries and rules to govern how to engage. Participants build physical models in response to structured prompts. They explain what they've built. Every model gets voiced, every voice gets heard. The protocol makes that non-negotiable, which matters enormously in rooms where hierarchy usually determines airtime.
Think of famous corkboard scenes in your favorite psychological crime show, where the detectives pin evidence to a wall and physically maps connections between people, events, and patterns no one could hold in their head simultaneously. The board doesn't solve the case. But it makes the case solvable by externalizing complexity into a shared object the whole team can see, point to, argue about, and revise. A well-facilitated LSP-grounded session does the same thing for a leadership team trying to see its own organization clearly.
The built model isn't a metaphor about the organization. In the logic of the methodology, it is the organization, at least enough of it to work with. That shift changes the emotional register of the conversation in ways that matter. You're not defending your position anymore. You're examining a model. That's a genuinely different conversation.
The Landscape Is the System
Here's where the LSP methodology moves from an interesting facilitation technique to an actual planning tool: the landscape build. After individuals construct and explain their own models, the methodology moves into a collective phase. Participants connect their individual builds into a shared landscape, a three-dimensional representation of the system they're all operating within. They build connections, name tensions, identify interdependencies, and begin to see the whole in a way that no individual mental model fully captures.
This is systems thinking made tangible. And that matters because systems thinking is genuinely hard to do in the abstract. Most organizational plans are linear: here's where we are, here's where we want to go, here are the steps. That structure isn't wrong. It's just incomplete. It treats the organization like a machine with predictable input-output relationships, when most organizations are better understood as living systems full of feedback loops, unintended consequences, and structural dynamics that operate well below the level of formal strategy. Donella Meadows (2008), whose work on systems thinking remains essential reading, argued that the most powerful leverage points in a system are rarely where you're looking. They're embedded in the relationships, the feedback loops, the places where small changes produce large effects. You can't find those leverage points in a slide deck. You can't find them in a verbal discussion where everyone is narrating their own piece of the system without anyone seeing the whole picture.
The landscape build creates conditions for seeing that whole. When a leadership team places their individual models into a shared space and begins connecting them, things become visible that weren't before. The functions that are overloaded. The relationships that are load-bearing. Where the informal systems diverge from the formal ones. What everyone assumed was aligned but actually isn't. Peter Senge (1990) wrote about mental models as a primary source of organizational inertia, the deeply held internal pictures about how the world works that shape what leaders see and what they do. The problem isn't that people have mental models. It's that those models are invisible, unexamined, and often quietly in conflict with each other in ways that never surface in a formal planning conversation. The landscape build is one of the most practical tools available for making those models visible, in the room, with the people who need to see them.
What This Is Not
A fair objection, worth naming: the LSP methodology can sound like a creativity exercise dressed up in academic language. If that's where you are, the skepticism is reasonable. The LSP methodology can absolutely be misused as an expensive icebreaker that produces interesting artifacts and no follow-through.
The methodology is only as good as the facilitation. A poorly designed session generates novelty without insight. A well-designed one changes what a team can see, and that is the precondition for changing what a team can do.
LSP-grounded work doesn't produce financial models or implementation plans. It creates the conditions under which rigorous analysis becomes possible by clearing the representational fog that sits between where a team is and what a planning process requires of them.
It's most valuable at specific moments: when an organization is navigating genuine strategic uncertainty, when a redesign effort keeps stalling because informal systems are working against formal ones, when a leadership team keeps having the same conversation and reaching the same impasse. In those moments, the question isn't whether the strategy is right. It's whether the team can actually see the system they're trying to change. The Roys, for what it's worth, could have used it.
The Question Worth Sitting With
If your last planning retreat produced a document your organization has mostly moved on from, the instinct is to question the strategy. Better analysis. Clearer priorities. A more rigorous process next time.
But what if the document isn't the problem? What if the conversation that produced it didn't surface what your organization collectively knows, sees, and is worried about? What if the format made certain things unsayable, and those things are now running quietly in the background, shaping outcomes that don't match the plan?
That's not a strategy problem. That's a representational problem.
At transform.forward, we think carefully about how the design of a planning conversation shapes what becomes possible inside it. If your organization is navigating real complexity and you want a planning process built to match it, we'd love to talk.
