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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Thanks for the comments.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

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. who is the customer? 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

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" Very good and informative. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. I always assumed I wouldnt manage anybody.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process. Get product into customers’ hands. More on that in a moment.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

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 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? Case Study: Continuous deployment makes releases n. March 19, 2009 6:11 PM Anonymoussaid. Ill be there!

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

MAY 27, 2009

This will be an in-depth discussion with a handful of entrepreneurs and founders that have been pre-selected. 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.

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. When it becomes possible to build products "live" with customers, the cycle time changes and design becomes a much more dynamic process.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. 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.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

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. So why you?

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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. Are the engineers in the customer development team allowed to push quick and dirty "prototypes" to production?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 24, 2009

Because of the incredible array of information available, we have a desperate need for filtering mechanisms. The key tools of this new marketing are: targeting, filtering, and customer insight. Mass blasts of information are ineffective, because the broadcast channels are suffering from information overload (even in social media).

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 16, 2010

It requires separating the product launch from the marketing launch (see Dont Launch ) as well as other staple Lean Startup tactics: minimum viable product, split-testing, customer development and the pivot. “We don’t give you all this Pro plan information right away when you join SlideShare.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

JANUARY 24, 2010

In fact, when I crossed the five subscriber threshold, I was moved to write about my excitement and about the advantages of having a pathetically small number of customers. 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.

San Francisco 104

San Francisco Continuous Deployment Lean DC 104

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

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

Startup Lessons Learned

APRIL 26, 2010

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. More information is available here. Case Study: Continuous deployment makes releases n.

Lean 113

Lean San Francisco Continuous Deployment DC 113

Startup Lessons Learned

JULY 15, 2010

When private capital is available in sufficient quantities to satisfy investor and founder liquidity needs, why go IPO? I freely admit that I have no inside information, no unique insight into what they are thinking. When private capital is available in sufficient quantities to satisfy investor and founder liquidity needs, why go IPO?

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

OCTOBER 19, 2009

It isnt until a customer actually clicks or calls to place an order that TPGTEXs developers will build the software. "We We do not develop a product until we get a paying customer," says Orit Pennington , who co-founded the six-employee company with her husband in 2002.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

JANUARY 27, 2009

For founders, I think it also has another big attraction: the ability to avoid a lot of " free vs paid " arguments. Take a cohort of new customers and expose them to a completely different approach, and measure their behavior over time. Use that data to make an informed choice about whether you want to change strategies.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

FEBRUARY 11, 2009

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. February 19, 2009 5:23 PM Maryam Asif said.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

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

NOVEMBER 5, 2008

This blog is very informative for me. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

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 13, 2009

Armed with that information, we can make rational trade-offs. What may be less obvious is that fast feedback also increases the efficiency with which we generate information and learn new things. Team New Zealand completed many more cycles of learning, and they generated more information in each cycle.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

OCTOBER 7, 2008

Need some isight into this if you have any information. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. 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

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

JULY 9, 2009

In fact, I remember sending him and his obscure-to-me co-founder (aka Reid Hoffman ) a bug report early-on, instead of taking them up on their offer of an in-person meeting. I managed to be envious of dozens of other companies, founders, and colleagues who seemed to be having tremendous success but later turned out to be a mirage.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

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

AUGUST 1, 2009

When a customer tells you how they feel about your ideas, that doesnt tell you anything about your ideas. It tells you something about what that customer thinks and feels. Figuring out whether and how to incorporate that new information into your vision is your job. Case Study: Continuous deployment makes releases n.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167