Ratan Tata, 2009

“We tried and we tried, and we improved, and we reconceived what we had to do. It’s no different in business.”

Ratan Tata said this in a 2009 Cornell documentary while reflecting on design education and his career. The sentence connects persistence with revision: progress did not come from repeating an unchanged attempt, but from improving and reconceiving the problem when the original approach proved insufficient. That distinction separates disciplined perseverance from stubbornness. A committed team preserves the purpose while remaining willing to alter the product, process, assumption, or even the definition of the problem. Each attempt should create information that makes the next one more intelligent. Read closely, the quotation is an operating claim rather than a decorative slogan. It asks leaders to connect an admired principle with the conditions, measures, and behavior through which customers and employees would actually experience it.

Teams can state the purpose and current hypothesis separately, run bounded tests, and document what the evidence changes. Review gates should ask whether to continue, modify, combine, or stop, with resources moving only when the next attempt is genuinely different. To make that connection visible, decision makers should name the choice the idea is meant to change, the evidence they will review, and the person responsible for follow-through. A principle becomes useful when others can observe its effect on work.

Persistence can consume money, time, and trust when leaders are emotionally attached or insulated from consequences. Reconceiving must include customer evidence, safety, affected communities, and opportunity cost. Stopping can be the responsible result of learning. The strongest interpretation holds ambition and restraint together. Teams should ask who benefits, who carries risk, what evidence would disconfirm the current belief, and how a person affected by the decision can question it before costs become difficult to reverse.

Rapid prototyping and AI make iteration cheaper, but they can also produce endless variations without deeper understanding. The advantage comes from better questions, representative feedback, and the courage to change the system rather than merely regenerate the surface. For one stalled initiative, write what has been learned across attempts, identify the assumption that no longer deserves protection, and design the next test so it can support a real decision rather than prolong momentum. A practical review should compare the promise with outcomes, experience, and unintended effects. The final test is not whether the words sound inspiring, but whether they help the organization learn earlier, act responsibly, and create value that can withstand scrutiny. Results should be shared in plain language, including disappointments, so later decisions begin with accumulated evidence rather than a polished story that hides the conditions under which the earlier choice succeeded.