Steve Blank

NOVEMBER 13, 2012

To celebrate the debut of the Japan edition of “The Startup Owner’s Manual” and to express great thanks to Steve and his co-author Bob Dorf, I would like to reflect back what first drew me to this book and offer Steve’s worldwide readers a look at the progress of Customer Development and the Lean LaunchPad class in Japan.

Japan 305

Japan Customer Development Developer Customer 305

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. This is the approach of test-driven-development (TDD).

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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

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 261

San Jose Technical Review Customer Development Software Review 261

Startup Lessons Learned

JANUARY 12, 2010

Lessons Learned by Eric Ries Tuesday, January 12, 2010 Amazing lean startup resources A year ago, there was no lean startup movement. I continue to believe that the explosion of interest in the lean startup has very little to do with me. If you are attempting to apply lean startup ideas in your own business - you are not alone.

Lean 146

Lean San Francisco Wiki Startup 146

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. Great post Eric! Expo SF (May.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Up and Running

JULY 6, 2016

Often, a business plan introduces a new technology that requires some explaining. On one hand, as a reader of business plans for investors, I see way too many business plans that ask a reader to wade neck-deep through technology to get to the business. Establish technology as a differentiator, when it is.

Technical Review 72

Technical Review Software Review Business Plan Development Team Review 72

Startup Lessons Learned

JUNE 17, 2010

I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. As a technical fix, it was brilliant. I remember one such meeting vividly. So they react in two ways.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Five Whys has its origins in the Toyota Production System. Applied to a start-up, heres how it works.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Professionals Musings

JANUARY 2, 2019

Most of you aspiring entrepreneurs have no idea how dramatically your own role has to evolve as you develop a solution, start a business, and expect it to scale into a successful self-managed company. Thus my job as a small business advisor really is really more about getting you developed than perfecting the business.

Leadership 248

Leadership Technical Review Cofounder Social Media 248

Startup Lessons Learned

DECEMBER 7, 2008

Its common to find a hacker at the heart of almost any successful technology company. When a startup encounters difficult technical problems, this is the guy you want solving them. As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. All is not lost, though.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

betashop.com

OCTOBER 8, 2012

90 Things I’ve Learned From Founding 4 Technology Companies. On October 27, 2010 I wrote a blog post about the “ 57 Things I Learned Founding 3 Tech Companies.”. 90 Things I’ve Learned Founding 4 Tech Companies: Find your company’s One Thing. ?? We do twice-yearly reviews of all Fab team members. So, here goes.

Technical Review 108

Technical Review Technology Software Review Valuation 108

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. Let me quote an example that I used recently: Remember IMVUs initial IM add-on product?

Software Review 87

Software Review Design Software San Francisco 87

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. Under continuous deployment, as soon as code is written, it’s on its way to production.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. There are too many products clamoring for attention. I’ve met a lot of gatekeepers in the past few months.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. There would be no Microsoft, Sun Microsystems, or countless other job-creating tech companies today if early computers required corporate authorization to use.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JANUARY 7, 2010

for Harvard Business Review) Im excited to have just published the first of several articles on entrepreneurship for the Harvard Business Review online. The Conversation - Harvard Business Review For most of us, the phrase management science conjures up a decidedly non-entrepreneurial image, and for good reason.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

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

Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. We also try to communicate the initial due date with as few people outside our company (investors, customers, etc) as possible to avoid losing credibility.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Both Sides of the Table

FEBRUARY 27, 2019

If you buy into the argument that a strong board can actually help you then this post will lay out how to help you have more productive meetings by preparing properly in advance. How Most Board Meeting Prep Works I’ve been sitting on tech boards for two decades so I have some experience with what goes wrong.

Stock Options 226

Stock Options Metrics Stock Valuation 226

This is going to be BIG.

AUGUST 22, 2012

Let’s start out with the basic functions of a tech company: 1) Engineering 2) Marketing 3) Sales 4) Business development 5) PR 6) Design 7) Product Management 8) HR 9) Operations 10) Finance Ok, that's just overwhelming. In a way, you can think of BD as “sales when you don’t know what the product is yet.”

PR 152

PR Technical Review Seed Stage Design 152

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. I joined a financial services tech startup in 1999. It was a disaster.

Lean 60

Lean San Francisco Software Review Continuous Deployment 60

Startup Lessons Learned

AUGUST 26, 2009

I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries. Im also excited to share two long-form reviews from actual attendees. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

JANUARY 15, 2010

Lessons Learned by Eric Ries Friday, January 15, 2010 Two Ways to Hold Entrepreneurs Accountable (for Harvard Business Review) The next part in the series I am writing for Harvard Business Review is online. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

FEBRUARY 11, 2009

Heres the short version: hire people from the online communities that develop free software. Yes, you may be more familiar with the term open source, but lets give credit where credit is due , at least for today). Ignore the famous people who are busy giving lots of speeches about how technology X will change the world.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

MARCH 22, 2010

Part of this is due to their determination to overtake us, but part is due to structural changes in the nature of entrepreneurship. For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 121

San Francisco Indiana Lean Startup 121

YoungUpstarts

AUGUST 17, 2018

It’s the latter category that’s especially vulnerable to premature marketing, but evolving technology, particularly security issues linked to the Internet of Things (IoT), can create post-market risks for both groups. And for non-FDA track products, there’s no requirement that companies fix technology vulnerabilities.

Software Review 100

Software Review Startup Technical Review Software 100

Startup Lessons Learned

NOVEMBER 6, 2008

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. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May. Conference streaming, sponsors, discounted tickets.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 18, 2008

Many of them have really cool products shipping or about to be released, and I wholeheartedly agree with my friends at the iFund that the next generation of applications is going to be amazing. From a technical point of view, its amazing. All I see is a name, an icon, a price, the developers name, and a review star-rating.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

ConversionXL

OCTOBER 7, 2021

These are the four stages of a product we’ll be focusing on. . However, on a more granular graph, the introduction phase would be preceded by a product development stage. This stage is used to determine the viability of your product and confirm when it should go to market. Image source.

Product 142

Product Marketing Software Review Social Media 142

Feld Thoughts

NOVEMBER 18, 2013

One of them used to be a lead developer at [insert hot consumer tech company here]. They need to raise money before building anything substantial after determining that they needed a little dough to follow the Lean Startup methodology. It’s enough time to hang yourself if you are not careful.

Burn Rate 153

Burn Rate Equity Software Review Early Stage 153

crowdSPRING Blog

MAY 11, 2012

Lean Marketing: Delivering Customer Service via Social Media – [link]. Six Myths of Product Development – [link]. Unlimited Vacation Doesn’t Create Slackers–It Ensures Productivity – [link]. So what exactly is a tech company? Six Myths of Product Development – [link].

Social Media 92

Social Media Small Business Design Media 92

This is going to be BIG.

JUNE 30, 2010

This way, you're getting the product feedback you need from customers and partners, I'm seeing what the market thinks of what you have, and we didn't even talk money at all yet. If the feedback is great, I'm going to lean forward with some more interest. Tags: First Round Capital Venture Capital & Technology.

Technical Review 107

Technical Review Due Diligence Venture Capital Later Stage 107