When implementing new processes, such as selling maintenance plans, leaders should not seek consensus from their team by asking for permission. Instead, they should present the new direction with confidence. This confident leadership inspires the team to adopt the changes, whereas asking for input can create resistance and undermine the initiative.

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.

To make new standards stick, don't just announce them. Gamify adoption by consistently offering small, public rewards (e.g., $20 for correct uniform). This makes the new process a recurring topic of conversation and embeds it into the company culture, avoiding the "announce-and-forget" failure loop.

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.

Projects fail not from lack of tools, but from a lack of executive sponsorship. Success hinges on leaders dedicating significant weekly time (e.g., half a day) to a few key projects, rather than passively sponsoring many with monthly check-ins. This deep engagement is a primary driver of success.

A leader's job doesn't end after designing a process. They must actively and continuously teach and reinforce the company's methods, especially as new people join. The goal is to ensure the right things happen even when the leader isn't present.

To handle leaders who demand results but offer no support, teams should create "forcing factors." By consistently documenting and reporting progress, impediments, and value alignment, you build a historical record. When leaders eventually ask "Why didn't this get done?", the data forces their engagement.

Real culture change doesn't happen because an executive reviews a dashboard once a year. It happens when managers practice small, positive behaviors every day. The focus should shift from large-scale measurement to enabling continuous, small-scale action, even if based on imperfect data.

To prevent post-sprint momentum loss, create structural "bookends" of support. An executive sponsor provides strategic alignment and resources from the top, while embedded innovation champions on the team provide the day-to-day passion and skills to navigate obstacles from below.