Steve Blank

MAY 9, 2017

The second thing that’s changed is that we’re now Compressing the Product Development Cycle. In the 20 th century startups I was part of, the time to build a first product release was measured in years as we turned out the founder’s vision of what customers wanted. Today startups build products differently.

Restful 249

Restful Silicon Valley San Jose Puerto Rico 249

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Jeff Hilimire

OCTOBER 8, 2014

My name is Richard Simms and, I am a Cofounder of Tech Talent South. Our mission at TTS is to develop more tech talent in the South through beginner-focused programs teaching web development and computer programming. We actually met taking some web development classes in Chicago. Who are you and what do you do?

Cofounder 68

Cofounder Charlotte Raleigh Atlanta 68

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

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. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

SEPTEMBER 15, 2008

This kind of result is typical when you ship a redesign of some part of your product. The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Your CTO might be a great architect, evangelist, interface designer or incredible debugger.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

The Equity Kicker

AUGUST 20, 2014

I’m reproducing in full here because it’s a great explanation of our solo-founder hypothesis and how we work more generally. Are you a solo founder with an idea? Snaptrip started as an idea, an excel spreadsheet and a passionate founder called Matt. THE DYNAMIC BETWEEN FOUNDER AND TEAM. FINDING A COFOUNDER.

Cofounder 95

Cofounder Founder Technical Cofounder Technical Review 95

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. Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

View from Seed

MAY 11, 2016

Investors love the idea of backing second-time founders, especially if they have had success in their last company. etc… In addition, first-time founders I speak to often talk about how much they have learned and how they resolve to do things differently and better the next time. Is there a sophomore slump to avoid?

Founder 159

Founder Cofounder CTO Hire Early Stage 159

Startup Lessons Learned

NOVEMBER 8, 2008

You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Our goal in product development is to find the minimum feature set required to get early customers.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Professionals Musings

AUGUST 25, 2017

In case you haven’t noticed it, the rapid evolution of do-it-yourself (DIY) facilities for developers, including 3-D printers, SketchUp and makerspaces such as TechShop , have scaled down the cost of prototypes and hardware design by an order of magnitude. Quick low-cost design and fabrication alternatives are extremely valuable.

Technical Cofounder 153

Technical Cofounder Intellectual Property Wiki Cofounder 153

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 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

A Smart Bear: Startups and Marketing for Geeks

AUGUST 30, 2010

He blogs to 10,000 web entrepreneurs at Software by Rob and co-hosts the podcast Startups for the Rest of Us. A virtual assistant (VA) is a remote worker hired to complete tasks you should not be doing as the founder of a startup. As a developer, the features we dropped seem like a necessity from day 1. Introduction.

Software Review 284

Software Review Startup Technical Review Hosting 284

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

APRIL 29, 2013

This post was written by Sarah Milstein, co-host of The Lean Startup Conference. Eric has talked often about recognizing a startup as an organization designed to create a new product or service under conditions of extreme uncertainty. Often, in very young organizations, those people are simply the founders.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The same process works in Interaction Design. Take a look and let me know what you think.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

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.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

FEBRUARY 22, 2010

I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. Some designers also hate optimizing (which is why the “41 shades of blue&# test is so famous – a famous designer claims to have quit over it ).

San Francisco 154

San Francisco Lean Metrics Design 154

Steve Blank

JUNE 25, 2009

Their engineering teams didn’t have the expertise using off-the-shelf microprocessors (back then “real” computer companies designed their own instruction sets and operating systems.) They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 146

Technology Silicon Valley Fractional VPE Part-Time VPE 146

Startup Lessons Learned

APRIL 9, 2009

So instead of having sales, marketing, and business development, we have a problem team implementing customer development. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

APRIL 4, 2010

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Take a look and let me know what you think.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JULY 5, 2010

As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. It is incumbent upon you to listen. It is incumbent upon you to listen.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Hearpreneur

JANUARY 28, 2022

I was required to design the logos for each of the companies. I also inquired with a professor at a university that provided design about accepting the assignment as a practical. Enventys Partners was born when my company Command Partners, a digital marketing firm, vertically merged with Enventys, a product development firm.

Naming 161

Naming Entrepreneur Jordan Merger 161

Startup Lessons Learned

SEPTEMBER 13, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Take a look and let me know what you think.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

NOVEMBER 7, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Take a look and let me know what you think.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 28, 2009

None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones. Luckily for me, my co-founders eventually prevailed and we went on to build a product that customers actually wanted. Labels: product development 4comments: Doug said.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JUNE 2, 2010

And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Techniques from lean manufacturing can be part of a startups innovation culture.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. Thats what business is designed to do.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

JULY 28, 2010

Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The response was surprisingly positive.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158