Startup Lessons Learned

JUNE 2, 2010

Five Whys has its origins in the Toyota Production System. And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. October 13, 2008 6:47 PM Luke G said. Eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. My belief is that these lean startups will achieve dramatically lower development costs, faster time to market, and higher quality products in the years to come. July 15, 2009 11:18 PM markmontgomery said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

AUGUST 2, 2008

Its to everyones advantage to let the world think the founders thought of everything. I say this as a founder: the contribution of founders is always overestimated. The danger here is that new founders, looking at existing founders, will think that theyre supermen that one couldnt possibly equal oneself.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

YoungUpstarts

FEBRUARY 17, 2016

by Donovan Janus, founder of 17hats. of UC San Francisco. You’ll find that entrepreneurs do outscore the general population on learning, enjoyment, sense of purpose and other uplifting metrics. Join a co-working space or camp out in a coffee shop. My aim is not to scare anyone. Causes and Remedies.

Cost 100

Cost San Francisco Software Review Technical Review 100

Startup Lessons Learned

NOVEMBER 8, 2008

When we build products, we use a methodology. We know some products succeed and others fail, but the reasons are complex and the unpredictable. a roadmap for how to get to Product/Market Fit." The theory of Product/Market Fit is one key component of customer development, and I highly recommend Marcs essay on that topic.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JULY 28, 2010

It’s common, perhaps the norm, for startups to pivot like that—to discover that a product is catching on in unintended ways worth pursuing. Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. The response was surprisingly positive. Thus far the results are encouraging.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

MAY 31, 2010

I had really debated about whether there was any value in spending the time and money to fly to San Francisco when there was a perfectly serviceable simulcast going on in Cleveland. I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

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. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Duct Tape Marketing

AUGUST 23, 2023

He is the co-founder of Boast.ai, where he leveraged the Community-Led Growth model to bootstrap the company. He is also the co-founder of Traction, a community empowering over 100k innovators through connections, content, and capital. He is the co-founder of Boast.ai This is John Jansen.

Community 52

Community Kuwait Cofounder Bootstrapping 52

Startup Lessons Learned

JULY 5, 2010

I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. The results of the Customer Development process may indicate that the assumptions about your product, your customers and your market are all wrong. In fact, they probably will.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. If you can build cars with it, Im pretty sure you can use it to add agility and flexibility to any product development process.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 2, 2008

► 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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? April 23, 2010 in San Francisco.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JANUARY 12, 2010

Rich also organized the first Lean Startup Meetup right here in San Francisco. Rich also organized the first Lean Startup Meetup right here in San Francisco. I also use it to collect feedback from all my talks and presentations, so its a great place to find out what real people think about the ideas.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

JULY 9, 2010

Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. Are we solving the right problem? We can do better by focusing on process instead of personality.

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

NOVEMBER 27, 2013

If you missed these when they went out live, we encourage you to watch them now , as they lay a strong foundation for The Lean Startup Conference , December 9 -11 in San Francisco—less than two weeks from today. Classic minimum viable product.

Lean 165

Lean San Francisco Cofounder Programming 165

Startup Lessons Learned

MARCH 16, 2009

In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. But, over the years I’ve realized that the toughest problem - the one that matters most and was consistently the most challenging - was figuring out what the product backlog should be.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JANUARY 15, 2010

Two Ways to Hold Entrepreneurs Accountable - The Conversation - Harvard Business Review Way back when the money was doled out, the team made a compelling pitch about the large market that was going to adopt their new innovative product or service. They are on-schedule and on-budget, but their gross metrics are way off.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. April 23, 2010 in San Francisco. Bring your questions.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process. Similar results apply in product management, design, testing, and even operations. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 26, 2009

As a result, for a lot of these companies, Boulder is just a gateway to San Francisco. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. TechStars encourages them to go wherever opportunities take them. And every year, it looks as if one or two entrepreneurs from the program decide to stay.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

JANUARY 7, 2010

► 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. April 23, 2010 in San Francisco. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you?

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

APRIL 14, 2009

This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. Every board meeting, the metrics of success change. More on that in a moment.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Startup Lessons Learned - the Conference (April 23.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JULY 6, 2009

Say you're not creating a product but doing a service? ► 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. Labels: events , slides , video 7comments: Eemo said.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

SEPTEMBER 12, 2008

► 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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? April 23, 2010 in San Francisco.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 10, 2008

► 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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? April 23, 2010 in San Francisco.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 6, 2008

All of the incentives described in the article focus on making it easy and highly desirable to launch your product: [He] claimed that launching projects is the natural state that Googles internal ecosystem tends towards, and its because they pump so much energy into pointing people in that direction. April 23, 2010 in San Francisco.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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. Ive been there: is it me or my cofounder thats crazy? Yet, I think this definition is too important to leave out. Iterating at whiteboard !=

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

MARCH 29, 2010

Weve gone from total obscurity to something people are beginning to misunderstand and even co-opt. I believe it means were achieving product/market fit for a set of ideas. These case studies range in size and scope: from pre-product/market fit to already exited, bootstrapped to venture-backed, solo practitioner to large organization.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

SEPTEMBER 14, 2008

In the very early days, the trick is to find anyone at all who can understand you when you are talking about your product. In our first year at IMVU, we thought we were building a 3D avatar chat product. As product people, we thought of competition in terms of features. that we learned different.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Its not enough just to build a product with great features - you have to figure out if there is a market for it.

Lean 102

Lean San Francisco Agile Continuous Deployment 102