Posts

Welcome to the new LeanTechPro. Same content, same mission — but this site no longer runs on a WordPress server. It’s now a static site hosted on Cloudflare Pages, which means: Faster page loads — every page is pre-built and served from Cloudflare’s edge network Nothing to hack — no PHP, no database, no plugins to update Free hosting — Cloudflare Pages’ generous free tier covers a blog easily Version-controlled content — every article is a plain-text Markdown file in Git If anything looks off, it’s probably a leftover from the migration — let me know.

This post is a note-to-self: the exact steps to publish a new article on LeanTechPro. 1. Create the file cd ~/dev/leantechpro hugo new content posts/my-new-post.md Or just copy an existing post in content/posts/ and rename it. 2. Write Open the file. Update the front matter (title, date, tags), set draft: true while writing, and write the body in Markdown. Images go in static/images/ and are referenced as /images/my-photo.png. 3. Preview locally hugo server -D Open http://localhost:1313 — the site reloads as you type. ...

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

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

KEY TAKEAWAYS Lead time measures a process from start to finish, at any scope. Cycle time measures the duration of a recurring process. The scope you define determines which lead time or cycle time you measure. Define it explicitly, to have meaningful numbers for improvement leverage. High cycle time variability makes reliable delivery impossible. Reducing it is what turns a capable team into a predictable one. A product owner adds a feature request to the backlog. A developer picks it up 38 days later. He does the coding, then the testing, and pushes it to the deployment team. All that takes 7 more days. In the end, it takes the client 45 days to see anything. ...

KEY TAKEAWAYS A DevOps team cut its infrastructure deployment lead time by more than half. The team followed Agile practices well. The blockers hid in cross-team handoffs where no ceremony could reach. Value stream mapping revealed about half the lead time lost in a single queue due to unclear routing and missing documentation. Simple interventions drove the result: checklists, front-loaded requests, early handovers. No new tools. No reorganization. The Problem A DevOps team at a large enterprise handled cloud infrastructure deployments. A small DevOps team, working across multiple projects, supported development teams who needed environments to build and test their applications. ...

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

KEY TAKEAWAYS If your sprint velocity looks fine but features keep slipping, the problem is invisible to any dashboard you have access to. A non-technical founder can assess engineering health without reading code. You just need to know which signals to look for. The most expensive engineering teams are often the quietest ones. Silence is not a good sign. Not sure your engineering team is performing? Book a free 30-min call. I’ll tell you exactly what to look for. Book a Free Call ...

KEY TAKEAWAYS AI tools made your developers faster. Your delivery system wasn’t built to absorb that speed. The bottleneck moved from writing code to reviewing it, and most teams haven’t noticed. You don’t need new tools. You need to redesign the system around the ones you have. Before you read on: I built a free diagnostic guide that covers everything in this article as a step-by-step framework. If you’d rather act than read, start there. Get the Free Diagnostic Guide ...

KEY TAKEAWAYS A 13-person billing test team increased productivity by 24% in three months by making work visible, setting daily targets, and solving problems one at a time with PDCA. Diagnostic before action: observing testers at their workstations revealed hidden waste like seven help requests in three hours, repeated tests without conclusions, and two-hour solo investigations. When the project manager changed mid-project, the new manager walked into a team that ran itself. Visual boards, tracked indicators, and clear action plans made the transition seamless. Get the Lean Testing Quick-Start Kit. 4 practices, real results, a two-week plan to start Monday. Get the Kit → ...