Startup Lessons Learned

JANUARY 30, 2009

Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. As far as I know, there are no products that are immune from the technology life cycle adoption curve. Case Study: Continuous deployment makes releases n. We can skip the chasm.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. Very few startups fail for lack of technology. Case Study: Continuous deployment makes releases n. for Harvard Business Revie.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuous deployment makes releases n. Seeing whats possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

SEPTEMBER 8, 2009

Much of what makes the USA, and Silicon Valley in particular, such a great place to start a company is the result of good government policy. I'll add one more point: The SBIR program is based on a dated notion of small business research, and the multi-year process doesn't line up with the speed of many modern startups.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

NOVEMBER 29, 2008

If done right, a programming interview serves two purposes simultaneously. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. My technique is to structure a technical interview around an in-depth programming and problem-solving exercise. Have you tried it? Any advice?

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 17, 2008

For example, should we invest a week of engineering time into making our website more failure-proof (which were pretty sure will pay off right away) or into experimenting with a new technology (that might pay off in months, years, or never)? Case Study: Continuous deployment makes releases n. for Harvard Business Revie.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

NOVEMBER 5, 2008

What I found particularly interesting, looking back, is that the McCain campaign had superior technology, voter lists, and numbers on their side. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

NOVEMBER 19, 2008

What all these teachers had in common were two things: they were technology early adopters that were willing to take a chance on a new software product, and they all had similar problems organizing their classes and students. Case Study: Continuous deployment makes releases n. Learning is better than optimization (the local ma.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60