Steve Blank

JUNE 25, 2009

They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. He complemented their elegantly designed minicomputers and made some astute comment about their architecture (now I’m rolling my eyes, their computers were dinosaurs) and asked who were the brilliant designers.

Technology 138

Technology Silicon Valley Fractional VPE Part-Time VPE 138

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Open APIs and data-oriented architecture (aka "web 2.0").

Product Development 88

Product Development Developer San Francisco Product 88

Steve Blank

JUNE 23, 2016

ARM, a competitor, not only had a better, much lower power processor, but a better business model – they licensed their architecture to other companies that designed their own products. Today that’s built on the premise that an x86 architecture is the one best suited for big data. Startups are unencumbered by the status quo.

Architecture 227

Architecture IRR Balance Sheet Liquidity Event 227

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. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

Steve Blank

AUGUST 27, 2012

It was great to watch him embrace the spirit and practice of customer development. He was constantly in front of customers, listening, selling, installing and learning. It seemed like once a week Yuri would come back from a customer meeting brimming with new insights. Filed under: Customer Development.

Founder 316

Founder Cofounder Advisory Board Burn Rate 316

Startup Lessons Learned

JUNE 17, 2010

Even more surprisingly, the engineering team was equally vocal about their contention that adding rounded corners would add weeks of development time to the project, which would have pushed it out way past its hard deadline, effectively killing it. The engineering team wasn’t happy either. The engineering team wasn’t happy either.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. 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 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Thoughts on scientific product development Lo, my 5 subscribers, who are you? Were in a new wave of platform evolution.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

JUNE 15, 2009

If youre looking for resources on getting started, see " Continuous deployment in 5 easy steps ") The goal of continuous deployment is to help development teams drive waste out of their process by simultaneously reducing the batch size and increasing the tempo of their work. How severely is failure punished?

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Steve Blank

FEBRUARY 23, 2016

As a formal method, the Lean Startup consists of three parts: The Business Model Canvas – to frame hypotheses, Customer Development – to test those hypotheses in front of customers, and Agile Engineering – to build Minimum Viable Products to maximize learning. Customer Relationships is changed to Buy-in/Support.

Business Model 120

Business Model Revenue Channel Community 120

Startup Lessons Learned

DECEMBER 28, 2009

Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. So asking customers if theyd like to receive new releases more often usually leads to a consistent answer: "No, thank you." Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

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

andrewchenblog.com

MARCH 10, 2010

Coupled with A/B testing, customer development, and thinking through business problems in a scientific, hypothesis-driven way, you end up with a powerful cocktail of techniques to build a modern startup in the most iterative way possible. They’ve also done a lot to actually remove options from the menu and navigation. See [link].

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. The goal of iterative development is to give us guard rails so we dont veer off to either extreme. you can be incredibly scientific.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. Wanted to add one additional note from the perspective of someone who was intimately involved in developing this system. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. Its common to find a hacker at the heart of almost any successful technology company.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Customer data is normally partitioned according to customer id.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

FEBRUARY 16, 2009

Lets start with a distinction between shipping new software to the customer, and changing the customers experience. The idea is that often you can change the customers experience without shipping them new software at all. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 8, 2009

I started my last company with 100% off-shore resources because I could never have completed Customer Development at a reasonable cost of money or regulatory burden had I employed US Citizens. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? September 10, 2009 4:37 AM Dale B.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

JANUARY 30, 2009

Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Even a great architecture becomes inflexible.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. Doesnt that sound good?

San Francisco 79

San Francisco Lean Continuous Deployment DC 79