Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Unfortunately, customers hated that initial product.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 8, 2009

One of the topics that raised heated debate was whether I had conflated technical design with product design , because I made the admittedly counter-intuitive claim that sometimes good technical design actually leads to increased technical debt. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

Steve Blank

AUGUST 27, 2012

He turned his PhD thesis into a killer product, got it funded and now was CEO of a company of 30. It was great to watch him embrace the spirit and practice of customer development. He was constantly in front of customers, listening, selling, installing and learning. We’re building the wrong product!”

Founder 321

Founder Cofounder Advisory Board Burn Rate 321

Startup Lessons Learned

JUNE 17, 2010

The art team would often be involved in the specification phase of a new feature, since they were responsible for the look-and-feel of the product. When the art team would review the final product, they were inevitably outraged – it deviated from the spec in ways they considered major.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

SEPTEMBER 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

DECEMBER 28, 2009

Most customers of most products hate new releases. Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. Keep split-testing, but keep this iron rule: if it doesnt change customer behavior, its not a feature.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JUNE 15, 2009

This condition makes it much easier for teams to innovate, experiment, and achieve sustained productivity. One large source of waste in development is “double-checking.&# One is used by engineers to refer to the process of getting code fully integrated into production. Continuous deployment also acts as a speed regulator.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. At IMVU , most of them thought our product was ridiculous at best; hopeless at worst. Still, a startup product development team is a service organization.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. The "just fix it" mentality is counter-productive here.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document. and so forth.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. In this scheme, all of the data related to a specific feature of a product are stored on the same machines. Customer data is normally partitioned according to customer id.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

FEBRUARY 16, 2009

Joe Ludwig goes through his current release process and determines that the current time to make and deploy a release is about seven and half hours, which is why his product is released about once a month. Lets start with a distinction between shipping new software to the customer, and changing the customers experience.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 8, 2009

I started my last company with 100% off-shore resources because I could never have completed Customer Development at a reasonable cost of money or regulatory burden had I employed US Citizens. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

DC 90

DC Washington San Francisco SBIR 90

ConversionXL

SEPTEMBER 10, 2012

The aim of marketing is to know and understand the customer so well the product or service fits him and sells itself. how they choose and compare products in your category, you know how to structure and prioritize content on your site. The data you need to know depends on the product and whether you have a B2B or B2C business.

Audience 122

Audience Analytics B2B eCommerce 122

techcrunch.com

OCTOBER 23, 2010

So for this first post, here’s the best advice I can give you: join an awesome founding team and get your product out the door ASAP. But six months in, you’re gonna cry when you see someone else put out that same product you’re pitching me right now. Like I said, forget everything else and just get your product out the door.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

www.quora.com

JANUARY 16, 2011

" => I have not bothered to put up a landing page, survey to test customer demand, or done any customer development whatsoever. "Where is the best place to find a rockstar developer to bring it to life?" Nor does picking apart 200 web products and analyzing what works and doesn't.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

Startup Lessons Learned

JANUARY 30, 2009

Build a truly mainstream product. Build the product in stealth mode to build buzz for the eventual launch. The whole company and board play-tested the product to see its new features first hand. Everyone had fun; the product worked. But that was two full years before any customers were allowed to use it.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

They have a product that has a moderate number of customers. Its well done, looks professional, and the customers that use it like it a lot. Still, theyre not really hitting it out of the park, because their product isnt growing new users as fast as theyd like, and they arent making any money from the current users.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79