Startup Lessons Learned

SEPTEMBER 7, 2008

Customers found it confusing and it turned out to be at odds with our fundamental value proposition (which really requires an independant IM network). Labels: agile , continuous deployment , customer development , events , listening to customers , slides 3comments: Sean Murphy said. Talk about waste.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

AUGUST 26, 2009

And they expose the startups to a vast network of mentors, none of whom get paid for their involvement. As a result, the companies get a lot of exposure to VCs, investors, and partners in larger, more traditional startup hubs. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. Herein lies the reason my partner and I started Dillotronics - as well as the reason your take on the matter resonated so well here. Case Study: Continuous deployment makes releases n.

Lean 60

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

The site is now a sad footnote in the history of Social Networking Services. For example, we simply cannot make the changes we need because weve already promised something to partners. Case Study: Continuous deployment makes releases n. How did they do it? By listening to their users. Were doomed! Or the press.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

DECEMBER 7, 2008

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. My responsibility at the time I joined the company was to develop a product that is to be deployed on a social network (hint hint, FB). Case Study: Continuous deployment makes releases n.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

APRIL 7, 2010

I’ve previously documented that early-on in IMVU’s life, we made the mistake of building an IM add-on product instead of a standalone network. What about companies, like Siebel, that started with partner distribution first? What about companies, like Siebel, that started with partner distribution first?

San Francisco 154

San Francisco Lean Metrics Design 154