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.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

techcrunch.com

OCTOBER 23, 2010

It is the first in a series of posts he’s writing about the decisions a young entrepreneur needs to make when she/he is first starting a business. So for this first post, here’s the best advice I can give you: join an awesome founding team and get your product out the door ASAP. I don’t know any developers.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

www.quora.com

JANUARY 16, 2011

If you can't find what you are looking for, hit enter or click "Add Question" again. Find Questions, Topics and People Add Question Add Question Non-Technical Co-Founders Co-Founders Technical Co-founders Finding Co-Founders Startups & "How Important Are Ideas?

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

Startup Lessons Learned

JANUARY 30, 2009

Build a truly mainstream product. Build the product in stealth mode to build buzz for the eventual launch. Lessons Learned by Eric Ries Friday, January 30, 2009 Achieving a failure We spend a lot of time planning. We even make contingency plans for what to do if the main plan goes wrong. Dont get distracted by trying to flip it.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

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. Finding great engineers is hard; figuring out whos good is even harder. If done right, a programming interview serves two purposes simultaneously.

San Francisco 146

San Francisco Lean Agile Java 146

Steve Blank

JUNE 25, 2009

Twenty eight years ago I was the bright, young, eager product marketing manager called out to the field to support sales by explaining the technical details of Convergent Technologies products to potential customers. So their management teams were insisting that they OEM (buy from someone else) these products.

Technology 143

Technology Silicon Valley Fractional VPE Part-Time VPE 143

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. 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

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. Customers dont care if you have good metrics, only if you have a good product. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

maplebutter.com

JANUARY 8, 2013

For the most part they were written at 2AM while I was working – however, I thought you might find them useful. If you’re an Entrepreneur, you can do it from any place in the world. Maple Butter. Search for: Videos. You are here: Home » Hiring » Crazy! 189 Answers To The Top Startup Questions On Your Mind.

Technical Review 44

Technical Review Startup Cofounder Software Review 44

Startup Lessons Learned

MAY 31, 2010

Having had a few weeks to recover from the adrenaline crash, I find myself full of gratitude. I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. These posts are the result. Erin Turner helped organize the dozens of simulcast venues.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

FEBRUARY 22, 2010

As entrepreneurs, more than any other industry, we’re in the meritocracy business. If women face structural barriers to becoming entrepreneurs, then those few who are able to overcome those barriers are probably exceptional to begin with. Or, maybe it is true that women make better entrepreneurs than men.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 10, 2009

I find these on-the-ground descriptions of the system and how they work so much more credible than just theory-type posts that I am excited to share them with you. Nobody gets here overnight, but every step along the way has made us better developers. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

Startup Lessons Learned

JULY 3, 2009

The same has been true of an unfortunate number of startups, they manage to generate a lot of hype, raise a lot of money, and sometimes make some of their investors, employees, or founders rich. As usual, Id like to post the slides and then offer some additional commentary. Note: there is video from this event, but its not online yet.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

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. So I thought I would walk you through exactly how to run a "fake landing page" test using cheap tools that require no technical skills whatsoever. Oops - there went several precious weeks of development effort down the drain.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. 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. Lessons Learned by Eric Ries Thursday, June 17, 2010 No departments Big companies have departments.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JULY 6, 2009

Say you're not creating a product but doing a service? Lessons Learned by Eric Ries Monday, July 6, 2009 Lean Startup fbFund slides and video As a follow-up to my previous post on my talk for fbFund at Facebook , there was enough interest in watching video of the talk that I have finally uploaded it using Apples MobileMe.

Lean 115

Lean Video San Francisco Continuous Deployment 115

www.quora.com

JANUARY 16, 2011

If you can't find what you are looking for, hit enter or click "Add Question" again. 3d - developer, designer and distributor. If you want to read just one answer and get most out of it, read the first answer 36 Answers Saul Klein , Student of - and sometime co-conspira.

Technical Review 51

Technical Review Startup CTO Hire Cofounder 51

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. A better way is to see it as a learning opportunity.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 17, 2008

If you dont have customers, a product, investors, or a board of directors, you can pretty much stay focused on just one thing at a time. If you dont have customers, a product, investors, or a board of directors, you can pretty much stay focused on just one thing at a time. Playing with new technologies.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

betashop.com

OCTOBER 8, 2012

It has been awesome, flattering, and humbling to see that post went viral and has been seen by so many thousands of people — mainly aspiring entrepreneurs — and has been translated into many languages. 90 Things I’ve Learned Founding 4 Tech Companies: Find your company’s One Thing. ?? It’s all about the product.

Technical Review 108

Technical Review Technology Software Review Valuation 108

Startup Lessons Learned

NOVEMBER 4, 2008

Steve and I worked to find a metaphor that would help explain the power of lean startups, and why they have a serious competitive advantage, especially in these challenging economic times. Agile software development. Customer development. Hopefully others will find it useful as well. you get the idea.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JULY 30, 2009

A discounted price is available for early stage entrepreneurs and students. 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. Ill be in Boulder for two days.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

AUGUST 26, 2009

But theres no denying the level of support for entrepreneurs that we enjoy. They take common stock, not preferred, a fact that the entrepreneurs mentioned to me many times. It was a great experience to see a relatively new startup hub in action - and thriving. Its easy to take Silicon Valley for granted.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

JULY 2, 2009

It allows teams to diagnose sources of waste in their development process and continuously improve, reversing the usual trend of teams getting slower over time. These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. First, a caveat.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. They have a product that has a moderate number of customers. Still, theyre not really hitting it out of the park, because their product isnt growing new users as fast as theyd like, and they arent making any money from the current users.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. Its common to find a hacker at the heart of almost any successful technology company. And please forgive the fact that I use male pronouns to describe the archetype.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Designmantic Blog

MARCH 6, 2018

Here are some of the most interesting facts about female founders as well as startups. Rebekah Radice is an accomplished entrepreneur with a marketing experience of over 20 years. She had over 15 years doing product management and corporate management before she became an entrepreneur. Background Image: Unsplash/Rawpixel.

Entrepreneur 76

Entrepreneur Social Media B2B Cofounder 76

Startup Lessons Learned

DECEMBER 6, 2008

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. Having early customers means balancing the needs of your existing customers with the desire to find new ones.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 18, 2008

Many of them have really cool products shipping or about to be released, and I wholeheartedly agree with my friends at the iFund that the next generation of applications is going to be amazing. From a technical point of view, its amazing. All I see is a name, an icon, a price, the developers name, and a review star-rating.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

DECEMBER 28, 2009

Most customers of most products hate new releases. Most customers of most products hate new releases. Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Or variations thereof. I understand why people would think that a consumer internet service like IMVU isnt really mission critical.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

NOVEMBER 17, 2008

But they are often counter-productive when placed in a management role for other kinds of work. When startups grow, they tend to have problems handling the inevitable conflicts that emerge from having to do multiple kinds of work all at once. In order to grow effectively, its important to have a technique that mitigates these problems.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

OCTOBER 5, 2009

Lessons Learned by Eric Ries Monday, October 5, 2009 The curse of prevention Beware! I have detected a secret virus in your CPU. Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. OK, I admit it. There is no virus.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

JUNE 15, 2009

If youre looking for resources on getting started, see " Continuous deployment in 5 easy steps ") The goal of continuous deployment is to help development teams drive waste out of their process by simultaneously reducing the batch size and increasing the tempo of their work. Both options have some attraction.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. In other words, they are facing conditions of extreme uncertainty, just like startups.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

FEBRUARY 16, 2009

Joe Ludwig goes through his current release process and determines that the current time to make and deploy a release is about seven and half hours, which is why his product is released about once a month. Your team could focus on fixing issues that players on the test server find while those players are still online.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68