Startup Lessons Learned

OCTOBER 26, 2009

Lessons Learned by Eric Ries Monday, October 26, 2009 A real Customer Advisory Board A reader recently asked on a previous post about the technique of having customers periodically produce a “state of the company&# progress report. Many companies seek to involve customers directly in the creation of their products.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Hearpreneur

SEPTEMBER 22, 2021

It drives media attention and fosters customer retention rate, which is why most companies strive to have it in their mission statement. It seeks to solve customer problems in a better and modern way and helping such companies edge the competition. Before the COVID-19 epidemic, this platform was a great video conferencing tool.

Technical Review 120

Technical Review Entrepreneur Software Review SEO 120

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. 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.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. You can imagine how well that worked. On the plus side, that means its a great deal. I think theyve succeeded.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. They are gaining valuable customer data.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

AUGUST 3, 2009

Below youll find the video of my remarks as well as the full slides embedded below. First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. But I wanted to say a few words first.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

DECEMBER 14, 2009

Lessons Learned by Eric Ries Monday, December 14, 2009 Business ecology and the four customer currencies Lately, I’ve been rethinking the concept of “business model&# for startups, in favor of something I call “business ecology.&# Let’s begin with the four customer currencies. And this is true outside of games.

Customer 156

Customer San Francisco Viral Lean 156

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

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did). Labels: product development Speed up or slow down? Expo SF (May.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

APRIL 4, 2010

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? ▼ April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 22, 2008

The law of large numbers (of customers) says you cant help but make at least some money - your valuation is determined by how well you monetize the tidal wave of growth. Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

JUNE 9, 2009

Lessons Learned by Eric Ries Tuesday, June 9, 2009 The Lean Startup Tokyo edition I had a blast speaking at Startonomics Tokyo , which was organized to foster ties between the startup cultures in Japan and Silicon Valley. benjaminjoffe : early adopters of buggy product are visionary customers, sometimes smarter than founders!

Lean 60

Lean San Francisco Japan Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 2, 2008

After all, the worst kind of waste in software development is code to support a use case that never materializes. Scalable systems are no exception - if your assumptions about how many customers youll have, or how they will behave are just a little bit wrong, you can wind up with a massive amount of wasted code. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

AUGUST 1, 2009

When I try to unpack what people mean by the question, heres my best take on what they are asking: "Look, Steve Jobs doesnt go out and ask customers what they want. He doesnt put out crappy, buggy products and then ask for feedback. He tells customers what they want, and he gets it right. Maybe they do it at the whiteboard.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MAY 3, 2009

Lessons Learned by Eric Ries Sunday, May 3, 2009 Videos galore Two new videos are online from recent speeches. The first is my talk on engagement loops and the levers of engagement from the Kontagent/Facebook Developer Garage. Ive embedded the slides below the video feed. Slides from this talk are available here.

Video 104

Video San Francisco Continuous Deployment DC 104

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. Labels: agile , listening to customers 3comments: hauteroute said.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. One of the most important of these hypotheses is always: what will the customer care about?

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JANUARY 30, 2009

Here are a few: We know what customers want. By hiring experts, conducting lots of focus groups, and executing to a detailed plan, the company became deluded that it knew what customers wanted. Everyone had fun; the product worked. But that was two full years before any customers were allowed to use it.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? Slowly, over time, we optimized (or eliminated) each step in the process of becoming a customer by giving us money. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

MAY 31, 2010

Sean Murphy has an excellent and comprehensive roundup of resources about the conference: all of the slides, videos, summaries, notes and write-ups are listed on his blog here. All video from the conference is available for free at Justin.tv If not, youd better watch video of his talk ASAP. And then you can buy a t-shirt.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

SEPTEMBER 10, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

JUNE 2, 2010

The Entrepreneur’s Guide to Customer Development ▼ June (3) What is a startup? ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time). Read the rest.

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. The report is set up to show you what happened to customers who registered in that period (a so-called cohort analysis ). This report is set up to tell you about new customers specifically. One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 4, 2008

Customer development. Its not enough just to build a product with great features - you have to figure out if there is a market for it. The biggest source of cost/time advantage that all lean companies have is avoiding building features that customers dont want. Im working on a post that links to those videos too.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 12, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

FEBRUARY 28, 2009

Customers dont care if you have good metrics, only if you have a good product. And while its true that metrics sometimes can lead to a better product, in my experience just as often they had led to no insight whatsoever, like fancy reports that nobody reads or after-the-fact rationalizations (with graphs!)

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

APRIL 29, 2010

Lessons Learned by Eric Ries Thursday, April 29, 2010 Video update on the Startup Visa Act The Startup Visa Act continues to gain momentum on Capitol Hill, thanks to grassroots support of all of you. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

San Francisco 143

San Francisco Video DC Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 30, 2008

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. There are no customers for that feature, UI issues or no.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? 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.&#

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

AUGUST 26, 2009

If you watch the video/audio below, youll get to see some of the questions I was asked after my presentation. And do your customer development. These quotes are, as is my custom, straight from twitter. leanstartup I could recap these - but just go watch the video already! bdnt nbauman : When to split test?

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

FEBRUARY 10, 2009

As Ive argued elsewhere , my belief is that startups (and anyone else trying to find an unknown solution to an unknown problem ) have to measure progress with validated learning about customers. This was an effective approach to discovering a business by using a sequence of product prototypes to get early customer feedback.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. Talking to potential customers and competitors customers.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

OCTOBER 5, 2008

But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. However, that cant be the end of the story.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128