DiscoverPeople Solve Problems
People Solve Problems
Claim Ownership

People Solve Problems

Author: Jamie Flinchbaugh

Subscribed: 6Played: 38
Share

Description


People Solve Problems is an engaging new podcast hosted by Jamie Flinchbaugh, the author of the book with the same title. In this insightful series, Jamie interviews a diverse array of guests – from thought leaders and authors to practitioners and everyday individuals, delving into their unique perspectives on problem solving. This compact, interview-style podcast offers valuable insights into what constitutes effective problem-solving, the challenges faced in the process, and the strategies employed. It aims to equip listeners with a wealth of ideas, best practices, and approaches to enhance their problem-solving skills. Stay tuned for the upcoming episodes by clicking the follow button and signing up today.
85 Episodes
Reverse
On this episode of People Solve Problems, host Jamie Flinchbaugh welcomes Allan Coletta, Principal of Lean 3P Associates and author of the Shingo Award-winning book “The Lean 3P Advantage: A Practitioner's Guide to the Production Preparation Process.” A chemical engineer and former Senior Director of Engineering and Facilities at Siemens Healthineers, Allan has spent his career designing new operations and turning around struggling plants. Beneath this practical tour of 3P runs a steady belief that the people closest to the work have more to offer than most organizations ask of them. Allan explained that 3P, short for the Production Preparation Process, was developed by Chihiro Nakao of Shingijutsu, a Toyota veteran who learned under Taiichi Ohno. Allan describes it as a faster, lighter version of the way Toyota designs products and the processes that make them side by side. He sees it used in three ways: designing a new product together with its manufacturing process, building a new operation when demand grows, and redesigning the layout of an existing building. Hospitals adopted that last use years ago, but manufacturers are only now catching on. Most plants, Allan noted, grow one machine at a time, each placed wherever it fits, until the people running them spend their days crossing the floor. Why can’t skilled engineers handle this alone? Allan's answer came from experience: at Siemens he led a large group of talented engineers and noticed that their new designs were mostly refreshed versions of the old ones. He wanted a leap forward, and 3P gave him a way to get it by putting supply chain, operations, research, and every other group that touches a product in the same room for about a week. Allan prefers to call the result informed consent rather than consensus, because every need is heard and understood before choices are made. Allan's enthusiasm shows most in the process itself. Teams begin by listing seven ways a function could be carried out, starting with how it happens in nature. Engineers often freeze, but Allan has watched it level the room within minutes, until a senior scientist and a forklift driver are laughing and trading ideas as equals. The group narrows those ideas to three, then splits into teams for what Allan calls try-storming, building rough models from cardboard and scraps. The forklift driver points out what he cannot reach, and the operator asks where the tools will go. The final design almost always borrows from all three models, and Allan has seen teams sign their names to it with pride, some feeling heard for the first time in years. Allan also described how naming each step by its purpose, rather than its current method, opens new doors. Treating a label as a way to identify a product has led teams to rethink packaging and shipping, and sometimes the product itself. Asked when a process needs a full rethink instead of a small fix, Allan admitted it is usually forced by an outside change, such as a new customer or a competitor's new offering. For sponsors, his advice is to invite a wide range of people, choose optimists over constant critics, bring decision-makers in at key moments so they learn alongside the team, and find an experienced facilitator who can steady the group when the event seems about to go off the rails. He recalled a boss who told him to change nothing, then became the biggest supporter of 3P after watching the work unfold. Connect with Allan on LinkedIn at www.linkedin.com/in/AllanColetta and find his book, “The Lean 3P Advantage,” at https://www.amazon.com/Lean-3P-Advantage-Allan-Coletta/dp/1439879117.  
In this episode of People Solve Problems, Jamie Flinchbaugh speaks with Mark Fegley, VP and Team Manager at Gartner. Mark brings more than 20 years of global supply chain leadership in consumer products, process improvement, and business development, and today leads a team of executive partners who advise supply chain leaders at client companies. The two also share Lehigh University roots. Jamie opens with a question he rarely gets to ask: how do you know when a problem calls for deliberate, careful thinking rather than a quick fix?  Mark explains that the answer is often instinctive, but it rests on understanding the nature and importance of the issue. He describes how his executive partners kept running into the same wall: they lacked the material to lead workshops with clients on artificial intelligence. Before building anything, Mark had the team name the real problem: clients were taking those conversations to competitors. Over six to eight weeks, the team shaped a solution, deciding what to include and what to throw out. Mark credits staying close to customers for spotting the problem early, noting that the people nearest the client are often the first to tell you something needs solving. On intuition, Mark observes that it usually grows out of experience. When a client asks a hard question, he often draws on how he solved something similar as a supply chain leader. Mark believes a problem should be roughly 80 percent understood before anyone starts talking solutions, and his team relies on careful questioning to get beneath the surface. He traces his own appreciation for this style back to a Lehigh government professor whose relentless questions felt like a rude awakening at the time. Today, Mark looks for that same curiosity when hiring, asks candidates to present to a panel, and has every new team member read “The Coaching Habit,” supported by training from “Box of Crayons.” Mark also explains that questioning only works when there is trust. With clients who are reluctant to open up, he encourages his team to build rapport first, sometimes through a conversation about family or college football.  When the discussion turns to finding root causes, Mark points to familiar tools such as lean and the five whys, which means asking why repeatedly until the real cause appears. He warns against the common belief that new technology will fix a struggling operation. Moving a broken process into a new system, he explains, only helps you discover faster that it doesn’t work. He sees the same risk with AI and urges leaders to treat it like any other improvement effort: start with strategy, define the problem, and then decide where the technology fits. On leading his team, Mark describes listening in on client calls to see how each executive partner works. He looks at two things: whether they truly understood the client’s problem, and whether they connected the client with the right help. He steps in only when a call drifts away from what the client needs, perhaps 10 to 15 percent of the time, and he encourages his team to find the courage to do the same. Mark closes with an enthusiastic case for supply chain careers, a field that is changing quickly, becoming more professional, and drawing in more talented people. He sees the growing need for skills in data and technology not as something to fear but as something to embrace. To learn more, visit Gartner at https://www.gartner.com or connect with Mark on LinkedIn at https://www.linkedin.com/in/markfegley.
On this episode of People Solve Problems, host Jamie Flinchbaugh welcomes Dr. Rebecca Teeters, Senior Vice President of Business Supply Chain and President of Chemical Operations at 3M. Over more than three decades at 3M, Rebecca has led plants, global operations, enterprise strategy, and business transformation. The conversation, something of a reunion for two people who go back a long way, shows how a self-described systems thinker keeps a very complex organization pointed in the right direction. Rebecca began with the sheer volume of problems that surface every day across her two roles. Rather than sorting them one at a time, she relies on connected systems: supply chain design tied to value stream improvement plans, change management practices, and a daily management system that runs from the shop floor to the top floor. When something new appears, it moves through that same system, and the team decides deliberately whether it deserves attention now or can wait. She described a framework introduced by Paul Gallagher, who leads 3M's Enterprise Supply Chain, that sorts work into three categories: Run, Improve, and Transform. Run gets a fifteen-minute standing meeting every Friday. Improve is reviewed monthly against a twelve-month horizon, and transform follows a monthly and quarterly rhythm. Rebecca sees a clear role for AI here, not as a decision maker but as a way to digest large amounts of information and spot early warning signs across dozens of projects. Asked how she divides her own attention, Rebecca explained that her business supply chain team should spend about ninety percent of its effort on improving and transforming, with clear lines drawn about which processes the team belongs in. Personally, she is working to flip a balance that historically tilted toward keeping the business running. A well-designed daily management system makes that possible, she said, because she can trust that decisions happen at the right level and that problems are raised before they require a recovery effort. On competing priorities, Rebecca pointed to operational excellence principles, noting that a flow problem deserves attention because the rest of the organization feels its waste quickly. She admitted that gut instinct still plays too large a role in trade-off decisions, so her team is building a capital allocation model that frames options in clear financial terms. She uses AI to challenge her own assumptions rather than to make the choice for her. On blind spots, Rebecca believes the best defense is inviting outside perspective on a regular schedule, chosen with intent. Her team recently spent a day with Amazon and AWS. To cut down on fires, she has sent teams to learn from NASA. To understand flow, she points them to quick service restaurants. The lesson, she said, is to study the principles behind how others design their systems rather than dismissing them because their products look nothing like yours, and then to be humble enough to act on what you see. Reflecting on her career, Rebecca shared that she never plans for the next role. She focuses on doing today's job as well as she can, keeps learning, and lets opportunities come, including a period leading environmental stewardship that she counts among the most educational of her career. She and her son share a phrase about being humble enough to be bad at something long enough to become good at it. And for all her senior responsibilities, she admitted she still misses being a plant manager. You can learn more about 3M at https://www.3m.com/ and connect with Rebecca on LinkedIn at https://www.linkedin.com/in/rebecca-teeters-8870b917/.
On this episode of People Solve Problems, host Jamie Flinchbaugh welcomes Kathy Coffey Solberg, CEO of CommonUnity Consulting and author of the new book “Reweaving What Matters.” Kathy has spent 25 years helping leaders across business, government, and nonprofits see what is really happening before they try to fix it. Her central claim reframes most change work: organizations can see the results they do not like, but rarely the patterns producing them. The framework grew out of an actual loom. Kathy is a weaver twice over, a community weaver by profession and a fiber weaver by practice. Looking at a loom fully set up, with its threads and heddles, she saw a system, and she has not stopped seeing systems since. She had planned to write only about reweaving, then made a mistake at the loom, had to go back and undo her own work, and recognized that the phase before the rebuild is the one organizations keep skipping. She named it unweaving. Unweaving has three steps: Notice, Clarify, and Act. Noticing is a hard place to begin, Kathy admitted, because it feels passive when every instinct says to do something. It asks how communication actually moves, whether money is spent in ways that match the mission, and who holds influence that no title reflects. Clarify turns those observations into understanding, following the pattern of what, so what, now what. Act stays small and deliberate: thirty-day experiments that teach something whether or not they succeed. Her example is the standing two-hour meeting where everyone reports out and then leaves, replaced by a fifteen-minute huddle where people ask for what they need. Underneath it all are what Kathy calls the warp threads, the structural pieces an organization hangs everything else on. Policies written for a world that no longer exists. Hierarchies built decades ago. Positions unchanged in twenty years even though the work around them moved on.  Reweaving becomes possible only once that space is cleared, and it carries three steps of its own: Envision, Structure, and Weave. Envision asks what is possible with the foundation now in place. Structure answers how, on what timeline, and with which positions. Weave is where people, systems, and programs come together to deliver the work. Kathy usually starts at the bottom of an organization, with the staff closest to the clients, because they see what is needed differently than leaders three levels up. Leaders who react and throw solutions at problems burn trust with the people counting on them, and each new push meets a little more fatigue. Kathy said early readers of her book kept returning to one word: mattering. Belonging tells people they have a place. Mattering sees each person for what only that person brings. Asked what behavior a leader has to show for this work to produce results, she pointed to listening and to naming plainly when something is not working, which she said is often missing because people do not want to look like they might not know everything. You can learn more about Kathy Coffey Solberg at https://www.kathysolberg.com/ and connect with her on LinkedIn at https://www.linkedin.com/in/kathy-solberg-98897730/.
On this episode of People Solve Problems, host Jamie Flinchbaugh welcomes Matt Zayko, Senior VP and Head of the Global Lean Office at GE HealthCare. Matt brings one of the broadest lean backgrounds in the field, and the conversation traces how that breadth shaped his thinking about what makes change actually last. Matt describes his lean origin story as being in the right place at the right time. As a graduate student in industrial engineering at the University of Michigan in the early 1990s, his advisor connected him with John Shook, who had just arrived from Toyota. Surrounded by thinkers like Jeff Liker, Al Ward, and Durward Sobek, Matt studied how Toyota developed products in half the time and with better quality, then applied that learning in industry roles at Chrysler, Delphi, and Pall under Danaher. He later spent fifteen years with the Lean Enterprise Institute, including work on Jim Morgan's lean product and process development team, before joining GE in 2021 and ultimately leading lean for GE HealthCare. Jamie notes a shared concern from their parallel paths: too many practitioners lock in what they learned early and apply it as dogma. Matt agrees, calling the confusion of principles with dogma one of the lean community's real failure modes. Asked about a particularly difficult problem, Matt goes straight to a lesson from his early career. Being technically right, he explains, is only half right. As a young engineer, he was convinced his solution was correct, and on paper it was. But the same idea had been proposed before and never sustained, so people had lost trust that anything would stick. The deeper insight followed: the problem is rarely improving; it is sustaining. Ideas are often only 80% right, and without a management system that catches the remaining 20%, the old problems return, and the people who invested in the change lose hope. Matt calls this the go slow to go fast approach, and he argues the sustainment side of change still gets far less attention than it deserves. The conversation then turns to breaking down problems in complex environments like product development and healthcare, where feedback arrives slowly, and the consequences of decisions may not be felt for months. Matt's advice is to recreate the gemba. Because a development program is a learning cycle rather than a repeating system, teams have to deliberately reconstruct how the work really happened on something real, such as a recently launched product. Visualizing that work, he says, is one of the most powerful starting points available, and from there a team can diagnose, set a target condition, and run the play again. On collaboration, Matt is direct: problem solving is a team sport. He credits GE's consistent problem-solving process as a standard that lets everyone read a problem the same way, but he stresses that the paper only matters if people build it together. When colleagues see their fingerprints on the document, ownership replaces resistance, and implementation moves fast. Matt closes with what inspires him about GE HealthCare: proof that a company more than 125 years old can transform. If it can be turned around there, he says, it can be turned around anywhere, and the lean community needs more examples like it. Learn more about Matt's work at www.gehealthcare.com, connect with him on LinkedIn at linkedin.com/in/matt-zayko-b3522811, and find his book, The Power of Process: A Story of Innovative Lean Process Development, on Amazon at https://www.amazon.com/dp/0367690306.
loading
Comments