Management Obeya: How an IT Services Team Built Their Own War Room

KEY TAKEAWAYS A management Obeya is the leadership team’s operating system made visible. It tracks the health of the business, not project deliveries. Seven boards on the walls of one room replaced opinion-based meetings with weekly data-driven sessions in 60 minutes. The agency director continued to run the Obeya after the engagement ended. The boards evolved, the weekly rhythm never stopped. An IT services agency director wanted to change how his management team worked together. He had a strategy and objectives. He also had talented people running operations, commercial development, and client delivery. What he did not have was a way to see it all in one place, discuss it factually, and solve problems before they became crises. ...

April 24, 2026 · 9 min

From 24% to 55% On-Time Delivery: A Project Obeya Room Case Study

KEY TAKEAWAYS A BI team managing nearly 20 projects across several continents built an Obeya room and doubled on-time delivery in 3 months. The Obeya surfaced milestone collisions, quality failures, and ownership gaps that no status report had ever shown. Three PDCAs run inside the Obeya rescued a go-live, halved defects per delivery, and created a standard that the team still uses. Get the Full Project Obeya Template with all the boards layout: Strategy, performance, macro planning, and problem-solving. Ready to print and fill in. [Download Free Template →] ...

April 24, 2026 · 11 min

How a 15-Person COBOL Team Cut Defects 91% in 60 Days

A financial software case study. How visual management, daily flash meetings, and team-led PDCAs replaced rework with ownership. KEY TAKEAWAYS A 15-person COBOL team at a financial institution reduced defects from 93 per month to 8 in two months. The team ran their own PDCAs using visual management and daily flash meetings. The method works the same for different tech teams: software development, testing, tech support, IT operations, and project delivery. Results from real coached teams: 91% defect reduction in financial software, 160% testing productivity gain, 94% backlog cleared in e-services support, 70% on-time resolution improvement in energy sector IT operations. Does Your Team Have the Same Problem? Take the 3-minute Delivery Scorecard to find out: Where your delivery system breaks down Whether you’re fixing symptoms or root causes Your biggest improvement opportunity right now Find Your Team’s #1 Bottleneck (Free) → ...

March 13, 2026 · 12 min

When Agile Coaching Doesn’t Deliver: A Results-Based Alternative for Tech Leaders

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. ...

December 22, 2025 · 14 min

Voice Of Customer (VoC): A Complete Guide for Tech Teams

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). ...

December 18, 2025 · 10 min

What Is an Obeya Room? A Complete Guide With Examples

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. ...

December 14, 2025 · 15 min

Value Stream Mapping: The Missing Piece in Your ARTs

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. ...

December 14, 2025 · 8 min

Value Stream Mapping for Software Teams: A Complete Guide With Examples

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. ...

December 14, 2025 · 16 min

A3 Problem Solving: A Complete Guide (With Template & Examples)

KEY TAKEAWAYS A3 Problem Solving is a structured one-page method that forces clarity: define the problem, find root causes, implement countermeasures, and confirm results. Successful A3 implementation requires pilot projects, leadership buy-in, and integration into existing team rituals — not a top-down rollout. A tech support team used A3 to eliminate a 145-ticket backlog in 2 months, boosting productivity 72% and customer satisfaction 35%. A tech support team cleared a 145-ticket backlog in 2 months. Here’s the one-page method that made it happen. ...

December 14, 2025 · 13 min

The ‘Top Priority’ Problem: Why Engineering Teams Struggle With Delivery

KEY TAKEAWAYS When everything is marked urgent, delivery stalls. Without real prioritization based on capacity, teams drown in work and nothing flows. Good tools and talent can’t fix broken systems. AI and fast coding mean little if reviews, testing, and handoffs stay overloaded or unmanaged. Leaders must design for flow, not push for speed. The real shift comes from limiting WIP, creating pull, and making the delivery system visible and stable. Does Your Team Have the Same Problem? Take the 3-minute Delivery Flow Scorecard to find out: Your team’s flow score (0-100) Whether you’re pushing or pulling work Your #1 hidden bottleneck Find Your Team’s #1 Bottleneck (Free) → ...

July 12, 2025 · 9 min