Collaborative Design Problem-Solving Techniques

What’s the difference? Problem Framing vs. Foundation Sprint vs. Design Sprint. Before discussing differences, let’s talk about the one thing they have in common—and why every team should use these methods. They break the norm of work as usual: 🚫 Siloed teams 🚫 Endless meetings with no decisions 🚫 Juggling multiple priorities but making little progress Work as usual keeps us busy. It’s soul sucking. Instead, these methods are about bursts of work that give teams intense focus to tackle one important goal collaboratively. But…when do you use which one? 🎯Problem Framing When to use it: ✅ When dealing with complex problems ✅ When uncovering root causes before jumping to solutions ✅ When you need leadership buy-in for high-stakes decisions Format: 1-day workshop (with heavy pre-work) Level: strategic Who’s involved: Leadership, senior stakeholders (6-8 people) Difficulty: Hard – requires deep preparation and skilled facilitation Key Inputs: Customer insights, data, business goals Key Output: A validated problem statement or opportunity ❓Foundation Sprint When to use it: ✅ When you have a general solution approach but need to refine it ✅ When exploring alternative strategies before committing ✅ When you want to align a team quickly Format: 2-day workshop Level: both strategic & tactical Who’s involved: Founders & leadership (startups) / Decision-makers & SMEs (enterprises) Difficulty: Medium – no pre-work required, but deep thinking needed Key Inputs: Team knowledge, expertise, and insights Key Output: A hypothesis that needs testing 🚀Design Sprint When to use it: ✅ When the problem is well-defined ✅ When you need to rapidly test solutions with real users ✅ When you want quick validation before building Format: 4-day workshop Level: tactical/operational Who’s involved: Cross-functional team, SMEs (7-10 people) Difficulty: Easy but intense work – clear steps, structured process Key Inputs: Validated problem statement (from Problem Framing) OR Founding Hypothesis (from Foundation Sprint) Key Output: A customer-tested prototype Which One Should You Use? 👉 If the problem is unclear or complex, start with Problem Framing—especially in enterprises where stakes are high and risk is a major concern. 👉 If you feel confident about a solution but want to test different angles, use a Foundation Sprint to challenge your assumptions and align the team. 👉 Once you’re ready to validate a solution with real users, the Design Sprint helps you quickly test and refine before investing in execution. TL;DR: Problem Framing → Foundation Sprint → Design Sprint. Each plays a different role, but together, they create a structured system for solving problems and validating solutions efficiently. More importantly, they help people work together and actually enjoy it.

Passionate problem solvers are easy to label as "too negative" or "having an agenda". Here's a good approach to bringing people on the journey: 1. Start with what you see and hear Describe specific behaviors, patterns, or outcomes as objectively as possible (knowing that we can never be truly objective). Be mindful of your potential biases. Are your emotions and perspective narrowing what you bring up? Avoid using loaded or triggering language. Keep it neutral and clear. 2. Invite others to share what they see and hear By starting with your own observations, you are setting an example for the rest of the team. Invite the team to share their perspectives and observations in ways that focus on understanding, rather than labeling or jumping to conclusions. In the right context, it might be better to start here. 3. Look inwards, observe, and listen Just as you describe outward behaviors, turn inward and notice how you feel about what you’re seeing and hearing. Instead of saying, “This place is a pressure cooker,” try, “I feel a lot of pressure.” Avoid jumping to conclusions or ascribing blame. Again, invite other people to do the same. 4. Spot areas to explore With observations and emotions on the table, identify areas worth examining. Avoid rushing to label them as problems or opportunities. Instead, frame them as questions or areas to look into. This keeps the tone open and focused on discovery. 5. Explore and go deeper As potential areas emerge, repeat the earlier steps: describe what you see, invite others to share, and observe how you feel. It is a recursive/iterative process—moving up and down levels of detail. 6. Look for alignment and patterns Notice where people are starting to align on what they’d like to see more—or less—of. Pay attention to areas where there’s consistent divergence—these are opportunities as well. Ask, “What might it take to narrow the divide?” 7. Frame clear opportunities Once patterns emerge, focus on turning them into clear opportunities. These are not solutions—they’re starting points for exploration. For example: “We could improve this handoff process” or “We’re not all on the same page about priorities.” Keep it actionable and forward-looking. 8. Brainstorm small experiments Use opportunities as a springboard to brainstorm simple, manageable experiments. Think of these as ways to test and learn, not perfect fixes. For example: “What if we tried a weekly check-in for this process?” Keep the ideas practical and easy to implement. 9. Stay grounded and flexible Be mindful of how the group is feeling and responding as you brainstorm. Are people rushing to solutions or becoming stuck? If so, take a step back and revisit earlier steps to re-center the group. 10. Step back. Let the group own it Once there’s momentum, step back and hand over ownership to the group. Avoid holding onto the issue as “your problem.” Trust the process you’ve built and the team’s ability to move things forward collectively.

One of the world’s largest companies told us "We need all the digital for the CES trade show booths ready in weeks." We said no. This was a huge opportunity, and someone else said yes….AND, they failed to deliver it (it was a mission doomed to failure). The easy path is saying “yes” to every piece of work that pays. The hard path is saying “no” to everything that isn’t going to be successful. The way to “win” is finding a win for both parties. When a client comes with an "impossible" timeline, we don't immediately reject it – sometimes we are even known as people who pull off the impossible. We can do this because we transform these situations into a collaborative problem-solving exercise: "If that date is your constraint, then let's adjust what we deliver and how we work together." This solution-finding approach has become our superpower. We move multiple levers simultaneously — scope, process, team structure, and feedback cycles — until we find a configuration that works. Sometimes, that means delivering 5 pages instead of 20, in time for the event, with a clear path to complete the rest quickly. Sometimes, it means restructuring the team to have fewer people with less hurdles dedicated 100% to the project. The magic happens when we treat clients as partners in solving the problem, not just buyers of services. We empower them with choices rather than ultimatums. This isn't just about managing expectations — it's about creating a partnership where both sides are invested in finding the best possible solution within the constraints.

How the Double Diamond method helped me think and design better at Microsoft: I wish I learned the Double Diamond design process earlier at Microsoft. The Double Diamond is a tool that can help more leaders solve problems better. Too many people run around with a hammer looking for a nail: "If the only tool you have is a hammer, you tend to see every problem as a nail." -- Abraham Maslow And too many people brainstorm the solution, without even brainstorming the problem. The Double Diamond helps fix this. How? 𝗧𝗪𝗢 𝗗𝗜𝗔𝗠𝗢𝗡𝗗𝗦 𝗢𝗙 𝗧𝗛𝗘 𝗗𝗢𝗨𝗕𝗟𝗘 𝗗𝗜𝗔𝗠𝗢𝗡𝗗 The Double Diamond is a design thinking approach with two diamonds: 1. 𝗧𝗵𝗲 𝗣𝗿𝗼𝗯𝗹𝗲𝗺 𝗦𝗶𝗱𝗲: The first diamond represents the problem side. 2. 𝗧𝗵𝗲 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗦𝗶𝗱𝗲: The second diamond represents the solution side. That right there helps. I had a manager early on at Microsoft that would run up and tell me I had to solve Y. But Y was a solution. I didn't even know what the problem was yet. Neither did he. Now when somebody brings me a "problem" to solve, I ask them: "Are we on the problem side or the solution side?" 𝗧𝗛𝗘 𝗣𝗢𝗪𝗘𝗥 𝗢𝗙 𝗗𝗜𝗩𝗘𝗥𝗚𝗜𝗡𝗚 + 𝗖𝗢𝗡𝗩𝗘𝗥𝗚𝗜𝗡𝗚 The second aspect of the Double Diamond that I find useful is diverging and converging. When you are brainstorming and expanding you are diverging. You are diverging when you brainstorm the problem or the solution. When you are narrowing or contracting the range of options, you are converging. You are converging when you narrow the problem and narrow the solution. Now when someone brings me a "problem" to solve, I ask them: "Are we exploring the solution, or did you already have one in mind?" "Are we exploring the problem, or are you already set on the problem?" 𝗣𝗥𝗢𝗕𝗟𝗘𝗠 𝗦𝗜𝗗𝗘 𝗢𝗥 𝗦𝗢𝗟𝗨𝗧𝗜𝗢𝗡 𝗦𝗜𝗗𝗘, 𝗘𝗫𝗣𝗔𝗡𝗗𝗜𝗡𝗚 𝗢𝗥 𝗖𝗢𝗡𝗧𝗥𝗔𝗖𝗧𝗜𝗡𝗚? It sounds simple, yet years at Microsoft taught me that even smart people can fall for traps. With the Double Diamond in mind, you have a simple approach to remind you to: 1.  𝗦𝗼𝗹𝘃𝗲 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 2.  𝗦𝗼𝗹𝘃𝗲 𝘁𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗿𝗶𝗴𝗵𝘁 With the Double Diamond, you can quickly visually check: 1. 𝘼𝙧𝙚 𝙮𝙤𝙪 𝙤𝙣 𝙩𝙝𝙚 𝙥𝙧𝙤𝙗𝙡𝙚𝙢 𝙨𝙞𝙙𝙚 𝙤𝙧 𝙩𝙝𝙚 𝙨𝙤𝙡𝙪𝙩𝙞𝙤𝙣 𝙨𝙞𝙙𝙚? 2. 𝘼𝙧𝙚 𝙮𝙤𝙪 𝙙𝙞𝙫𝙚𝙧𝙜𝙞𝙣𝙜 𝙤𝙧 𝙘𝙤𝙣𝙫𝙚𝙧𝙜𝙞𝙣𝙜? Sometimes all it takes is a quick check to remember where you are in the process. 𝗚𝗘𝗧 𝗧𝗘𝗔𝗠𝗦 𝗢𝗡 𝗧𝗛𝗘 𝗦𝗔𝗠𝗘 𝗣𝗔𝗚𝗘 Even better, the Double Diamond gives you a way to orient teams. It's rare to find everyone on the same page when it comes to solving problems. Some people are brainstorming the solution. Some are exploring the problem. Some are diverging, while others are converging. But if you use the Double Diamond you can at least check in and get people on the same page. This is where having a simple process can shine. #innovation #leadership #creativity  

Wanna increase your organization's ability to learn? 👀 I’m a big fan of frameworks. Although they are an oversimplification of reality, they give us a way to start when we don’t know exactly what the first step is. Systems thinking, experience design, behavioral science, and other disciplines have come up with AMAZING ways for discovery, design, measurement, and experimentation and I chose a few of my favorites to share with you. 💜 ✨ For discovery you can use － The Iceberg Model to uncover hidden factors that shape your learning culture － Causal Loop Diagrams to map feedback loops and understand how different elements influence learning behaviors － The Fishbone Diagram to identify and analyze the potential causes of the discovered problems － The Self-Determination Theory to identify if people have the incentives to be internally motivated, and act upon the results. ✨ For strategy & design, you can use － The Impact - Effort Matrix to prioritize problems or solutions based on their impact (how much they will contribute to goals) and the effort required to solve them － Participatory Design to involve everyone directly in the design process to ensure solutions are relevant and user-centered. － Kotter’s 8-Step Change Model to create a plan for change and sustain it long-term － Appreciative Inquiry to increase awareness about the initiatives that already work well, and scale them ✨ For implementation, you can use: － Communities of Practice to build peer networks for ongoing knowledge sharing and problem-solving － Co-Development to create spaces where peers collaborate to solve real challenges, share insights, and co-create solutions through structured group discussions. － Action Learning to use real problems to drive team learning and reflection. ✨ For measurement, you can use: － Randomized Control Tests to test solutions on a small scale, measuring their impact and ensuring they deliver the desired results before scaling up. What's another one you'd add to the list? 💬 #learninganddevelopment #learningarchitecture

Forget top-down decision-making. Collaboration is the ultimate problem-solving superpower. It amplifies perspectives. It sparks innovation. It builds solutions that stick. Here’s 11 ways collaborative voices can revolutionize your solutions: 1/ Diverse Perspectives: Unlock Hidden Angles → Every voice brings unique insights to the table. → From frontline workers to execs, varied viewpoints spot blind spots. 💡 Leaders: Host cross-functional brainstorms to capture diverse ideas. 2/ Collective Creativity: Ignite Breakthrough Ideas → Collaboration fuels sparks that solo thinkers miss. → Group dynamics turn good ideas into game-changers. 💡 Teams: Use ideation tools to crowdsource creative solutions. 3/ Shared Ownership: Build Buy-In from the Start → When voices shape the solution, commitment follows. → Co-creation ensures everyone’s invested in success. 💡 Managers: Involve teams early in planning to foster accountability. 4/ Real-Time Feedback: Refine Ideas on the Fly → Collaborative rooms catch flaws before they grow. → Instant input sharpens solutions in real time. 💡 Teams: Use platforms like Slack for quick, open feedback loops. 5/ Cultural Alignment: Solutions That Reflect Values → Inclusive voices ensure solutions fit the organization’s ethos. → They bridge gaps between strategy and culture. 💡 Leaders: Invite voices from all levels to align solutions with core values. 6/ Problem-Solving Agility: Adapt Faster Together → Collaborative teams pivot quickly when challenges arise. → Shared knowledge speeds up course corrections. 💡 Teams: Run agile sprints with diverse contributors to stay nimble. 7/ Knowledge Sharing: Amplify Expertise → Every voice adds specialized know-how to the mix. → Collective wisdom outperforms individual expertise. 💡 Managers: Create knowledge hubs for teams to share insights. 8/ Conflict as Catalyst: Turn Tension into Progress → Differing opinions spark deeper exploration. → Healthy debate refines solutions to their strongest form. 💡 Leaders: Foster safe spaces for constructive disagreement. 9/ Inclusive Decision-Making: Solutions That Serve All → Voices from all corners ensure equitable outcomes. → Inclusive processes build trust and fairness. 💡 Teams: Use anonymous voting tools to democratize decisions. 10/ Momentum Through Motivation: Energize the Room → Collaborative environments inspire action. → Shared purpose drives teams to execute with passion. 💡 Managers: Celebrate collective wins to keep morale high. 11/ Scalable Solutions: Built to Last → Solutions shaped by many are robust and adaptable. → They withstand scrutiny and evolve with needs. 💡 Leaders: Document collaborative processes to replicate success. Collaboration redefines problem-solving by blending voices into solutions that are smarter, stronger, and more sustainable. __________ ♻️ Repost if your network needs these reminders. Follow Carolyn Healey for real-world leadership insights.

Are you showing admiration for a problem? I listened to someone on the phone the other day, basically for the day, “admiring the problem”. If that whole 8 or so hours could have been spent on solution seeking, asking “what’s right with this?” the person and their team might be a little ahead. To move beyond this unproductive #mindset, here are some strategies people can adopt: 1. Reframe the Problem • Shift the focus from describing the problem to exploring opportunities for change. • Use solution-oriented language, such as “How might we…?” 2. Clarify the Desired Outcome • Define the goal or the ideal state you want to achieve. • Ask, “What does success look like?” 3. Break It Down • Deconstruct the problem into smaller, manageable pieces. • Address each part with specific actions. 4. Prioritize Action Over Analysis (Paralysis) • Set a time limit for discussing the problem, then transition to brainstorming solutions. • Encourage trying small, experimental solutions (e.g., prototyping in #designthinking). 5. Adopt a #Collaborative Approach • Engage diverse perspectives to generate ideas and build momentum. • Create an environment where everyone feels safe to contribute solutions. 6. Use Frameworks and Tools • Apply structured tools like root cause analysis, the 5 Whys, or SWOT analysis to understand and address the issue. • Visualize the path forward with a decision matrix or action plan. 7. #Empower Accountability • Assign ownership for tasks and follow up on progress. • Build systems that encourage responsibility, such as regular check-ins or deadlines. 8. Encourage a Bias Toward Experimentation • Shift from “getting it perfect” to “getting it started.” • View failures as learning opportunities. 9. Challenge Complacency • Ask tough questions to disrupt the cycle of inaction: • “What happens if we don’t solve this?” • “What’s one thing we could do right now to make progress?” 10. Leverage Emotional Intelligence • Identify emotional barriers, such as fear or frustration, that might keep people stuck. • Foster optimism and resilience in the face of challenges.

Interactive planning, developed by Russell L. Ackoff, revolutionizes traditional problem-solving in organizations by addressing interconnected issues, or ‘messes,’ holistically. Disillusioned with the technique-driven focus of operational research, Ackoff promoted participative and systemic approaches. This method involves diverse stakeholders in a collaborative redesign process, treating problems as interconnected systems rather than isolated issues. Ackoff argued that solving problems individually often leads to short-term success but long-term failure due to new issues arising. Interactive planning represents a shift towards a systemic worldview, emphasizing root cause analysis and collaborative innovation. It is particularly relevant in today’s volatile, uncertain, complex, and ambiguous (VUCA) world, where traditional methods may fall short. Ackoff’s ideas laid the foundation for Problem Structuring Methods and influenced the systems thinking community globally. This approach, known for its adaptability, fosters sustainable competitive advantage through stakeholder engagement and intellectual asset utilization, providing a sense of security and confidence in its applicability. In summary, interactive planning addresses complex organizational challenges by embracing complexity, encouraging participative problem-solving, and fostering innovation through a systemic lens. It continues to shape systems theory and organizational development today. #systemsthinking #designthinking #Strategicplanning #changemanagement #complexproblemformulation https://lnkd.in/er8V3eei

A designer’s role in multidisciplinary creative collaboration In the world of product development, the most innovative solutions often result from intense collaboration across diverse perspectives Diversity comes in many flavors… cultural, gender, specialties, disciplines, skillsets and more Let’s talk about the designer's role in a multidisciplinary setting As designers, we're more than just creators We’re the translators, mediators, and catalysts that bring different perspectives together to shape meaningful products and experiences When we worked on the John Deere 1R electric tractor at BMW Designworks, our core team consisted of designers, engineers, product marketers, and model makers We were a small but accomplished group of around six people, united by one common goal… to design, engineer, and convert a 1R combustion tractor into a drivable 1R electric tractor Looking back, my roles as the creative director and lead designer wasn’t just about designing and building the tractor… it became a lot more than that… _Translator... Acting as the bridge between engineering, marketing, and business strategy, turning complex ideas into tangible, user-centric solutions. Clear communication was crucial to ensure everyone understood the project's vision and goals… and stay on track _Holistic Problem Solver... Integrating insights from various disciplines allowed us to approach problems from multiple angles in real time. It's about finding solutions that are both innovative and feasible, balancing creativity with practicality _Rapid Prototyping & Iteration... True innovation requires rapid iteration with input from all corners. By involving designers, engineers, and model makers in the prototyping phase, we could address real-world constraints while keeping the user experience front and center _Aligning a Shared Vision... Design isn't just about aesthetics… it's about empathy. By aligning with other disciplines on a user-centric goal, we ensured every aspect of the product resonated with the people it was designed for _Mediating Ideas and Realities... Navigating the delicate balance between bold ideas and practical limitations was key. We had limited time, and our role was to champion creativity while mediating conflicts, ensuring the final product was both innovative, viable and on time _Championing Innovation Together... Collaboration is about co-creation. By combining diverse expertise, we were able to push boundaries, generate breakthrough ideas, and build products that truly stood out _Building a Collaborative Culture... Great design emerges when we acknowledge and celebrate diverse contributions. It’s about fostering a collaborative culture where every voice is heard and every idea is valued The magic happens when we bring together minds from different disciplines to create something that none of us could have achieved alone. In your experience, how has cross-disciplinary collaboration impacted your design process?