Adding to the stress was the fact that weâd left ourselves so little time to get it all done. We had a self- imposed deadline of July 1984 - just eight months after John came aboard - because that was when the annual SIGGRAPH Conference would be held in Minneapolis. This week-long computer graphics summit was a great place to find out what everyone in the field was up to, the one time every year that academics, educators, artists, hardware salesmen, graduate students, and programmers all came together under one roof.
Related Quotes
When Rebecca launched Asana Labs in 2022, she was inspired by Armeetingeddon to recruit a small group of colleagues for a pilot program called Meeting Doomsday. All participants started by removing all standing meetings with five or fewer people from their calendars for forty-eight hours. They used the break to think about which meetings were valuable, deciding which to subtract, modify, or keep. As we detail later in this chapter, this prototype âmeeting repair and removalâ tool showed much promise. We worked with Rebecca to scale lessons from Meeting Doomsday to sixty employees who participated in the subsequent Meeting Reset program. We learned that people wanted a fine-grained but simple way to assess meetings. We asked them to use a three-point scale to rate how much effort each meeting required and its value for helping them achieve goals. Of over 1,100 standing meetings, those Asana employees rated more than 50 percent as low value and identified more than 150 that required great effort and had low value.
In fact, Lou Gerstner claims that his greatest ally in breaking free from the past was IBMâs own precipitous collapse. But he also knew that the task of shaking people out of their stupor and getting them âto think and act collaboratively, as hungry, curious self-starters,â would take at least five years - and even then, he confesses, he underestimated the time required.
At the other end of the spectrum, if you have an organization thatâs generally working pretty well, you want to protect the part thatâs working by going a little slow, as McNerney did.
The product was known as a âgraphics accelerator,â and at least thirty-five competitors were trying to build one. Huang worried there was no space for a thirty-sixth. The leading expert in computer graphics was Jon Peddie, who had written several textbooks on the topic. Huang had reached out to Peddie to get a sense of the market, and the two soon became friends, with Huang calling incessantly, asking questions late into the night. Peddie advised Huang that the space was too crowded and that many of the best engineers were already working for other start-ups. âI told him not to do it,â Peddie said. âThat was the best advice he never took.
FOUR: Thirty Days
âWhen David Kirk arrived at Nvidiaâs offices for the first time, in 1996, he could see at once that the company was doomed. Kirk was a graphics expert who consulted throughout the Valley, which was like being a connoisseur of failure. He had watched a great many start-ups falter, including his own, and Nvidia exhibited all of the symptoms of a company hurtling toward insolvency. The employees looked haggard and demoralized, the quirky product didnât fit with the market, and the supposedly chummy founders were now deadlocked in a âtechnical discussionâ that was obviously more than just a discussion and obviously about more than just technology.
Nvidiaâs frenzied six-month shipping cycle left the perfectionists at 3dfx at a disadvantage. At one point, one of 3dfxâs founders publicly speculated about declaring a truce between the two companies so that technical standards could be established before the next generation of products shipped. âThatâs when I knew we had him,â Kirk said. âWe were in a death struggle with 3dfx, and one of us had to die.