Steve Blank

FEBRUARY 23, 2009

This product development diagram had become part of the DNA of Silicon Valley. Were startups failing because of product failures or was there some other failure mode? Reply A real time story start-up | Failed Screenwriter , on April 8, 2009 at 6:33 pm Said: [.] familiar with Customer Development you should be.

Product Development 143

Product Development Developer Silicon Valley Product 143

Steve Blank

NOVEMBER 5, 2009

It should go without saying that this post is not advice, nor is it recommendation of what you should do, it’s simply my observation of how companies using Customer Development positioned themselves to successfully raise money from venture investors. I believe all this advice is wrong. It’s akin to putting lipstick on a pig.

Customer Development 262

Customer Development Developer Customer Silicon Valley 262

Steve Blank

NOVEMBER 2, 2009

For those of you who have been following the discussion, a Lean Startup is Eric Ries ’s description of the intersection of Customer Development , Agile Development and if available, open platforms and open source. Where is the budget for purchasing the type of product you’re selling? Something else? Who’s the customer?

Lean 244

Lean Silicon Valley Startup RSS 244

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. Geoffrey also talked through the product adoption cycle, but this was less applicable to the products I deal with as a Micropreneur.

Software Review 47

Software Review Software San Francisco RSS 47

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 138

Technology Silicon Valley Fractional VPE Part-Time VPE 138

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 260

Silicon Valley Product Startup Product Development 260

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

AUGUST 1, 2009

Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. He doesnt put out crappy, buggy products and then ask for feedback.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

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 195

Customer Silicon Valley RSS California 195

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 292

Japan Customer Development Developer Customer 292

Steve Blank

MAY 18, 2009

Next, you have to deal with the daily crisis of product development and acquiring early customers. And here’s where life gets really interesting, as the reality of product development and customer input collide, the facts change so rapidly that the original well-thought-out business plan becomes irrelevant.

Founder 297

Founder Silicon Valley RSS China 297

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

AUGUST 24, 2009

How much longer until they start compromising their products or service under other dubious exercises in logic. Reply Michael Alan Miller » Crash , on August 24, 2009 at 8:47 am Said: [.] | Posted by Chill on 24 Aug 2009 at 11:47 am | Shattered. [.] I’m not buying it… literally. Reply Michael F.

Silicon Valley 184

Silicon Valley PR Technical Review RSS 184

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. Five Why’s rarely works for general abstract problems like “our product is buggy&# or “our team moves too slow.&#

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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 144

Vertical Silicon Valley Marketing Customer 144

Startup Lessons Learned

JANUARY 30, 2009

Lessons Learned by Eric Ries Friday, January 30, 2009 Achieving a failure We spend a lot of time planning. Build a truly mainstream product. Build the product in stealth mode to build buzz for the eventual launch. The whole company and board play-tested the product to see its new features first hand. Focus on quality.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Steve Blank

MAY 9, 2017

And to today, when its major product is simply innovation. When the product and channel are bits, adoption by 10’s and 100’s of millions and even billions of users can happen in years versus decades. The second thing that’s changed is that we’re now Compressing the Product Development Cycle.

Restful 222

Restful Silicon Valley Puerto Rico San Jose 222

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. This is precisely the dilemma that the doctrine of minimum viable product is designed to solve.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 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. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. It would be hard to argue against this product development strategy, in general.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

Startup Lessons Learned

SEPTEMBER 11, 2009

Lessons Learned by Eric Ries Friday, September 11, 2009 The cardinal sin of community management Once you have a product launched, you will the face the joys – and the despair – of a community that grows up around it. It took me a long time to understand that benefit of our product. This probably sounds illogical.

Community 158

Community Management Lean Software Review 158

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 131

Silicon Valley RSS California Customer Development 131

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? In a mature company with a mature product, the goal is to pay for lots of people to come to your website. SEM is a simple idea. chatted once?

SEM 164

SEM San Francisco Lean Continuous Deployment 164