Startup Lessons Learned

OCTOBER 4, 2008

Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) 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. Looking forward for your future posts.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 7, 2008

One major theory that has influenced the way I think about processes comes from Lean Manufacturing , where they use these same techniques to build cars. Names have, of course, been changed to protect the innocent: Hope youre well; I thought Id relay a recent experience and thank you. The Lean Startup Intensive is tomorrow at Web 2.0.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups. Expo SF (May.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 8, 2012

This post was co-written by Eric Ries and Sarah Milstein , co-hosts of The Lean Startup Conference this fall. Last week , we announced the date and venue for The Lean Startup Conference: Dec 3 - 4, 2012 at the InterContintenal in SF. When we're evaluating your application, we won't know your name, ethnicity, gender or age.

Lean 164

Lean Houston Continuous Deployment Technical Review 164

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. The book takes its name from Steves theory of the four stages of growth any startup goes through. Phases of product & company growth.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Lean vs. debt In the world of physical goods, the leaner a supply chain is, the less debt is required to operate it. A similar relationship applies to technical debt.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

MAY 9, 2012

TLDR: Brant Cooper and Patrick Vlaskovits , authors of The Entrepreneur's Guide to Customer Development are back with a new book called The Lean Entrepreneur. Since then, Brant and Patrick have been tireless advocates for the whole Lean Startup movement. Illustrations by FAKEGRIMLOCK. You can pre-order it starting today.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

FEBRUARY 22, 2010

Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. I already advocate cross-functional teams as part of the lean startup methodology. I already advocate cross-functional teams as part of the lean startup methodology.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 13, 2008

We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

OCTOBER 11, 2010

(I am often asked to explain how to apply Lean Startup approaches to domains beyond software. The key to understanding Lean Startup is to recognize two things: Lean Startup techniques confer maximum benefit in the upper-right quadrant, namely high market uncertainty coupled with fast cycle time.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. The event will include a talk from Eric on The Lean Startup over dinner, followed by moderated table discussion and then final Q&A with Eric.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

MARCH 16, 2009

Notice that the unit of progress changes as we move from waterfall to agile to the lean startup. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries. The Lean Startup Intensive is tomorrow at Web 2.0. Just a thought. March 19, 2009 7:47 AM Dan McGrady said.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

AUGUST 26, 2009

Accept that many successful companies are going to want to be backed by big-name firms in other cities. I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries. Articulate, inspirational.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

APRIL 14, 2009

Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. That leads to cashing many checks. Expo SF (May.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Amazing lean startup resources Is Entrepreneurship a Management Science?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JANUARY 4, 2009

Imagine you want to store data about customers, each of whom has "last name" field in your database. The problem should be familiar to anyone who plays Scrabble: not all letter are equally likely to be used as the first letter of someones name. Give each entity a name. For example, consider this simple scheme.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

MARCH 22, 2010

Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

DECEMBER 14, 2009

This attention is valuable to yet another set of people: namely, the traditional businesses (see above) who are using marketing to grow, and are looking to advertise to new prospects. These concepts have important implications for any lean startup. These concepts have important implications for any lean startup. Expo SF (May.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). That’s the local maximum. That’s right.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 10, 2008

Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

JUNE 5, 2009

This model of joint accountability is at the heart of the lean startup, and is just as applicable to venture-backed, bootstrapped, and enterprise startups. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Paul June 6, 2009 8:34 PM Nick Shepheard said. Expo SF (May.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

MARCH 24, 2009

March 26, 2009 12:18 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

SEPTEMBER 22, 2008

If you read Lean Thinking , you can enjoy numerous examples of companies that replaced multi-million dollar MRP systems with a simple white board. The lean manufacturing guys call this visual control and its very powerful. Simply put, we upload all the tasks and assign a name to each task. 1 comments: Josh Moore said.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 13, 2010

Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. for Harvard Business Revie.

San Francisco 154

San Francisco Metrics Lean PR 154

Startup Lessons Learned

FEBRUARY 7, 2010

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

OCTOBER 23, 2009

The lean startup methodology is based on enlisting customers as allies, which requires honesty and integrity. The following was written an actual lean startup practitioner. It was originally posted anonymously to the Lean Startup Circle mailing list, and then further developed on the Lean Startup Wiki ’s Case Studies section.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. 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

JULY 9, 2009

All the good domain names were taken, all the good ideas were being implemented. If Id bought just a handful of the "best of the rest" domain names that were available at the time (for a whopping $70 each), I probably could have just retired right then. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

JULY 31, 2009

lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Its incredibly simple, and its called joblink.tw. Expo SF (May.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

OCTOBER 20, 2008

But we were cutting corners in the development methodology as well as in the code, in the name of increased speed. I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost. Expo SF (May.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). In reality, most quality problems are systemic in nature.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

APRIL 18, 2013

This post was written by Sarah Milstein, co-host of The Lean Startup Conference. Exciting news: we’ve nailed down dates for The Lean Startup Conference 2013. We know Lean Startup methods are being applied by people around the globe, in startups and established organizations alike, and in sectors of every stripe.

Lean 167

Lean San Francisco Startup Continuous Deployment 167

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Thats not the goal of a lean startup. Your writing is certainly not lean. I like this term.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167