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 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. After all, the worst kind of waste in software development is code to support a use case that never materializes. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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

MAY 28, 2009

Markets with Customer/Market Risk are those where the unknown is whether customers will adopt the product. is whether there is a customer and market for the product as spec’d. These are markets where it may take 5 or even 10 years to get a product out of the lab and into production. The real risk in markets like Web 2.0

Vertical 162

Vertical Silicon Valley Marketing Customer 162

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. This condition makes it much easier for teams to innovate, experiment, and achieve sustained productivity.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

AUGUST 14, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference, who has created content for a number of startups. In our ongoing exploration of how people actually implement Lean Startup methods in their workplaces, we’re asking practitioners to share their techniques. Steph: Segmentation and timing. Steph: For me, it leads.

Lean 167

Lean Conversion Audience Design 167

Steve Blank

JUNE 25, 2009

Twenty eight years ago I was the bright, young, eager product marketing manager called out to the field to support sales by explaining the technical details of Convergent Technologies products to potential customers. They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 143

Technology Silicon Valley Fractional VPE Part-Time VPE 143

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

Hearpreneur

APRIL 13, 2022

One of the most important lessons entrepreneurs can learn from Dropbox is to adopt the lean start-up methodology and start. Their innovation lay not just in their product, but their viral video marketing campaign involving slamming raw eggs on their mattress to show that they wouldn’t break due to their mattresses’ high-tech cushioning.

Artificial Inteligence 76

Artificial Inteligence Entrepreneur Technical Review Software Review 76

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

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.

Product Development 68

Product Development Developer San Francisco Product 68

Steve Blank

SEPTEMBER 25, 2014

It wasn’t always perfect, but it was way more right than wrong, It informed our product development to a great degree and kept us working on more or less the right stuff. Relational architecture (a collection of data organized as a set of formally described tables) in the first place—all new stuff, and technically compelling.

Technical Review 334

Technical Review Venture Capital Software Review Database 334

Up and Running

AUGUST 4, 2016

If your construction tastes lean toward the more aesthetic, check out Contract. This publication puts the spotlight on commercial interior design and architecture, an angle most other sites don’t take. Read the blog, or subscribe to the magazine here. Construction Enquirer.

United States 60

United States Architecture America Lean 60

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. Why do they harbor that paranoia?

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

Seeing Both Sides

AUGUST 3, 2012

The Lean Start-Up movement, as exemplified in Eric Ries' book The Lean Start-Up, has appropriately focused a great deal of attention on the hard decisions and techniques required to create a company from nothing. I have been thinking lately about how hard it is to scale start-ups. Scaling Akamai – Part 1: A Little Fat.

Distribution 49

Distribution Lean Massachusetts Cofounder 49

YoungUpstarts

APRIL 14, 2014

This is the magic number for leadership teams, product teams, research teams, design teams, and more. Not too long ago, German software giant SAP blew up the management framework for its 20,000-person development department and replaced it with “mini-teams” of roughly 10 people. The principle works in business, too.

Agile 196

Agile Leadership Architecture Product Development 196

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. Two of my favorites are from Flixster and LiveJournal. Easy to understand.

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. This is a great example of lean startup thinking. But I think its more productive to think of this as a spectrum.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 8, 2009

Beyond just those who will be hearing about the lean startup for the first time, Im expecting to shake a lot of hands and have a lot of interesting side conversations. Government IT solutions can be iterative, they don't have to be designed down to the last detail by architecture astronauts before implementation. Expo SF (May.

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

andrewchenblog.com

MARCH 10, 2010

If you haven’t finished developing your product yet, that’s no excuse! In fact, in many ways talking to your customer and understanding them great detail is often much more powerful before you even go through the product development process. Customer driven products are the only way to go. our product?

Customer 42

Customer Advisory Board RSS Software Review 42

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

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. Even a great architecture becomes inflexible. Focus on quality.

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. 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. 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