Continuous Improvement In Project Management

Manufacturing Efficiency is More Than Numbers…It’s Transformational Science that Delivers Value. In my experience of deploying continuous process improvement, I’ve seen one truth repeat itself: small changes in cycle time create massive changes in organizational success. Consider a real-world example from a Fortune 500 distribution center. The facility struggled with a 12-hour lead time from order receipt to shipping. When we applied Manufacturing Cycle Time (MCT) and Manufacturing Cycle Efficiency (MCE) analysis, the data revealed that only 35 percent of production time was true value-added work. The rest was waiting, unnecessary movement, or inefficient scheduling. Through Lean tools like value stream mapping, Kaizen events, and standard work design, we cut average lead time from 12 hours to 8 hours. That 4-hour reduction meant faster customer fulfillment, increased throughput capacity, and a remarkable financial impact, more than 3.2 million dollars in annualized savings through reduced overtime, lower inventory holding costs, and fewer expedited shipments. The return on investment went far beyond financials. Employees who once felt pressured by bottlenecks were now empowered to work in a smoother, more predictable system. Morale increased as they could focus on craftsmanship and problem-solving rather than firefighting. When people feel their contributions directly improve performance, you build a culture of ownership and innovation. I have led these transformations across industries, from aerospace to government services and the outcomes are consistent. The combination of measuring cycle efficiency and acting on it with Lean methods delivers scalable success. Organizations gain profitability, employees gain pride, and customers gain trust. Continuous improvement is not just about efficiency metrics. It is about unlocking hidden capacity, protecting margins, and most importantly, enabling people to thrive in environments designed for excellence. That is the real power of Lean.🔋

There's a gap between digital transformation and operational excellence. A gap that can be narrowed with a lean approach. For true operational excellence, we need technologies to work seamlessly across departments and functions. But...companies are investing and 'going digital' without fully aligning new technologies with existing systems, processes and people! So people are often spending more time figuring out how to use a new tool or duplicating efforts across disconnected systems 🤷♀️ Done right...a lean approach can provide a structured framework for integration that takes into account organizational culture and people.  Here's how it can help: 1️⃣ Sets clearer goals for the technology 💠 Lean thinking and tools help you figure out what problem the technology should solve and how it will make things better. 💠 Discussions about the technology involve the people doing the work so people feel involved from the start and are more likely to support the changes. 2️⃣ Improves processes before adding technology 💠 Lean thinking and tools encourages cleaning up messy or inefficient workflows first, so you don’t end up using technology to automate bad processes. 💠 Streamlining things first ensures the technology works smoothly and brings real improvements. 3️⃣ Builds a mindset for ongoing improvement (not once-off solutions) 💠 A Lean approach shapes a culture where change is the norm and people are always looking for ways to do things better. 💠 It encourages small, manageable changes and pilot programmes that build trust and confidence in new technologies. 4️⃣ Helps people adjusts to change 💠 A lean approach emphasizes people development, good communication and training so that everyone understands how to use new technology and why it’s helpful. 💠 Leadership development is part of a Lean approach (it is in my book anyway) so leaders are coached and trained to address concerns and enable smooth transitions. 5️⃣ Supports data management 💠 Advanced technologies produce a LOT of data, and a lean approach helps teams focus on what’s important and use that data to improve processes. 💠 People then feel empowered when they see how data can help them work smarter, not harder. 6️⃣ Standardizes how the technology is used 💠 A lean approach ensures new technology works across different teams and locations by standardizing how it’s used. 💠 It provides a framework for scaling up successful changes so the pace of change is not overwhelming for people. Basically...a #lean approach helps us to invest in technologies that can actually fix problems. It ensures that we involve people along the way and make work easier for everyone. Any thoughts on the topic? Leave your comments below 🙏

I’ve had to protect my team in the past, particularly when their time or focus was at risk. I’ve seen this happen at companies like Microsoft, Google, and Amazon, where mandates and initiatives would stack during the same timeframe. While each initiative alone might have been reasonable, together they overburdened the teams. Those compiled costs may be invisible to the folks driving the individual mandates. You may have seen teams get overwhelmed by a major release, a review cycle, and bi-annual business planning all at once. This type of time management stress is usually manageable, but there are times when teams can be stretched too thin and compromise morale and quality. When you witness this, I believe it’s crucial to step in. You will hear from your team and you need to be close enough to the issues to decide how to respond. This can be tricky for a leader: on one hand, you want to ensure your team can succeed; on the other, you’re part of the broader leadership and need to support the decisions being made. Sometimes, you have very little room to maneuver. In those cases, I find it most effective to have a private conversation with key decision-makers. Meeting behind closed doors allows you to present the reality of your team’s capacity without putting anyone on the spot. Armed with clear data or project plans, you can often negotiate more realistic timelines or priorities. Another common pressure is when stakeholders create frequent direction changes. Repeated shifts in goals or features will thrash your team and waste energy. This often reflects deeper issues with strategy, alignment, and communication. However, you may not have time for a complete overhaul of your planning processes, and you still need a way to prevent thrash. A short-term fix is to set firm near-term milestones or “freeze” dates, after which any changes must go through a formal triage process. This ensures that if changes are necessary, they follow a transparent, deliberate sequence rather than blindsiding. After the freeze, broader project changes can be considered. Ultimately, I see my responsibility as a leader as fostering an environment where my team can perform at a high level, stay motivated, and avoid burnout. Part of a leader's role is to protect their team’s capability and long-term health. There will always be sprints and times when you need to push, but you also need to consider the long view and put on the brakes when required. People who feel supported are more productive, more creative, and likely to stay engaged.

Adopting Lean Six Sigma principles could trim excess or fine-tune workflows, and it’s a strategic move that encourages a culture of continuous improvement, where data and discipline guide smarter decisions and sustained performance. Lean Six Sigma (LSS) merges the strengths of Lean methodology, which targets waste reduction, and Six Sigma, which zeroes in on minimizing process variation. This combination helps businesses streamline operations and deliver consistent quality. For example, in a manufacturing setting, Lean tools might reduce idle machine time while Six Sigma ensures that product defects stay within tight limits. In healthcare, it’s used to cut patient wait times and reduce medical errors. Structured training roles—like Yellow, Green, and Black Belts—enable teams to lead improvements systematically using the DMAIC cycle: Define, Measure, Analyze, Improve, and Control. This fosters efficiency, cost savings, and greater customer satisfaction across industries. #LeanSixSigma #LSS #ProcessImprovement #OperationalExcellence #QualityManagement #DigitalTransformation

I can spot a doomed project in four sponsor moves. Want to know how? 𝗪𝗮𝗿𝗻𝗶𝗻𝗴 𝗦𝗶𝗴𝗻 #𝟭 - 𝗧𝗵𝗲 𝗗𝗲𝗹𝗲𝗴𝗮𝘁𝗶𝗼𝗻 𝗖𝗮𝘀𝗰𝗮𝗱𝗲: Sponsors who offload project communication to direct reports have disengaged. What starts as “Loop Sarah in on updates” becomes “Sarah will handle all project communication going forward.” Sounds great in theory, but Sarah’s not the one responsible for project success. Assure them that you’re only going to bring them issues that require their input - and bring Sarah in, she’s the gatekeeper now. 𝗪𝗮𝗿𝗻𝗶𝗻𝗴 𝗦𝗶𝗴𝗻 #𝟮 - 𝗧𝗵𝗲 𝗦𝘁𝗮𝗹𝗹: If week-long delays in communication and “let me think about that” have become their go-to, your project has dropped in priority. Reframe your requests with consequences front and center, and offer options to help expedite their thinking. Your job isn’t JUST to elevate the risk, it’s to help them mitigate it. You don’t make the final call, but you need to inform it. 𝗪𝗮𝗿𝗻𝗶𝗻𝗴 𝗦𝗶𝗴𝗻 #𝟯 - 𝗠𝗲𝗲𝘁𝗶𝗻𝗴 𝗧𝗵𝗲𝗮𝘁𝗲𝗿: Sponsors show up to status meetings, but treat them like a box to check, not a place to engage. Stop running status updates with your executives. Make meetings about current risks and decisions that require their input, ask about their current priorities and how the project connects and cancel meetings when there’s nothing that requires their input. 𝗪𝗮𝗿𝗻𝗶𝗻𝗴 𝗦𝗶𝗴𝗻 #𝟰 - 𝗕𝘂𝗱𝗴𝗲𝘁 𝗔𝗻𝘅𝗶𝗲𝘁𝘆: Sponsors who approved 500k are suddenly questioning every expense? This isn’t fiscal stewardship, they’re questioning project value. Tie every expense to business outcomes. “This integration saves us 100k in manual costs” is more persuasive than “you signed off three months ago.” Then, figure out what’s killed their confidence and work with them to restore it. Strong PMs recognize these signs, and manage up to ensure sponsors are engaged, and the project has what it needs to go over the finish line. #projectmanagement #stakeholdermanagement #changemanagement ___________ If this resonated, let’s connect. I work with organizations to diagnose and fix the dynamics that kill projects and profitability.

Problems for Project Managers start small. Then grow quietly. Not because people don’t care. Because a few basics get ignored. Good project management is rarely dramatic. It’s consistent. Here’s what usually helps: → Clear goals People work better when success is obvious. → Consistent communication Silence creates stories. Updates create trust. → Team ownership When people feel trusted, they step up. → Flexibility Plans matter. So does adapting when reality changes. → Progress tracking What gets reviewed gets improved. Now the other side. What usually creates friction: → Micromanaging Control rises. Ownership drops. → Ignoring risks Small warnings become bigger problems. → Weak documentation Decisions get forgotten. Work gets repeated. → Skipping reflection The same mistakes return. → Delayed conversations Tension grows when clarity waits. That’s the pattern. Strong PMs don’t rely on pressure. They build clarity. They create rhythm. They remove confusion early. Because projects rarely fail on a single big moment. They slip through small habits repeated daily. P.S. Which PM habit creates the biggest difference in your experience?

Most companies fail at Lean before they even start. The reason is simple: they begin with tools instead of the customer and the problem. After leading manufacturing transformations across global automotive operations, I keep seeing the same pattern. But Lean does not start with tools. It starts with the customer need and what is the problem.? Lean is fundamentally a way of thinking about work, people, and waste. Some lessons learned along the way: • Real quality improvement is systemic. When quality improves the right way, financial performance, safety, and morale improve together. • Copy-paste Lean rarely works. Trying to replicate Toyota or any “best practice” without understanding your own culture usually fails. • Understanding the problem is already half the solution. • Lean tools are countermeasures to minimize specific waste. • Culture and leadership matter more than tools. ⸻ A real example. At one of the largest assembly complexes in the world, the plant was competing to secure a new powertrain program. Failure would put thousands of jobs at risk. The challenge seemed impossible: • Highest operating cost in the network • Supposedly no space available But when we went to the Gemba, we discovered something surprising. Almost 40% of the plant was used to store only a few hours of inventory — in what was considered one of the leanest operations in North America. The problem wasn’t space. It was material flow design. A cross-functional team developed a progressive Electronic Kanban system to visualize several days of customer demand based on the vehicle assembly sequence — something not previously used in powertrain operations. This enabled: • Continuous small-lot deliveries • Direct flow to line racks • Synchronization between production and deliveries The supply chain became an extension of the assembly line, freeing massive space. ⸻ Another example: Operators were spending nearly 20% of their time walking just to pick up small parts. Using the Kowake principle, small-part containers were attached directly to the conveyor system, bringing parts directly to operators. The impact: • No walking for parts • Higher assembly focus → better quality • Less fatigue → better ergonomics • Less line-side inventory Combined with tools such as kitting, Minomi, Kowake, Electronic Kanban, Kamishibai, and direct delivery, the operation achieved: • ~50% space reduction • Significant cost improvement • High double-digit inventory savings Most importantly, thousands of jobs were preserved, and the plant secured the new engine program. ⸻ The lesson Lean does not start with tools. It starts with understanding the problem, the people, and the customer. Go to the Gemba. Listen. Understand. Then act. ⸻ Where do Lean transformations fail most often in your experience? • Tools • Culture • Leadership ⸻ #LeanLeadership #OperationalExcellence #Manufacturing #ContinuousImprovement #Gemba #Leadership © 2026 Yuri Rodrigues

PRACTICAL PROJECT MANAGEMENT FOR ENGINEERS Practical Project Management for Engineers provides commonsense solutions to get projects rolling from contract award to delivery while using the Pareto principle to drastically increase productivity. The book walks the new technical project manager (PM) through step-by-step processes on how to deliver high-quality, robust products and services while strengthening one’s team and customer relationships. While creating the book, Department of Defense (DoD), NASA, and Project Management Institute (PMI) project life cycle processes were compared and the best practices that have worked for our panel of experts on real-world projects are presented. This book is practical, not theoretical. We tell you “what you need to do on Monday.” The project guidance from the DoD, NASA, and PMI and best practices from management and leadership gurus like Steven Covey, Peter Drucker, and Jim Collins have all been distilled into an easy-to-follow dialog. This knowledge will equip the new technical project manager to deliver quality products on time and on budget. Each chapter provides you with the most important activities and techniques that will aid any new project manager. The last chapter of this book, Tales from the Trenches, was written by our panel of industry experts and gives insight to their lessons learned on real-world projects. In the real world, projects rarely meet schedules or avoid changes in scope. By providing a practical outline of what is critically necessary for project success, efficient solutions are presented that will show you how to manage recovery plans and customer relationships to continue the future growth of your company and your career. A project scope is defined by a set of requirements that define the characteristics of the desired products and services along with the conditions in which the project team will execute its work. It consists of a life span with a starting point and a defined end to deliver a quality product and/or service. The objective of project management is to deliver the products and services defined by the project scope within the constraints defined by the project’s customer. The project’s customer is the party that will benefit from the project’s outcome. Project customers and sponsors can be internal or external to the PM’s organization. Effective project management requires specific knowledge, skills, tools, and abilities. Project management involves the application of these knowledge, skills, tools, and abilities to meet the project’s requirements. Project management also requires a level of understanding of the environmental, operational, and technical aspects of the domain in which the project operates.

Project delivery doesn’t fail because people don’t work hard. It fails because decisions are made on poor data. The newly published Programme and Project Data Standard from Government Project Delivery is a quiet but significant moment for the UK project profession. It doesn’t introduce a new methodology. It doesn’t mandate a tool. And it doesn’t create extra reporting for the sake of it. Instead, it does something far more important. It defines what “good project data” actually looks like. For the first time, there is a common, structured view of the core data that underpins confident decision-making across programmes and projects — from risks and issues, to costs, milestones, benefits, and people. And that matters. Because most programme challenges don’t start with failure — they start with: - inconsistent baselines - unclear ownership of data - optimistic forecasts - late escalation - and reports that look “green” until they suddenly aren’t This standard is a recognition that governance is only as strong as the data behind it. What’s particularly important is what the document doesn’t do: - It doesn’t tell organisations which system to buy - It doesn’t centralise everything into one platform - It doesn’t treat data as an administrative by-product Instead, it places accountability where it belongs — with delivery leaders, SROs, PMOs, and project control professionals. In many ways, this is a statement about the maturing of the profession. It elevates the role of project controls from “reporting support” to decision-enabling capability. It reinforces that risk, cost, schedule, benefits, and people data are not separate conversations. And it makes clear that professional judgement must be backed by structured, auditable evidence. For organisations delivering complex change — infrastructure, digital transformation, defence, public services — this is a timely reminder: If you want confidence at board level, you need discipline at data level. The conversation now needs to move from: ❌ “Are we compliant?” to ✅ “Do we have the capability to produce data we can trust?” That’s not a technology question. It’s a capability, leadership, and professionalism question. And the organisations that take this seriously will not just deliver better projects — they’ll make better decisions, earlier, with fewer surprises. #ProjectDelivery #ProjectControls #PMO #Governance #PublicSector #DataDriven #Leadership #UKProjects