How to Structure Problem-Solving Methods

🎯 Why Most Business Problems Remain Unsolved (And How to Fix That) Last week, I had the privilege of facilitating a Problem Solving & Business Acumen workshop for our teams at L'Oréal Indonesia. 💡 The Problem We All Face (But Rarely Talk About) Here's an uncomfortable truth: we're wired to jump to solutions. In business, this looks like: ✔️ Launching promotions without understanding why sales declined ✔️ Hiring more people without diagnosing process inefficiencies ✔️ Copying competitor tactics without validating if they fit our context The cost? Wasted resources, frustrated teams, and recurring problems that never truly go away. According to the World Economic Forum's Future of Jobs Report 2023, analytical and critical thinking are the #1 and #2 most important skills for workers. Yet, most of us were never formally taught how to think critically or solve problems systematically. 🛠️ The Problem-Solving Process: A Step-by-Step Guide Step 1: Define the Problem (Don't Jump to Judgment!) 📝 Craft a Problem Statement with 6 components: "How can [responsible party] improve/reduce [reality] to meet [expectation] within [timeline] without [anti-goals], in order to fulfill [reason]?" Example: "How can the product team launch a new product on time in Q4 2024 without sacrificing key processes, in order to meet the sales target?" Step 2: Find Alternatives (Issue Tree + MECE) Once the problem is clear, break it down using an Issue Tree. For instance, if mascara sales dropped -14% YoY: 📦 Placement → Gondola compliance, visibility, signage 🎁 Promotion → BOGO mechanics, POS materials 💰 Price → Elasticity, perceived value 🎨 Product Claims → Content freshness, reviews 🔥 Competition → Share of voice, endcap presence ✅ Ensure hypotheses are MECE (Mutually Exclusive, Collectively Exhaustive)—no overlaps, no gaps. Step 3: Test Your Hypotheses Don't fall in love with your first idea. Run quick tests: 📊 For a skincare serum declining in pharmacies, we tested: ✔️ Hypothesis A: Reduced pharmacist advocacy is the issue → Micro-detailing pilot in 10 stores ✔️ Hypothesis B: Cold chain OOS drives lost sales → Warehouse SOP audit + temperature logs ✔️ Hypothesis C: Execution gaps suppress promo ROI → Endcap compliance audit Each hypothesis had clear KPIs and timelines—no guessing, just data. Step 4: Make the Decision (Impact vs. Effort Matrix) Not all solutions are equal. Prioritize: 🟩 Quick wins—do this! 🟦 Strategic bets 🟨 Fill-ins 🟥 Avoid Focus on low effort, high impact moves first. Build momentum, then tackle the big bets. 🚨 What Happens When We Skip These Steps? A mascara brand saw sales drop -14% YoY. The reaction? "Let's run a BOGO promo!" The result? Sales stayed flat. Why? Because the real issues were: ❌ Poor gondola compliance (only 68% correct facings) ❌ Weak influencer share of voice ❌ Competitor secured prime endcap space The lesson: Solutions applied to the wrong problem = wasted budget and missed targets.

Most candidates practice interviews the wrong way. They just… rehearse answers in their heads. ❌ No structure. ❌ No stress simulation. ❌ No feedback loop. And then they wonder why they go blank when the real interview starts. If you want to actually master problem-solving under stress → Here’s the step-by-step mock interview framework I use to train my students who now work at Google, Amazon, Deloitte & more: 🧩 Step 1: Simulate the Stress, Don’t Avoid It Your brain can’t learn resilience in comfort. 👉 Set a timer for 2 minutes to answer each problem. 👉 Ask a friend/mentor to throw curveball follow-ups. 👉 Record yourself to see body language under pressure. This mimics real interview tension → making stress your training partner, not your enemy. 🧩 Step 2: Use the CFS Formula to Structure Every Answer Every problem-solving response must hit these 3 beats: 👉 Clarify: Restate the problem in your words (“If I understood correctly, the issue is…”). 👉 Frame: Lay out 2–3 logical buckets (MECE principle). 👉 Solve: Dive into each bucket with reasoning + examples. This ensures clarity even if nerves hit. 🧩 Step 3: Practice the Think-Aloud Method According to MIT research, interviewers rate candidates higher when they can follow their reasoning. Instead of silently panicking → verbalize: “I see two possible causes for this issue… Let me evaluate both.” This signals confidence and buys time. 🧩 Step 4: Apply the Red Team Test Before finalizing your solution, challenge it. Ask yourself: “If I were the interviewer, how would I poke holes in this?” This trains you to anticipate objections and build stronger answers. 🧩 Step 5: Run the Reflect-Refine Loop After each mock session: 👉 Write down exactly where you froze. 👉 Note what structure saved you (CFS, MECE, etc.). 👉 Refine → Run again. Within 5–6 cycles, you’ll notice dramatic improvements. Interviewers aren’t looking for instant geniuses. They’re looking for candidates who show: ✅ Calm thinking ✅ Clear structure ✅ Resilience under pressure And those skills are built in practice rooms, not just interview rooms. If you follow this framework, you won’t just “answer questions.” You’ll prove you can think like the kind of professional every company wants on their team. Would you like me to also share a real problem-solving case study (with sample answers) from one of my students who cracked a top consulting firm? Comment “Case Study” and I’ll post it next. #interviewtips #mockinterview #careergrowth #dreamjob #interviewcoach

🎯 400 LeetCode problems solved - but this isn't your typical "grinding problems" post. Like training a machine learning model, I approached algorithmic problem-solving with a focus on data quality and diversity. Just as ML models need varied, high-quality data points to generalize well, I found that solving diverse problems across different patterns and domains builds better problem-solving intuition. My systematic approach: Pre-coding Analysis (Link to sample doc in comments) • Document multiple potential approaches • Analyze time & space complexity for each approach • Think through tradeoffs before writing any code • Consider edge cases and constraints Practice Execution • Used stopwatch to measure performance • Aimed to solve while explaining clearly within: - Easy: 10 minutes - Medium: 15 minutes - Hard: 25 minutes • Focus on thinking aloud - crucial for interviews Deep Dive Process • Rigorous complexity analysis • Explore optimization opportunities • Document learnings and patterns • Regular mock interviews on Pramp The goal wasn't to solve all 3000+ problems, but to build a robust "model" that could generalize to new problems effectively. Each solved problem is like a new training data point, helping my brain recognize patterns and edge cases. Key learning: The magic happens in the pre-coding analysis. Writing down different approaches and analyzing tradeoffs before coding helped me: - Build stronger problem-solving intuition - Communicate my thought process clearly - Make better engineering decisions - Save time during actual coding I'll share a sample doc in the comments. It's been crucial for building a systematic approach to problem-solving. To those on this journey: Keep your head down, document your thinking, and remember - you're not just solving problems, you're building a framework for approaching any technical challenge.

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.

Most people chase quick fixes. Here's how experts actually solve problems. The blueprint for solving problems effectively: 1. IDEAL Framework ↳ Identify the problem ↳ Define the context ↳ Explore possible strategies ↳ Act on the best strategy ↳ Look back and learn 2. 5 Whys Technique ↳ Ask "Why?" repeatedly ↳ Dig deeper beyond surface symptoms ↳ Find root causes of problems 3. Design Thinking ↳ Empathise with user needs ↳ Define the problem clearly ↳ Ideate creative solutions ↳ Prototype low-fidelity versions ↳ Test and refine with feedback Expert frameworks for structured problem-solving: PDCA Cycle ↳ Plan: Identify and analyse ↳ Do: Implement solutions ↳ Check: Evaluate results ↳ Act: Standardize or restart OODA Loop ↳ Observe: Collect information ↳ Orient: Analyse and synthesise ↳ Decide: Choose action ↳ Act: Follow through Kepner-Tregoe Method ↳ Situation Appraisal ↳ Problem Analysis ↳ Decision Analysis ↳ Potential Problem Analysis The biggest mistake isn't trying to solve problems. It's not using a systematic approach when needed. ♻️ Reshare to help others solve problems better. 🔔 Follow Luke Tobin for more problem-solving insights.

Want to solve problems like a McKinsey consultant? Top strategy firms like McKinsey, BCG, and Bain rely on a structured, hypothesis-driven approach to tackle complex challenges. The McKinsey Problem-Solving Process: Define the Problem Craft a clear, concise problem statement to ensure alignment among stakeholders. Structure the Problem Break down the problem into smaller, manageable components using frameworks like issue trees. Prioritize Issues Identify which components have the most significant impact and address them first. Develop a Work Plan Outline the analyses needed, assign responsibilities, and set timelines. Conduct Analyses Gather data and test hypotheses to uncover insights. Synthesize Findings Combine insights into a coherent story that addresses the problem. Develop Recommendations Formulate actionable solutions backed by data and analysis. Communicate Results. Key Principles: Hypothesis-Driven: Start with an educated guess and test it. MECE Framework: Ensure components are Mutually Exclusive and Collectively Exhaustive. Iterative Process: Refine your approach as new information emerges. Learn More: For a deeper dive into this methodology, check out McKinsey's guide on mastering the seven-step problem-solving process. https://lnkd.in/gKHEWKJ2 What strategies do you use for problem-solving in your organization? Share your thoughts below!

PMs often face messy and ambiguous problems, from untangling unclear user needs to making tough trade-offs between competing priorities. It could be a product design interview or a real life product decision. In these moments, the difference between a scattered discussion and a clear, confident recommendation often comes down to one thing: having a structured way to think. One of my go-to frameworks for this is Lewis C. Lin's CIRCLES method. It is a powerful, repeatable approach that works just as well in high-stakes interviews as it does in day-to-day product decision-making. I have used it multiple times to tackle product design questions with clarity and deliver stronger outcomes. The CIRCLES method breaks problem-solving into 7 actionable steps: - Comprehend the situation - Identify the customer - Report the customer’s needs - Cut through prioritization - List solutions - Evaluate trade-offs - Summarize your recommendation Its real strength lies in its versatility, as it guides you from understanding the context to presenting a well-structured solution that balances desirability, feasibility, and viability. Whether you are aligning cross-functional teams or tackling a tricky interview question, CIRCLES helps you focus on what matters most: building the right product, the right way. #productmanagement #product #pm #career #growth

Problem Solving Mastery What is the secret of efficient problem-solving? It is having a great framework to follow: Today I want to share this framework with you. Even though it may sound straightforward, Many people just forget about some steps, And then the process becomes inefficient. There are 8 key steps of problem solving: 1. Define problem “A problem well stated is a problem half solved.” - John Dewey Identify the problem, understand the context and implications. 2. Gather Data Accumulate relevant information through observation, research, and consultation. Make sure you have all relevant resources for a comprehensive understanding of the issue and its underlying causes. 3. Analyze Data Examine the collected data systematically to identify patterns, trends, and relationships. This will enable informed insights into the problem's nature and potential solutions. 4. Generate Solutions Brainstorm a range of potential solutions, considering diverse perspectives and innovative approaches. Try to generate the most effective solutions. 5. Select Solution Evaluate the generated solutions based on feasibility, impact, and alignment with objectives. Selecting the most suitable course of action to implement. 6. Plan Implementation Develop a detailed plan outlining the steps, resources, and timeline required to execute the chosen solution effectively Ensure clear communication and accountability. 7. Implement & Test Execute the planned solution, monitoring its implementation closely. Gather feedback to assess its effectiveness and identify any necessary adjustments. 8. Continue to Improve "Perfection is not attainable, but if we chase perfection we can catch excellence." - Vince Lombardi Iterate and refine the implemented solution based on ongoing evaluation and feedback. Foster a culture of continuous improvement and innovation within the organization. As you can see - one missing point can destroy the full process. If you do not define the problem well: You might work in the wrong direction. If you do not gather data: You might not understand the root causes. If you do not improve existing solutions: You might stick to the inefficient processes. Make sure to remember all the steps: This way you will ensure top efficiency.

Master Problem-Solving Like a Boss 💪 Crushing complex problems requires a solid framework. Here's a comprehensive playbook to flex your problem-muscles: ✅ Step 1 - Validate You're Solving the Right Problem Use "5 Whys" to get to the root cause 🧐 Quantify business impact 🌊 Ensure it aligns to company goals 🎯 Consider opportunity cost ⚖️ Analyze cost of inaction 💀 🖼️ Step 2 - Frame Problems Broadly Identify the "jobs" customers need done 🤔 Envision how competitors could disrupt 👀 Get ahead of market trends 🔮 Expand your problem space 🤸♀️ 🛣️ Step 3 - Select the Optimal Solution Path Clarify risk appetite 🤞 Consult on technical feasibility 🤓 Find simplest viable solution 🔍 Pressure test thoroughly 🥊 Validate quickly with users 🚀 📆 Step 4 - Execute Structured Iterative Cycles Frame problem by gathering perspectives 🤹♀️ Explore solutions widely via brainstorming 💡 Prioritize ruthlessly ⚖️ Prototype and validate concepts quickly 🤝 Communicate updates clearly 🗣️ 💡 Step 5 - Apply Core Problem-Solving Principles Collaborate openly 🤝 Prioritize ruthlessly ⚖️ Prototype rapidly 🚀 Obsess over customers 🤝 Work incrementally 📈 Measure rigorously 📊 Communicate clearly 🗣️ Stay nimble ↩️ Now get out there and flex your problem-crushing muscles! 💪 Let me know your top problem-solving tips in the comments. 👇