\n| \n Liberating Structure<\/strong><\/p>\n<\/td>\n| \n Application in project management<\/strong><\/p>\n<\/td>\n| \n Briefly explained<\/strong><\/p>\n<\/td>\n<\/tr>\n\n| \n Appreciative Interview<\/strong><\/p>\n<\/td>\n| \n Identify success factors in retros or project closures<\/p>\n<\/td>\n | \n Partner interview about particularly positive experiences in order to derive strengths from them<\/p>\n<\/td>\n<\/tr>\n | \n| \n Troika Consulting<\/strong><\/p>\n<\/td>\n| \n Collegial advice on specific challenges in the project<\/p>\n<\/td>\n | \n One person presents a concern, two others take turns advising them<\/p>\n<\/td>\n<\/tr>\n | \n| \n 25\/10 Crowd sourcing<\/strong><\/p>\n<\/td>\n| \n Evaluate ideas for measures, features or suggestions for improvement<\/p>\n<\/td>\n | \n Everyone writes an idea, which is then evaluated by everyone over several rounds. This is how the top ideas prevail <\/p>\n<\/td>\n<\/tr>\n | \n| \n Nine Whys<\/strong><\/p>\n<\/td>\n| \n Clarification of overarching project goals and motivations<\/p>\n<\/td>\n | \n By asking \"Why?\" 9 times, a deeper purpose becomes visible<\/p>\n<\/td>\n<\/tr>\n | \n| \n Celebrity Interview<\/strong><\/p>\n<\/td>\n| \n Communicate goal clarification or change topics in a clear and entertaining way<\/p>\n<\/td>\n | \n One person takes on the role of a well-known personality and is interviewed on the subject of<\/p>\n<\/td>\n<\/tr>\n | \n| \n Drawing Together<\/strong><\/p>\n<\/td>\n| \n Making complex relationships or processes visible<\/p>\n<\/td>\n | \n Participants visualize their project vision or collaboration, for example<\/p>\n<\/td>\n<\/tr>\n | \n| \n Impromptu Networking<\/strong><\/p>\n<\/td>\n| \n Entry into workshops, promotion of personal exchange<\/p>\n<\/td>\n | \n Several short 1:1 conversations on prepared questions<\/p>\n<\/td>\n<\/tr>\n | \n| \n Heard, Seen, Respected<\/strong><\/p>\n<\/td>\n| \n Empathic understanding of conflicts or emotional issues in the team<\/p>\n<\/td>\n | \n Partners share difficult situations - without judgment, just listening<\/p>\n<\/td>\n<\/tr>\n | \n| \n Helping Heuristics<\/strong><\/p>\n<\/td>\n| \n Promote knowledge sharing or coaching within the team<\/p>\n<\/td>\n | \n Mutual aid guidelines are reflected upon and improved<\/p>\n<\/td>\n<\/tr>\n | \n| \n Open Space<\/strong><\/p>\n<\/td>\n| \n Topic-centered work in large groups<\/p>\n<\/td>\n | \n Participants bring in their own topics and organize sessions themselves<\/p>\n<\/td>\n<\/tr>\n | \n| \n Panarchy<\/strong><\/p>\n<\/td>\n| \n Expand understanding of system interrelationships and dynamics in the project environment<\/p>\n<\/td>\n | \n Consideration of topics at different system levels (e.g. micro\/macro)<\/p>\n<\/td>\n<\/tr>\n | \n| \n Ecocycle <\/strong><\/p>\n<\/td>\n| \n Gain an overview of ongoing, planned and blocked activities<\/p>\n<\/td>\n | \n activities into four fields: Birth, Maturity, Creative Destruction, Renewal<\/p>\n<\/td>\n<\/tr>\n | \n| \n Integrated Autonomy<\/strong><\/p>\n<\/td>\n| \n Reflecting on the balance between personal responsibility and team coordination<\/p>\n<\/td>\n | \n Reflection on tensions between freedom and coordination<\/p>\n<\/td>\n<\/tr>\n | \n| \n Social Network Webbing<\/strong><\/p>\n<\/td>\n| \n Analyze stakeholder networks<\/p>\n<\/td>\n | \n Making relationships and communication flows visible<\/p>\n<\/td>\n<\/tr>\n | \n| \n Simple Ethnography<\/strong><\/p>\n<\/td>\n| \n Understanding user needs<\/p>\n<\/td>\n | \n Observation of real behavior instead of just questioning<\/p>\n<\/td>\n<\/tr>\n | \n| \n Design storyboards<\/strong><\/p>\n<\/td>\n| \n Making projects or processes visible as \"history\"<\/p>\n<\/td>\n | \n Create a sequence of images or scenes to make processes understandable<\/p>\n<\/td>\n<\/tr>\n | \n| \n Wicked Questions<\/strong><\/p>\n<\/td>\n| \n Making contradictory requirements visible in the project<\/p>\n<\/td>\n | \n Formulate opposing but equally important questions<\/p>\n<\/td>\n<\/tr>\n | \n| \n Wise Crowds<\/strong><\/p>\n<\/td>\n| \n Making complex decisions in a participatory manner<\/p>\n<\/td>\n | \n One person describes a concern, group discusses in a structured way with observers<\/p>\n<\/td>\n<\/tr>\n | \n| \n Discovery & Action Dialogue<\/strong><\/p>\n<\/td>\n| \n Joint problem solving for difficult situations in the project<\/p>\n<\/td>\n | \n Participants jointly analyze causes and develop practicable solutions<\/p>\n<\/td>\n<\/tr>\n | \n| \n Min Specs<\/strong><\/p>\n<\/td>\n| \n Focus on the essentials in project rules or framework conditions<\/p>\n<\/td>\n | \n Distinction between mandatory and optional criteria<\/p>\n<\/td>\n<\/tr>\n | \n| \n What I Need From You (WINFY)<\/strong><\/p>\n<\/td>\n| \n <\/p>\n Clarification of expectations and support in the team or with stakeholders<\/p>\n<\/td>\n | \n People clearly formulate what they need from others - and what they can offer<\/p>\n <\/p>\n<\/td>\n<\/tr>\n | \n| \n Critical Uncertainties<\/strong><\/p>\n<\/td>\n| \n Develop scenarios for unclear project dynamics<\/p>\n<\/td>\n | \n Confronting two uncertainties and developing strategies<\/p>\n<\/td>\n<\/tr>\n | \n| \n Agree\/Certainty Matrix<\/strong><\/p>\n<\/td>\n| \n Clarifying how to deal with complex decision-making situations<\/p>\n<\/td>\n | \n Classify problems according to the degree of unity and security and find suitable strategies<\/p>\n<\/td>\n<\/tr>\n | \n| \n Purpose-to-Practice<\/strong><\/p>\n<\/td>\n| \n Structure project start from vision to implementation<\/p>\n<\/td>\n | \n Jointly define goal, principles, participants, structures, practices<\/p>\n<\/td>\n<\/tr>\n | \n| \n Impromptu prototyping<\/strong><\/p>\n<\/td>\n| \n <\/p>\n Making ideas tangible at an early stage, generating feedback<\/p>\n<\/td>\n | \n <\/p>\n Concepts or processes are quickly sketched or played to encourage reactions and insights<\/p>\n<\/td>\n<\/tr>\n | \n| \n User Experience Fishbowl<\/strong><\/p>\n<\/td>\n| \n Experience user feedback directly and openly<\/p>\n<\/td>\n | \n Users speak in an inner circle, team listens actively<\/p>\n<\/td>\n<\/tr>\n | \n| \n Generative Relationships<\/strong><\/p>\n<\/td>\n| \n <\/p>\n Strengthening collaboration through relationship quality<\/p>\n<\/td>\n | \n Reflection on which relationships are beneficial in the project and how to actively maintain them<\/p>\n <\/p>\n<\/td>\n<\/tr>\n | \n| \n Shift & Share<\/strong><\/p>\n<\/td>\n| \n Disseminate best practices within the project team<\/p>\n<\/td>\n | \n Small groups rotate through stations with success stories<\/p>\n<\/td>\n<\/tr>\n | \n| \n 15% Solutions<\/strong><\/p>\n<\/td>\n| \n Strengthen personal responsibility, identify small, feasible steps<\/p>\n<\/td>\n | \n Everyone thinks about what he or she can implement immediately - without additional resources or approval<\/p>\n<\/td>\n<\/tr>\n | \n| \n Conversation Caf\u00e9<\/strong><\/p>\n<\/td>\n| \n Open dialog on complex or sensitive topics<\/p>\n<\/td>\n | \n In rounds, everyone talks about a key question, with a focus on listening, understanding and changing perspectives<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n\t\t\t<\/div> \n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t <\/span>Best practices for use in the project environment<\/span><\/h2>\n\n- \n
Start small:<\/strong> You don't have to turn the entire project upside down immediately with LS. One method in a workshop is enough to get you started and to test whether the Liberating Structures work for your team and your needs. <\/p>\n<\/li>\n- \n
Prepare the moderation:<\/strong> Even if LS seem simple, a clear process, time frame and roles are essential.<\/p>\n<\/li>\n- \n
Prepare participants:<\/strong> Especially in formal settings, a brief context helps, e.g. why everyone stands up or writes cards at the same time.<\/p>\n<\/li>\n<\/ol><\/div>\n\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t Common pitfalls - and how to avoid them<\/h2>\n\n- \"Let's do something new\" without a goal:<\/strong> LS are not an end in themselves. Every structure needs a clear objective that it is intended to achieve. The appropriate structure is then selected depending on the objective. <\/li>\n
- Too many methods at once:<\/strong> one, well-applied structure is enough. Otherwise, \"unfolding freely\" quickly becomes \"wildly tangled\". <\/li>\n
- False expectations:<\/strong> LS do not work miracles immediately, but invite you to develop together. Those hoping for finished results may be happier with a classic brainstorming session. <\/li>\n<\/ul><\/div>\n\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t<\/div>
\n\t\t\t\t \n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t \n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
![\"Liberating](\"https:\/\/parm.com\/wp-content\/uploads\/2025\/05\/Post_Liberating_Structures.jpg\" "\\"Post_Liberating_Structures\\"")
<\/span>\n\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t<\/div>