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. This engineering manager is a smart guy, and very experienced.

Software Review 164

Software Review Engineer Management Technical Review 164

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. The product manager was clearly struggling to get results from the rest of the team. Lets start with what the product manager does.

San Francisco 158

San Francisco Management Software Review Product 158

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. (See

Lean 168

Lean San Francisco Startup Continuous Deployment 168

The Next Web

DECEMBER 2, 2013

Could $100,000 and the right developer skills make you an overnight billionaire? How much does it really take to build a product like Twitter or Instagram? Still, a product is nothing without scalability. You can’t just build a product today, you need to build a venture. 3) Facebook.

Cost 168

Cost San Francisco New York City Ruby 168

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." You get increasing growth by optimizing the viral loop , and you get revenue as a side-effect, assuming you have even the most anemic monetization scheme baked into your product.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 30, 2008

So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. I want to add one last idea, even though I recognize it is controversial, bordering on the boundary between the CTO and VP Engineering. Heres my take.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

APRIL 4, 2010

April 23, 2010 in San Francisco. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading. Bring your questions. Take a look and let me know what you think.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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. The batch size is the unit at which work-products move between stages in a development process.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Steve Blank

MAY 9, 2017

I’ve seen the Valley grow from Sunnyvale to Santa Clara to today where it stretches from San Jose to South of Market in San Francisco. And to today, when its major product is simply innovation. The second thing that’s changed is that we’re now Compressing the Product Development Cycle.

Restful 222

Restful Silicon Valley Puerto Rico San Jose 222

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? Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted. April 23, 2010 in San Francisco.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JUNE 17, 2010

I was an engineer on the engineering team. The art team would often be involved in the specification phase of a new feature, since they were responsible for the look-and-feel of the product. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

AUGUST 1, 2009

He doesnt put out crappy, buggy products and then ask for feedback. My normal answer is that I dont really think thats how Apple products are built. Thats what so many techniques that I advocate are all about: customer validation , minimum viable product , vision pivots , and even throwing away working code. It just wasnt great.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence. hey eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Each five whys email is a teaching document.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

OCTOBER 16, 2013

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. During this period, the Palantir Gotham team grew from five developers to around 35. During this period, the Palantir Gotham team grew from five developers to around 35. It wasn’t always this way.

Lean 167

Lean Startup Software Engineering Agile 167

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. This is precisely the dilemma that the doctrine of minimum viable product is designed to solve.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JUNE 2, 2010

Five Whys has its origins in the Toyota Production System. And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. Five Whys has its origins in the Toyota Production System. April 23, 2010 in San Francisco. Bring your questions.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. 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. I have found this quite rare in engineers. Thats OK, were not trying to hire a therapist.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JANUARY 30, 2009

Build a truly mainstream product. Build the product in stealth mode to build buzz for the eventual launch. The whole company and board play-tested the product to see its new features first hand. Everyone had fun; the product worked. After years of engineering effort, changing these assumptions was incredibly hard.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

AUGUST 8, 2009

One of the topics that raised heated debate was whether I had conflated technical design with product design , because I made the admittedly counter-intuitive claim that sometimes good technical design actually leads to increased technical debt. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JULY 29, 2009

The human tendency to moralize about debt affects engineers, too. 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.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JULY 28, 2010

It’s common, perhaps the norm, for startups to pivot like that—to discover that a product is catching on in unintended ways worth pursuing. With 21 employees today, kaChing is devoted to recruiting professional managers and finding product/market fit , first for money managers, then for consumers.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. April 23, 2010 in San Francisco. Seth Godin: How often should you publish?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JUNE 22, 2009

As Steve writes in the Four Steps to the Epiphany , we always seek to find a market for the product as currently specified , not conduct a focus group to tell us what the spec should be. It gave the whole company license to go heads-down building product as fast as possible during the development cycle, acting as a solution team should.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

JULY 2, 2009

Five Why’s rarely works for general abstract problems like “our product is buggy&# or “our team moves too slow.&# We started with a simple wiki page with a few bullet points of things that new engineers had tripped over recently. We never set out to build a world-class engineering-training process.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 2, 2008

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

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way. Focus on launching.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Austin Startup

APRIL 8, 2019

Team morale is high, we are exceeding the [REDACTED] KPI by several months, burn went up faster than expected, and product development is ticking along well except for one hiccup. At the end of the month, I will be in San Francisco for a customer meeting but am padding a day on either side to meet amazing people.

San Francisco 48

San Francisco Balance Sheet Startup Austin 48

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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. We know some products succeed and others fail, but the reasons are complex and the unpredictable. a roadmap for how to get to Product/Market Fit." Whats wrong with this picture?

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

MAY 31, 2010

I had really debated about whether there was any value in spending the time and money to fly to San Francisco when there was a perfectly serviceable simulcast going on in Cleveland. April 23, 2010 in San Francisco. In the meantime his two books, The Monk and the Riddle and Getting to Plan B are both a must-read.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

FEBRUARY 10, 2009

This also literally can’t catch every problem, because your test sandboxes or test clusters will never be exactly like the production system. But I will tell you not to have too little or too much, because those definitely ruin the food or product. It would be hard to argue against this product development strategy, in general.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

AUGUST 26, 2009

As a result, for a lot of these companies, Boulder is just a gateway to San Francisco. You can learn more about that by reading The engineering managers lament.) leanstartup We organized our engineering team at IMVU to try and maximize cross-functional collaboration. April 23, 2010 in San Francisco.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113