Up and Running

MAY 23, 2016

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. Noah has been a key figure in the making of LivePlan, our own SaaS product. Step 1: Start with a lean plan. Your competition, and a brief description of how you differ from them.

Software Review 74

Software Review Software Delaware Forecast 74

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. Do you fix bugs before writing code?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. A new bit of code contained an infinite loop!

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. The product manager was clearly struggling to get results from the rest of the team. Lets start with what the product manager does.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

SoCal CTO

DECEMBER 1, 2010

I continue to collect great content that is the intersection of startups, products, online and technology. The United States is now a debtor nation to China and that the bill is about to come due. Five Reasons You Haven’t Launched - Software By Rob , November 10, 2010 Photo by stevendepolo. But I don’t think so. call to arms.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Up and Running

DECEMBER 6, 2012

Today, I want to introduce you to a new concept for starting and growing successful companies: Lean Planning™. Before I dive too deeply into the Lean Planning methodology, it makes sense to talk about its history and where it comes from. Lean Planning is born.

Lean 147

Lean Silicon Valley Forecast Technical Review 147

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Steve Blank

OCTOBER 15, 2019

This article previously appeared in the Harvard Business Review. Once upon a time every great organization was a scrappy startup willing to take risks – new ideas, new methods, new customers, targets, and mission. Process Versus Product. People who manage processes are not the same people as those who create product.

Government 320

Government Technical Review Acquisition Metrics 320

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

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

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Steve Blank

AUGUST 3, 2012

Long before there was the Lean Startup, Business Model Canvas or Customer Development there was a guy in Santa Barbara California who had already figured it out. Frank Robinson of SyncDev has been helping companies figure out their minimum viable product and pivots since 1984, long before I even knew what it meant.

San Jose 259

San Jose Technical Review Customer Development Software Review 259

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

conversionxl.com

SEPTEMBER 10, 2013

It’s Not a Conversion Problem, It’s a Customer Development Problem. 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? Change who your product is for.

Customer Development 60

Customer Development Conversion Developer Customer 60

ConversionXL

JUNE 14, 2021

The USP that communicates this is: “ConvertKit helps you find your audience, turn them into true fans, and earn a living as a creator with our audience building and email marketing software.”. The best approach is going straight to the source, asking your customers what they want, need, and already love about your products or services.

Software Review 158

Software Review Audience Differentiation Framework 158

Steve Blank

APRIL 5, 2017

I was having coffee with the CEO of a new startup, listening to her puzzle through how to communicate to potential customers. She was an academic on leave from Stanford now selling SAAS software to large companies, but was being inundated with marketing communications advice. “My Who’s the user of product? with a strategy.

Marketing 316

Marketing Audience Technical Review PR 316

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

David Teten

OCTOBER 1, 2015

Should you co-found your company with a software development shop? I’ve talked with a number of software development shops who are eager to get into the business of cofounding companies, i.e., getting product revenue and equity instead of just consulting revenue. mentor VCs, e.g., most VCs.

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. If we accept the verdict of customers instead of pundits, I think these claims are easy to dismiss.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

crowdSPRING Blog

MARCH 15, 2013

Lean Business: Capacity Management, Overhead, and Your Business – [link]. The science of how temperature and lighting impacts our productivity | The Buffer – [link]. Bad Customer Development Questions and How to Avoid My Mistakes – [link]. Crowdsourced Workforces Rising | Xconomy – [link].

Social Media 105

Social Media Small Business Design Media 105

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. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. But what about Commodity?

Software Review 87

Software Review Design Software San Francisco 87

Steve Blank

MARCH 19, 2009

While I was consulting for them, I got a call from a recruiter for a company called SuperMac, which made add-on products for the Macintosh. They sold their product through the computer retail channel, something I knew nothing about. They sold to a set of customers I knew nothing about.

Silicon Valley 165

Silicon Valley Software Review Technical Review RSS 165

Startup Lessons Learned

FEBRUARY 10, 2009

Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day. Code reviews and pairing Great practices. That’s 6 deploys an hour.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. But there is more to technical debt than just the interest payments that come due. Unfortunately, customers hated that initial product.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Both Sides of the Table

NOVEMBER 1, 2009

They communicated this to product management who looked at all of the internal requirements we had generated (e.g. some came from our customer service, some were to improve performance / scalability from tech ops, some were bug fixes, etc.) and product management worked with me to decide what to build & when.

Customer 280

Customer Technical Review Software Review Mexico 280

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. This shift allowed us to crank out working software quickly as a service.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

steveblank.com

JULY 8, 2011

Home Books for Startups Guide Secret History-Bibliography Steve Blank Startup Tools Steve Blank Entries RSS | Comments RSS Email Subscription Get Steve Blank via your RSS Feed RSS - Posts RSS - Comments Categories Air Force (12) Ardent (10) Audubon (1) Big Companies versus Startups: Durant versus Sloan (39) Business Model versus Business Plan (..)

Software Review 110

Software Review Startup Silicon Valley Analytics 110

Both Sides of the Table

NOVEMBER 3, 2009

People mistook extra doses of Ajax for a successful product. The last couple of years has also seen the huge initial success of Ycombinator, the Lean Startup and many other product driven approaches to going to market. I have seen really great product people espouse the death of the business plan. Do so at your peril.

Business Plan 334

Business Plan AJAX Venture Capital Technical Review 334

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. The Lean Startup Intensive is tomorrow at Web 2.0.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Every change required a server restart.

PHP 166

PHP Software Review Ruby San Francisco 166

SoCal CTO

AUGUST 3, 2010

5 Lessons from 150 startup pitches - A Smart Bear: Startups and Marketing for Geeks , July 11, 2010 I just reviewed several hundred startup pitches for Capital Factory. should have leaned on them a lot more, but I didn't, or at least not in the right ways. Most were on paper and video; 20 were invited to pitch in person. Silly, right?

Software Review 217

Software Review Startup Venture Capital Technical Review 217

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MAY 7, 2009

They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place. Initially, IMVU sought to quickly build a product that would prove out the soundness of their ideas and test the validity of their business model.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131