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. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

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

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. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Customer data is normally partitioned according to customer id.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? What is customer development? No departments The Five Whys for Startups (for Harvard Business R.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JUNE 17, 2010

I suggested that we change the underlying architecture of our UI system so that the artists would be able to build their own UI pieces themselves and then integrate them into the product without requiring new code every time. The Entrepreneur’s Guide to Customer Development ▼ June (3) What is a startup?

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. The "just fix it" mentality is counter-productive here. Just change it.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.)

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JUNE 15, 2009

Both sides start to think of their point of view in moralistic terms: “those guys don’t see the economic value of fast action, they only care about their precious architecture diagrams&# or “those guys are sloppy and have no professional pride.&# No departments The Five Whys for Startups (for Harvard Business R.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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

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. Filed under: Customer Development.

Founder 323

Founder Cofounder Advisory Board Burn Rate 323

Startup Lessons Learned

FEBRUARY 16, 2009

Lets start with a distinction between shipping new software to the customer, and changing the customers experience. The idea is that often you can change the customers experience without shipping them new software at all. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

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

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

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. Eric, Is this post about Architecture? Good luck, engineering manager.

Software Review 164

Software Review Engineer Management Technical Review 164

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. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture?

San Francisco 146

San Francisco Lean Agile Java 146

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

DECEMBER 28, 2009

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. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

ConversionXL

SEPTEMBER 10, 2012

“ There are no facts inside your building, so get outside ,” is one of the mantras of Steve Blank , the father of customer development and author of The Startup Owner’s Manual. Use it for your product development (and for deciding what to sell in the first place). Talk to people.

Audience 122

Audience Analytics B2B eCommerce 122

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?" "I am a creative guy with a startup idea." However, I do spend a lot of time daydreaming.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

techcrunch.com

OCTOBER 23, 2010

it really doesn’t matter if you’re not in SV, i think that’s what the author is trying to say [link] tenthings what he’s saying is he partnered up with engineers, not with other business grads/entrepreneurs, and that’s what’s important to have a team that can produce the product not just market it.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Startup Lessons Learned

JANUARY 30, 2009

Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Even a great architecture becomes inflexible.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. On the other, they already have a team fully engaged on making their product architecture better.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79