Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Take the example of a design team prepping mock-ups for their development team.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

MAY 9, 2012

TLDR: Brant Cooper and Patrick Vlaskovits , authors of The Entrepreneur's Guide to Customer Development are back with a new book called The Lean Entrepreneur. It took the idea of Customer Development and made it accessible to a whole new audience. Illustrations by FAKEGRIMLOCK. You can pre-order it starting today.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

SEPTEMBER 22, 2008

is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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? All things being equal, of course, you’d rather have more revenue rather than less. And yet revenue alone is not a sufficient goal.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

DECEMBER 23, 2009

If all the engineers work on the same thing at the same time, and all the marketers do the same, and QA, and ops, all the way down the line, then each department develops its own team-based private reality. They were accustomed to measuring their progress primarily by gross revenue compared to their targets. Expo SF (May.

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JANUARY 15, 2010

They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market. Usually, they are delivering only a fraction of the revenue they promised. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JUNE 5, 2009

And so the spreadsheet is built with conservative assumptions, including a final revenue target. No matter how low we make the revenue projections for this new product, it’s extremely unlikely that they are achievable. In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

NOVEMBER 17, 2008

Now its time to start to think seriously about how to find a repeatable and scalable sales process, how to position and market the product, and how to build a product development team that can turn an early product into a Whole Product. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JANUARY 2, 2009

For the rest of us, there is an alternative: to create credibility by building a lean startup. We were even more embarrassed by the pathetically small number of customers we had, and the pathetically low amount of revenue we had earned so far. My 2008 revenues were over $100k on a 35k inventory. Retention cohort analysis.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

SVPG

NOVEMBER 22, 2013

But one of the real advantages from a product point of view is that there’s no legacy to drag along, there’s no revenue to preserve, and there’s no reputation to safeguard. However, once your product develops to the point that it can sustain a viable business (congratulations!), Protect Revenue and Brand.

Product 67

Product NDA Continuous Deployment Reputation 67

Startup Lessons Learned

AUGUST 24, 2009

All successful media companies had at their heart a series of editors, producers, and agents tasked with discovering and developing new talent. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. What is the right revenue model? My blog has over 14000 subscribers, for example.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 30, 2008

Lessons Learned by Eric Ries Thursday, October 30, 2008 John Doerrs 10 lean startup tips I just saw video of John Doerrs talk yesterday at VentureBeat’s “How to manage your start-up in the downturn&# roundtable event. Not just about expenses, about increasing revenue. Everyone from the receptionist to engineers is selling.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

MAY 1, 2009

Lessons Learned by Eric Ries Friday, May 1, 2009 Lean Startup webcast post-game Wow, what an incredible turnout for webcast this morning, right on the heels of a phenomenal crowd at startup2startup last night. Its been a great twelve hours for the lean startup! wogsland : Still not understanding the "lean" aspect. What a thrill.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

AUGUST 16, 2010

First, SlideShare is a fantastic product (that I use on a regular basis) and an impressive company example of Lean Startup practices in action. Second, their story illustrates a key Lean Startup idea: proving the business in micro-scale. That is customer development. Did you find this post useful? How are we doing?

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

JANUARY 27, 2009

These are companies that generate revenue by offering a free product with an upsell or premium version. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Expo SF (May. .

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. Let me end with a challenge: see if you can find and kill just one myth in your development team.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Startup Lessons Learned

JULY 9, 2009

We were focused on revenue, but we didnt understand that revenue is not important for its own sake in an early stage company. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

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. For one, capacity development.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

DECEMBER 14, 2009

A great product enables customers, developers, partners, and even competitors to exchange their unique currencies in combinations that lead to financial success for the company that organizes them. We cultivated a passionate community that nurtured a skilled set of developers.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

MARCH 27, 2009

In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. To increase the number of iterations you have left, you can either increase cash on hand (by raising money or increasing revenues), reduce burn rate, or increase the speed of each iteration. Work in small batches.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

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. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. That’s the local maximum.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 13, 2008

And one day a remarkable thing happened: we started making more than five dollars a day in revenue. Only much later did I realize that this was an application of customer development to online marketing. There is much work that I need to do (the only developer so far) before we have something customers can use. Expo SF (May. .

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 29, 2008

Revenue is always my preferred measure, but you can use anything that is important to your business: retention, activation, viral invites, or even customer satisfaction in the form of something like net promoter score. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. .

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

usersknow.blogspot.com

APRIL 30, 2010

It’s not enough to just launch a feature and see if your revenue increases. You need to have some sort of plan for testing to see how it’s affecting key metrics , whether those are revenue, retention, registration, user happiness, or some other number you care about. How Am I Going to Get Feedback on this Feature?

Software Review 40

Software Review Agile San Francisco Advisory Board 40

Startup Lessons Learned

NOVEMBER 22, 2008

It is an essential lean startup tool that combines seemingly irreconcilable attributes: it provides operational, actionable, real-time feedback that is truly representative of your customers experience as a whole. The whole episode cost us hundreds of thousands of dollars in lost revenue. Unfortunately, revenue a trailing indicator.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. Labels: agile , product development , Test-driven development 11comments: William Pietri said.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

SEPTEMBER 11, 2009

At a certain point in IMVU’s development, we faced a difficult choice. This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline. I agree that listening and communicating is a key to success, but customer development can only do so much.

Community 158

Community Management Lean Software Review 158