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 266

Silicon Valley Product Startup Product Development 266

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. They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 140

Technology Silicon Valley Fractional VPE Part-Time VPE 140

Steve Blank

SEPTEMBER 24, 2009

While it is “just business,” many customers form emotional bonds sometimes with products, other times with the company itself. In fact, if you’re doing your job right as a startup, you’re encouraging customers to be passionate about your company and products. No discount for existing users? You’ve been an idiot for sticking with us.”

Customer 203

Customer Silicon Valley RSS California 203

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

YoungUpstarts

NOVEMBER 18, 2019

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. However, the right CRM doesn’t exist on its own separate from sales, customer service, marketing and product development.

Small Business 113

Small Business Sales Colorado Technical Review 113

Steve Blank

NOVEMBER 13, 2012

I discovered my product was a “nice to have,” not a “must have,” and we shut the company down a year a later. However, when I looked into the detail, most of them did not have even early adaptors and the problem wasn’t “chasm crossing,” it was that almost nobody wanted their products. Evangelizing Customer Development in Japan.

Japan 299

Japan Customer Development Developer Customer 299

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. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Similar results apply in product management, design, testing, and even operations.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. But all things are never equal. What’s going on?

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

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. (See

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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

SEPTEMBER 30, 2008

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. Labels: product development 15comments: mukund said. January 18, 2009 8:22 AM Dan Khan 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. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

MAY 28, 2009

Markets with Customer/Market Risk are those where the unknown is whether customers will adopt the product. is whether there is a customer and market for the product as spec’d. These are markets where it may take 5 or even 10 years to get a product out of the lab and into production. The real risk in markets like Web 2.0

Vertical 148

Vertical Silicon Valley Marketing Customer 148

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. 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." Whats wrong with this picture?

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? This condition makes it much easier for teams to innovate, experiment, and achieve sustained productivity. One large source of waste in development is “double-checking.&# In traditional batch-and-queue development, these two concepts are linked.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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

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. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

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

Startup Lessons Learned

OCTOBER 4, 2008

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. Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence. Would love to get in touch.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Steve Blank

JULY 30, 2009

As the (very junior) product marketing manager I got a call from our local salesman that someone at Apple wanted more technical information than just the spec sheets about our new (not yet shipping) chip. Market Type But most startups aren’t in existing markets. Its Woz-inspired creativity set the tone for the rest of the project.&#

Silicon Valley 134

Silicon Valley RSS California Customer Development 134

Startup Lessons Learned

SEPTEMBER 22, 2008

You get increasing growth by optimizing the viral loop , and you get revenue as a side-effect, assuming you have even the most anemic monetization scheme baked into your product. 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

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. Blog at WordPress.com. Theme: Digg 3 Column by WP Designer.

Silicon Valley 126

Silicon Valley RSS Venture Capital Customer Development 126

Startup Lessons Learned

APRIL 4, 2010

Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha. Amazing lean startup resources Is Entrepreneurship a Management Science? Take a look and let me know what you think. Take a look and let me know what you think.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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. September 3, 2009 12:25 PM Omar Ead said. Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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. the version that would facilitate the investment of real money) was planned for late-2009. The result? Thus far the results are encouraging. “If something fails, we cut it off.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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

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

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. Five Whys has its origins in the Toyota Production System. Techniques from lean manufacturing can be part of a startups innovation culture.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 2, 2008

Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Update: PDF version for "lazy linux users" and others who love freedom. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. This post describes such a model.

Customer Development 248

Customer Development Developer Customer Silicon Valley 248

Startup Lessons Learned

JUNE 8, 2009

Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. I had it all set up to a jury-rigged SurveyMonkey - PayPal minimum viable product. So the product development team was busy creating lots of split-tests for lots of hypotheses.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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. Change who your product is for. Most startups fail.

Customer Development 126

Customer Development Conversion Developer Customer 126

Steve Blank

SEPTEMBER 3, 2009

This post describes how the traditional product development model distorts startup sales, marketing and business development. Once the product begins to ship, startup sales execs use orders and revenue as its marker of progress in understanding customers. Freemium models have their own scorekeeping.) What plan says that?

Customer Development 221

Customer Development Developer Customer Silicon Valley 221

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). Customer development. February 13, 2009 4:05 AM Eric said. March 29, 2009 9:05 PM Pierre-Olivier Charlebois said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

ConversionXL

MAY 1, 2017

One of the greatest threats to long-term success is when companies aren’t vigilant enough about responding to the changes in their market—whether it’s by failing to spot product or channel fatigue, acknowledge new competition, make needed updates to products or marketing adjustments in a timely fashion, or embrace new technology coming online.

Technical Review 127

Technical Review Algorithm Channel Analytics 127