Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. They were interested in the tools and new distribution medium kaChing provided. kaChing has been very active in the Lean Startup movement.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 7, 2008

The basic idea is to extend agile, which excels in situations where the problem is known but the solution is unknown, into areas of even greater uncertainty, such as your typical startup. Can this methodology be used for startups that are not exclusively about software? No departments The Five Whys for Startups (for Harvard Business R.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 10, 2008

Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process. Expo SF (May. .

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

JULY 9, 2010

And that narrow definition of entrepreneurship doesn’t count all of the managers inside established companies who are effectively engaged in the same process of building an internal startup (see What is a startup? Let’s start with the startup personality attributes. for my more expansive definition).

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 2008

October 17, 2009 10:34 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. .

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 14, 2008

Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" The people who are the lifeblood of an early-stage startup are earlyvangelists. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Dont confuse passion with volume.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

APRIL 26, 2009

Its a force that allows startups to build products at parity with much larger companies - cheaper and much faster. Its a key lean startup concept. We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels. Leveraged distribution channels.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? In an early-stage startup especially, revenue is not an important goal in and of itself. Let’s start with a simple question: why do early-stage startups want revenue?

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 18, 2008

I want to get an idea of how startup guys think. As a shoestring entrepreneur with a SaaS (well, not really, but sort of) offering that we present to very large companies (think 10K+), I love your common sense suggestions about metrics and testing. My background isnt metrics, but we came to it as a matter of practicality.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 1, 2008

Labels: Test-driven development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 6, 2008

Ive been even more impressed by the various Greasemonkey compilers out there, that let you turn a Greasemonkey script into a full-blown Firefox extension, for easy distribution. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 2, 2008

A growing startup with a well-run product team will have a history of steady progress. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. How do you plan for it?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 10, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 10, 2008

I have been thinking a lot about what a new version of this test would look like, given what Ive seen work and not work in startups. but I have not seen that dysfunction in any of the startups I advise, so hopefully its behind us. What other questions would you ask a brand-new startup about its product development practices?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 10, 2008

I see startups struggle with this all the time. Update : bonus thought from Dharmesh Shahs 8 Startup Insights Inspired By The Mega Mind of Seth Godin: 6. Too often, startup founders talk about how they are pushing to get to “critical mass&# and how “economies of scale&# are going to kick in. But then what?

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 16, 2008

thanks for the mention:) September 17, 2008 11:56 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 8, 2008

I was building a new startup in 1999, and wanted to do it right. That startup didnt turn out so well, but not for lack of technology. I cant really imagine how much it cost our "grownup" counterparts at other dot-com startups to get their first app up and running. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

MARCH 28, 2010

Lessons Learned by Eric Ries Sunday, March 28, 2010 Two new scholarship programs for lean startups Thanks to the generosity of sponsors, Im pleased to be able to announce two scholarship programs for upcoming lean startup events. Now the company is growing, profitable, and proving that lean startups can scale.

Lean 109

Lean Programming San Francisco Continuous Deployment 109

Startup Lessons Learned

SEPTEMBER 18, 2008

Lessons Learned by Eric Ries Thursday, September 18, 2008 How to get distribution advantage on the iPhone I have had the opportunity to meet a lot of iPhone-related companies lately. There are other models, in other distribution channels. On Facebook, viral distribution has proved decisive. I havent found any yet.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

JULY 15, 2010

My belief is that the root cause of the IPO shortage is that successful startup companies cannot find productive ways to invest large amounts of money to scale anymore. For software companies especially, scaling distribution and development is comparatively cheap. The old ways aren’t working. But these are still early days.

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

OCTOBER 7, 2008

Lessons Learned by Eric Ries Tuesday, October 7, 2008 The App Store after the gold rush I wrote earlier about the issue of distribution advantage on the iPhone. I think its helpful to think about two kinds of competition for distribution: acquisition competition and retention competition. So what can you do? I am a little curious here.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

SEPTEMBER 27, 2010

Yet startups rely on collective learning in order to find their way. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. Startups are different, leading to this axiom: if you do not know who the customer is, you do not know what quality is. No vanity metrics should be looked at.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

FEBRUARY 10, 2009

It’s also not a new technique here, we’ve been practicing continuous deployment for years; far longer than I’ve been a member of this startup. Our tests suite takes nine minutes to run (distributed across 30-40 machines). But, unfortunately, startups cant afford to adopt that standard. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 28, 2008

Lessons Learned by Eric Ries Sunday, September 28, 2008 The lean startup comes to Stanford Im going to be talking about lean startups (and the IMVU case in particular) three times in the next two weeks at Stanford. I struggle to try and make the students actually experience how confusing and frustrating startup environments are.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. For example, I’m a big believer in split-testing.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

FEBRUARY 22, 2010

For startups (and other innovators ), that’s a decisive advantage. The work itself, especially in startups, depends primarily on intelligence, communication, creativity and empathy. Their recent article suggests that startups led by women are actually more successful, on average, than those led by men.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 29, 2008

Luckily, the metrics helped us figure out the difference. Question 2: If your product has areas where people read and then different areas where people interact, are there ways to do metrics to determine where people spend their time? Were looking to metrics to determine how users interact with our product. Expo SF (May.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 13, 2008

Its now a technique I recommend for any web-based startup. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Lessons Learned - the Conference (April 23.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 5, 2008

MogileFS - "Distributed (meta) file system. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Lessons Learned - the Conference (April 23.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

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. Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start. But startups rarely have either luxury. to store it.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 You dont need as many tools as you think Im always excited to see someone else writing about lessons learned from their startup, and wanted to link today to Untitled - Startup Lessons Learned -- Take it with a grain of salt. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 22, 2008

Labels: product development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

OCTOBER 23, 2009

The lean startup methodology is based on enlisting customers as allies, which requires honesty and integrity. The following was written an actual lean startup practitioner. It was originally posted anonymously to the Lean Startup Circle mailing list, and then further developed on the Lean Startup Wiki ’s Case Studies section.

San Francisco 144

San Francisco Customer Wiki Lean 144