Startup Lessons Learned

JULY 29, 2009

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. Remember Hamlet?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Steve Blank

JUNE 25, 2009

Twenty eight years ago I was the bright, young, eager product marketing manager called out to the field to support sales by explaining the technical details of Convergent Technologies products to potential customers. They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 138

Technology Silicon Valley Fractional VPE Part-Time VPE 138

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. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. February 21, 2009 12:10 AM Harold Fowler said. Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

YoungUpstarts

NOVEMBER 18, 2019

When Small Business Saturday drives customers to seek out your product, it’s vital that you take the opportunity to collect their contact information and log it in your CRM. However, the right CRM doesn’t exist on its own separate from sales, customer service, marketing and product development.

Small Business 113

Small Business Sales Colorado Technical Review 113

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. And what of the product development team?

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Steve Blank

NOVEMBER 13, 2012

A few of the many quotations that struck me: “Most startups fail due not to the failure of product development but due to the lack of customers”. Learning and discovering who a company’s initial customers will be and what market they are in, requires a process separate and distinct from product development”.

Japan 292

Japan Customer Development Developer Customer 292

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. February 14, 2009 11:12 PM Eric said. May 15, 2009 1:17 AM neocoder said.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

FEBRUARY 23, 2009

I was between my 7th and 8th and final startup; licking my wounds from Rocket Science, the company I had cratered as my first and last attempt as a startup CEO. Blog at WordPress.com. Theme: Digg 3 Column by WP Designer.

Silicon Valley 125

Silicon Valley RSS Venture Capital Customer Development 125

Steve Blank

MAY 28, 2009

Market Risk vs. Invention Risk - Click to Enlarge For companies building web-based products, product development may be difficult, but with enough time and iteration engineering will eventually converge on a solution and ship a functional product - i t’s engineering, not invention.

Vertical 144

Vertical Silicon Valley Marketing Customer 144

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. krasicki April 3, 2009 7:19 AM control valves said.

Software Review 164

Software Review Engineer Management Technical Review 164

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. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Take a look and let me know what you think.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Steve Blank

JULY 30, 2009

Look for some “ skunk works &# project where the product developers are actively seeking alternatives to their own engineering organization. Reply Terence Pua , on July 30, 2009 at 9:27 am Said: Steve, I’ve read and re-read that section in Chapter 2 re: market types and I still don’t fully comprehend.

Silicon Valley 131

Silicon Valley RSS California Customer Development 131

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. January 2, 2009 8:54 AM mancjew said. January 2, 2009 8:57 AM Abbas said. Abbas February 22, 2009 3:33 PM cwillu said. Would love to get in touch.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Changes queued for over a year, meetings to decide if a change was safe to release, and changes would still fail in production. June 15, 2009 7:41 AM William Pietri said. June 15, 2009 8:24 AM Stevesaid. June 15, 2009 8:20 PM Anonymoussaid.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

APRIL 4, 2010

Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha. Amazing lean startup resources Is Entrepreneurship a Management Science? Take a look and let me know what you think. 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. September 3, 2009 12:25 PM Omar Ead said. Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JULY 6, 2009

Lessons Learned by Eric Ries Monday, July 6, 2009 Lean Startup fbFund slides and video As a follow-up to my previous post on my talk for fbFund at Facebook , there was enough interest in watching video of the talk that I have finally uploaded it using Apples MobileMe. July 6, 2009 4:21 PM Anonymoussaid. July 6, 2009 8:43 PM Eric said.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

OCTOBER 5, 2008

But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said. This post has been removed by the author. one more thought, where were the code reviews?

San Francisco 158

San Francisco Management Software Review Product 158

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 economics of these process trade-offs are discussed in the Principles of Product Development Flow.)

Software Review 87

Software Review Design Software San Francisco 87

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 260

Silicon Valley Product Startup Product Development 260

Startup Lessons Learned

SEPTEMBER 22, 2008

Sometimes we have the attitude that the Product Development team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already). Take a look and let me know what you think.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. March 14, 2009 8:34 AM Can Sar said. April 11, 2009 1:22 AM CeeTee said.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 2, 2008

Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Update: PDF version for "lazy linux users" and others who love freedom. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JULY 28, 2010

the version that would facilitate the investment of real money) was planned for late-2009. the version that would facilitate the investment of real money) was planned for late-2009. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. The result? The result?

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

NOVEMBER 7, 2008

February 7, 2009 5:40 AM Major_Grooves said. May 6, 2009 3:03 PM Ivan Acosta-Rubio said. We run a web development company and we start by creating a splash page very similar to what is describe here. June 22, 2009 6:30 AM Anonymoussaid. June 28, 2009 2:51 PM beorn said. Great post - I think Ill try this.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 22, 2009

Lessons Learned by Eric Ries Sunday, February 22, 2009 Please teach kids programming, Mr. President Of course, what I really mean is: let them teach themselves. February 22, 2009 5:54 PM CapnCleaver said. February 22, 2009 10:14 PM Aleks said. February 23, 2009 2:22 AM Clement said. February 23, 2009 9:23 AM Clement said.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

bizthoughts.mikelee.org

MARCH 8, 2012

Categories Blogs (35) Book Summaries (5) Business (76) Business Travel (7) Design (27) Entrepreneurship (89) Environmentalism (9) Finance (13) Friday Fun (33) Globalization (6) Ideas (42) Innovation (20) Investing (23) Leadership (10) Management (50) Marketing (82) Media (27) Mobile (18) Organizational Behavior (34) Product Development (7) Psychology (..)

Technical Cofounder 40

Technical Cofounder Cofounder Technical Review Software Review 40

Startup Lessons Learned

AUGUST 26, 2009

Lessons Learned by Eric Ries Wednesday, August 26, 2009 Building a new startup hub Last week, I had a unique opportunity to spend some time in Boulder at the behest of TechStars. August 28, 2009 1:15 PM Derek Scruggs said. August 29, 2009 8:54 AM Ben Casnocha said. Its easy to take Silicon Valley for granted.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

NOVEMBER 4, 2008

Eric, Any thoughts on how forum feedback fits into customer development and agile product development? Youve probably addressed this in the past, but I continue to be blown away by how fast Blizzard reacts to noise in their forums and rapidly makes fixes to the product. February 13, 2009 4:05 AM Eric said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 15, 2008

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. March 26, 2009 6:15 PM Will said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Steve Blank

SEPTEMBER 17, 2009

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development. This post describes such a model.

Customer Development 242

Customer Development Developer Customer Silicon Valley 242

Steve Blank

SEPTEMBER 3, 2009

This post describes how the traditional product development model distorts startup sales, marketing and business development. The Use of a Product Development Model to Measure Sales Using the product development diagram for startup sales activities is like using a clock to tell the temperature.

Customer Development 215

Customer Development Developer Customer Silicon Valley 215

Startup Lessons Learned

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. July 30, 2009 7:35 AM Hazem Awad said. Ill be in Boulder for two days. Stay tuned for more details.) Labels: events 2comments: Andy said.

Lean 68

Lean San Francisco Continuous Deployment DC 68