Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." a roadmap for how to get to Product/Market Fit."

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Unfortunately, positioning our product as an "IM add-on" was a complete mistake.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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

ConversionXL

SEPTEMBER 6, 2013

I feel like “conversion rate optimization” is in 2013 what “social media marketing” was in 2009. Not because they have a conversion problem but because they never really nail the product or how to market it. This is a customer development problem. So What is Customer Development?

Customer Development 126

Customer Development Conversion Developer Customer 126

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

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

YoungUpstarts

NOVEMBER 18, 2019

And with that thought in mind, here are five ways your customer relationship management (CRM) system can help you turn Small Business Saturday into future sales. When Small Business Saturday drives customers to seek out your product, it’s vital that you take the opportunity to collect their contact information and log it in your CRM.

Small Business 113

Small Business Sales Colorado Technical Review 113

Steve Blank

FEBRUARY 23, 2009

This product development diagram had become part of the DNA of Silicon Valley. Reply A real time story start-up | Failed Screenwriter , on April 8, 2009 at 6:33 pm Said: [.] a customer before you try and build a business. familiar with Customer Development you should be.

Product Development 163

Product Development Developer Silicon Valley Product 163

Software By Rob

NOVEMBER 16, 2009

Geoffrey Moore Author of Crossing the Chasm and four other books, Geoffrey Moore has been thinking about high-tech product development longer than most of have been doing anything on a computer. Simplicity is mostly a way to avoid looking like you’re releasing a product that lacks features. Subscribe via RSS On Twitter?

Software Review 47

Software Review Software San Francisco RSS 47

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

Steve Blank

JUNE 25, 2009

Twenty eight years ago I was the bright, young, eager product marketing manager called out to the field to support sales by explaining the technical details of Convergent Technologies products to potential customers. These companies would take our computers and put their name on them and resell them to their customers.

Technology 146

Technology Silicon Valley Fractional VPE Part-Time VPE 146

Steve Blank

SEPTEMBER 17, 2009

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development.

Customer Development 256

Customer Development Developer Customer Silicon Valley 256

Steve Blank

SEPTEMBER 3, 2009

This post describes how the traditional product development model distorts startup sales, marketing and business development. The meaning of alpha test , beta test, and first customer ship are pretty obvious to most engineers. For example, some startup sales execs believe hiring the core sales team is a key objective.

Customer Development 229

Customer Development Developer Silicon Valley Customer 229

Startup Lessons Learned

JULY 29, 2009

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. Remember Hamlet?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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

Steve Blank

FEBRUARY 23, 2009

I was between my 7th and 8th and final startup; licking my wounds from Rocket Science, the company I had cratered as my first and last attempt as a startup CEO. We’ve managed startups like this forever; there is no other way to manage them.” Blog at WordPress.com. Theme: Digg 3 Column by WP Designer.

Silicon Valley 133

Silicon Valley RSS Venture Capital Customer Development 133

Steve Blank

JULY 30, 2009

Your Customers are Not Who You Think For years I thought this “million unit chip sale by accident&# was a “one-off&# funny story. That is until I saw that in startup after startup customers come from places you don’t plan on. Your board nods sagely at your target customer list.

Silicon Valley 146

Silicon Valley RSS California Customer Development 146

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

Steve Blank

SEPTEMBER 10, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. They never understood Market Type. Why does Market Type matter?

Customer Development 223

Customer Development Developer Customer Silicon Valley 223

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

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. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. February 21, 2009 12:10 AM Harold Fowler said. Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? If we accept the verdict of customers instead of pundits, I think these claims are easy to dismiss. One is used by engineers to refer to the process of getting code fully integrated into production.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

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?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JULY 28, 2010

the version that would facilitate the investment of real money) was planned for late-2009. Third, the company expected hundreds of amateurs who performed poorly in the game to realize they weren’t good at investing and therefore become customers. in fact only five people converted into paying customers. The result?

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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? ) In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. January 2, 2009 8:54 AM mancjew said.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Steve Blank

NOVEMBER 5, 2009

Chasing funding versus chasing customers and a repeatable and scalable business model, is one reason startups fail. Chasing funding versus chasing customers and a repeatable and scalable business model, is one reason startups fail. Are there customers for what you are building? How many are there? Can it scale?”

Customer Development 270

Customer Development Developer Customer Silicon Valley 270

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

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. We finally settled on a $1.99

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

APRIL 4, 2010

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. No departments The Five Whys for Startups (for Harvard Business R. Take a look and let me know what you think.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. Yet a huge class of modern software projects are being developed in a very different context.

Software Review 87

Software Review Design Software San Francisco 87

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

Steve Blank

AUGUST 27, 2009

This series of posts is a brief explanation of how we’ve evolved from Product Development to Customer Development to the Lean Startup. The Product Development Diagram Emerging early in the twentieth century, this product-centric model described a process that evolved in manufacturing industries.

Silicon Valley 272

Silicon Valley Product Startup RSS 272

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.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JULY 6, 2009

Lessons Learned by Eric Ries Monday, July 6, 2009 Lean Startup fbFund slides and video As a follow-up to my previous post on my talk for fbFund at Facebook , there was enough interest in watching video of the talk that I have finally uploaded it using Apples MobileMe. Say you're not creating a product but doing a service?

Lean 115

Lean Video San Francisco Continuous Deployment 115