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

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

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

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. Good luck, engineering manager. It was painful for a lot of people.

Software Review 164

Software Review Engineer Management Technical Review 164

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

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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

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. Take a look and let me know what you think.

San Francisco 158

San Francisco Management Software Review Product 158

Austin Startup

APRIL 14, 2020

a story for another time; I could already tell Austin was going to be a ride. Lazarus: Credit Before COVID-19 madness ensued, we were ramping up our beta community outreach, finalizing our Ambassador program, nailing product development, and flirting with guerrilla marketing ideas for a classic post-SXSW launch.

Austin 64

Austin New York City Matching Cofounder 64

Startup Lessons Learned

FEBRUARY 10, 2009

Luckily, Chad Austin has recently weighed in with an excellent piece called 10 Pitfalls of Dirty Code. This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. It would be hard to argue against this product development strategy, in general.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?)

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Its really helped me articulate my thinking on this topic, and includes an entire chapter on the topic of reducing batch size.)

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

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. Take a look and let me know what you think.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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 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

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

Austin Startup

JULY 23, 2010

In fact, for the semi-curious as well as die-hard fans of UFC, you’ll get your first opportunity to attend an Austin-local event on September 15 , with a full program beginning at 8 pm, central, at the Frank Erwin center. It’s among the highest trafficked sites in its category, providing training videos, tips and techniques.

Sweat Equity 60

Sweat Equity Technical Review Software Review Austin 60

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. This is a common mistake. Take a look and let me know what you think.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. Still, a startup product development team is a service organization. Labels: hiring , product development 5comments: TedHoward said.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 13, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode. Take a look and let me know what you think.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

APRIL 4, 2010

Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. I really enjoyed this article, my first time reading any of your stuff. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. I think Drucker said it best.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

AUGUST 2, 2008

Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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. When we’re optimizing, product development teams encounter similar situations. I mean, here we are, paying them to be there, and they won’t use the product!

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 12, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode. Take a look and let me know what you think.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

crowdSPRING Blog

SEPTEMBER 19, 2014

Six Things Physical Product Development Taught Me About Experience Design | UX Magazine – crowdspring.co/X7NCjD. Outstanding review of the iPhone 6/Plus focusing on photo and video capabilities (versus 5S) – Austin Mann crowdspring.co/XNQsuX. How to Use Storytelling to Design Delightful UX – crowdspring.co/X7LqZI.

Social Media 94

Social Media Small Business Design Media 94

Startup Lessons Learned

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Leave your thoughts in a comment. If you’ve tried Five Whys, please share your experiences so far. I’ll do my best to help.) Great article as always, Eric. Take a look and let me know what you think.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

NOVEMBER 7, 2008

Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

OCTOBER 4, 2008

Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Labels: product development 4comments: Doug said. Everything else, including anything that optimizes any other goal, is waste. Thank you Eric. March 2, 2009 1:58 PM programiTV said.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Steve Blank

MAY 7, 2009

Reply Thomas Finsterbusch , on May 7, 2009 at 2:24 pm Said: I’m a PhD Student in CS at UT Austin, and Austin too has all the crucial resources necessary for startups (VCs, angels, law firms, top talent, etc.). If you’re text averse like i am, try to diagram these key items and then write-up the diagrams.

Business Plan 160

Business Plan Silicon Valley RSS Venture Capital 160

Startup Lessons Learned

SEPTEMBER 14, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode. Take a look and let me know what you think.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

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. . =) November 4, 2008 10:58 PM IMVU said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

APRIL 9, 2009

Looks like Ill be at TiEcon 2009 in mid-may, and at an event to be announced in Austin in early June. Product development leverage Validated learning about customers Built to learn Web 2.0 Product development leverage Validated learning about customers Built to learn Web 2.0

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132