Startup Lessons Learned

SEPTEMBER 30, 2008

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? Labels: product development 15comments: mukund said. October 1, 2008 2:13 AM archenland said. Great article youre now in my rss feeds :) October 2, 2008 4:37 AM kamilski81 said. October 2, 2008 8:58 AM Chad said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. September 15, 2008 9:12 PM Hitchens said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 The three drivers of growth for your business model. 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. Choose one.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. Labels: product development 8comments: Vincent van Wylick said. October 6, 2008 12:16 AM Vincent van Wylick said.

San Francisco 158

San Francisco Management Software Review Product 158

Steve Blank

SEPTEMBER 5, 2018

They needed to be sure that what they were building was what customers wanted and needed. And if their initial guesses were wrong, they needed a process that would permit them to change early on in the product development process when the cost of changes was small – the famed “pivot”.

Lean 335

Lean Burn Rate Startup IPO 335

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. October 20, 2008 9:34 PM Nivi said. But, it is so worth it.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a key lean startup concept. Great post!

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. October 13, 2008 6:47 PM Luke G said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. November 13, 2008 8:59 PM eisrael said.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 29, 2008

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. October 6, 2008 9:41 PM Eric said.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. Customer development. How dare you! =) November 4, 2008 10:58 PM IMVU said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. What other questions would you ask a brand-new startup about its product development practices? Please leave feedback!)

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? 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

Startup Lessons Learned

SEPTEMBER 18, 2008

Lessons Learned by Eric Ries Thursday, September 18, 2008 Lo, my 5 subscribers, who are you? When you have an infinitesimal number of customers, it can be embarrassing. But as long as your ego can take it, there are huge advantages to having a small number of customers. September 19, 2008 2:08 PM gmlk said. Still new.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Ideas. Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Just-In-Time Scalability At my previous company, we pioneered an approach to building out our infrastructure that we called "Just-In-Time Scalability." The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. In those cases, the product may stay mostly the same, but the positioning, marketing, and - most importantly - prioritization of features changes dramatically. This is an exciting kind of change, usually.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

JULY 28, 2010

kaChing launched a virtual portfolio management game on Facebook in January 2008 and a similar version shortly thereafter on kaChing.com. kaChing launched a virtual portfolio management game on Facebook in January 2008 and a similar version shortly thereafter on kaChing.com. How’d it happen? How’d it happen?

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

SoCal CTO

DECEMBER 1, 2010

The Ultimate Combination of Startup Business Development Methods - ArcticStartup , November 16, 2010 I've been a huge fan of Steven Blank's Customer Development methodology for a long time. In 2008, we couldn’t find a technical co-founder for Yipit. Your First Iteration of an Idea Will Be Wrong. What went wrong?

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

SEPTEMBER 12, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Thoughts on scientific product development Lo, my 5 subscribers, who are you? No departments The Five Whys for Startups (for Harvard Business R. ► May (3) Thank you Philosophy Helps Start-Ups Move Faster (WSJ on the.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

DECEMBER 8, 2008

Lessons Learned by Eric Ries Monday, December 8, 2008 Continuous integration step-by-step Lets start with the basics: Martin Fowlers original article lays out the mechanics of how to set up a CI server and the essential rules to follow while doing it. December 10, 2008 6:37 AM Anonymoussaid. March 26, 2010 8:42 AM ankur aggarwal said.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Want to learn more about me?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 5, 2008

Lessons Learned by Eric Ries Friday, September 5, 2008 Great open source scalability tools from Danga If you are trying to build a scalable LAMP service, its always best to start with the original and still quite relevant presentation, from Brad Fitzpatrick when he was at LiveJournal. You can find the 2005 version here.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. Some of these reaffirm that they do indeed validate assumptions through interaction with customers.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. At the end of the day, the product development team of a startup (large or small) is a service organization. Great article.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

APRIL 4, 2010

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

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. What is customer development?

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

FEBRUARY 10, 2009

This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. It would be hard to argue against this product development strategy, in general. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123