Startup Lessons Learned

OCTOBER 28, 2008

We pitch to potential partners, vendors, publishers, conferences, employees, and even lawyers. Ill exclude those non- lean startups who basically exist for the purpose of raising bigger and bigger sums of money. One last piece of advice: dont forget that potential partners are evaluating the strength of your pitch, not you.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

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. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? It strokes your ego.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JUNE 8, 2009

I got a powerful taste of datablindness recently, as I’ve started to work with various large companies as partners in setting up events, speeches, and other products to sell around the Lean Startup concept. There are lots of good reasons why I can’t have instantaneous access to this data, and each partner has their own.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

JANUARY 1, 2009

I see that as a great way for my product to grow, but while Ive partnered with companies in my consulting business, its not something Im as familiar with now that Im on the product side. I question what numbers I would need to be considered respectable and/or worth a potential partners time. Expo SF (May. for Harvard Business Revie.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

MARCH 13, 2009

Establish credibility with potential partners. You need to combine your product with others, and this requires partners like OEMs or system integrators. A marketing launch can help you get in the door with those partners, if youre having trouble getting their attention. Do some Customer Development instead.

San Francisco 168

San Francisco PR Lean Early Stage 168

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. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

DECEMBER 7, 2008

This is one of the bedrock practices of any lean startup , and so its a common piece of advice I give out. It exists to serve the needs of customers, and it does this by offering its capabilities to other functions in the company, and partnering with them. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

DECEMBER 14, 2009

A great product enables customers, developers, partners, and even competitors to exchange their unique currencies in combinations that lead to financial success for the company that organizes them. These concepts have important implications for any lean startup. These concepts have important implications for any lean startup.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. The Lean Startup methodology does not advocate using optimization techniques to make startup decisions. That’s the local maximum. That’s right.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

OCTOBER 23, 2009

The lean startup methodology is based on enlisting customers as allies, which requires honesty and integrity. The following was written an actual lean startup practitioner. It was originally posted anonymously to the Lean Startup Circle mailing list, and then further developed on the Lean Startup Wiki ’s Case Studies section.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

JANUARY 2, 2010

Lessons Learned by Eric Ries Saturday, January 2, 2010 Towards a new entrepreneurship When I started writing about the lean startup , my aspiration was to do more than just share a handful of tips and tricks that work for consumer internet startups. This belief led me to the lean startup, and to an amazing 2009.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

steveblank.com

JULY 8, 2011

Github - Free public repositories, collaborator management, issue tracking, wikis, downloads, code review, graphs Pivotal Tracker – Agile project management tool that enables real time collaboration. WebSequenceDiagrams - sketch sequence diagrams. Lighthouse – Issue Tracking Tool.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

www.vccafe.com

MARCH 11, 2013

A group of Seedcamp entrepreneurs started a startup tools wiki for that purpose, and we thought it would be well suited here. Lean Methodology Sources. Steve Blank on Lean Customer Development. Part 3- Lean Cust. Steve Blank’s Lean Startup Resources. Lean Startup Circle â?? Agile project management.

Software Review 53

Software Review Technical Review Startup 53

Startup Lessons Learned

SEPTEMBER 11, 2009

Suffice to say that our partners, vendors, and most importantly regular mainstream customers all found the idea disturbing. Eric, I am not only a member of the IMVU community, but I am your business partner. I was especially moved by this: "I am not only a member of the IMVU community, but I am your business partner.

Community 158

Community Management Lean Software Review 158