Steve Blank

AUGUST 31, 2009

After 20 years of working in startups, I decided to take a step back and look at the product development model I had been following and see why it usually failed to provide useful guidance in activities outside the building – sales, marketing and business development. So what’s wrong the product development model?

Customer Development 242

Customer Development Developer Customer Silicon Valley 242

Steve Blank

SEPTEMBER 25, 2014

It wasn’t always perfect, but it was way more right than wrong, It informed our product development to a great degree and kept us working on more or less the right stuff. Being distributed/network ready (even though Ethernet was just barely coming into use in the enterprise). Pragmatic and Lean. What a gift!

Technical Review 334

Technical Review Venture Capital Software Review Database 334

ConversionXL

FEBRUARY 3, 2022

This philosophy comes from The Lean Startup methodology , which relies on testing hypotheses to better understand your customers’ pain points and goals. It outlines four major growth strategies: market penetration , market development , product development , and diversification. Product development.

Marketing 115

Marketing Framework Metrics Channel 115

Startup Lessons Learned

MARCH 17, 2009

Lessons Learned by Eric Ries Tuesday, March 17, 2009 Join the Lean Startup discussion at Web 2.0 Expo for free Im honored to announce that my Lean Startup session at the Web 2.0 Everyone else can register to come to both sessions for free, including the Lean Startup talk in the main conference. What does this mean for you?

Lean 76

Lean San Francisco Web Continuous Deployment 76

Steve Blank

NOVEMBER 4, 2021

Lean Methodology consists of three tools designed for entrepreneurs building new ventures: The Business Model Canvas – to write down all the hypotheses about a new business; Customer Development – a process for testing those hypotheses outside the building; Agile Engineering – to rapidly build minimal viable products to test product/market fit.

Customer 424

Customer Marketing Lean Vertical 424

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. We already know who to distribute the product to (or else why would we care what they think?).

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. Please leave feedback!) Do you fix bugs before writing code?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. Can this methodology be used for startups that are not exclusively about software? Expo SF (May.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

FEBRUARY 10, 2009

Our tests suite takes nine minutes to run (distributed across 30-40 machines). You cant make these global efficiency improvements until you get clear about the goal of your development process. That leads to a seemingly-obvious question: what is progress in software development? On commit automatically run all tests.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" He doesnt put out crappy, buggy products and then ask for feedback. So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard. I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Expo SF (May. for Harvard Business Revie.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 21, 2013

Lean Analytics is the latest addition to the Lean Series. Business growth comes from improving one of these five “knobs”: More stuff means adding products or services, preferably those you know your customers want so you don’t waste time building things they won’t use or buy. People will behave irrationally. Inertia is real.

Analytics 167

Analytics Lean Metrics Churn Rate 167

Startup Lessons Learned

AUGUST 24, 2009

One is explaining the world as it used to work: the importance of gatekeepers, the scarcity implied by limited distribution, and the resulting quality bar that the industry is so proud of. Mostly it is the time and expense required to create the means of distribution for that industry. It’s just taking some longer than others.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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. Were a software company, so what we do everyday is turn ideas into code.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 23, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. Analytics spark more questions and discussion than almost any other aspect of the Lean Startup method. Alistair and Ben, co-authors of the book Lean Analytics, will help you sort it out in our next webcast, Lean Analytics for Non-tech Companies.

Analytics 167

Analytics Lean Widget Metrics 167

Startup Lessons Learned

FEBRUARY 22, 2010

Even the most radical Bell Curve -style thinkers have to concede that even if there are differences between men and women in the distribution of these traits on average, these curve have substantial overlap, and there should still be a lot more of them represented in high-tech startups. Demographic diversity is an indicator.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." How long does the software sit un-deployed? Software is generally always getting better or getting worse. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

YoungUpstarts

JUNE 6, 2018

In today’s rough-and-tumble startup scene, “lean” is all the rage, and the ability to cut costs without compromising performance is prized above virtually any other managerial competency. Product Development. Most lean startups simply don’t have the wherewithal to get a dozen consumers in a room somewhere.

CPA 124

CPA Bandwidth Lean Startup 124

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. The Lean Startup Intensive is tomorrow at Web 2.0. Automated tests make defects visible.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

steveblank.com

JULY 8, 2011

signup, upgrade, trial pricing Zuora – online subscription management FeeFighters – find the cheapest credit card processors HealPay – Collections made easy Customer Support Tender – support, knowledgebase tool for your site GetSatisfaction - conversations between companies / customers.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

bizthoughts.mikelee.org

MARCH 8, 2012

Active software engineers probably get two offers a month or more. I was able to hire phenomenal software engineers and grow a strong team culture. link] # 4 hours ago Going #lean and testing with imagemaps, cuz concepts are cheap and code is expensive. # I was lucky enough to have worked for Yahoo! YHOO ) in its second act.

Technical Cofounder 40

Technical Cofounder Cofounder Technical Review Software Review 40

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. As always, Paul is right.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 10, 2008

His post is ostensibly about how often to release new work (whether youre a blog writer, movie star, software team.) I’ve been in the software industry for a long time. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 8, 2008

It felt like software that grownups were supposed to use, and we didnt qualify. It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. The Lean Startup Intensive is tomorrow at Web 2.0. I dont really remember why it didnt work.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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

Startup Lessons Learned

SEPTEMBER 18, 2008

Its enourmously helpful when you need to generate new ideas about what to do, or when you face a product problem you dont know how to solve. For example, we used to be baffled at IMVU by the significant minority of people who would download the software but never chat with anyone. Lean Start-up SlideShare prez at Web 2.0

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 22, 2008

My favorite instance of this is scheduling software. If you read Lean Thinking , you can enjoy numerous examples of companies that replaced multi-million dollar MRP systems with a simple white board. The lean manufacturing guys call this visual control and its very powerful. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

techcocktail.com

OCTOBER 23, 2010

But while you are small and lean, take advantage of everyone skills; if someone on your team is a great writer, have them take charge of your press releases and marketing content. be the manager and product developer). Software Engineer—PHP—Energy Software for the Smart Grid @ Agentis Energy (Elmhurst, IL) Sr.

San Francisco 44

San Francisco Startup PHP San Diego 44

Startup Lessons Learned

JANUARY 4, 2009

Incremental and proportional software complexity. This is great for something like a huge DHT or a distributed work queue. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JULY 15, 2010

And the fact that the effects of this IPO vanishing act are being felt first and foremost in the software business also makes sense to me. In fact, I believe that the software business is the canary in the coal mine: increasingly, all businesses are going to look more and more like software businesses. We have much work to do.

IPO 166

IPO San Francisco Lean Silicon Valley 166

www.vccafe.com

MARCH 11, 2013

Lean Methodology Sources. Steve Blank on Lean Customer Development. Part 3- Lean Cust. Steve Blank’s Lean Startup Resources. Lean Startup Circle â?? free/cheap web customer relationship mgmt software. marketing automation software. email blast and mgmt software. Codeacademy.

Software Review 53

Software Review Technical Review Startup 53

K9 Ventures

AUGUST 13, 2010

In fact, at the time (1996-1997) we offered both a downloadable product, that our customers could install on their own servers, and a “hosted-offering”, which came to be known as “On-Demand”, then the “ASP” (Application Service Provider) model, and today we call it “SaaS” (Software as a Service). Patrick is completely correct here.

Revenue 72

Revenue Developer Java Customer Development 72

Up and Running

MARCH 1, 2016

So, if I were going to invent something, I’d probably start by creating an affordable jeweler’s workbench, not least because I’d be able to test it, and because I already know all the distribution channels I’d need to hit in order to sell it. You can do this on your own too using the lean planning methodology.

Non-disclosure Agreement 60

Non-disclosure Agreement NDA Non-Compete Naming 60

Startup Lessons Learned

SEPTEMBER 11, 2009

Loyalty is not something that people distribute to all and any that they come into contact with regardless of warrant. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Users felt themselves to be valued partners because you made them feel that way.

Community 158

Community Management Lean Software Review 158

Steve Blank

JUNE 8, 2009

Execution by Vertical Market As the class progressed, students asked how the activities/functions of a startup; (Sales, Marketing, Business Development, Product Development, etc.) How does product development differ in communications hardware versus enterprise software, etc. Waterfall, Agile, Lean?

Vertical 123

Vertical Silicon Valley RSS Marketing 123