Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. Unfortunately, its easy to lose track of positioning effects when optimizing for a single metric.

Metrics 88

Metrics San Francisco Lean Viral 88

Up and Running

MAY 23, 2016

“If you can fix a problem for someone and do it better, quicker, and/or cheaper than your competitor, you’re off to a good start.” – Gabriel Kuperman, founder and CEO of CuePin. We created UpKeep to fill this void—a cloud-based solution that was affordable for any size business.” – Ryan Chan, founder of UpKeep.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. October 13, 2008 6:47 PM Luke G said. Eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Techniques from lean manufacturing can be part of a startups innovation culture. Expo SF (May.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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

Steve Blank

MARCH 29, 2012

I thought they might be worth enumerating here: A Startup Is a Temporary Organization Designed to Search. Pair Customer Development with Agile Development. Failure is an Integral Part of the Search for the Business Model. Success Begins with Buy-In from Investors and Co-Founders. Preserve Cash While Searching.

Customer Development 328

Customer Development Developer Customer Cofounder 328

Startup Lessons Learned

AUGUST 3, 2009

In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. In fact, MVP is quite annoying, because it imposes extra overhead. Thank you. August 13, 2009 3:43 AM Robert said.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JANUARY 30, 2009

This is why agility is such a prized quality in product development. Departments were built and were even metrics-driven. But there was no feedback loop to help the company find the right metrics to focus on. I know of at least five former employees that went on to become startup founders. We can skip the chasm.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 25, 2010

Pretty soon, a soul-searching meeting ensues. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Pretty soon, a soul-searching meeting ensues. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. I used to think that investments in metrics were a form of waste. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Ive attempted to embed the relevant slides below. What about a hardware business with some long-lead-time components?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

Google's search algorithm was just better, therefore they won the eyeballs, therefore they were able to monetize. Google has spent hundreds of millions of dollars on their search algorithm, the single biggest focus of the company even today, a decade after they decided that was their One Thing. The Dream Team. Existing customers.or

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Some startups fail because the founders cant have this conversation - they either blow up when they try, or they fail to change because they are afraid of conflict. Thats why its so essential to have a co-equal problem team.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

AUGUST 2, 2008

Its to everyones advantage to let the world think the founders thought of everything. I say this as a founder: the contribution of founders is always overestimated. The danger here is that new founders, looking at existing founders, will think that theyre supermen that one couldnt possibly equal oneself.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

NOVEMBER 7, 2008

Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Another way to promote the website is doing organize search. For example, make sure your website is in the first page of Google search for the given keyword. Eric -- This is a pretty interesting idea. November 8, 2008 8:44 AM OneDish said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. Instead, we do everything possible to validate the founders belief. We dont just abandon the vision of the company at every turn.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. This speeds up the Ideas-Code-Data feedback loop.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you. Expo SF (May.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

SEPTEMBER 13, 2008

Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. You declare how much someone clicking an advertisement is worth to you, and then the search engine does its best to get you as many clicks as it can at that price. Labels: search engine marketing 4comments: Tauya said.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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. Every board meeting, the metrics of success change. These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. October 6, 2008 12:17 AM r& said. Expo SF (May.

San Francisco 158

San Francisco Management Software Review Product 158

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. Some companies and founders refuse to serve existing customers, and are always lurching from one great idea to the next. Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

MAY 31, 2010

I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. All video from the conference is available for free at Justin.tv Expo SF (May.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JULY 30, 2009

In 2002 I became exposed to the idea of “agile software development&# and subsequently was a first round investor in Rally Software which is now the market leader in Agile application lifecycle management software. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 10, 2009

Heck, thats what it says right there in the agile manifesto. The first version of the 3D IMVU client took about six months to build, and as the founders iterated towards a compelling user experience, the user base grew monthly thereafter. That leads to a seemingly-obvious question: what is progress in software development? We made it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , listening to customers 3comments: hauteroute said. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Split-test experiments that go on forever? Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

MARCH 22, 2010

For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder. Similarly, 24% of all the patents filed in the US in 2006 had a foreign resident as inventor or co-inventor. For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

MARCH 17, 2009

Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Tried it with multiple browsers.

Lean 76

Lean San Francisco Web Continuous Deployment 76

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 on-schedule and on-budget, but their gross metrics are way off. They are on-schedule and on-budget, but their gross metrics are way off. Expo SF (May.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

NOVEMBER 13, 2008

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 29, 2008

The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. To probe for agility, you have to ask the candidate questions involving something that they know little about. December 2, 2008 10:56 AM Ryan said.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

OCTOBER 11, 2009

Every experiment has to be evaluated based on a single standard report of 5-10 (no more) key metrics. Any team that creates an experiment must monitor the metrics and customer reactions (support calls, forum threads, etc) while the experiment is in-progress, and abort if something catastrophic happens. It promotes rapid iteration.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133