Startup Lessons Learned

NOVEMBER 7, 2008

So, if youre interested in helping avoid mistakes like that, here are the steps: Get a domain name. It doesnt have to be the worlds catchiest name, just pick something reasonably descriptive. If youre concerned about sullying your eventual brand name, dont use your "really good" name, pick a code name.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. Expo SF (May.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 27, 2010

I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. I won’t apologize for this aspect of the Lean Startup methodology. I understand this fear.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

MARCH 22, 2010

Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder. Similarly, 24% of all the patents filed in the US in 2006 had a foreign resident as inventor or co-inventor.

San Francisco 121

San Francisco Indiana Lean Startup 121

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. Instead, we do everything possible to validate the founders belief. We dont just abandon the vision of the company at every turn.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. For example, take the lean dictum of working in small batches.

Product Development 153

Product Development Developer San Francisco Product 153

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

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. Thats why I prefer to think of them as two co-equals: the problem team and the solution team. Just a thought.

Agile 111

Agile Customer Development Developer San Francisco 111

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 Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey. 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

FEBRUARY 10, 2009

In a lot of cases, thats just a fancy name for revenue or profit, but not always. The first version of the 3D IMVU client took about six months to build, and as the founders iterated towards a compelling user experience, the user base grew monthly thereafter. The Lean Startup Intensive is tomorrow at Web 2.0. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

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

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 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. ► 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. .

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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. ► 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. . Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. 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. More on that in a moment.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 12, 2009

Some of them are probably still cursing my name, because - lets face it - PHP can be pretty painful. Almost every PHP-based website is burdened with ugly URLs that contain the name of the file that implements each page. The IMVU downloadable client, just to name one example, is written primarily in python.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

online.wsj.com

SEPTEMBER 23, 2012

NAME Comcast. NAME Verizon Communications. NAME Yahoo. NAME Shikhar Ghosh. NAME Toby Stuart. NAME Daniel Dreymann. NAME Charles Holloway. NAME David Cowan. Consider Daniel Dreymann, a founder of Goodmail Systems Inc., Harley Goes Lean to Build Hogs. Domain Name/Basic Site.

Venture Capital 107

Venture Capital Software Review Rhode Island North Dakota 107

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. Startup founders need to use their own judgment to ask: which is the riskiest assumption underlying my business plan? Successful startups don’t.

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

MARCH 13, 2009

Founders push for it. Who doesnt want to see their name in print? In some ways, founders are even worse. My experience is that many founders actually have a deep anxiety that maybe they are not succeeding. Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us.

San Francisco 168

San Francisco PR Lean Early Stage 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

JANUARY 18, 2010

Ash Maurya is the founder of WiredReach , a bootstrapped startup that he has been running for seven years. Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. The Lean Startup Intensive is tomorrow at Web 2.0.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

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

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.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. ► 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. . And what distinguishes a good app?

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Entrepreneurs-Journey.com by Yaro Starak

OCTOBER 6, 2013

Walter Haas , who was the lead developer and co-founder in CrankyAds, and I jumped on to record what I hope will be a new and ongoing feature here on EJ – a talk show in podcast form. We don''t have a name for the show yet, and in true lean style, we are throwing this out there to you and looking for your feedback.

Founder 95

Founder Cofounder Australia Lean 95

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. Amazing lean startup resources Is Entrepreneurship a Management Science? Paul June 6, 2009 8:34 PM Nick Shepheard said.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. Ironically, meetings like this had given data and experimentation a bad name inside this company. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science?

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

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 11, 2009

As a founder of a company, there is nothing more painful than to see your most loyal and devoted customers suffering. No, I am the troll who who stood proudly on the APC until a man who was nothing more than an egotistical and maniacal bully named Clifford Hicks proved once and for all that IMVU only cared about IMVU - and not its community.

Community 158

Community Management Lean Software Review 158

The Next Web

DECEMBER 6, 2013

However, rather than simply acting as yet-another TV guide, Tank Top TV, uses its proprietary algorithm to recommend content for individual users, as well as using it to push “good” content to the top of the list, Liz Rice, co-founder of Tank Top TV explained.

Croatia 147

Croatia Bulgaria Startup Cofounder 147

Hearpreneur

AUGUST 2, 2019

That’s the story of Zima Media, and the co-founders, Michael Zima and Damien Bouvier. How did you come up with your business name? From the ashes, I started to do a consultancy that had a rather long name, and Artur suggested, “hey, go with Zima Media” on a brief phone call about what to do after the startup failure.

North America 67

North America Entrepreneur South America America 67