A key principle of lean management is "Genba" (go and see). To truly improve a process, leaders must be physically present, observing and talking with the people who perform the tasks daily. Speculating from an office based on data alone leads to ineffective or out-of-touch changes.

Treat organizational learning like technical debt. A 'learning backlog' is a dedicated, prioritized list of skills, processes, and knowledge gaps the team needs to address. This transforms continuous improvement from an abstract goal into a planned, trackable activity, ensuring it doesn't get lost in the rush to deliver features.

Applying AI to an inefficient workflow with unnecessary approvals or handoffs won't solve the core problem. Teams must first optimize their manual processes to be efficient before looking to AI for automation. This ensures AI adds value rather than just automating existing flaws.

Many companies rush to automate messy processes, which only locks in inefficiency. Instead, learn and refine the process by doing it manually first, as early Amazon and DoorDash did. Only automate once the system is optimized, using technology to speed up good systems, not paper over bad ones.

To move beyond static playbooks, treat your team's ways of working (e.g., meetings, frameworks) as a product. Define the problem they solve, for whom, and what success looks like. This approach allows for public reflection and iterative improvement based on whether the process is achieving its goal.

Traditional business culture rewards immediate action. For continuous improvement to succeed, you must instead reward the counterintuitive behavior of slowing down to thoroughly define a problem first. This prevents teams from wasting time solving the wrong issues.

A system's output is limited by its single least efficient step (the bottleneck). Focusing improvement efforts on this single point provides the highest possible leverage. The core principle is simple but powerful: find the one thing holding everything back and fix only that. Everything else is wasted effort.

Methodologies like Agile are just tools. The fundamental principle is creating a feedback mechanism for error correction. Instead of dogmatically following a framework, leaders should choose a system that provides the right frequency of feedback and adjustment for their specific project.

A highly effective sequence for process improvement is to first use Lean principles to remove systemic waste and complexity ("cleaning out the noise"). Only after the process is streamlined should you apply Six Sigma to analyze and squeeze down the remaining, true process variation.