Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo (and a call for help) Ive been asked to speak this year at the Web 2.0 The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The same process works in Interaction Design. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Hearpreneur

JANUARY 28, 2022

I was required to design the logos for each of the companies. I also inquired with a professor at a university that provided design about accepting the assignment as a practical. Enventys Partners was born when my company Command Partners, a digital marketing firm, vertically merged with Enventys, a product development firm.

Naming 152

Naming Entrepreneur Jordan Merger 152

Startup Lessons Learned

MARCH 17, 2009

Lessons Learned by Eric Ries Tuesday, March 17, 2009 Join the Lean Startup discussion at Web 2.0 Expo for free Im honored to announce that my Lean Startup session at the Web 2.0 Eric- I am an industrial design student at Virginia Tech. The chance to not only be at the Web 2.0 What does this mean for you? Expo SF (May. .

Lean 76

Lean San Francisco Web Continuous Deployment 76

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. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MARCH 25, 2010

(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. 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

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

APRIL 4, 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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. . Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 15, 2008

This kind of result is typical when you ship a redesign of some part of your product. The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

ConversionXL

JANUARY 18, 2022

Product marketing informs strategic positioning and ensures alignment across the company. It partners with sales to close more revenue, informs product teams to deliver better products, and in some cases, co-owns demand generation activities with marketing teams. Take Bellroy , a leather accessories retailer.

Marketing 110

Marketing Product Audience Equity 110

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

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 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. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Was it an important or irrelevant fact that most of our web code was procedural and not object-oriented?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JULY 3, 2009

If your practice is not designed to cope with uncertainty, it has no place in a startup - even if your startup is located in government or enterprise. Now, I dont think even most dot-com era founders were bad people, I just think traditional startup methods make it too easy to become confused about whether were creating real progress or not.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

NOVEMBER 8, 2008

You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Our goal in product development is to find the minimum feature set required to get early customers.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 22, 2008

For Neopets, its simply a side-effect of their game-like product design. Either way, you can use any marketing channel thats available to bring in new customers, including word of traditional advertising, SEO, SEM - wherever you can find prospects who are going to find your product addicting. Expo SF (May. . Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Expo SF (May. . Expo SF (May.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

JUNE 2, 2010

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

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. This is still an essential practice, especially on the web.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. . Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries. Expo SF (May. . Expo SF (May.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

MAY 31, 2010

Lessons Learned by Eric Ries Monday, May 31, 2010 Thank you The past month has been an incredible roller coaster: #sllconf was a trending topic (briefly topping Justin Bieber before the wifi in the hotel gave out), the Web 2.0 There are so many more people to thank: Sarah Milstein and the Web 2.0

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JULY 5, 2010

As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. 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 Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. .

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. . Expo SF (May.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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. Good luck, engineering manager. It was painful for a lot of people.

Software Review 164

Software Review Engineer Management Technical Review 164

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

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. . Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. . Expo SF (May.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 6, 2009

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, No departments The Five Whys for Startups (for Harvard Business R. Expo SF (May. . Expo SF (May.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

AUGUST 26, 2009

And one last specific practice that came up at this session: feverishaaron : UI, design and programmers are all in the same department, all have the same title, and all are evaluated the same. That meant getting designers, programmers, and QA folks to cross-train and work together as peers. August 29, 2009 8:54 AM Ben Casnocha said.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

JULY 30, 2009

► 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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. . Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 14, 2008

Most of the people building our product werent themselves target customers. So there was simply no substitute for seeing actual customers with the product, live. Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131