Posts

KEY TAKEAWAYS The product vs. productivity debate creates a false choice: Delivery capability is not separate from your product—it’s part of what customers buy and experience. Product ≠ offer: A product includes features, delivery system, quality level, and support experience. Toyota never separated “the car” from “how the car is made.” Customers experience your delivery system directly: They pay for speed, uptime, and responsive support. Amazon’s product isn’t “stuff online”, it’s “stuff online, delivered tomorrow.” Speed enables learning, learning finds value: Faster delivery creates faster feedback loops. Teams that ship quickly learn what customers actually want. Slow teams guess. Most teams don’t lack ideas—they lack delivery capability: The bottleneck is rarely “we don’t know what to build.” It’s “we can’t ship what we know we should build.” I keep hearing the same advice: focus on your product, not your productivity. The argument sounds strategic: focus on what matters rather than internal mechanics. Stop rearranging deck chairs. Build something customers want. ...

KEY TAKEAWAYS Lean Testing makes testing problems visible so teams can solve them at the root, instead of hiding waste behind status reports. One team cut false defects from 44% to 4% and nearly tripled productivity by using visual boards, andon signals, and PDCA. Teams that practice Lean Testing are ready for AI. Teams that don’t will automate their waste instead of removing it. Get the Lean Testing Quick-Start Kit. 4 practices, real results, a two-week plan to start Monday. Get the Kit → ...

KEY TAKEAWAYS False defects dropped from 44% to 4% by implementing an andon system where testers call for help before reporting uncertain bugs Testing productivity more than tripled (from 1.5 to 8 tests per person per day) through a pull flow system with daily targets Failed corrections dropped from 23% to 10% using a quality wall with expert verification Client satisfaction recovered after years of complaints, with the client noting clear improvement in service quality This case study was co-presented with Arnaud Cailleau, then Director of Testing Services at Sopra Steria. [Download the original presentation (PDF)] ...

A Lean approach for startups growing faster than their support team can handle KEY TAKEAWAYS On-time resolution jumped from 40% to 68% by switching from push-based assignment to a pull system where technicians take tickets when they have capacity Escalation rate dropped from 20% to 11% through quality standards and visual management Client satisfaction improved from 7/10 to 8/10 with no additional headcount 44-ticket backlog cleared by making flow visible and enforcing a 24-hour assignment rule Your inbox is a disaster. Tickets are piling up. Your support team is stressed, working late, and still falling behind. Customers are getting angrier. Response times are slipping. ...

KEY TAKEAWAYS Frameworks organize work, they don’t fix it: 84-96% of Agile transformations fail because they optimize the container (sprints, ceremonies, roles) without addressing how work actually flows through the system. Define outcomes first, then work backward: Results-based coaching starts with a specific, measurable performance gap and identifies the changes that will close it, rather than adopting a methodology and hoping for results. Four practices drive measurable improvement: Performance gap framing, direct observation, value stream mapping, and root cause analysis reveal problems that retrospectives and dashboards miss. Case study proof: A DevOps team running Scrum reduced infrastructure deployment lead time from 64 to 29 days (55%) by tracing actual work across team boundaries and fixing specific root causes. Start this week: Trace one feature end-to-end, spend one hour observing your team work, and define one performance gap with specific metrics. If coaching engagements have disappointed you by promising transformation yet delivering nothing more than process buzzwords, you are not alone. ...

Most LLM teams waste 40-60% of their AI budget without realizing it. KEY TAKEAWAYS Most LLM teams waste 40-60% of their API budget on operational inefficiencies, not model limitations Six common waste patterns: redundant API calls, missing caching, bloated prompts, slow retrieval, no quality measurement, and misallocated training investment University of Chicago research on 86,000 developers found experienced workers achieve 6% higher AI acceptance rates because they plan before implementing and evaluate systematically These are Lean skills: planning (PDCA), quality at the source, standard work, and gemba. The technology changes, but the operational capabilities that drive results remain constant Example savings: 67% reduction in API costs by combining redundant calls, 72% reduction by optimizing prompts, 64% faster responses by fixing retrieval pipelines Get the full framework →“The 12% Framework” explains what teams who ship AI to production do differently. Free PDF, 19 pages. Download the 12% Framework → ...

KEY TAKEAWAYS Voice of Customer (VoC) captures what customers expect, prefer, and dislike, uncovering both expressed and hidden needs In Lean management, VoC defines value from the customer’s perspective, without it teams cannot distinguish value-adding work from waste Example: An IT operations team used structured VoC collection to improve client satisfaction from 6.4 to 8.7 (+45%), double their 2-hour resolution rate, and reduce daily incidents by 37% Collect VoC data fresh: same-day feedback yields actionable insights, delayed surveys suffer from recall bias VoC feeds directly into PDCA cycles, turning customer input into measurable improvement What is Voice of Customer? Voice of Customer (VoC) captures customer expectations, preferences, and dislikes about products or services. It uncovers both expressed needs (what customers state directly) and hidden needs (what they reveal through behavior but never articulate). ...

KEY TAKEAWAYS An Obeya is a physical or virtual space where the project lives on the walls, and the team meets weekly to decide what to change. Toyota built the first one during the Prius program in the 1990s. The method now runs in software, hospitals, banks, and creative agencies. A BI team I coached went from 24% to 55% on-time delivery in three months, cut defects in half, and raised customer satisfaction from 5.5 to 9.4. Across my engagements, I’ve used three types: project Obeya for delivery, management Obeya for business health, and product Obeya for customer fit. Pick by what you are trying to manage. The wall is not the point. The weekly conversation in front of the wall is. Without an animator running it, the room becomes wall decoration. A BI (Business Intelligence) team went from 24% on-time delivery to 55% in three months, using one room and six visual boards. ...

KEY TAKEAWAYS Stop Building “Agile Silos”: Rushing to form ARTs around technical specialties reinforces old bottlenecks. Value Stream Mapping re-centers everyone on real customer value. Start with Data-Driven Fixes: Use Value Stream Mapping to quickly pinpoint dependencies and inefficiencies—no major restructures needed. Focus on high-impact workflows for faster, visible wins. Accelerate and Scale: In one claims process, lead time halved from 94 to 45 days and customer satisfaction rose 15%. Quick wins build momentum for lasting change. The Rush to Structure: A Common Transformation Pitfall Organizations embracing Agile at scale often stumble at the first hurdle: setting up their Agile Release Trains (ARTs). The pressure to show quick progress pushes leaders toward the familiar – organizing teams around technical specialties rather than customer value. ...

KEY TAKEAWAYS A value stream is the end-to-end flow of activities required to deliver software from idea to production, mapping it reveals bottlenecks, handoffs, and waste Value Stream Mapping (VSM) in tech focuses — amongst others — on lead time, process time, and percent complete/accurate (%C/A) at each step Example: A 30-person engineering team reduced delivery lead time by 45% and cut process steps from 14 to 6 using VSM and 7 PDCA initiatives The 5-step approach: Learn Lean techniques → Map “As Is” → Formulate improvements → Create “To Be” → Align on action plan VSM builds lasting capability; teams equipped with Lean techniques proactively surface and resolve delivery issues What is a Value Stream? Traditional Lean Management Definition A value stream encompasses the complete sequence of activities, both value-adding and non-value-adding, required to bring a product or service from its initial conception to the final delivery to the customer. ...