エピソード

  • What the State of SAFe Survey Actually Tells Us (and What it Doesn't)

    What the State of SAFe Survey Actually Tells Us (and What it Doesn't)
    2025/05/26
    “Information is crucial. If you use it the wrong way, it’s the wrong data—it will influence your actions in a drastic way.” —Stephan Neck In this episode, the Unleashed crew—Mark Richards, Ali Hajou, Stephan Neck, and Nikolaos Kaintantzis—bring a practitioner’s lens to the latest State of SAFe survey. Instead of glossing over findings or defaulting to boosterism, they pull apart the data, the context, and the stories those numbers can (and can’t) tell. Ali keeps the conversation grounded, Niko brings fresh metaphors and questions, and Mark and Stephan bridge the gap between framework theory and lived experience. The result is a thoughtful exploration of how coaches and leaders can use survey insights to inform—rather than define—their next moves. Actionable Insights Here’s what the Unleashed crew surface—explicitly and between the lines—about navigating survey data, SAFe transformation, and what to do next: - Context transforms data into insight: Numbers alone aren’t enough. As the crew note, understanding who’s responding and what lens they’re using can shift a piece of data from trivia into guidance. - Patterns reveal opportunities, not just problems: Ongoing role confusion—especially between PO and PM—signals systemic friction. But it also points to clear spaces where targeted coaching, structure clarification, and realignment can unlock better outcomes. - Framework evolution is a call to creative action: SAFe, like any framework, moves forward through practical experimentation and responding to what actually works. Adaptation isn’t a burden—it's the path to staying relevant and making a real impact. Highlights The Database Dilemma: Can We Trust What We’re Reading? Instead of accepting the survey at face value, the team probe what’s beneath the surface. Stephan sets the tone: “Where’s your database? How did you gather it? ...Is it telling a good story, or is it pouring in what the challenges are?” With many responses coming from managers rather than coaches, positive statistics require a second look. “I would have expected more coaches, more SPCs… When I hear managers and being critical, is it telling a good story, or is it pouring in? What are the challenges we have?” —Stephan Neck Mark urges a tailored approach to what the survey tells us: “I want to be able to go, what if you did that same analysis and you split it by cohort—what would the difference be?” The message: questioning is healthy, and segmenting data can lead to greater clarity and more precise action. Hybrid Agility and the Trap of Surface Change Ali surfaces a recurring reality: many organizations try to “do SAFe” in parallel with established systems—resulting in overlap, frustration, and the temptation to rebrand instead of rethink. Niko highlights the missing perspective: the survey tracks practices, but less so the people-focused work of coaching and enabling adaptive change. “A lot of SAFe practices, but also the roles, are in a way done next to the existing way of working…rebranding a meeting, or rebranding a role, just giving it the new name.” —Ali Hajou The crew encourage looking beyond relabeling—real change lives in how roles are experienced and supported, not just how they’re titled. Why Are POs and PMs So Dissatisfied? One insight stands out: product owners and product managers report the lowest satisfaction. Niko notes, “POs have the most decrease in satisfaction, and the most less increase is for PMs.” Mark explains the root: “That product owner is not going to have a lot of fun, because the team’s not going to want to talk about business problems—they’re going to want to talk about mainframe COBOL.” Responsibility without genuine autonomy creates frustration. But here’s the upbeat twist: coaching and clarifying role responsibilities, especially on complex subsystem teams, offers a real lever for positive change. The data simply shines a light on where to focus next. The Language Games: Rename with Care, Build with Intention Niko points out the risk in constant renaming: “Just inventing everything new with a new vocabulary, then you have the worst of both.” Mark sums it up for coaches: “I don’t care what you call it, so long as you all call it the same thing… Let’s grow from the language you’ve got today.” The opportunity: meet teams where they are, align language deliberately, and create shared meaning rather than confusion. Data Is a Compass, Not a Map Throughout, the crew resist easy headline takeaways. As Mark puts it with a grin: “The box didn’t blow my mind, but it did confirm that I’ve been shopping at the right chocolate store.” The true gift of the survey is in confirming patterns and pointing practitioners towards areas where their energy will matter most. “It’s comforting to have the survey confirm my beliefs about the common challenges, and ...
    続きを読む 一部表示
    53 分
  • From Framework to Fieldwork: Making Sense of SAFe’s New Disciplines

    From Framework to Fieldwork: Making Sense of SAFe’s New Disciplines
    2025/05/26
    “The disciplines are about problem solving. They’re a way to navigate to knowledge… Different people love to find their knowledge different ways.” — Mark Richards Introduction SPCs Unleashed returns with a stepwise, hard-nosed look at the new Scaled Agile “disciplines” announced in Sorrento—an architectural shift intended to make the framework more usable, less dogmatic, and ultimately more valuable in the context of enterprise change. With Mark Richards guiding the connection points and Stephan Neck leading the inquiry, the team (joined by Nikolaos “Niko” Kaintantzis) explores what this modular reframe really means for practitioners and transformation leaders invested in real agility, not just surface adoption. No hype here. The Unleashed crew does what they do best: challenge received wisdom, probe for real-world risks, and test whether the new direction delivers what coaches and organizations actually need. Actionable Insights Here’s what the crew surfaces—directly and by friction—about adopting the “disciplines” model for Scaled Agile: - Navigation over prescription: The move from static configurations to adaptable disciplines creates more tailored entry points for actual business problems—if you’re willing to begin with context, not the “one true path.” - Optionality introduces risk and clarity: The flexibility is real, but so is the risk of new “disciplinary silos.” Systemic glue—often in the form of LACE or a Value Management Office—matters more than ever. - Depth and teaming over overwhelm: Coaches shouldn’t be daunted by the number of disciplines now in play. The days of aspiring to be a master of everything are gone; the model favors T-shaped expertise—broad awareness, with real depth in focus areas, working in cross-functional teams where strengths combine instead of one coach trying to cover all bases. - Leadership isn’t a module: While there’s a dedicated discipline for Leadership & Culture, raising actual executive capability will almost always demand more than the framework prescribes. Highlights Goodbye “Fit All” Configurations—Hello Study, Inquiry, Focus The team unpacks what a discipline means—a field of study, not just a “box to tick.” As Stephan frames it: “You study something… you inquire—it’s not a given, then you dive into the methods, theories, and principles.” For coaches, this isn’t a theoretical shift. Navigation starts with the problem at hand. Mark calls out the storytelling value: “You can now sit and see a connected story… Discipline names guide you, then the disciplines can tell a story that is meaningful to you.” The Silo Risk: Specialization Without System Fragmentation There’s energy around the newfound freedom to “specialize”—but also caution. Niko reframes the “silo” anxiety, saying: “If there are silos, I love them—as areas of specialization. It’s better than forcing full SAFE because you think you have to do everything.” Still, the LACE becomes responsible for ensuring the overall flow: “The LACE should be the glue between the disciplines.” Not Just Clicking Around: Adaptive Learning and Agentic Guidance Mark and the crew recognize that modern knowledge-seeking isn’t about browsing static pictures: “Structuring your knowledge for a modern person means providing clarity to the information and guidance SAFE has to offer—in their particular context and situation. People are going to do what most of us do… ask our CoPilots or ChatGPT questions.” This has implications for framework design—and for the way coaches help others find, not just receive, useful knowledge. Practice as Organism, Not IT Upgrade Niko spotlights a critical mindset shift: “With disciplines, it feels more human—a living organism you actively tend, not just a system to install or upgrade.” The conversation pushes for systemic coaching and change—not checklist compliance. In Stephan’s words: “It’s a step from crawling to walking, even running.” Leadership & Culture: Essential, Yet (Still) Not Enough On the leadership discipline: Mark is frank—perhaps provocatively so: “Personally, I don’t know that teaching senior leaders to be better leaders is SAFE’s strong suit… If an enterprise wants better leaders, they’ll go elsewhere.” Niko echoes the call for “outside bodies of knowledge” and cautions that even with more content, “leadership training is not everything.” Yet, the team affirms the new model’s “red thread”: contextual, cross-cutting, lived behaviors matter. Stephan frames it clearly: “Culture isn’t a poster on the wall; it’s the sum of our behaviors… you either live it or it doesn’t exist.” Product Development Flow: Feedback Isn’t Optional When exploring the Product Development Flow discipline, Niko delivers a caution to those who see themselves as “special cases”: “Never say, ‘I don’t need this competency; ...
    続きを読む 一部表示
    51 分
  • Decouple, Contextualize, Evolve: A Sorrento Summit Debrief

    Decouple, Contextualize, Evolve: A Sorrento Summit Debrief
    2025/05/05

    “Safe is evolving in small batches now—not just big bangs.” - Nikolaos Kaintantzis

    Introduction

    Niko 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 Insights

    Here’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.

    Highlights

    Configuring SAFe for Continuous Delivery

    The 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 Richards

    The New Discipline and Competency Model

    The 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 Kaintantzis

    Insights from the State of SAFe Survey

    Ali 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 Denver

    Instead 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.

    Conclusion

    If 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.

    References

    • State of SAFe Report
    • SAFe Explained PDF
    続きを読む 一部表示
    54 分
  • Value Stream Mapping: When it Works, and Why it Fails

    Value Stream Mapping: When it Works, and Why it Fails
    2025/05/02

    “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 Richards

    Introduction

    This 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 Insights

    From 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.”

    Highlights

    Don’t Let the Map Derail the Dialogue

    Ali 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 Hajou

    Stephan agrees: the core challenge is “this competition between over-complication and over-simplification.”

    Delegate ≠ Disengaged

    Stephan 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 Sensemaking

    Ali 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 Breathe

    Mark’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 Richards

    Conclusion

    This 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.
    続きを読む 一部表示
    50 分
  • Running a Smarter Value Stream and ART Identification workshop

    Running a Smarter Value Stream and ART Identification workshop
    2025/04/24

    "Don't underestimate how much fear is in the room" - Ali Hajou

    In 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 Highlights

    1. A Honeypot With Bees

    Stephan 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 Neck

    2. It Can Make or Break a Transformation

    Ali 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 Works

    Nikolaos 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 Kaintantzis

    4. Set the Stage for Learning

    Mark 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 Richards

    5. Use Two Workshops, Not One

    The 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 Takeaways

    • Set 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.
    続きを読む 一部表示
    1 時間 7 分
  • The software behind high-impact virtual workshops

    The software behind high-impact virtual workshops
    2025/04/17

    “Good flow is invisible, but it takes a lot of work to get there” - Nikolaos Kaintantzis

    In 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 Highlights

    1. Craft Before Convenience

    Ali 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 Hajou

    2. Their Actual Software Stack

    The team share a range of tools they rely on in different contexts, including:

    • OBS: For managing transitions and camera scenes
    • Stream Deck: As a control panel for switching inputs smoothly
    • Miro and MURAL: Go-to tools for interactive whiteboarding
    • Mentimeter: To gather quick input and keep energy high
    • Slack: Used between facilitators during live sessions for coordination
    • Jamboard, Teams, Zoom, Webex, PowerPoint, Confluence: Mentioned as tools they’ve used or adapted to depending on client setup

    The focus isn’t on using every tool—it’s about configuring the right mix to serve the group.

    3. It's About Reducing Friction

    Mark 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 Richards

    4. It’s Performance, But Grounded in Purpose

    Stephan 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 Neck

    Actionable Takeaways

    • Be 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.
    続きを読む 一部表示
    1 時間 1 分
  • Agile: Dead, Misunderstood, or Evolving?

    Agile: Dead, Misunderstood, or Evolving?
    2025/04/10

    “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 Neck

    Is 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 Check

    Over 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 Star

    An 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 Takeaways

    1. Emphasize Mindset Over Method: The best frameworks fail if you don’t deeply understand customer value and empower teams to learn fast.
    2. Invest in Technical Agility: Automated testing, continuous delivery, and modern engineering practices are the foundation of true adaptability.
    3. Collaboration Is King: Whether you call it Agile or not, bringing the right people together to solve problems and share knowledge remains critical.

    Conclusion

    If 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.
    続きを読む 一部表示
    55 分
  • Stand, Share, Engage: Innovating your Remote Facilitation Setup

    Stand, Share, Engage: Innovating your Remote Facilitation Setup
    2025/04/04

    “A cheap writing tablet can transform your PowerPoint into a shared canvas.” - Ali Hajou

    Remote 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 & Highlights

    • Start 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 Touch

    Each 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 Takeaways

    1. Focus on Comfort First: Good lighting, clear audio, and a decent camera angle will solve 80% of remote issues.
    2. Use Breaks Wisely: Add a 10–15 minute break every hour to maintain energy and let participants recharge.
    3. Experiment Gradually: Before investing in expensive gear, test software solutions like OBS or the Stream Deck app for your phone.
    4. Stay Authentic: Don’t chase every shiny new tool; pick what truly enhances your facilitation style.

    Conclusion

    Ready 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.

    References

    Work Together Anywhere by Lisette Sutherland
    続きを読む 一部表示
    1 時間 4 分