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 7, 2008

Lessons Learned by Eric Ries Friday, November 7, 2008 Using AdWords to assess demand for your new online service, step-by-step If you want to build an online service, and you dont test it with a fake AdWords campaign ahead of time, youre crazy. November 7, 2008 7:36 PM nitesh said. November 7, 2008 7:41 PM nitesh said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. December 4, 2008 4:43 PM Valto said. Eric, love the blog. Connect (off)line? Thanks much.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Warm Regards Sean Murphy www.skmurphy.com September 19, 2008 4:35 PM Eric said.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. Customer development is a parallel process to product development, which means that you dont have to give up on your dream. November 9, 2008 5:40 PM Chris said.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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

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

Steve Blank

SEPTEMBER 5, 2018

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”. This same risk averse, conserve the cash, VC mindset would return after the 2008 meltdown of the housing market.).

Lean 335

Lean Burn Rate Startup IPO 335

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

David Teten

JULY 9, 2012

Some companies, on the other hand, address very specific types of audiences: the key, here, is to remember that an understanding of the core customer is just as important as product development / technical expertise as an asset to the company. This is dangerous, the author argues, to the development of an adaptable, thoughtful culture.

Hiring 138

Hiring Technical Review Affiliate Audience 138

YoungUpstarts

JUNE 1, 2011

Department of Energy, more than $172 billion dollars of government money was spent on new energy technology between 1961 and 2008, with the bulk of it being used during the 1970s. According to the Pacific Northwest National Laboratory for the U.S. In the 1980s, the spending accounted for only 1 percent of all federal investment.

.Net 157

.Net Government Technical Review Product Development 157

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

SEPTEMBER 18, 2008

Lessons Learned by Eric Ries Thursday, September 18, 2008 Lo, my 5 subscribers, who are you? September 19, 2008 2:08 PM gmlk said. September 19, 2008 2:25 PM Eric said. Thanks again, Eric September 19, 2008 2:26 PM Eric said. September 19, 2008 2:27 PM gmlk said. September 19, 2008 2:35 PM gmlk said.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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. How dare you! =) November 4, 2008 10:58 PM IMVU said. Excellent ideas!

Lean 102

Lean San Francisco Agile Continuous Deployment 102

David Teten

JULY 9, 2012

Some companies, on the other hand, address very specific types of audiences: the key, here, is to remember that an understanding of the core customer is just as important as product development / technical expertise as an asset to the company. This is dangerous, the author argues, to the development of an adaptable, thoughtful culture.

Hiring 128

Hiring Technical Review Affiliate Audience 128

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

ReadWriteStart

NOVEMBER 12, 2022

In recent years, however, frugal innovation has also gained traction in developed countries. This is partly due to the global financial crisis of 2008, which led many companies to reassess their spending to cut costs. As a startup, you probably don’t have much money to spend on marketing or product development.

Startup 198

Startup Technical Review Ghana Guerilla 198

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

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." Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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? Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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. but rest assured they would be.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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. Its really helped me articulate my thinking on this topic, and includes an entire chapter on the topic of reducing batch size.)

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

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. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?)

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Both Sides of the Table

APRIL 28, 2010

The investment will be used for product development initiatives. Marketing and lead automation software for businesses; claim to have largest market share in sector since March 2008. Clients include Pepsi, Sony, CNN, Universal, AT&T, Victoria’s Secret and Facebook, which has used the service for multiple campaigns.

Venture Capital 270

Venture Capital Cofounder Spain San Diego 270

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

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.

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

SEPTEMBER 12, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 5, 2010

Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. We try to take advantage of that phenomenon twice if possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries.

Agile 111

Agile Customer Development Developer San Francisco 111

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. In the very early days, the trick is to find anyone at all who can understand you when you are talking about your product.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

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