Alan Mulally, 2016

“Working together always works.”

Alan Mulally has used this phrase to summarize the leadership system he practiced at Boeing and Ford. His approach joined a shared plan, visible operating facts, regular business-plan reviews, and norms that made it possible to surface a problem without being punished for bad news. Working together is more demanding than general goodwill. It requires common goals, consistent data, clear ownership, and a process for asking for help. Coordination improves when leaders respond to a red indicator with curiosity and resources instead of blame. Behind the concise wording is a claim about how organizations create results. It encourages leaders to look beyond individual effort and examine design, incentives, information, relationships, and the customer context that determine whether a good intention becomes reliable performance.

Teams can review one integrated plan at a steady cadence, show status with the same definitions, and explicitly recognize early disclosure of risk. Cross-functional help should have an owner and follow-up date so collaboration produces a changed condition. Managers can translate the claim into a small experiment with a baseline, an owner, a defined customer or employee outcome, and a review date. Specificity protects the work from drifting into broad language that nobody can challenge or verify.

Consensus is not the objective, and collaboration cannot excuse slow decisions or weak accountability. Leaders still set direction, resolve conflict, and make calls when evidence remains divided. Psychological safety must be paired with accurate reporting and performance standards. Responsible use also requires naming the tradeoff. Speed, cost, autonomy, safety, equity, and learning may not all improve at once. People closest to the consequences should have a meaningful voice, and uncertainty should be reported instead of hidden behind confidence.

Complex products depend on software, supply chains, regulation, security, and service partners. AI increases interdependence further because data, models, workflows, and human oversight cross organizational boundaries. A shared operating picture is essential for responsible speed. A weekly plan review can make every major commitment, variance, dependency, and request for help visible, then record who will change what before the next meeting. Evidence from the experiment can guide scaling, revision, or stopping. The durable lesson is to join purpose with measurement and human judgment, so the organization becomes better at seeing reality and responding before a local success or failure hardens into mythology. Recording the decision and its limits gives colleagues a foundation they can inspect, challenge, and improve instead of asking them to rely on memory, authority, or an unexplained result.