Steve Blank

OCTOBER 5, 2009

As the conversation began to get down to how much stock and salary we could offer van Dam, we left the barber to finish his work and went to a payphone to call our CEO to confirm the deal. Wasn’t he a CTO or something? (He We were painting a picture of hypertext on every desktop computer. The response from across the country?

North Carolina 131

North Carolina Silicon Valley Fractional VPE Part-Time VPE 131

Startup Lessons Learned

SEPTEMBER 15, 2008

I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. March 26, 2009 6:15 PM Will said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

SoCal CTO

DECEMBER 1, 2010

aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. Call it facts for hire. It would be a bit like the hired gun in the old west, but more suited for today’s times. What went wrong?

Technical Review 175

Technical Review Technology Product CTO Hire 175

SoCal CTO

SEPTEMBER 8, 2010

August was a slow month in terms of traffic and I was away for a lot of the month, but there were some really great posts at the intersection of startups, technology, product and being a Startup CTO. thought it would be helpful to put some of my thoughts into a blog post and hopefully spur some conversation in the comments and over email.

Startup 191

Startup CTO Hire Cofounder Venture Capital 191

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

MAY 7, 2009

Lessons Learned by Eric Ries Thursday, May 7, 2009 Fear is the mind-killer Fear is an emotion that slows teams down. 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. link] May 11, 2009 9:04 PM Ian Wilson said.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

SEPTEMBER 13, 2008

And then we would use that simple analytics system I mentioned to monitor the conversion rates of customers from each campaign. Those rates gave us a map that told us a lot about our customers; insights that proved stable even when the company grew orders of magnitude bigger. Thank yo u January 3, 2009 4:07 PM BillSeitz said.

SEM 164

SEM San Francisco Lean Continuous Deployment 164