Startup Lessons Learned

JUNE 8, 2009

Sometime later, a guide would rattle off useful information, like the density of cars in the immediate vicinity, how that density compares to historical averages, the average mass and velocity of recent cars. So the product development team was busy creating lots of split-tests for lots of hypotheses. It required two things.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

APRIL 29, 2013

You can give advice about applying Lean Startup ideas to business areas other than product development. Our talks range from five minutes to three hours, and we structure them based on the information you have to share, so don’t worry too much about length. So, no, you absolutely do not have to be a developer to give a talk.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 8, 2008

True, there are the rare products that have literally no market risk; they are all about technology risk ("cure for cancer"). For the rest of us, we need to get some facts to inform and qualify our hypotheses ("fancy word for guesses") about what kind of product customers will ultimately buy. Lots of good usable information.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. Case Study: Continuous deployment makes releases n. Slides are below: The Lean Startup fbFund Edition View more documents from Eric Ries.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

OCTOBER 4, 2008

Your blogs are full of rational thoughts and has nuggets of information. It is encouraging to know someone with your reputation and connections is evangelizing truly valuable information for start-ups. Case Study: Continuous deployment makes releases n. Looking forward to more of these. Is ShareThis really necessary?

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

AUGUST 8, 2009

During the course of implementing a design, new information will arise, which many times will change the original design. The kinds of "new information" in the quote above are implementation details. 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

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. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

NOVEMBER 7, 2008

Depending on the type of product, postings on forums, classifieds and emails could give enough information to help gauge potential response. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 28, 2008

I have come to believe that there is a hierarchy of pitches, and that understanding where your pitch falls on this spectrum can assist in making decisions about what information to highlight. If you cant close the deal, maybe your company is at the wrong stage of its development, and its time to try a different tack.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

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. Case Study: Continuous deployment makes releases n.

Software Review 164

Software Review Engineer Management Technical Review 164

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. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Ill be there! Nope, no love.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

AUGUST 24, 2009

Because of the incredible array of information available, we have a desperate need for filtering mechanisms. Mass blasts of information are ineffective, because the broadcast channels are suffering from information overload (even in social media). There are too many products clamoring for attention. Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MAY 27, 2009

The presentation was informative, insightful, and humorous - as you pointed out the many ridiculous assumptions we make as entrepreneurs! Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 18, 2008

I originally thought I might get some development process tips (I manage developers), but I find that Im really enjoying your business tips (SEM, listening to customers, etc.). I agree with the other comments, more information on yourself and what topics youll focus on would be helpful. More of the same.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

JUNE 17, 2010

But scope negotiations between departments are an example of an “iterated prisoner’s dilemma&# situation, where the same parties repeatedly negotiate, and rely on their previous experience to inform their choices in the current round. Case Study: Continuous deployment makes releases n. Here’s why.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

MARCH 4, 2009

Today, Id like to spend some time on two techniques: the problem presentation and learning what channels of information reach customers. If this was a startup, Id be asking it of a sample of customers even more often, because getting a regular tracking result is helpful for informing your decision loop.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

APRIL 26, 2010

Lean mindsets and methods for innovation in any company a free webinar featuring: Eric Ries April 28, 2010 at 2:00 PM EDT The "Lean Startup" is the application of lean thinking to the process of innovation in startup companies — defined as a type of business where both the problem (customer need) and the solution (product) are unknown.

Lean 113

Lean San Francisco Continuous Deployment DC 113

Startup Lessons Learned

JANUARY 24, 2010

And, in the survey that was attached, I learned a lot of useful information about how to make this blog better. And, in the survey that was attached, I learned a lot of useful information about how to make this blog better. Case Study: Continuous deployment makes releases n. Welcome to the latest installment.

San Francisco 104

San Francisco Continuous Deployment Lean DC 104

Startup Lessons Learned

JULY 15, 2010

I freely admit that I have no inside information, no unique insight into what they are thinking. Comprehensive means it has to address all aspects of a startups life: marketing and product development, especially. I freely admit that I have no inside information, no unique insight into what they are thinking.

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

OCTOBER 4, 2010

Lessons Learned by Eric Ries Monday, October 4, 2010 Stop lying on stage Entrepreneurs crave information about successful startups, and they should. This is the same issue we see with vanity metrics : companies are giving the appearance of sharing information while actually engaging in spin or outright deception.

San Francisco 167

San Francisco Lean PR Metrics 167

Startup Lessons Learned

FEBRUARY 8, 2010

When those teams face difficult choices, its incredibly hard for them to come together and make an informed, fact-based decision. When those teams face difficult choices, its incredibly hard for them to come together and make an informed, fact-based decision. Case Study: Continuous deployment makes releases n.

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

Startup Lessons Learned

MARCH 23, 2009

This just isn’t a viable product.&# Labels: minimum viable product 5comments: Hazem Awad said. Nice post Eric thanks for sharing such useful information with us. users are clicking through) what happens if they find out there is NO product yet? Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

FEBRUARY 11, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Please teach kids programming, Mr. President Work in small batches Continuous deployment with downloads What is a market? (a

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

OCTOBER 19, 2009

TPGTEXs approach is an example of a trend in business that has been dubbed minimum viable product or microtesting. The idea is to develop something with the minimum amount of features or information needed to gauge the marketability of a product online. Case Study: Continuous deployment makes releases n.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

AUGUST 16, 2010

SlideShare used the two streams of information to segment their market and come up with three plans that recombined the custom channel features in meaningful ways. “We don’t give you all this Pro plan information right away when you join SlideShare. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

JANUARY 27, 2009

Use that data to make an informed choice about whether you want to change strategies. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. 8comments: Anonymoussaid.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

OCTOBER 16, 2013

As Shutterstock has grown, there are a few key elements to our continued development speed: Small, autonomous teams: The more a team can do on their own, the faster they can go. Continuous deployment: A key component of speed is to keep pushing out work. Over a thousand people work here now.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

JANUARY 1, 2009

My challenge for the new year is getting the word out about our product (AwayFind), while of course improving on conversions, etc. I see that as a great way for my product to grow, but while Ive partnered with companies in my consulting business, its not something Im as familiar with now that Im on the product side.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 5, 2008

This blog is very informative for me. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Education Guideline Book (1st Edition) Sep 2006 View SlideShare document or Upload your own.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

AUGUST 20, 2009

Specially because of Twitter and this information overload, I think many people have been struggling to reduce the number of RSS feeds they actually follow (it is my case), so it´ll become easier for us to keep track of your writing even if we´re not reading those blogs that often. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

JULY 31, 2009

lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager. The actual exchange of information occurs in private, in email. Case Study: Continuous deployment makes releases n. Using it to recruit takes less than a minute.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

APRIL 9, 2009

Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. Heres the promo; more information is available on their site. Both informative and inspiring! Case Study: Continuous deployment makes releases n.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

OCTOBER 7, 2008

Need some isight into this if you have any information. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Now the question is does Apple count this as two downloads or only as one?

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

NOVEMBER 13, 2008

The advantage of sharing this information widely is that it gives everyone insight into the kinds of problems the team is facing, but also insight into how those problems are being tackled. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167