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

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. "Spy satellites produced far more raw information than the government's battalion of overworked analysts could handle.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

MARCH 16, 2009

As it was, if you followed the XP practices, which included frequent releases, most people in the product management hot seats quickly realized that the users and (real) customers were the often-unwitting source for a lot of information key to product success. Brilliant insights, advice and information on your blog.

Agile 111

Agile Customer Development Developer San Francisco 111

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. Great information on the hierarchy of pitching. Case Study: Continuous deployment makes releases n.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

NOVEMBER 8, 2008

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. You can start to think through the consequences of this information before its too late. Lots of good usable information. I plan to pick up this book though.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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

SEPTEMBER 30, 2008

Very good and informative. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. April 21, 2009 4:51 PM Geethan said. April 26, 2009 8:40 PM RubyFocus Groups said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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). I used to be skeptical of all this talk of “personal brand.&#

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

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. Case Study: Continuous deployment makes releases n. These principles are every bit as true today as then.

Software Review 87

Software Review Design Software San Francisco 87

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

SEPTEMBER 18, 2008

I agree with the other comments, more information on yourself and what topics youll focus on would be helpful. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. More of the same.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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. They want to do activities.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

JULY 29, 2009

To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. Case Study: Continuous deployment makes releases n. One last thought. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 14, 2009

Very thorough and informative post. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. I appreciate it! April 23, 2009 12:46 PM Anonymoussaid. Great post!!

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 20, 2008

I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. By shipping software early, you give them continuous feedback about how it well its working. Case Study: Continuous deployment makes releases n.

Software Review 164

Software Review Engineer Management Technical Review 164

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

APRIL 26, 2010

Want to talk about applying the lessons beyond software, internet, and small companies? This is intended for anybody who is working on new innovations, whether that means continuous improvement at the front lines, or new product development in a mature manufacturing company. More information is available here. Details are below.

Lean 113

Lean San Francisco Continuous Deployment DC 113

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 Metrics PR 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

Nice post Eric thanks for sharing such useful information with us. "Selling information you research, into well-constructed, content-rich PDF files for $6 is a great way of getting the contacts you need to [get a minimal viable product for SAS]. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

www.subelsky.com

FEBRUARY 25, 2010

This tool adds a lot of context to bug discussions, because nonprogrammers can reference the exact Hoptoad URL containing all of the information a programmer needs to fix a bug (including backtraces). Because it has an RSS feed, one could also use "Unresolved Hoptoad Errors" as a metric influencing the continuous deployment system.

Lean 41

Lean Baltimore Ruby Maryland 41

Startup Lessons Learned

JULY 15, 2010

I freely admit that I have no inside information, no unique insight into what they are thinking. I freely admit that I have no inside information, no unique insight into what they are thinking. Case Study: Continuous deployment makes releases n. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

IPO 166

IPO San Francisco Lean Silicon Valley 166

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

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

JULY 13, 2009

Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. If we showed the Toyota Production System to an Internet protocol engineer, it is likely that he would remark, "That is a tail-dropping FIFO queue.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JANUARY 1, 2009

As for a topic Im particularly interested in, Id be curious about partnerships: the type of formal or informal relationships one tech co has with another in terms of either cross marketing or integrating each others products. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

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

OCTOBER 19, 2009

The idea is to develop something with the minimum amount of features or information needed to gauge the marketability of a product online. 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 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. Who wants that stuff posted on the internet? The actual exchange of information occurs in private, in email. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

OCTOBER 7, 2008

This is completely analogous to the situation elsewhere on the internet, where launching a new website, product, or service with PR is getting harder and harder. Need some isight into this if you have any information. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 68

San Francisco Lean Retention SEM 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

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

Startup Lessons Learned

JULY 9, 2009

Id been on the internet since I was playing MUDs as a kid, but by 1999 I felt Id already missed the boat. That was one of the most informative post I've ever read. Case Study: Continuous deployment makes releases n. I pretty much missed all the trends. Thanks for sharing your stories along the way.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

SEPTEMBER 18, 2008

They cant present much information, unless you take the box off the shelf and look at it. Im on the team that released one of the Taxi apps, and we agree that the "SEO" and placement on the App Store can sometimes leave users with insufficient or inaccurate information to make decisions. Hey Eric, very interesting post.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74