DiscoverVerbonden
Verbonden
Claim Ownership

Verbonden

Author: Elise Luyckx

Subscribed: 0Played: 2
Share

Description

The podcast about Enterprise Architecture where we combine insights from experienced professionals with valuable real-world examples from architecture.
Why? I believe we are not asking the right questions and I'm sharing this proces to progress together. This way, it becomes less

De podcast over Enterprise Architectuur waarin we inzichten van ervaren professionals combineren met waardevolle praktijkvoorbeelden uit de architecturale wereld.
Waarom? Ik geloof dat we niet de juiste vragen stellen en deel mijn proces om samen vooruit te gaan. Zo wordt het minder mythisch en meer concreet.
47 Episodes
Reverse
Why do IT departments and business strategies often drift apart? In the conclusion of this special "reverse" episode, Elise Luyckx (interviewed by Edzo Botjes) argues that organizations are networks of people—"dots on a map"—that must move together. Elise explains her shift toward Enterprise Design and why she now focuses on facilitation to bridge the gap between C-level strategy and technical execution.What you will learn:* The "Dots on a Map" metaphor for organizational connection.* Why the "service provider" mindset is dangerous for IT.* How workshops and Lego Serious Play create safe spaces for strategic change.
The Personal Journey

The Personal Journey

2026-05-2625:19

What happens when an architect stops looking at blueprints and starts asking blunt questions? In this special episode of Verwerking, host Elise Luyckx becomes the guest. Interviewed by Edzo Botjes, Elise reflects on her transition from the City of Antwerp to independent consulting. She shares the honest story behind starting "Verbonden"—a podcast born not from expertise, but from a desire to learn and a need to overcome shyness.What you will learn:* Why a podcast is the ultimate networking tool for "shy" architects.* The reality of moving from a stable government role to the "heavy" world of consulting.* Why frameworks and certifications often leave a gap in our practical knowledge.Welcome to Verwerking, the podcast where we make deep architecture human and concrete. My name is Elise Luyckx, and today, I share my own "Why."
Can an organization function perfectly without any chaos? According to veteran CIO and architect Bard Papegaaij, the answer is a hard "no". In this first part, we explore why the desire for order is the architect's greatest pitfall. Bard shares his journey from semantics to the boardroom and explains why "fixing" a problem often just moves it deeper into the system. We discuss the "Nokia lesson" of efficiency versus effectiveness and why the most powerful tool an architect has is not a diagram, but a conversation. Welcome to Verwerking, the podcast where we make complex architecture human. My name is Elise Luyckx, and today we learn to stop fixing and start understanding.
Three Layers of Change

Three Layers of Change

2026-05-0526:28

How do you scale collaboration beyond the "tribe"? In this final part with Bard Papegaaij, we move from the individual to the organizational culture. We discuss why teams are almost never "built" for performance, but only for technical skills. Bard shares the secret of "World-Class" sports teams and how to avoid the "Us vs. Them" games that kill transformation. We explore why there are no "wrong" cultures—only cultures that produce things you don't want. Welcome back to Verwerking. My name is Elise Luyckx, and today we learn to design for humans, not for boxes on a chart.
How do you merge two complex organizations without losing the human element? In the conclusion of our talk with MichaëlKusters, we look at the "Machine" of strategy. We discuss the reality of M&A, the importance of "Serial Acquisition Playbooks," and why the best architects are actually "Simplification Architects." What you will learn: * Why unclarity is more stressful for employeesthan a strict timeline.* How to learn from mistakes by forcingyourself back to the "painful moments." * Why Enterprise Architects should start withthe experience and work backwards to the tech.
loading
Comments