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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

SEPTEMBER 14, 2008

Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" The people who are the lifeblood of an early-stage startup are earlyvangelists. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Dont confuse passion with volume.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Campus Entrepreneurship

OCTOBER 10, 2013

GWU, University of Maryland and Virginia Tech have taken the lead in our region (the DC I-Corps ) and have some great people working on the program. From Baum , Here’s a sample of the healthcare and device technologies involved in the program, which runs through November 19. It’s led by Nathan Castro, a Ph.D. Exciting time.

DC 38

DC Lean Maryland Virginia 38

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 24, 2009

In other words, they are facing conditions of extreme uncertainty, just like startups. The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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. After all, our startup is on a fixed budget.

Software Review 164

Software Review Engineer Management Technical Review 164

Both Sides of the Table

MARCH 12, 2016

So while some people go mad that I would publish a Snapstorm (a short lesson on startup entrepreneurship) in a platform where it disappears in 24 hours – I actually love it. Not yet completely reported but Snapchat is snapping up some really great ad technology professionals from FB and from the LA ecosystem. Engagement.

Advertising 150

Advertising Iowa Campaign DC 150

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 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?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 2, 2009

For the rest of us, there is an alternative: to create credibility by building a lean startup. Rather than just focus on the right kind of pitch to use, I wanted to write about the kinds of startups that create lasting value, and therefore are great companies to fund even in down times. Thanks for the article. Is there s choice?

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

FEBRUARY 5, 2013

Yes, there are Lean Startups even in the United States federal government. For my take on how this is possible, you can see my previous post on Lean Government here. Today, I'm excited to share the latest round of startups that are being run by the Presidential Innovation Fellows program. The objective of the RFP-EZ 2.0

Fractional CTO 158

Fractional CTO Government Technical Review Analytics 158

techcocktail.com

OCTOBER 23, 2010

Tech Cocktail Connecting, educating and amplifying the startup technology community and having fun doing it since 2006. So, today we’d like to highlight a few main points to consider when building your startup team. Startup’s can be stressful and there may be many times when people want to quit.

San Francisco 44

San Francisco Startup PHP San Diego 44

Steve Blank

DECEMBER 10, 2014

The University of Maryland is now integrating the Lean LaunchPad ® into standard innovation and entrepreneurship courses across all 12 colleges within the University. It was Steve who first brought Will Harvey to visit Immersion, which led to a strategic investment in There.com, Will’s stealth-mode but sure-fire, can’t-miss startup.

Maryland 278

Maryland Lean DC Virginia 278

Startup Lessons Learned

SEPTEMBER 18, 2008

I want to get an idea of how startup guys think. Lean Start-up SlideShare prez at Web 2.0 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.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 1, 2008

Labels: Test-driven development 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?)

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Among his ideas are that todays kids should be taught in class in a way that is relevant to their actual lives, which necessarily means allowing them to use technology. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60