Great Quote by Gillian Tans
“A long time ago, we had to build interfaces to connect with other companies, and I thought that was a great idea. The company had to pay a lot of money to build it and basically launched it, but our whole operating system almost broke. So, we couldn't continue it. In the end, I had to go on the train to Paris to explain that I had spent millions.”
About This Quote
A costly interface project failed, nearly breaking the operating system, leading to a costly explanation trip to Paris.
In simple terms: A big, expensive project failed and required costly damage control.
Key Takeaway
Learn from failures to prevent costly overruns.
Themes
failure
technology
budget
communication
Mood
cautious
reflective
Type
case study
lesson
When to use this quote
- software development
- large‑scale integration
- financial oversight
- crisis communication
Key Concepts
project management
risk assessment
Questions to Reflect On
- What safeguards could have prevented the failure?
- How to improve stakeholder communication?
A Different Perspective
The narrative may oversimplify complex technical issues.
![“Lehman and Belady have studied the history of successive releases in a large operating system.[6] They find that the total number of modules increases linearly with release number, but that the number of modules affected increases exponentially with release number. All repairs tend to destroy the…” quote by Frederick P. Brooks Jr](https://sms4smile.com/quotes/img-quotes/115/frederick-p-brooks-jr-11230_history_lehman-and-belady-have-studied-the-histo_145780.jpg)
