Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

SEPTEMBER 10, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. After twelve months Handspring’s revenue was $170 million. They never understood Market Type. End result?

Customer Development 205

Customer Development Developer Customer Silicon Valley 205

Steve Blank

NOVEMBER 5, 2009

Chasing funding versus chasing customers and a repeatable and scalable business model, is one reason startups fail. Product Development – Getting Funded as The Goal In a traditional product development model, entrepreneurs come up with an idea or concept, write a business plan and try to get funding to bring that idea to fruition.

Customer Development 266

Customer Development Developer Customer Silicon Valley 266

Steve Blank

APRIL 30, 2009

And the final lesson was that we were keeping score on our packaging with the wrong metrics – it wasn’t about awards, it was about sales in the retail channel. We had been outsourcing an important part of our demand creation strategy – packaging – to an outside agency without having the expertise to judge or manage the results.

Sales 120

Sales Silicon Valley RSS Las Vegas 120

Steve Blank

JULY 30, 2009

Unfortunately most startups learn this by going through the “Fire the first Sales VP&# drill: You start your company with a list of potential customers reading like a “who’s who&# of whatever vertical market you’re in (or the Fortune 1000 list.) Your board nods sagely at your target customer list.

Silicon Valley 134

Silicon Valley RSS California Customer Development 134

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. February 21, 2009 12:10 AM Harold Fowler said. February 21, 2009 7:39 AM Rocky1138 said. February 21, 2009 12:26 PM Anonymoussaid. February 21, 2009 3:08 PM SCC said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. 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

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. And so the spreadsheet is built with conservative assumptions, including a final revenue target.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

AUGUST 24, 2009

Lessons Learned by Eric Ries Monday, August 24, 2009 Marching through quicksand I have been spending a lot of time lately talking to people in various media companies: editors and agents, executives, journalists, producers and directors. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? June 15, 2009 7:41 AM William Pietri said. June 15, 2009 8:24 AM Stevesaid. One thing you seem to be treating lightly is how to use continuous development in business systems. Corporate customers seem to prefer regular but distinct releases.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

JANUARY 2, 2009

Lessons Learned by Eric Ries Friday, January 2, 2009 Lessons Learned on Mashable today I had the good fortune to be asked to write a guest post over at Mashable , which is running today, called HOW TO: Raise Money in a Down Economy. January 2, 2009 11:54 AM Daniel Davie said. January 2, 2009 4:48 PM Chris Desouza said.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Occam's Razor

APRIL 8, 2013

To win in business you need to follow this process: Metrics > Hypothesis > Experiment > Act. We are far too enamored with data collection and reporting the standard metrics we love because others love them because someone else said they were nice so many years ago. That metric is tied to a KPI.

Metrics 156

Metrics Analytics Lean Churn Rate 156

Startup Lessons Learned

NOVEMBER 17, 2008

Growth - when you have existing customers, the pressure is on to grow your key metrics day-in day-out. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

DECEMBER 28, 2009

Lessons Learned by Eric Ries Monday, December 28, 2009 Continuous deployment for mission-critical applications Having evangelized the concept of continuous deployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it. Monitoring of real-world metrics.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Steve Blank

DECEMBER 7, 2010

We’ll build the class around the business model / customer development / agile development solution stack. Instead you will be getting your hands dirty talking to customers, partners, competitors, as you encounter the chaos and uncertainty of how a startup actually works. What are the 9 parts of a business model?

Wiki 315

Wiki Lean Management Business Model 315

Steve Blank

APRIL 22, 2009

Achieving consensus about every corner case from each stakeholder in the room is something large companies with large revenues, shareholders and employees need to do. Customer Development.) Unlike large corporations, startup meetings are not about achieving consensus for every objection raised.

Silicon Valley 185

Silicon Valley RSS California Customer Development 185

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. That is customer development. “But it never happened.&# [Alas, customers dont know what they want!

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

JANUARY 27, 2009

Lessons Learned by Eric Ries Tuesday, January 27, 2009 Three freemium strategies Im excited to see so much attention being paid to freemium businesses lately. These are companies that generate revenue by offering a free product with an upsell or premium version. January 28, 2009 1:46 AM Anonymoussaid. I like that concept.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

OCTOBER 30, 2008

Not just about expenses, about increasing revenue. Make sure for planned revenues you have "leading indicators" to know if you will hit it. Over-communicate with employees, investors, customers. This can take the form of a traditional sales pipeline or a registration-activation-revenue chart. Offer equity instead of cash.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

JULY 9, 2009

Lessons Learned by Eric Ries Thursday, July 9, 2009 10 years of entrepreneurship I recently passed my ten-year anniversary of becoming an entrepreneur. We were focused on revenue, but we didnt understand that revenue is not important for its own sake in an early stage company. July 9, 2009 7:32 AM Peter Kane said.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

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. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. July 3, 2009 3:11 AM Eric Williamson said.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 1, 2009

Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. Not even if its generating revenue. August 1, 2009 7:39 AM Ravi Mohan said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. 2009 05 01 How To Build A Lean Startup Step By Step View more presentations from Eric Ries. May 3, 2009 4:45 AM Eric said.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

MARCH 27, 2009

Lessons Learned by Eric Ries Friday, March 27, 2009 Cash is not king Cash on hand is just one important variable in a startup’s life, but it’s not necessarily the most important. Customer Development : a disciplined approach to finding out if there is a market for your product before its too late.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

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. In a lot of cases, thats just a fancy name for revenue or profit, but not always.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

APRIL 7, 2010

At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. Instead, we try to accelerate with respect to validated learning about customers. Even if it shows improvement in some micro metric, does that invalidate the overall design? No one feature is to blame.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

DECEMBER 14, 2009

Lessons Learned by Eric Ries Monday, December 14, 2009 Business ecology and the four customer currencies Lately, I’ve been rethinking the concept of “business model&# for startups, in favor of something I call “business ecology.&# And this is true outside of games. And this is true outside of games.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

SEPTEMBER 13, 2008

Slowly, over time, we optimized (or eliminated) each step in the process of becoming a customer by giving us money. 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.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

andrewchenblog.com

MARCH 10, 2010

Coupled with A/B testing, customer development, and thinking through business problems in a scientific, hypothesis-driven way, you end up with a powerful cocktail of techniques to build a modern startup in the most iterative way possible. Portals that want to unify news, communication, tools, etc. Please comment!

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

SEPTEMBER 29, 2008

Turns out, what customers really meant was "let me use IMVU with somebody I dont know" so they could get a feel for the social features of the product without incurring the social risk of recommending it to their friend. Luckily, the metrics helped us figure out the difference. Lets run a thought experiment.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

www.rocketwatcher.com

NOVEMBER 8, 2010

Rocket Watcher Product Marketing for Startups Product Marketing for Startups About Speaking Contact Email Posts Startups Product Marketing Messaging Social Media Commentary Uncategorized Marketing Metrics 101 for B2B Startups 13. Rocket watcher b2b marketing metrics View more presentations from April Dunford.

B2B 42

B2B Metrics Marketing Startup 42

Steve Blank

MAY 26, 2009

on May 26, 2009 at 6:18 am Said: [.] Reply Dmitriy , on May 26, 2009 at 6:54 pm Said: I would like to humbly suggest banning the term “vertical&# altogether. Reply steveblank11 , on May 26, 2009 at 7:57 pm Said: Dmitry, I think your comment makes my point. What is it that’s unique about the market I’m in?

Vertical 153

Vertical Silicon Valley Intellectual Property RSS 153

Startup Lessons Learned

SEPTEMBER 28, 2008

In fact, in the early days, when IMVU would experience unexpected surges of revenue or traffic, it was inevitable that every person in the company was convinced that their project was responsible. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Seth Godin: How often should you publish?

Lean 68

Lean San Francisco Continuous Deployment Startup 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

The whole episode cost us hundreds of thousands of dollars in lost revenue. In fact, it was the revenue trends that eventually alerted us to the magnitude of the problem. Unfortunately, revenue a trailing indicator. Im a big believer in increasing customer loyalty, especially during tough economic times. Great post!

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JANUARY 28, 2009

Lessons Learned by Eric Ries Wednesday, January 28, 2009 Refactoring yourself out of business Let me start out by saying I am a big fan of refactoring , the ongoing process of changing code so that it performs the same behaviors but has more elegant structure. Its an essential discipline of good software development, especially in startups.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

SEPTEMBER 11, 2009

Lessons Learned by Eric Ries Friday, September 11, 2009 The cardinal sin of community management Once you have a product launched, you will the face the joys – and the despair – of a community that grows up around it. There are many articles by many experts ( myself included ) extolling the virtues of listening to customers.

Community 158

Community Management Lean Software Review 158