Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. Fundamentally, lean startups do more with less, because they systematically find and eliminate waste that slows down value creation.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo to explain the lean startup concept to a larger audience. The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: No departments The Five Whys for Startups (for Harvard Business R.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

JULY 11, 2019

Among her early investments are Lyft, TaskRabbit and Modcloth, which, as our recent conversation shows, are only part of the reason Forbes called her “the most powerful woman in startups.” Ann will be speaking at this year’s Lean Startup Conference in October about all of this and more. I've been in venture now twice.

Founder 68

Founder Lean Venture Capital Cofounder 68

ReadWriteStart

APRIL 8, 2013

I know these things like I know that Jacoby Ellsbury is a pretty good centerfielder for the Boston Red Sox. So, when I found myself sitting at the Harvard Club in Boston listening to Facebook COO Sheryl Sandberg talking about her new book Lean In , I told myself that I know what she is talking about. What Did I Understand?

Lean 60

Lean Technical Review Boston Public Relations 60

Startup Lessons Learned

SEPTEMBER 30, 2008

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? What does your Chief Technology Officer do all day? But I dont think most startups really have a need for someone to do that on a full time basis. Thats an important job, for sure, and Ive been called upon to do it from time to time.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 28, 2008

Lessons Learned by Eric Ries Sunday, September 28, 2008 The lean startup comes to Stanford Im going to be talking about lean startups (and the IMVU case in particular) three times in the next two weeks at Stanford. Labels: events , lean startup 5comments: Hitchens said. How did we combat this tendency?

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Steve Blank

DECEMBER 17, 2015

Silicon Valley, Boston). In the second stage, it moves into Investing, Inventing, Incubating and Acquiring technologies and companies, and in the third stage building product(s ). Stage 1: Networking and Partnering – the Technology Connectors. Startups, entrepreneurs, and management teams. see the previous post.).

Silicon Valley 120

Silicon Valley Incubator Acquisition Business Model 120

Startup Lessons Learned

SEPTEMBER 8, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 Waves of technology platforms I still remember the first time I switched to LAMP. I was building a new startup in 1999, and wanted to do it right. That startup didnt turn out so well, but not for lack of technology. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Steve Blank

OCTOBER 5, 2009

I had last been in Chapel Hill on a winter’s day in 1986, traveling with the VP of Sales of our new supercomputer startup, Ardent. It was the best of times, it was the worst of times Ardent would be my third technology company as a VP of Marketing (Convergent Technologies and MIPS Computers were the other two.)

North Carolina 125

North Carolina Silicon Valley Fractional VPE Part-Time VPE 125

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. It increases the runway without additional cash.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

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? ) He previously co-founded and served as Chief Technology Officer of IMVU. He previously co-founded and served as Chief Technology Officer of IMVU.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. In my opinion, every startup needs to "pick a major" among these three drivers of growth. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. It just wasnt great.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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. How to Fund a Startup [link] Its obvious why investors delay. Investing in startups is risky!

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. However, a technological solution cant necessarily resolve all human root causes. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JUNE 17, 2010

Startups are companies. Startups aspire to become big companies. Therefore, startups should have departments. Each of these benefits also exists in startups, which is why most startups are also organized in departments. I once worked at a startup with an exceptional functional department system.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

SEPTEMBER 7, 2008

The basic idea is to extend agile, which excels in situations where the problem is known but the solution is unknown, into areas of even greater uncertainty, such as your typical startup. Can this methodology be used for startups that are not exclusively about software? No departments The Five Whys for Startups (for Harvard Business R.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. I highly recommend this book for all entrepreneurs, in startups as well as in big companies. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 9, 2010

And that narrow definition of entrepreneurship doesn’t count all of the managers inside established companies who are effectively engaged in the same process of building an internal startup (see What is a startup? Let’s start with the startup personality attributes. for my more expansive definition).

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

JANUARY 7, 2010

As an entrepreneur, I often saw the best practices of general management fail startups. My most recent startup created a marketplace for customers to buy and sell virtual goods for their 3D avatar. So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. Expo SF (May.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

FEBRUARY 22, 2010

For startups (and other innovators ), that’s a decisive advantage. The work itself, especially in startups, depends primarily on intelligence, communication, creativity and empathy. Their recent article suggests that startups led by women are actually more successful, on average, than those led by men.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JANUARY 15, 2010

And when companies pursue sustaining innovations — like a product line extension or a new technology designed to serve an existing customer segment — this procedure makes complete sense. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

OCTOBER 28, 2008

Ill exclude those non- lean startups who basically exist for the purpose of raising bigger and bigger sums of money. Now there was nothing wrong with their analysis: anyone who invents a technology as sophisticated as The Transformers is definitely going to make a lot of money. can we make a product out of this technology?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

SEPTEMBER 8, 2009

Lessons Learned by Eric Ries Tuesday, September 8, 2009 What would you want to tell Washington DC about startups? Beyond just those who will be hearing about the lean startup for the first time, Im expecting to shake a lot of hands and have a lot of interesting side conversations. And what hurdles could be eliminated?

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

SEPTEMBER 13, 2008

Its now a technique I recommend for any web-based startup. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. I just came across this post. Expo SF (May. .

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 2, 2008

October 17, 2009 10:34 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. .

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 10, 2008

I have been thinking a lot about what a new version of this test would look like, given what Ive seen work and not work in startups. but I have not seen that dysfunction in any of the startups I advise, so hopefully its behind us. Just like in lean manufacturing, its generally more efficient to drive down the batch size.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

DECEMBER 30, 2014

The landscape for how to turn life science and health care technologies into viable companies has changed more in the last 3 years than in the last 30. Our Lean Launchpad® for Life Sciences is one of them. Co-working spaces seem to be evolving into the startup garages of the future.

San Diego 261

San Diego North Carolina Chicago Lean 261

Startup Lessons Learned

SEPTEMBER 12, 2008

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

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

NOVEMBER 29, 2008

By far the most important thing you want to hire for in a startup is the ability to handle the unexpected. Those people also tend to go crazy in a startup. The "lone wolf" superstar is usually a disaster in a team context, and startups are all about teams. Still, a startup product development team is a service organization.

San Francisco 146

San Francisco Lean Agile Java 146

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. Playing with new technologies. Seeing whats possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

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