Agents Unleashed

Decouple, Contextualize, Evolve: A Sorrento Summit Debrief

“Safe is evolving in small batches now—not just big bangs.” - Nikolaos KaintantzisIntroductionNiko moderates this debrief of the 2024 SAFe Summit in Sorrento—but it quickly becomes more than a recap. While only he and Ali attended in person, Stephan and Mark bring layered reflection from the sidelines. What begins as a highlight reel turns into a conversation about direction: not just where the framework is going, but how change agents are meant to meet it. What does it mean to decouple without diluting? How do we contextualize without fragmenting? And how do you lead when the framework’s evolving beneath your feet?Actionable InsightsHere’s what the Unleashed crew surfaced—explicitly and between the lines—about navigating SAFe's latest shifts:Modularity is in. The shift toward continuous delivery and context-driven overlays marks a departure from SAFe’s monolithic past.Contextualization is canon. Tailoring is now core guidance, not subtext.Disciplines over dimensions. The new structure invites varied learning paths—and sharper competency focus.HighlightsConfiguring SAFe for Continuous DeliveryThe crew probes both the mechanics and the implications of breaking the framework into modular, industry-specific parts. While the monolith gave SAFe stability, it also limited adaptability—especially in fast-moving or heavily specialized environments. Now, there's a growing shift toward a leaner, more customizable ecosystem, one where guidance can evolve continuously without requiring a complete re-release.“How do we decouple it? How do we set ourselves up to get into more of a continuous delivery model with SAFe?” —Mark RichardsThe New Discipline and Competency ModelThe team reflects on the practical limits of the old competency model and the opportunities created by the new discipline format. The previous structure forced symmetry, even when some dimensions overlapped or felt redundant. With disciplines, SAFe can hold complexity without enforcing uniformity. It also creates clearer on-ramps for learners—and clearer invites for contributors.Niko shares his own internal tension when offered the chance to contribute to one of the new competencies. At first, he planned to focus tightly—but the new structure made that harder than expected.“I always had in my mind, I want to specialize... then I realized everything is so interesting.” —Nikolaos KaintantzisInsights from the State of SAFe SurveyAli brings in results from the 2024 State of SAFe report, and the conversation turns toward implementation integrity. From misused titles to rebranded hierarchies, the crew reflects on what makes a transformation feel hollow—and what makes it stick. Rather than avoid hard truths, the report appears to be surfacing them, prompting a more honest community conversation.Looking Ahead: Between Sorrento and DenverInstead of closing with conclusions, the crew opens the door to what’s next. They speculate on competency expansions, story-first navigation, and new learning tools—along with risks of fragmentation or fatigue. It’s a hopeful segment, but not a naive one. They’re excited—but they also want to keep the purpose intact.ConclusionIf SAFe is shifting, so are the questions we ask of it—and of ourselves. This episode doesn’t just explore new structures. It shows what happens when a community chooses curiosity over certainty, and depth over dogma. For the Unleashed crew, the goal isn’t to protect the past. It’s to help shape what’s next—one thoughtful step at a time.ReferencesState of SAFe ReportSAFe Explained PDF

Value Stream Mapping: When it Works, and Why it Fails

“There are at least four different versions of a process: how managers believe it operates, how it's supposed to operate, how it really operates, and how it could operate.” —Mark RichardsIntroductionThis episode begins with beach envy and ends with facilitation mastery. In between: a sharp, field-grounded discussion about Value Stream Mapping—its purpose, practice, and perils.Ali, Stephan, and Mark trace their own learning curves, revisit facilitation misfires, and offer clear-eyed advice to SPCs who want more than “a map on the wall.” They’re not trying to convince anyone that Value Stream Mapping is magic. They’re trying to make it useful.Actionable InsightsFrom anecdotes and cautionary tales, here’s what emerges:Start with intent, not format. Mark opens the frame: “What are you trying to use this, the Value Stream Map for?” It’s a design question, not a tooling one​.Avoid detail spirals. Ali cautions against over-indexing on passionate specifics: “Even though they're valid, they're not that valid in that detail, in the grand scheme of things.”.Don’t outsource ownership. Stephan warns, “It looked like a delegate workshop… that doesn't work.” The lesson? Delegates can prepare, but decisions require presence from empowered leaders.Operationalize the map. Mark reminds: “Your Value Stream Map should become your Kanban… then you'd get your data for free.”HighlightsDon’t Let the Map Derail the DialogueAli recalls early workshops where things spiraled into endless details—some valid, some not.“People are really passionate… even though they're valid, they're not that valid in that detail, in the grand scheme of things.” —Ali HajouStephan agrees: the core challenge is “this competition between over-complication and over-simplification.”Delegate ≠ DisengagedStephan names the trap bluntly: “It looked like a delegate workshop… that doesn't work.” But Mark reframes it. Delegates can help build the map—if the real decision-makers show up to own the outcomes. And those delegates must speak from real experience: “It’s their ‘aha’ moment that comes out of that.”Mapping as SensemakingAli offers a systems lens: Value Stream Mapping “is a trick to try to understand the system” as it really works—not just on paper.Stephan builds on that metaphor: “Value Stream Mapping for me is this magnifying glass… your crime scene of inefficiency.”Maps That BreatheMark’s closing gem is a pragmatic vision: when maps become systems, insight becomes flow.“Your Value Stream Map should become your Kanban… then you'd get your data for free.” —Mark RichardsConclusionThis episode isn’t about selling Value Stream Mapping. It’s about rescuing it.From vague templates. From overzealous data obsession. From workshops that deliver nothing but fatigue.And the biggest rescue move? Invite the right people. Ask the right question. Then let the map do its real job: show you what’s really going on.

Running a Smarter Value Stream and ART Identification workshop

"Don't underestimate how much fear is in the room" - Ali HajouIn this episode of SPCs Unleashed, Mark Richards, Stephan Neck, Ali Hajou, and Nikolaos Kaintantzis bring their collective experience to one of the most pivotal—and high-risk—moments in a SAFe transformation: the Value Stream and ART Identification Workshop.Each voice brings a distinct perspective. Stephan sets the stage with a sharp metaphor and a focus on structure. Ali warns of the workshop’s destructive potential if rushed or misused. Nikolaos grounds the conversation in organizational reality and long-term systems thinking. And Mark reminds us that the goal isn’t to get it perfect, but to start the journey of learning and adaptation.Key Highlights1. A Honeypot With BeesStephan opens with a perfect metaphor: this workshop is a honeypot—but it attracts bees. While it promises alignment and flow, it also brings organizational tension and complexity to the surface.“It aims to address organizational complexity… But there are some bees around this honeypot.” —Stephan Neck2. It Can Make or Break a TransformationAli calls it potentially the most destructive workshop in a SAFe rollout. Get it wrong, and you embed misalignment from day one—creating teams that still can't deliver value together.3. Respect What Already WorksNikolaos cautions against wiping the slate clean. While redesigning for value flow is essential, facilitators must acknowledge existing relationships, patterns, and practices that are already enabling success. Change for change’s sake is just as risky as standing still.“We always say start with what you do well. There’s already value flowing somewhere—your job is to find it, not replace it.” —Nikolaos Kaintantzis4. Set the Stage for LearningMark emphasizes that the real outcome of this workshop isn’t finality—it’s understanding. It's a first draft of a system that will evolve through inspection and adaptation.“You don’t need to get it right—you need to get started, and keep learning.” —Mark Richards5. Use Two Workshops, Not OneThe group strongly advocates for a second workshop. The first is about exploring the system, the second about committing to decisions. The gap between the two allows for assumption testing and fact finding to enable more informed commitments.Actionable TakeawaysSet expectations up front: This isn’t a two-day org design sprint—it’s the start of a systems-thinking journey.Don’t overwrite what works: Start from current state patterns that are already delivering value.Pause before deciding: Come back in a second workshop to refine, adjust, and commit.Focus on learning over certainty: Evolution, not perfection, is the goal.If you’re preparing to run a Value Stream and ART Identification Workshop—or coaching leaders through one—this episode is a must-listen. It’s a real-world guide to helping organizations shift from structure-first to value-first thinking.

The software behind high-impact virtual workshops

“Good flow is invisible, but it takes a lot of work to get there” - Nikolaos KaintantzisIn this episode of SPCs Unleashed, Mark Richards, Ali Hajou, Nikolaos Kaintantzis, and Stephan Neck take you behind the scenes of their virtual facilitation setups. It’s a follow-up to their earlier hardware episode—but this time, the spotlight is on software: the tools, flows, and tweaks that help them deliver seamless, engaging remote workshops.What emerges is less about specific apps and more about a mindset—crafting experiences that support learning, participation, and energy in distributed environments.Key Highlights1. Craft Before ConvenienceAli kicks off the conversation by reflecting on how tweaking and refining their setups became a creative obsession—not just to impress, but to enable smoother sessions. The group agrees: great online workshops don’t happen by default.“It becomes a passion over time to tweak things a little… and create a better working environment.” —Ali Hajou2. Their Actual Software StackThe team share a range of tools they rely on in different contexts, including:OBS: For managing transitions and camera scenesStream Deck: As a control panel for switching inputs smoothlyMiro and MURAL: Go-to tools for interactive whiteboardingMentimeter: To gather quick input and keep energy highSlack: Used between facilitators during live sessions for coordinationJamboard, Teams, Zoom, Webex, PowerPoint, Confluence: Mentioned as tools they’ve used or adapted to depending on client setupThe focus isn’t on using every tool—it’s about configuring the right mix to serve the group.3. It's About Reducing FrictionMark emphasizes the importance of flow—both technical and emotional. Tools should fade into the background, allowing participants to stay focused and feel safe. Nikolaos adds that even internal facilitator backchannels (like Slack) help keep delivery smooth.“Even if you’re improvising, you want people to feel like they’re in safe hands.” —Mark Richards4. It’s Performance, But Grounded in PurposeStephan compares facilitation to a performance—but stresses it’s not theater for the sake of it. The tech is in service of connection, trust, and clarity.“You can’t fake facilitation—people feel it when you’re tuned in.” —Stephan NeckActionable TakeawaysBe intentional: Every tool you introduce should remove friction, not add it.Start simple and scale: You don’t need every app—just the right few, well-configured.Practice transitions: Good flow builds participant confidence and focus.Coordinate backstage: Use backchannel tools (like Slack) to manage live facilitation seamlessly. If you’ve ever juggled tabs mid-session or wished your workshops felt more alive—this episode offers practical setups, mindsets, and inspiration from seasoned practitioners who’ve been there.

Agile: Dead, Misunderstood, or Evolving?

“It’s weeding time, right? Sometimes you have to weed out stuff that doesn’t work. Dead wood is not good on a tree.” - Stephan NeckIs Agile really “dead,” or just misunderstood and badly applied? In this lively podcast episode, Mark, Stephan, and Niko challenge the buzz about Agile’s demise and share why core principles of flexibility, fast feedback, and collaboration remain essential—even if the word “Agile” has lost some of its shine.The Agile Hype and the Reality CheckOver the past year, you may have heard conflicting headlines—“Agile is Dead!” versus “Agile is Thriving!” The truth seems to lie somewhere in between. The hosts argue that many organizations adopted Agile by the book—Scrum ceremonies, product owners, and endless backlogs—without truly embracing the mindset that underpins it. This results in rituals with little substance and disappointment when promised benefits don’t materialize.Misunderstood Child StarAn entertaining analogy emerges: Agile as a once-celebrated child actor. Just like Macaulay Culkin or Lindsay Lohan, Agile gained rapid fame but got derailed by an industry eager to exploit it. The hosts note how corporate certification factories and “by-the-numbers” rollouts diluted Agile’s original spark and led to frustration, leaving many asking: “Is it even worth it anymore?”What Really Killed “Agile”?Rather than pointing fingers at one person or movement, the conversation highlights multiple factors:Oversimplification: Believing that simply running sprints or adding stand-ups ensures success.Lack of Technical Depth: Neglecting engineering practices like continuous integration or test automation erodes the agility needed to release quickly.Religious Framework Wars: Distracting debates over Scrum vs. Kanban vs. SAFe overshadow the goal: deliver customer value and adapt rapidly.Weak Commitment: Leadership often wants the label but not the deeper change in culture and mindset.So…Is It Dead?Not really. The panel agrees the core idea of responding to change and delivering outcomes rapidly is more vital than ever. They note that what people call “Agile” may be morphing—focusing on product thinking, DevOps, or simply excellent collaboration. You might not see as many “Agile Coach” job titles, but businesses still crave those skills: facilitation, iterative development, and an experimental mindset.Actionable TakeawaysEmphasize Mindset Over Method: The best frameworks fail if you don’t deeply understand customer value and empower teams to learn fast.Invest in Technical Agility: Automated testing, continuous delivery, and modern engineering practices are the foundation of true adaptability.Collaboration Is King: Whether you call it Agile or not, bringing the right people together to solve problems and share knowledge remains critical.ConclusionIf you’re intrigued by whether “Agile” should be retired or revived, give this episode a listen. Join the discussion: share your experiences, comment on social, and consider how the spirit of agility can be rekindled in your organization.

Stand, Share, Engage: Innovating your Remote Facilitation Setup

“A cheap writing tablet can transform your PowerPoint into a shared canvas.” - Ali HajouRemote facilitation has come a long way since the early days of clunky video calls. In this lively episode, four experienced facilitators—Mark, Ali, Stephan, and Niko—swap stories about how they transformed their home offices into high-energy digital studios. From teleprompters and standing desks to iPhone cameras strapped to arms, they prove that you don’t necessarily need massive budgets to build an engaging remote-training setup.Key Insights & HighlightsStart Small, Then Iterate: Ali kicked off his remote facilitation journey using an old smartphone as a second camera, proving that you don’t need high-end equipment right away. Simple upgrades like a cheap writing tablet (Wacom One) or extra monitor can quickly elevate the online learning experience.Stand and Deliver: Mark discovered that switching to a standing desk injected fresh energy into his sessions. Standing mirrors the dynamic feel of an in-person workshop and helps prevent the infamous “Zoom slump.”Keep It Authentic: Stephan emphasized not overcomplicating gear. If you’re not into flashy overlays or spinning graphics, that’s okay. A good microphone, decent lighting, and an accessible digital board (like Miro or even Excel) may be all you need.Break It Up: Niko’s approach reminded everyone that pacing matters more than ever in virtual settings. Frequent short breaks—enough time to actually stand, stretch, or even jog—help participants stay engaged instead of flipping over to email.Next-Level Tools: For those who want to geek out, open-source OBS software allows you to switch seamlessly between multiple cameras, add fun overlays, and keep the focus on the content. If you prefer a more plug-and-play style, look at hardware switchers (like the Blackmagic ATEM Mini) or a Stream Deck to simplify switching scenes and slides.Human TouchEach host has a unique style. Ali is the “hardware guy,” always tinkering with his suitcase studio so he can set up anywhere in 10 minutes. Stephan, self-proclaimed “old dog,” embraced new gadgets like a teleprompter to simulate direct eye contact. Niko loves mixing analog tools (like paper cards) with digital meeting rooms, ensuring creative variety. Mark ties it all together with a stand-up energy that keeps participants on their toes—literally.Actionable TakeawaysFocus on Comfort First: Good lighting, clear audio, and a decent camera angle will solve 80% of remote issues.Use Breaks Wisely: Add a 10–15 minute break every hour to maintain energy and let participants recharge.Experiment Gradually: Before investing in expensive gear, test software solutions like OBS or the Stream Deck app for your phone.Stay Authentic: Don’t chase every shiny new tool; pick what truly enhances your facilitation style.ConclusionReady to level up your remote facilitation game? Start by experimenting with one new piece of gear or software—then let your creativity lead the way. And be sure to tune in for the next episode, where the team dives into the software side of remote workshops, sharing demos, tips, and more.ReferencesWork Together Anywhere by Lisette Sutherland

The Dual Operating System in Practice

“Leaders have to do more than simply say ‘we have two systems.’ They have to actively steer the organization so it’s both robust and free to innovate.” - Stephan NeckWhat happens when an organization outgrows the myth that “all you need is cross-functional teams”? In this episode of SPCs Unleashed, Stephan, Ali, Niko, and Mark dig into the Dual Operating System—the concept that healthy enterprises need both a stable hierarchy and a network of agile teams. Balancing these two “systems” can be tricky: too much network, and chaos creeps in; too much hierarchy, and innovation stalls.The group shares real-world stories where line managers struggled to find their place in an agile environment, and teams were forced to “figure out” things like career growth, performance management, and compliance. The central point? A thriving enterprise can’t ignore its operational backbone or the people who keep it running—yet it also can’t let old school structures choke the flow of value.Key HighlightsHierarchy Still Matters: Killing off management leads to confusion, with nobody taking care of essential processes or people’s long-term growth.Network for Speed & Innovation: Agile teams excel at quick delivery and iterative feedback, but that alone can’t address bigger structural needs.Role of Leadership: Far from being “evil,” leaders must shift focus—away from daily task management and toward supporting employees’ development and well-being.Avoid Over-Fluffiness: Simply “trusting teams” without clarifying accountability and career pathways can create a ticking time bomb.Concrete Mechanisms: Allocating a fixed budget or “time code” (e.g., a 10% buffer) ensures capacity for improvement and competence development in the network.Actionable InsightsInvolve HR Early: They offer critical expertise for dual reporting lines, role clarity, and setting up the right systems (e.g., Workday, SAP) to support both hierarchy and network.Formalize Time & Budget for Growth: Reserve capacity for improvement and cross-team learning—otherwise urgent priorities push it aside.Educate Managers on “New Leadership”: Shift from daily control to integrator responsibilities—connecting people across silos and guiding their professional journeys.ConclusionEmbracing a Dual Operating System means recognizing that “manager” isn’t a bad word—hierarchies can be powerful for stability and talent development, while agile networks spark rapid innovation. With the right balance, clear processes, and respect for both sides of the coin, enterprises can keep their core strong while racing forward into new possibilities.ReferencesSix Simple Rules by Eve Morieux and Peter Toolman 

Designing for Distance: Remote Facilitation Done Right

“If you do no pre-work, the first 20 minutes are lost—someone can’t open Miro, doesn’t have the password, so you lose that time sorting out technical difficulties.” - Mark RichardsRemote facilitation may feel like juggling blindfolded—especially when every participant has a muted mic and a hidden camera. In this episode of SPCs Unleashed, our hosts (Mark Richards, Ali Hajou, Stephan Neck, and Nikolaos Kaintantzis) share what they’ve learned about driving engagement when no one’s in the same room. From innovative digital whiteboard designs to “crazy” energizers, they show that running remote sessions is more than swapping your physical whiteboard for a screen—it’s about designing for human connection in a virtual space.Whether you’re leading a PI Planning event or training new teams, remote facilitation demands empathy, flexible tools, and a heavy dose of creativity. If you’ve struggled with black squares on video calls, endless background noise, or total silence from participants, this conversation will spark fresh ideas for making digital gatherings productive and even fun.Key HighlightsDesign for Comfort: Encourage participants to try the collaboration tools (e.g., Miro, Teams) before the workshop. Simple pre-work like creating avatars or adding photos helps them ease in.Amp Up Visibility: Since you can’t “walk the room,” build boards and back channels that let you observe activity. Moving cursors, color-coded sticky notes, and quick status checks reveal who’s stuck and who’s on track.Energize with Novelty: From tossing a virtual ball between co-facilitators to spinning a “wheel of names,” tiny sparks of fun can keep everyone alert and participating.Focus on Flow, Not Just Talk: A 90-minute monologue is deadly. Instead, break up the session with breakouts, short tasks, or interactive polls—anything that makes participants do something rather than sit passively.Actionable InsightsShorten & Stagger Sessions: Avoid back-to-back marathons. Build in small buffer zones so people can regroup between calls.Use Multi-Modal Channels: Combine a shared board, a voice channel, and possibly a chat thread for real-time text. This mimics the multi-layered communication of an in-person room.Plan Twice as Much: Remote sessions often require more upfront prep. Test your platforms, arrange breakout flows, and consider a second facilitator to troubleshoot tech.ConclusionRemote facilitation has traveled far beyond “new reality” status—it’s simply how many of us work. With the right preparation, a dash of human empathy, and a few creative tricks, even digital distance can spark real engagement. Tune in for practical insights on orchestrating seamless, lively virtual sessions that your teams will remember for all the right reasons.

Sparking Change through Scaled Retrospectives

“If you ask questions about the past, it’s always about going to a corpse and opening it up... If you ask questions about the future, it’s always about values" -  Nikolaos Kaintantzis“Are you all dumb?” When a senior stakeholder dropped that bombshell mid-retro, chaos threatened to derail everything. In this episode of SPCs Unleashed, Mark, Ali, Stephan, and Niko reflect on what makes art-level retros truly transformative. Spoiler: It’s a balance of authentic emotion, precise data, and a willingness to experiment with new formats.Key HighlightsData as a Compass: Mark argues that each retro needs measurable goals or it slides into empty talk.Controlled Chaos: Stephan highlights the value of quick reflection moments before huge problems boil over.Offbeat Creativity: Ali and Niko champion “the James Bond approach,” metaphors, and playful prompts that unlock honest feedback.Facilitation Matters: Big groups require multiple moderators, as no single person can handle tears, confusion, or conflict alone.Action is King: From budget constraints to final approvals, no outcome will stick without leadership buy-in and resource allocation.Actionable InsightsFocus on Real Tension: Don’t shy away from conflict; friction often drives breakthroughs if handled professionally.Vary Your Timing: Pick ad-hoc retros for urgent crises and scheduled ones for deeper reflection.Measure, Then Improve: Use metrics to confirm progress; otherwise, your next retro may feel like a hollow repeat.ConclusionRetrospectives aren’t a cozy chat—they’re a critical lever for cultural and operational gains. Whether dealing with emotional blow-ups or nailing down the data to validate success, this episode offers a roadmap for art-level retros that genuinely deliver.ReferencesAgile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen

Mastering Distributed PI Planning

“If you do it right, if you have the right people, and if you have some nerds and lots of engineering DNA, it really works on the tool side" - Stephan NeckIf you’ve ever believed that failing once in remote PI Planning means catastrophe, this episode of SPCs Unleashed proves otherwise. Mark Richards, Ali Hajou, Stephan Neck, and Nikolaos Kaintantzis discuss how their early horror stories—teams flying to the wrong city, frantic breakout links—led them to design stronger approaches for future PI events.Key HighlightsFail Forward: Mark shares why the first distributed attempt bombed—and how reflection turned it into a gold mine of learning.Engineering the Experience: Ali’s meticulous tip sheets and distribution-list tactics show how to orchestrate a seamless remote event.Trust Before Tools: Stephan and Niko emphasize that real alignment arises from respect, empathy, and creative team rituals.Agenda as a Design Task: Spreading sessions over multiple days, blending synchronous and asynchronous touchpoints, and scheduling “handover time” across time zones.Leader Visibility: Dispersed teams need more leadership presence—Gemba time is crucial, even if it’s virtual.Actionable InsightsCustomize Your Toolkit: Match your collaboration tools to your security constraints, culture, and level of remote maturity.Establish a “Summon” Method: Instantly ping relevant players with at-mentions, shared boards, or specialized scripts.Prototype Your Flow: Small-scale tests of your agenda can reveal hidden friction points before the big day.ConclusionDistributed PI Planning isn’t a fallback option; it can be a fresh opportunity for stronger collaboration. By preparing deeply and focusing on human connections, you’ll discover remote sessions can be surprisingly powerful—even under pressure.