The Equity Kicker
MAY 7, 2013
These firms have had a significant impact on growth over the last 20 years through the bubbles and crashes they create – e.g. the Long-Term Capital Management crash of 1998, the Dot-Com crash of 2000, and the housing meltdown of 2008.
Steve Blank
MARCH 18, 2011
Startups built every possible feature the founding team envisioned (using “Waterfall development,”) into a monolithic “release” of the product taking months or years to build a first product release. Customer Development , Agile Engineering and the Lean methodology enforced a process of incremental and iterative development.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Steve Blank
NOVEMBER 1, 2010
But nine months after the first call was made in 1998, Iridium was in Chapter 11 bankruptcy. Second, since it knew the solution, it went into a 8 -year Waterfall engineering development process. Waterfall development is a sequential way to develop a product (requirements, design, implementation, verification – ship.)
Steve Blank
JANUARY 4, 2012
1998 – the MPAA got congress to pass the Digital Millennium Copyright Act (DMCA), making it illegal for you to make a digital copy of a DVD that you actually purchased. Ironically, it was Valenti’s skill in hobbling competitive innovation that negated any need for studios to develop agility, vision and technology leadership.
Startup Lessons Learned
FEBRUARY 7, 2013
The Embrace infant warmer was developed - by getting out of the country -- and how Rob Emrich learned and scaled his non-profit, Road of Life. Struggling to explain the successes and failures of those companies, I discussed principles like continuous deployment, customer development, and a hyper-accelerated form of agile.
Startup Lessons Learned
JANUARY 19, 2009
One, which is described in great detail in the Mythical Man-Month (in finding that link, I discovered that today is coincidentally the exact 11th anniversary of my first purchasing that book: Jan 19, 1998), is that as you add people to a team or project, there is an increase in communications overhead that makes everyone slightly less productive.
Startup Lessons Learned
JUNE 8, 2009
So the product development team was busy creating lots of split-tests for lots of hypotheses. Within a few weeks, they have already discovered that huge parts of their product, which cause a lot of extra work for the product development team due to their complexity, are not affecting customer behavior at all. Expo SF (May.
Expert insights. Personalized for you.
94 
Let's personalize your content