AI & Product Management | Founder, Author @ The Product Compass Newsletter | Join 119,000+ PMs

Follow me for actionable tips, resources, and step-by-step playbooks for AI and AI-empowered PMs. 

The Product Compass Newsletter trusted by 125,000+ PMs: https://www.productcompass.pm/

---

I can no longer accept connections because LinkedIn limits the number of 1st-level connections to 30K. 

To connect with me, join our premium Slack community: https://www.productcompass.pm/p/product-management-resources, or engage with my content.

Paweł Huryn

1,100+ GitHub stars in 3 days — I didn't expect this.

I built an open-source PM Skills Marketplace for Claude: 100+ skills and commands that turn AI into a product management partner.

Not generic prompts. Structured skills that actually know PM frameworks.

8 plugins covering the full PM lifecycle:

→ Product Discovery: problem & solution space exploration
→ Product Strategy: vision, business model, strategy docs
→ Execution: PRDs, OKRs, roadmaps, sprint planning, user stories
→ Market Research: personas, segmentation, TAM/SAM/SOM
→ Data & Analytics: cohorts, A/B testing, retention analysis
→ Go-to-Market: GTM strategy, beachhead, ICP, growth loops
→ Marketing & Growth: positioning, North Star Metric
→ PM Toolkit: including PM resume review

Built for Claude Code and Cowork. Compatible with Gemini CLI, Cursor, Codex CLI, and Kiro.

Repo URL + instructions for Claude Code & Cowork: https://lnkd.in/dxdTj24P

Want to contribute? The repo is open. Check CONTRIBUTING[.]md.


For more about Cowork, see the Ultimate Guide for PMs: https://lnkd.in/dyY-jhvG

AI PM | Deep research. I build, test, then teach | 130K+ subscribers

Anthropic's plugins wiped $285 billion from legacy software stocks in a single day. They're now sitting in your Cowork sidebar.

Now available on Windows and Intel-based macOS.

Most people think Cowork is an improved Chat. It's not. It can do any knowledge work Claude Code can — without a terminal and with a better UX.

𝗪𝗵𝗼 𝗲𝗮𝗰𝗵 𝘁𝗼𝗼𝗹 𝗶𝘀 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗳𝗼𝗿:

→ Chat — conversations, artifacts, quick answers. No file access, no sub-agents, no plugins.

→ Cowork — autonomous knowledge work. Plans tasks, spawns parallel sub-agents, reads and writes real files, sandboxed VM. For PMs, legal, marketing, ops.

→ Code CLI — same power as Cowork, direct filesystem access, project-scoped config. For developers and engineers.

𝗛𝗼𝘄 𝘁𝗼 𝘀𝘁𝗮𝗿𝘁 𝗶𝗻 𝟱 𝘀𝘁𝗲𝗽𝘀:

1. Install Claude Desktop
2. Switch to the Cowork tab
3. Enable connectors and plugins
4. Select your working folder
5. Describe your task — done

𝗤𝘂𝗶𝗰𝗸 𝗴𝗹𝗼𝘀𝘀𝗮𝗿𝘆:

→ Skill — a reusable instruction set that teaches Claude a specific behavior 
→ Plugin — a bundle of skills + MCPs tailored to a business role
→ Connector — connects Claude to external or local apps via MCP

𝗧𝗼𝗽 𝟳 𝘀𝗸𝗶𝗹𝗹 𝗮𝗻𝗱 𝗽𝗹𝘂𝗴𝗶𝗻 𝗺𝗮𝗿𝗸𝗲𝘁𝗽𝗹𝗮𝗰𝗲𝘀:

→ github[.]com/anthropics/skills — official repo. Document skills plus creative, technical, and enterprise examples

→ github[.]com/anthropics/knowledge-work-plugins — Cowork's default plugin registry. The 11 business-role plugins

→ github[.]com/anthropics/claude-code — Developer-focused workflows.

→ claudemarketplaces[.]com — A marketplace of marketplaces

→ github[.]com/travisvn/awesome-claude-skills — Battle-tested skills for TDD, debugging, collaboration

→ github[.]com/sickn33/antigravity-awesome-skills — 868+ universal agentic skills. Role-based bundles: Startup Founder, Marketing & Growth, and more

→ skills[.]sh — Product strategy frameworks, pricing strategy, launch playbooks, interviews, PRD generator, analytics, resume optimizer

𝗪𝗵𝗲𝗿𝗲 𝘁𝗼 𝗳𝗶𝗻𝗱 𝗠𝗖𝗣 𝘀𝗲𝗿𝘃𝗲𝗿𝘀:

→ github[.]com/modelcontextprotocol/servers: Official MCP server repo — filesystem, GitHub, Google Drive, Slack, and more

→ modelcontextprotocol[.]io/examples: Official MCP directory — reference MCP implementations

→ github[.]com/punkpeye/awesome-mcp-servers: Community-curated list — hundreds of MCP servers by category

→ mcp[.]so: MCP server registry

𝗕𝗼𝗻𝘂𝘀: 𝟮 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗵𝗮𝘁 𝟮𝘅 𝗖𝗼𝘄𝗼𝗿𝗸'𝘀 𝗽𝗼𝘄𝗲𝗿:

→ Add Desktop Commander — full laptop access, file editing, installing MCPs.

→ Give Cowork cross-session memory — Global Instructions + Desktop Commander = memory that survives crashes and new sessions.


I broke it all down in my free guide. 

No email. No paywall: 
https://lnkd.in/dyY-jhvG

---

P.S. Want to break into AI PM? I recommend the AI PM Certification by leaders shipping in the top AI companies

A $500 discount + 1 year subscription to my newsletter with this link: https://bit.ly/aipmcohort

AI PM | Start building. Stop theorizing. I build with AI and share what works. 129K+ subscribe.

How to master Claude Cowork as a Product Manager 

Most people use Claude like a chatbot.

That's like using Photoshop only to crop photos.

Same models. Three surfaces. Very different results:

Chat → Thinking & Content
You type, Claude answers. No files, no workflow.

Cowork → Files & Workflows
Give Claude your files, set a task, step away.
Come back to real .docx/.pptx/.xlsx in your folder.

Code → Code & Systems
VS Code, terminal, desktop app, or browser.
No sandbox — git, bash, subagents, full workspace.

---

"I want to..."

Chat:
→ Draft an email or rewrite a paragraph
→ Roleplay as my VP of product 
→ Summarize a 30-page report

Cowork:
→ Research a topic — finished .docx in my folder
→ Extract tables from 50 PDFs
→ Draft replies to unreplied Slack DMs daily

Code:
→ Turn a PRD into a working prototype
→ Start on laptop, continue from phone
→ Run a long task with zero local setup (web)
→ Build systems that compound

---

What most people miss:

☑ Power Combo: Cowork /schedule for persistent daily cron that survives restarts. Code /loop for in-session monitoring. Same connectors. You can use both.

☑ Work From Anywhere: Start in VS Code, continue from your phone via /remote-control. Or kick off a long task on claude[.]ai/code with zero setup.

☑ Shared DNA: Same models (Opus, Sonnet, Haiku). Project instructions in Chat, CLAUDE[.]md in Cowork + Code. Web connectors, skills, extended thinking — all three. 

☑ Bonus: Real file access + shell commands — all three after installing Desktop Commander MCP for Claude Desktop. Switch mid-task when needed.

---

Free skill repos:
→ Knowledge work: https://lnkd.in/d6ZJbET3
→ Antigravity: https://lnkd.in/dYDzgYK6
→ Awesome Claude: https://lnkd.in/dEe8jcGa
→ Gemini: https://lnkd.in/d5dieggp
→ Product Management: https://lnkd.in/dxdTj24P

Free courses by Anthropic:
→ Claude 101 — https://lnkd.in/davAeVzv
→ Claude Code in Action — https://lnkd.in/dnK6MmnG
→ AI Fluency: Foundations — https://lnkd.in/dtvK8k2E
→ Introduction to MCP — https://lnkd.in/dU86EUTe
→ Introduction to Agent Skills — https://lnkd.in/dN2XTXSP

---

Not everyone needs Code.
But if you used Cowork, you're 70% there.

Using Code doesn't mean you stop using the others.

Pick the one that matches your task.

I wrote two full guides:

👉 Claude Cowork Guide for PMs: https://lnkd.in/dyY-jhvG
👉 Claude Code Guide: How to Transition: https://lnkd.in/dVFJ4Bix

---

By the way, if you want to break into AI PM, I recommend the AI PM Certification. A special $500 discount + 1-year subscription to my newsletter with this link: https://bit.ly/aipmcohort

JUST IN: Meet Code Review by Anthropic. It hunts for bugs at PR time. Loved it.

But security isn't just about reviewing changes. It's about stress-testing what's already there.

Here's how I approach it with Claude Code:

First, prepare. Before any security prompt works, Claude needs context:
→ Document your system architecture 
→ Document roles and permissions 
→ Document scheduled work and email flows 
→ Document secrets and variables

Then, stress-test your full codebase:
→ Someone just accessed a user's email. Figure out how. 
→ A user called an endpoint and got data they shouldn't. Trace it. 
→ User-submitted content executed JavaScript and stole admin cookies. 
→ An attacker tries to bypass access control — JWT manipulation, session hijacking, cross-tenant access. 
→ Compare what permissions.md says vs. what the API actually enforces. 
→ Audit Content Security Policy for weak directives.
→ Review against OWASP top 10.

The pattern: describe a breach scenario. Claude reverse-engineers how it could happen in your codebase. Outputs risk level, attack path, impact, and fix.

No coding required.

Run before launch, after major changes, or /loop into your pipeline.

You're welcome!

As the co-founder of The Liberators and Columinity, I liberate teams and organizations from outdated working modes. I create space for everyone to be involved in shaping the future and positively impact their organization.

I highly enjoy workshop facilitation. As a facilitator, I help teams and groups think creatively and find local solutions to persistent challenges. 

My toolkit is packed with Liberating Structures. They make everyone feel heard, seen, and respected and help me get the most out of group interactions. 

I write blog posts, host meetups, and participate in conferences to share my lessons learned.

Barry Overeem

Has Scrum peaked too soon? 🤔 

I rarely write about Scrum anymore. Not because I suddenly dislike it, but because my work has gradually moved in a different direction.

Still, I sometimes wonder whether Scrum peaked too soon. During the 10 years I worked as a Professional Scrum Trainer at Scrum.org, I delivered dozens of training sessions. One thing always stood out to me...

The case studies used to explain the urgency of Scrum were often quite old. Think of the Kodak story. A company that missed the shift to digital photography.

We also talked a lot about the VUCA world and why organizations needed to become more agile to survive. But looking back, the past decade did not really feel that VUCA for many organizations. Business was generally good. Training budgets were high. Agile and Scrum spread rapidly. 🥳 

Yet, in many places, it felt more like a nice-to-have than a necessity.

Ironically, today’s world actually feels far more VUCA. Markets shift quickly. Technology evolves fast. Many organizations struggle to stay relevant. The need for innovation, adaptation, and agility has probably never been higher.

The golden age for Agile Coaches, Scrum Masters, and Scrum Trainers! Right? Well, apparently not. Many people in those roles are currently struggling to find work. Just when agility is arguably needed most, many organizations seem to be moving away from Scrum and the roles around it.

So what happened? 🤷‍♀️ 

👉 Do organizations see Agile and Scrum as something optional after all?
👉 Do they believe agility matters, but they need different roles in times of crisis?
👉 Or did the Agile industry spend years optimizing for certifications, roles, and training… while organizations actually needed something else?

Curious to hear how others see this.

Co-founder The Liberators & Columinity. I design and facilitate workshops (with Liberating Structures). 🚀

My *final* public Liberating Structures Immersion Workshop, for now...

On 24/25 June, I’ll host another public LS Immersion Workshop at the Volkshotel in Amsterdam. This will be my final public workshop, at least for the foreseeable future. After this one, I’m pressing pause. I don’t see this returning anytime soon. As for the next 3 to 5 years, I’ll keep that open. 🤷‍♂️

🤔 "Didn't you stop before?"
Yes. I’ve announced a “final” public workshop before, and changed my mind. The messages from people who wanted to join but had missed out made me decide to continue for a while.

🤔 "What makes it different this time?"
To be clear: I still love Liberating Structures and running the workshop itself.
If every edition filled up easily, I would happily continue. What weighs on me is the ongoing marketing & sales effort and the financial uncertainty that comes with it.

Interestingly, so far, every public edition has gone ahead. I could likely rely on that. And still, this feels like the right moment to pause and free up mental space for what’s next.

🤔 "Why not schedule a date and simply wait for enough people to sign up?"
I’ve considered it. But if it’s on my calendar, it quietly drains attention and energy. There’s always something to optimise, adjust, or worry about. That ongoing background noise is what I want to step away from.

🤔 "What about the public LS meetups?"
I restarted the public LS meetups last year, each time at a different organization and centered on a single structure. I’ll definitely keep hosting those! They create the same cross-organizational exchange I value, but are easier to organize, run, and sustain.

🤔 "Are you available for running in-company LS workshops?"
Yes, absolutely. I’m only pausing the public immersion workshop. In-company workshops are a major focus of my work, and I already have several scheduled this year. I’m happy to add more.

More broadly, I want to help people and organizations use Liberating Structures to address real challenges. Not just running 1-2-4-ALL, but working with the full range of structures in meaningful contexts. For me, that means shifting the balance from teaching LS to practicing it together.

Questions? Just ask.

I’m looking forward to running this final public edition before pressing pause.
We already have a strong start with registrations, and I expect it to go ahead.

See you there? 😃

Check Eventbrite for more details: https://lnkd.in/gi_pTKN

If someone in your network would benefit, I’d appreciate it if you shared it. 🙏

Columinity kickoff workshop Kamer van Koophandel 🥳 

Yesterday, we facilitated a Columinity kickoff workshop at KvK. Recently, I've been fortunate to host sessions at awesome locations. The view of Amsterdam's city & harbor was spectacular! 

But when I shifted my focus from the scenery to the workshop, my purpose was to help participants... 

👉 Understand WHY it is important to use data to identify and remove impediments to team- and organizational effectiveness.
👉 Experience WHAT this looks like in practice with Columinity, and how it uses scientific insights to support change in teams and organizations.
👉 Learn HOW teams and organizations can use Columinity to perform Action Research - a collaborative, data-informed process to identify challenges, take action, and reflect on results to trigger continuous improvement and learning 

Topics we covered during the day:
✅ Systemic thinking: spotting patterns and trends across teams
✅ Making sense of results: retrospectives for team and org insights
✅ The science behind Columinity: research and how it’s applied in practice
✅ Ethical use: shared principles, trust, and a solid foundation
✅ Turning insight into action: engaging teams, stakeholders, and supporters

KvK will use Columinity with all 75-ish teams, which creates a real opportunity to spot improvement patterns across the organization. Exactly the kind of impact Christiaan Verwijs and I had in mind when we built Columinity.

If you’re curious to learn more about Columinity or want to explore running this workshop in your organization, feel free to reach out.

Looking forward to our collaboration, Dirk Bader, Dave V., Arjan B., Jeroen van Heek, Dennis Hobbelink, Yvette Roos, and everyone else!

Liberating Structures pitch 🥳 

Recently, someone left my public Liberating Structures meetup excited and ready to explain LS to their manager. Only to realise: while LS is easy to experience, it’s surprisingly hard to explain.

I totally get that. Every time I try, my explanation becomes abstract and vague… and instead of creating clarity, it creates confusion.

So I promised him to share a short, simple pitch. Something he could use to explain LS in just a few sentences, sparking enough curiosity to give it a try.

Here's the result. 👇 

====================================

Liberating Structures are simple facilitation techniques and interaction patterns that improve collaboration, decision-making, and trust. They ensure everyone has a chance to contribute, especially in larger groups.

Instead of long discussions dominated by a few voices, people work in small groups through short, structured interactions, quickly surfacing diverse perspectives.

This leads to:
✅ Better decisions, informed by a wider range of insights
✅ Higher engagement through active participation from everyone
✅ More creative solutions by tapping into the group’s collective intelligence

As a result, Liberating Structures make meetings and any gathering more effective, more inclusive, and simply more enjoyable. 🥳

====================================

Anything you'd remove, change, or add? 

PS: This illustration can also help explain Liberating Structures.

Liberating Structures in de praktijk! 🥳 

Ik heb mezelf voor dit jaar als doel gesteld om Liberating Structures (nog) meer zelf in de praktijk toe te passen. Ik wil voorkomen dat ik alleen LS "train" en alleen praktische voorbeelden kan delen van jaren geleden. Daarbij is het juist gaaf om te zien wat LS "in het echt" mogelijk kan maken! 

Deze week kreeg ik daarvoor een mooie gelegenheid op de "Werkconferentie WWZ038 Concilium". Het doel was om de 80-100 deelnemers van elkaar te laten leren en samenwerking tussen partijen te versterken. Denk aan de gemeente, corporaties, welzijns- en zorgpartijen, marktpartijen en provincie. 

Samen met Marijn Hofstee, en Annalies Idema - Hoornsman, hadden we een mooie flow van Liberating Structures bedacht:
👉 Presentatie door Sjoerd Feenstra
👉 Impromptu Networking om nieuwe connecties te maken, te reflecteren op de presentatie en als opwarming voor Conversation Cafe
👉 2x Conversation Cafe voor het delen en verdiepen van succesfactoren
👉 4-2-1-ALL voor het bepalen van concrete actiepunten en vervolgstappen

Dit alles werd vakkundig aan elkaar geknoopt door Martin Bleijenburg. 

Natuurlijk zijn we deels van het plan afgeweken. Tijd, energie, deelnemers en nieuwe inzichten zorgden voor wat last-minute aanpassingen, maar volgens mij waren dit uiteindelijke goede keuzes. 

Ook ik had de "stemmetjes" in mijn hoofd:
🤷‍♀️ "Gaat Impromptu Networking staand wel werken met deze groep in deze ruimte?"
🤷‍♂️ "Kunnen we het niet beter gewoon zittend doen?" 
🤷‍♀️ "Hoe gaat Conversation Café werken met de dynamische groepsvorming?"

Uiteindelijk is het een kwestie van gewoon doen met volle overtuiging en vertrouwen op de kracht van Liberating Structures! Ik kijk terug op een erg leuke middag en had de indruk dat dit voor meer deelnemers het geval was. 

Op naar de volgende "LS in de praktijk"-opdracht! Mocht je kansen zien, laat graag weten! 

Dank, Erik van der Spek voor deze mogelijkheid. 🙏

Columinity multi-team diagnose workshop bij Wigo4it 🥳

"Kijk, je vader mocht gisteren lekker ouderwets klassikaal lesgeven."

Wanneer ik een workshop heb gegeven, deel ik vaak wat foto’s met mijn gezin. In de hoop dat ze langzaam gaan begrijpen wat ik eigenlijk doe. Tot nu toe is het beeld vooral dat ik energieke, dynamische en interactieve workshops faciliteer.

Deze foto’s vroegen daarom om wat extra uitleg. 
🤔 Laptops
🤔 Bureaus
🤔 Een presentatie

Zeker!

Het doel van de sessie was om gezamenlijk meerdere teamscans te duiden, patronen te herkennen en concrete verbeteracties te formuleren.

In dit geval zaten vooral coaches in de ruimte. Zij gingen met de data aan de slag en onderzochten welke vraagstukken er werkelijk onder de resultaten lagen. Niet om besluiten voor de teams te nemen, maar om te leren hoe je dit soort gesprekken kunt voeren.

Twee thema’s kwamen daarbij duidelijk naar voren: hoe teams sneller kunnen releasen en hoe de samenwerking met stakeholders kan verbeteren.

Door samen betekenis te geven aan de data ontstond niet alleen meer begrip van deze vraagstukken, maar ook de motivatie om ermee verder te werken.

De volgende stap ligt nu bij de coaches: deze inzichten meenemen naar hun teams, managers en andere betrokkenen. Niet met kant-en-klare oplossingen, maar met gerichte vragen en eerste ideeën voor experimenten die ze samen verder kunnen onderzoeken en uitproberen.

Uiteindelijk gaat het niet om de data zelf, maar om de betekenisvolle gesprekken die ze op gang brengen. 💪 

Interesse om hierover meer te leren? Stuur gerust een bericht. 

PS: dank Ahmed Taha & Youri Schouten voor de fijne samenwerking!

Public Liberating Structures meetup EPAM Systems 🥳 

The monthly Liberating Structures meetups have quickly become my monthly highlight! Yesterday's meetup was another memorable gathering. This time, we focused on "Wicked Questions". 

Wicked Questions surface paradoxical challenges. They lead to powerful conversations and trigger tough/realistic choices, especially when tradeoffs are unavoidable. Simple to use, but not always comfortable. And that’s partly the point.

Examples of Wicked Questions are:

🤔 “How can we spend time on innovation, while also maintaining existing platforms?" 
🤔 "How can we standardize processes across teams, while also allowing local autonomy and creativity?"
🤔 "How can we move fast and experiment, while also ensuring stability and risk control?"

Together with ±20 participants we...
✅ Practiced the original Wicked Questions steps.
✅ Tried out different tweaks and variations.
✅ Learned how to combine it with other Liberating Structures.
✅ Exchanged experiences, ideas, and insights with others.
✅ Simply enjoyed good conversations and made new connections.

The flow we used was:
- Impromptu Networking focused on Friday the 13th
- Wicked Questions facilitated according to the "official" steps
- A self-facilitated Wicked Questions in small groups
- Shift & Share to share (online) tips, traps, combinations, and tweaks
- 25/10 Crowd Sourcing to generate questions and a simple open conversation to discuss them

This was definitely one of the most stunning views I've experienced in an office. It offered a beautiful view of the port of Amsterdam. 

Thanks for being such a gracious host, Sibylle Friedberg, and kudos to the supporting team, Guy Ben-Natan Grill, Olga Lavrienko, Bibiana Diaz del Castillo Koch. 🙏 

Interested in joining next month's meetup?
👉 Friday, April 10, 13:30 - 16:00
👉 Scrum Facilitators, Amersfoort
👉 Topic: Appreciative Interviews
👉 Registration: see the link in the first comment (turn on 'recent comments')

Use Appreciative Interviews to uncover and strengthen success factors 💪

It feels like almost everyone has either just gone through a reorganization, is in the middle of one, or is preparing for it. The reasons often point to AI, geopolitical tensions, or organizations bracing for “tougher times.” 

In these moments, organizations often focus heavily on problems. What’s broken? What needs fixing? That makes sense, but it can also make teams overlook something important: there are usually moments when things actually worked very well.

That’s where Appreciative Interviews, a Liberating Structure, can help. It invites people to explore successful experiences and learn from them. 

You can use it in two ways:
📌 Rediscover past success: identify moments when things worked well before and explore which success factors may be missing today.
📌 Strengthen current success: look at situations that are already going well and see how to amplify them.

👉 Step 1: Ask a clear question

- Past success: “When have you experienced this team or organization performing at its best?”
- Current success: “When do you currently see this team working really well?”

👉 Step 2: Interview in pairs
 People interview each other about their experience. Ask follow-up questions like: what made this possible, what did people do, and what conditions helped?

👉 Step 3: Look for patterns
 Pairs join another pair and identify recurring success factors.

👉 Step 4: Share insights
 Groups share the patterns they noticed with everyone.

👉 Step 5: Decide what to do next (with 15% Solutions)

Ask the group:
- What could we reintroduce from the past?
- What could we strengthen or spread today?

What I like about Appreciative Interviews is how quickly the conversation shifts. Instead of getting stuck in problems, people reconnect with strengths that already exist in the system.

People start telling real stories about moments when things actually worked well. That often makes the conversation more concrete. Rather than abstract statements like “we need better collaboration,” you hear what people actually did, what conditions helped, and what made the difference.

It also reminds teams that success is not hypothetical. It already happened at some point, somewhere in the organization. That makes it easier to ask a more constructive question: how could we create more of those moments again?

What is your experience with Appreciative Interviews? 
When & how have you used it?

From workshop to practice: 3 insights about Liberating Structures 🥳 

Last week, we did an online retrospective with participants from my previous public Liberating Structures Immersion Workshop. The goal was to share experiences with the structures they had used since the workshop.

Three insights that came up.

👉 Insight #1
Liberating Structures are often seen as methods for large workshops or events. I hear that from people who didn’t join the retrospective as well: “I haven’t had the chance to use them yet.” Meanwhile, calendars are packed with meetings. 🤷‍♀️ 

The strength of LS certainly shows in large groups. But smaller moments can benefit just as much:
- a 15-minute stand-up
- a quick 30-minute brainstorm
- a meeting or a presentation

That probably represents 80% of your sessions. Improve those, and the impact is often greater than that of the occasional large workshop.

👉 Insight #2
Practice using LS in a realistic space.

I’m fully aware that the Volkshotel (where the workshop takes place) is a pretty ideal workshop setting. Everything supports interaction. In most organizations, the reality is different. It often starts with simply finding an available room. Let alone one that is well set up.

And when the room screams “traditional meeting” (that big oak table in the middle), it can create a barrier to trying something interactive.

So here’s the idea: deliberately practice in suboptimal spaces. It often still works just fine. In fact, I personally enjoy the challenge of making LS work even in “crappy” rooms.

👉 Insight #3
Hybrid s*cks. Not a new insight. More of a confirmation.

What has been your experience with these topics?

On June 24–25, I’m running my last public Liberating Structures workshop in Amsterdam. Interested in joining? See the first comment (switch to “most recent” to find it).

taplio

The Battle

Paweł Huryn

Barry Overeem

Followers

Posts

Engagements

Likes

Performance ScorePaweł Huryn's LinkedIn Performance

Performance ScoreBarry Overeem's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Paweł Huryn

Barry Overeem

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Paweł Huryn's LinkedIn Performance

Performance ScoreBarry Overeem's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScorePaweł Huryn's LinkedIn Performance