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). Want to learn more about me?

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

APRIL 4, 2010

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Want to learn more about me? Try About the author.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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

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 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. Want to learn more about me? Try About the author.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

OCTOBER 5, 2008

They exchange countless emails, and hes being constantly interrupted and being asked to clarify exactly what the spec means. The fourth spec exists only in these emails, which are changing the design in an ad-hoc fashion. Labels: product development 8comments: Vincent van Wylick said. Want to learn more about me?

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Want to learn more about me? Try About the author. Trying to learn more about lean startups?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Up and Running

JULY 26, 2016

Selling a product is a tough process, full of “no’s,” whether they come on the phone with a prospect or as a low conversion rate on your landing page. This is what our hiring landscape looked like over the past year: Pre-2015, we hired three founders: 1x hustler in charge of strategic growth hacking. Big press (cheap or free).

Revenue 60

Revenue Acquisition Channel Campaign 60

Startup Lessons Learned

SEPTEMBER 12, 2008

You might get a bunch of inbound emails from other press and partners, and all of these things can contribute to a feeling that you’re on your way to getting tons of traffic. Thoughts on scientific product development Lo, my 5 subscribers, who are you? It strokes your ego. Want to learn more about me? Try About the author.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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

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

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

Startup Lessons Learned

JUNE 2, 2010

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Speed up or slow down? Want to learn more about me?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 14, 2008

is something like "yes, I personally answer the customer support emails." For example, my experience with teenagers is that they are very reluctant to call or email asking for support, even when they have a severe problem. If youre just getting negativity from someone, they are more likely a internet troll - not an earlyvangelist.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. The basic idea is to avoid building something based on what you think it might need to do in the future.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 10, 2008

Labels: Test-driven development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

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. Want to learn more about me?

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. I got my start programming on an old IBM XT; it was thanks to MUDs that I first discovered the internet. So much for timing.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JULY 6, 2009

If you have thoughts about the right balance of news, events, and commentary, feel free to leave it as a comment or drop me an email. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. As always, I welcome your feedback.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

AUGUST 2, 2008

0comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Want to learn more about me? Try About the author.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JANUARY 12, 2010

For the many entrepreneurs that send me cold emails asking for me to review a business plan or answer a strategic dilemma: Im much more likely to answer if youve already tried getting an answer on the mailing list. Youll probably get a better result, anyway. Youll probably get a better result, anyway. Want to learn more about me?

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

JULY 30, 2009

Congrats Eric.this is really awesome July 30, 2009 5:13 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

Lean 68

Lean San Francisco Continuous Deployment DC 68

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

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

FEBRUARY 9, 2009

If youd like to give feedback, feel free to post comments here, or get in touch on LinkedIn , Facebook , or try to beat the spam filter on email. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0 Check out what I am doing at.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

JULY 5, 2010

While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. This new volume also tackles examples from the Internet and wireless startups of today, both B2B and B2C. I cant wait to see whats next. Want to learn more about me?

Customer Development 166

Customer Development Developer San Francisco Customer 166

Steve Blank

SEPTEMBER 3, 2009

This post describes how the traditional product development model distorts startup sales, marketing and business development. For example, some startup sales execs believe hiring the core sales team is a key objective. Here’s what the product development diagram looks like from a sales perspective.

Customer Development 229

Customer Development Developer Silicon Valley Customer 229

David Teten

MAY 1, 2013

Domain names are less important than they were in the first Internet wave, because so many people will access your service on mobile and/or via apps, and because type-in traffic is declining. However, they remain key to your email identity, and fundamental to your marketing and even capital-raising.

Naming 114

Naming Semantic Venture Capital Startup 114

Startup Lessons Learned

JANUARY 7, 2010

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Read the rest at The Conversation - Harvard Business Review.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

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

NOVEMBER 7, 2008

Finally the day came, we unleashed the landing page, emailed our existing customers, and started advertising online. Depending on the type of product, postings on forums, classifieds and emails could give enough information to help gauge potential response. We finally settled on a $1.99 November 8, 2008 8:44 AM OneDish said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JULY 9, 2010

Our modern philosophy of management has this core belief (taken straight from scientific management) at its heart: that the performance of companies is determined by the systems they create, not just the people they hire. Want to learn more about me? Try About the author. Trying to learn more about lean startups?

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JUNE 8, 2009

I had it all set up to a jury-rigged SurveyMonkey - PayPal minimum viable product. Whenever someone decided to buy a ticket, I got an email immediately letting me know. Yet, when I tried other forms of promotion, I’d have to accept their failures when the emails failed to come. Yet it had one huge advantage.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

SEPTEMBER 8, 2008

So one of the first things we did was to hire an Oracle expert and get to work. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. 1 comments: flixsterwidgettest said. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

NOVEMBER 6, 2008

Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Want to learn more about me? Try About the author. Trying to learn more about lean startups? See Four Myths about the Lean Startup or The lean startup.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JANUARY 2, 2009

My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. I just emailed your article to him and recommended that he take your advice to heart. Thank you for this excellent article. January 2, 2009 11:54 AM Daniel Davie said. Thanks for the article.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60