Startup Lessons Learned

JANUARY 12, 2010

Recent economic events, technological change, and the rapid diffusion of information about the old models have combined to help us all realize just how important entrepreneurship is - and just how little we really know about it. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 146

Lean San Francisco Wiki Startup 146

YoungUpstarts

NOVEMBER 28, 2011

Customer development - along with acquisition and retention – is one of the primary firm activities that drive customer value. Increasing the frequency/volume of purchases of current products. Up-selling: moving customers up to higher level products/services.

Customer 162

Customer Customer Development Acquisition Pennsylvania 162

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

Startup Lessons Learned

AUGUST 1, 2009

When I try to unpack what people mean by the question, heres my best take on what they are asking: "Look, Steve Jobs doesnt go out and ask customers what they want. He doesnt put out crappy, buggy products and then ask for feedback. He tells customers what they want, and he gets it right. We tend to focus much more.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

OCTOBER 4, 2008

Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence. That institution will touch many people in its life: customers, investors, employees, and everyone they touch as well. Your blogs are full of rational thoughts and has nuggets of information.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. This last step is difficult, but I think its very helpful.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

MARCH 22, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection. The result is a profound democratization of the digital means of production. [.] We will not lose on their products -- after all, most of them are global.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

OCTOBER 28, 2008

Its different from selling a product, because it is not part of our regular business practice, is not something that relates to our core competence, and tends not to happen in a repeatable and scalable way. Most important slide: lessons learned Working product Key questions: what does the product do? who is the customer?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

JUNE 8, 2009

Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. For example, a recent event I held started with a customer validation exercise (actually, this example is fictionalized for clarity). Too much of this data is non- actionable.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

JULY 6, 2009

Before I close, let me quote just one additional bit of twitter feedback from one of the video beta-testers: bmeschke : @ ericries This is such GREAT information. Say you're not creating a product but doing a service? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

APRIL 14, 2009

This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 30, 2008

If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. Labels: product development 15comments: mukund said. Very good and informative.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 18, 2008

Many of them have really cool products shipping or about to be released, and I wholeheartedly agree with my friends at the iFund that the next generation of applications is going to be amazing. They cant present much information, unless you take the box off the shelf and look at it. Ive also been playing around with the App Store.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

APRIL 7, 2010

There are often counter-intuitive changes in customer behavior that depend on little details. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. Over many years, we’ve learned a lot about what customers want.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

JUNE 5, 2009

Lessons Learned by Eric Ries Friday, June 5, 2009 It’s a startup, not a spreadsheet Some people, when they start to realize the power of using data to inform their decisions, become obsessed with optimization. Sometimes an early negative result from an experiment is a harbinger of doom for that product, and means it should be abandoned.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

OCTOBER 19, 2009

Lessons Learned by Eric Ries Monday, October 19, 2009 Inc Magazine on Minimum Viable Product (and a response) Inc Magazine has a great new piece up about the increasing use of the Minimum Viable Product by businesses (and not just startups). Like many companies, TPGTEX rolls out new products several times a year.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

JANUARY 18, 2010

Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. The biggest waste in manufacturing is created from having to transport products from one place to another. The goal of both is to eliminate waste.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

AUGUST 24, 2009

Because of the incredible array of information available, we have a desperate need for filtering mechanisms. Customers will get to consume the content they want, and support the producers of that content directly, rather than having to rely exclusively on intermediaries. There are too many products clamoring for attention.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 17, 2009

It wont even get passed the registrant information screen to even get to selecting what you want to register for. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? March 19, 2009 6:11 PM Anonymoussaid. Ill be there! March 19, 2009 9:03 PM Anonymoussaid. Nope, no love.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Steve Blank

APRIL 15, 2016

Balancing business and family, and ensuring demand for your product were key lessons shared by two veteran entrepreneurs on today’s Entrepreneurs are Everywhere radio show. Before that, restaurateurs would never compare California with France. It was “France is great” and “California is jug wine.” Magdalena : I always did.

Silicon Valley 139

Silicon Valley California Entrepreneur Cofounder 139

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

MARCH 3, 2009

And if youre giving them all of the information they need to understand the companys strategy, customers, and processes, you can be confident that theyll be able to apply that understanding to their current responsibilities. Take a failed product launch. Whats that you say? Youre not currently doing all of those things?

Employee 146

Employee San Francisco Lean Software Review 146

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. Here’s why.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

SEPTEMBER 18, 2008

You can find out what it would take for them to adopt your product, and then follow up a week later and see if they did. Same with finding out what it would take to get them to recommend your product to a friend. I agree with the other comments, more information on yourself and what topics youll focus on would be helpful.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

JANUARY 2, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an internet connection. The result is a profound democratization of the digital means of production. The result is a profound democratization of the digital means of production.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

MAY 27, 2009

Sorry about this being out of context but I wonder if youve read "What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services". The presentation was informative, insightful, and humorous - as you pointed out the many ridiculous assumptions we make as entrepreneurs!

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Steve Blank

APRIL 15, 2016

Balancing business and family, and ensuring demand for your product were key lessons shared by two veteran entrepreneurs on today’s Entrepreneurs are Everywhere radio show. Before that, restaurateurs would never compare California with France. It was “France is great” and “California is jug wine.” Magdalena : I always did.

Silicon Valley 120

Silicon Valley California Entrepreneur Cofounder 120

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

SEPTEMBER 22, 2008

I usually recommend a three-part board, where the left column is where the scrum-style "product backlog" is maintained in priority order, the middle represents tasks in progress, and the right column is for tasks recently finished. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

FEBRUARY 22, 2010

Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. The work product is a more realistic test, although it requires much more work on the part of the candidate. For more on this subject, take a look at The product managers lament.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

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. For more information see [link] September 10, 2009 9:53 AM John Seiffer said. September 9, 2009 12:36 AM Richard Tibbetts said.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

MARCH 4, 2009

, it seemed time to return to the subject of investigating who my customers are. Today, Id like to spend some time on two techniques: the problem presentation and learning what channels of information reach customers. Every product ultimately is satisfying a need in the customers who buy it or use it.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

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

Startup Lessons Learned

JANUARY 4, 2009

In this scheme, all of the data related to a specific feature of a product are stored on the same machines. You need to store two kinds of information. This information is normally maintained by your operations team. hi, your artical and information is able to help me. The actual directory itself is straightforward.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

MARCH 24, 2009

In most applications, most of the time, customers return to use the application not in response to a notification or event, but under their own volition. These decisions are critical to the success of any high-engagement product, and they take place entirely inside the minds of customers. Impressive. It all depends on: 1.

Metrics 88

Metrics San Francisco Lean Viral 88

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. But I think its more productive to think of this as a spectrum. But I also think this could work in a lot of production scenarios.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68