Built to Last

Jim Collins and Jerry Porras's Built to Last investigates companies that sustained a distinctive identity across generations of leadership. Collins's official description highlights the relationship between preserving a core and stimulating progress, using comparative research over selected historical periods. [1] The useful question is what an organization should remain faithful to while adapting how it works.

This is relevant beyond large companies. A community institution may need to protect its purpose while replacing a failing process, technology, or habit. Confusing a familiar method with a core value can prevent improvement. Equally, pursuing every new opportunity can weaken the reason people trusted the organization in the first place.

The limit is that selected historical comparisons do not establish a guaranteed formula. Later performance can change, and the features associated with success may not all have caused it. Readers should also ask whether an enduring institution creates enduring value for employees, customers, and communities. Survival alone is an incomplete moral standard.

Best for: founders, successors, and leaders thinking beyond one project or one charismatic individual.

Seven-day value and service blueprint

Write three statements: the purpose worth preserving, a behavior that demonstrates it, and a method that could change. Ask colleagues and one person served by the organization whether the distinctions make sense. Test one modest process improvement using existing resources. Record whether service improved while the core commitment remained intact. The observable benefit is a clearer decision rule and a useful experiment. Document the lesson so someone else can continue it. Avoid making grand goals before establishing capacity and accountability.

Discuss: Which practice do you defend as a value even though it may simply be a familiar way of working?

Source-based editorial review with original applications; full text not supplied.