Startup Lessons Learned

JUNE 5, 2009

In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics. One way to conceive of our goal in an early-stage venture is to incrementally “fill in the blanks&# for the business model that we think will one day power our startup. June 8, 2009 1:16 AM Colin said.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

APRIL 14, 2009

What matters is proving the viability of the company’s business model, what investors call “traction.&# Of course this is not at all true of many profitable small businesses, but they are not what I mean by startups.) Every board meeting, the metrics of success change. And yet, their investors are frustrated.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JULY 29, 2009

For example, IMVU’s early business model was made possible by Paypal’s easy self-serve and open access payment system. To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 16, 2010

Designed for large businesses, the channels let a company share several types of documents, brand the channel with their own design elements, and then include display advertising, contest promotions, blog aggregation, social media integration and metrics reporting. ’&# They removed the core plan, and conversions went up.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

OCTOBER 6, 2008

Whats needed is a disciplined methodology for understanding the needs of customers and how they combine to form a viable business model. We tried and tried to boost our conversion numbers, each time analyzing what worked and what didnt, and iterating. Case Study: Continuous deployment makes releases n.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

JANUARY 28, 2009

I thought we were having a successful conversation. I was told they werent sure, because all of their engineers were currently busy refactoring. Back to my conversation with the company I met recently. Only one occasion was a substantial rewrite justified based on performance metrics. January 29, 2009 1:11 PM Paul W.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79