Does this sound familiar? A well‑intentioned leader decides it's time to deploy structured problem-solving throughout the organization. They roll out “A3” (or a similar problem‑solving methodology) training sessions, distribute templates, and set expectations that every employee will complete an A3 each quarter. There's energy and focus for a while. But soon, the effort starts to fizzle. The forms get filled out, yet A3 thinking never truly becomes “the way we do business.” In my last article , I shared the story of my first A3 at Toyota - the crumpled drafts, the red ink, and the eight revisions it took to successfully complete the certification process. That experience taught me that A3 problem‑solving isn’t about filling out a form; it’s about developing a way of thinking. Yet here’s the real challenge: How do we move beyond individual skill to organizational capability? How do we scale problem‑solving so it becomes the way the organization continuously improves- no...
I walked out of my mentor's office feeling dejected. I had just given him a progress update on my A3 project. "You do not fully understand the problem,” he said. “Go back and redo the second step.” At Toyota, I was required to earn A3 certification by applying the methodology to a real-life problem. It took 8 cycles of revision before the A3 was complete. The picture above shows the final document. What is not shown is the many crumpled versions covered in red ink. The most important lesson I learned from the experience is this: The power of the A3 is having the courage to stare at the broken process until you understand why it broke. Many leaders fail at problem-solving because they are afraid to look at the "Current State" (the truth). They jump straight to "Future State" (the solution) to avoid the discomfort of the unknown. This bias for action is paradoxically what prevents effective problem-solving. The following are my core takeaways from...